Integrations
Built for the standards your systems already use.
Interoperability is a design commitment, and this page is explicit about where it stands: ICD-10 coding and transactional email work today; SMS, FHIR APIs, ABDM, imaging, WhatsApp, payment gateways, and accounting export are planned scope from our product plan.
The clinic-core and inpatient (IPD) modules are built and in verification ahead of our first release. Everything marked Planned is scheduled scope from our product plan, not something you can use today.
Health standards
HL7 FHIR R4
PlannedThe clinical core is modeled on FHIR (Practitioner / PractitionerRole) so the FHIR R4 APIs and bundles can sit on top of it. The APIs are Phase 3 scope.
ICD-10 diagnosis coding
BuiltICD-10 lookup on the consultation screen, stored with the encounter. ICD-11 is planned.
SNOMED CT & LOINC
PlannedClinical terminology and lab codes, where licensed and applicable.
DICOM & PACS
PlannedImaging exchange and a DICOM viewer, with the Radiology module.
India digital health
ABDM & ABHA
PlannedABHA creation and linking, and consent-based record sharing. A patient's ABHA number can already be recorded against their file.
Scan-and-share OPD
PlannedFast OPD registration through the ABDM scan-and-share flow.
Communications & payments
Transactional email through MSG91, behind one provider abstraction, with idempotency on every send.
SMS
PlannedTransactional SMS on the same provider abstraction, pending DLT template registration before the first send.
WhatsApp Business
PlannedWhatsApp as an additional notification channel on the same abstraction.
Payment gateway & links
PlannedCards, net-banking, and shareable payment links, with no card data stored. Cash and UPI collection is recorded against the invoice today.
Tally & ERP export
PlannedVoucher and ledger-level financial export to Tally and other accounting systems.
See it running with your own workflows.
Book a walkthrough and we will map your clinic or hospital onto the platform, module by module.