For IT teams
The technical detail behind the simple story. Acronyms welcome here.
Architecture
- PostgreSQL is the only server database. Tenancy by hospital and facility with row-level security on every table.
- Every change is a typed Action — UI, voice, WhatsApp, phone agent, AI agents, REST and MCP all call the same registry.
- Risk tiers T0–T4 set the minimum confirmation, enforced on the server.
- Tamper-evident audit chain on every action.
Offline and on-site
- Edge Bridge: a small on-site box keeps OPD, billing, pharmacy and printing working during outages.
- Talks to thermal printers, barcode scanners, lab analysers (ASTM/HL7 v2) and PACS (DICOM).
- No inbound ports; signed auto-updates.
Standards
- ABDM milestones M1–M3 (ABHA, HIP, HIU, consent).
- NHCX claims as FHIR bundles; PM-JAY/CMCHIS package codes.
- FHIR R4 API, SMART on FHIR, SNOMED CT, ICD-10, LOINC.
- Webhooks and an MCP server for your own tools.
Security and privacy
- No PHI in logs or push notifications.
- Encryption at rest and in transit; India-hosted cloud.
- DPDP consent ledger, data-rights requests and breach timers.
- Clinical decision support is deterministic code — never an LLM.
Run it yourself
Everything, including a demo hospital, starts with one command:
git clone https://github.com/medlane/medlane.git
cd medlane
docker compose upIntegration status
Honest status. “Planned” means not built yet.
| Integration | Status |
|---|---|
| WhatsApp Business | In progress |
| ABHA / ABDM M1–M3 | In progress |
| NHCX claims | Planned |
| UPI / Razorpay | In progress |
| Tally export | Planned |
| Lab analysers | Planned |
| PACS / DICOM | Planned |
| Apple Health / Health Connect | Planned |