FHIR & OpenHIM health interop
Getting clinical data to flow between ERPNext, a FHIR server and DHIS2, so a hospital's records can feed aggregate health reporting.
Debit · what made it hard
Open-source health platforms each model patients and encounters their own way, and none of them spoke FHIR out of the box.
Credit · what shipped
Two-way FHIR/HL7 exchange for ERPNext Healthcare, routed through OpenHIM to DHIS2, plus telemedicine built into ERPNext.
Context
Health data is only useful if it can move between systems. A clinic’s records should be able to reach a national reporting system without someone retyping them. At Parallelscore I worked on that problem with open-source tools.
What I built
- FHIR and HL7 compliance for ERPNext. I extended its healthcare module and built two-way exchange between ERPNext and a FHIR server.
- OpenHIM as the interoperability layer. Clinical messages route through OpenHIM, which mediates between ERPNext, the FHIR server and DHIS2 for aggregate health reporting.
- Schema reconciliation. I mapped patient and encounter records from several open-source health platforms into FHIR resources, resolving the places where different EHRs disagree about what a “patient” or an “encounter” is.
- Telemedicine. I built a video-conferencing module into ERPNext so consultations can happen inside the system that holds the record.
Also at Parallelscore
Hospitality ERP work on white-labelled ERPNext, and a sports product: NestJS APIs that parse video data for analysing full 90-minute soccer matches.