Standards, not custom cables
Every interface EMSL builds uses a published standard, so it can be documented, tested against the other vendor's conformance statement, and maintained when either side upgrades.
HEALTHCARE INTEROPERABILITY · BANGLADESH
Healthcare Interoperability: HL7, FHIR & DICOM Integration in Bangladesh
No hospital runs a single system. There is a HIS from one vendor, modalities and analyzers from several manufacturers, an insurer's portal, a group head office. Interoperability is what lets them share one patient's data without re-typing. EMSL builds its own platform on open standards — HL7, FHIR, DICOM and DICOMweb — and offers the same integration capability to hospitals and vendors in Bangladesh that need systems to talk to each other.
Designed forHospital IT leaders, software vendors and equipment suppliers
Supported standards
HL7 v2FHIRDICOMDICOMwebASTMREST
Interoperability standards EMSL implements and integrates against.
CAPABILITIES
What the HL7 · FHIR platform does
Explore the core capabilities, then see how they fit into everyday work.
- ✓HL7 v2 messaging — patient administration (ADT), orders (ORM) and results (ORU) between HIS, LIS, RIS and third-party systems
- ✓FHIR REST APIs for resources such as Patient, Encounter, Observation and DiagnosticReport
- ✓DICOM and DICOMweb for imaging — modality connections, Modality Worklist, Query/Retrieve, WADO-RS, QIDO-RS and STOW-RS
- ✓Laboratory analyzer interfacing — bidirectional ASTM and HL7 over serial and TCP/IP
- ✓REST and web-service APIs for portals, mobile apps and third-party applications
- ✓Message logging and error handling on every interface
- ✓Integration of EMSL modules with an existing HIS, RIS, LIS or PACS from another vendor
- ✓Data migration from legacy systems during a replacement
Built around your daily work
Imaging, clinical and laboratory — one team
The same engineers connect a CT scanner over DICOM, a chemistry analyzer over ASTM and a third-party HIS over HL7, which is what a real hospital integration needs.
Vendors welcome
Equipment suppliers and software companies integrate with EMSL systems through documented HL7, FHIR, DICOM and REST interfaces, with EMSL's team supporting the work.
Built for mixed-vendor hospitals
Designed around the environments typical of hospitals in Bangladesh — several generations of equipment, more than one software vendor, and a head office that needs one view.
IN DEPTH
HL7 · FHIR in detail
What each standard is for
Healthcare interoperability is not one standard but several, each covering a different kind of data:
- HL7 v2 — the workhorse of hospital messaging: admissions, transfers and discharges, orders and results, charges. Almost every HIS, LIS and RIS speaks it.
- FHIR — the modern web API standard for the same information, expressed as REST resources. Used for portals, mobile apps, national reporting and newer systems.
- DICOM and DICOMweb — medical images and the services around them: storage, query and retrieve, Modality Worklist, and web access through WADO-RS, QIDO-RS and STOW-RS.
- ASTM — the protocol most laboratory analyzers use to receive orders and send results; newer analyzers also offer HL7.
Typical integration scenarios
EMSL PACS and viewer behind a third-party HIS: orders and patient administration arrive over HL7, the Modality Worklist is generated from them, and reports return to the HIS.
EMSL HIS and LIS with the hospital's existing analyzers: each analyzer is connected over ASTM or HL7 so results flow straight into the LIS.
A hospital group consolidating branches that run different systems into one head-office view through HL7 and FHIR feeds.
Patient-facing apps and portals reading appointments, results and reports through FHIR and REST APIs.
PLAN YOUR PROJECT
Start with your workflow.
A useful evaluation starts with the people, systems and handoffs in your organisation. Use these points to shape the conversation.
YOUR HL7 · FHIR DISCUSSION CHECKLIST
Bring the details that matter.
- List source and destination systems, versions and vendor contacts.
- Gather interface documentation and anonymised sample messages.
- Identify patient matching rules and which system owns each data field.
Walk through a real scenario
Choose a typical day in your department. Follow each handoff in the demo and check what each team needs to see or do.
Confirm the fit
Review existing systems, required interfaces, access roles and reporting needs. Agree what needs configuration or further validation.
Define the rollout
Discuss deployment, data migration, staff training and support. Agree the scope and acceptance checks before setting a go-live plan.
FAQ
A few things you may want to know.
Common questions about HL7 · FHIR, integration and day-to-day use.
Have a different question?Do you support HL7 v2 or FHIR?
Both. HL7 v2 for the messaging that hospital systems already exchange, and FHIR for web and mobile applications and newer systems.
Can the EMSL PACS work with a HIS from another vendor?
Yes. The HIS sends orders and patient administration over HL7, EMSL generates the Modality Worklist from them, and reports and study status return to the HIS.
Can you connect our existing laboratory analyzers?
Yes. Analyzers with a serial or network interface are connected over ASTM or HL7, bidirectionally where the analyzer supports it. Share your model list and EMSL will confirm each one.
Do you offer integration services to other software or equipment vendors?
Yes. Vendors integrate with EMSL systems through documented HL7, FHIR, DICOM and REST interfaces, and EMSL's team supports the integration and testing.