Connect HealthLedger to the systems your facility relies on.
FHIR-based clinical exchange, DHIS2/NHMIS reporting, LIMS laboratory workflows, and PACS-linked imaging workflows are supported today. We configure each connection around the facility's data and operating responsibilities.
HealthLedger supports FHIR clinical exchange, DHIS2 and NHMIS reporting, LIMS laboratory workflows, and PACS-linked imaging workflows. Specific mapping and data direction are confirmed during facility scoping.
HealthLedger Hospital OS
- Supported today
- FHIR-based clinical exchange
- Patient, visit, order, and observation information for approved connected workflows.
- Supported today
- DHIS2/NHMIS reporting
- Facility reporting datasets and the reporting responsibilities assigned to administrators.
- Supported today
- LIMS laboratory workflows
- Laboratory orders, sample status, results, and diagnostic review linked to the patient visit.
- Supported today
- PACS-linked imaging workflows
- Imaging orders, study references, reports, and linked clinical review.
Live interoperability coverage
Keep connected work grounded in the workflow staff actually perform.
The standard or external system is only one part of a useful connection. HealthLedger also keeps the patient context, facility responsibility, review step, and reporting outcome in view.
| Area | What teams can do | Connected outcome |
|---|---|---|
| FHIR-based clinical exchange | Patient, visit, order, and observation information for approved connected workflows. | Connected work remains tied to the patient, facility responsibility, and operating process. |
| DHIS2/NHMIS reporting | Facility reporting datasets and the reporting responsibilities assigned to administrators. | Connected work remains tied to the patient, facility responsibility, and operating process. |
| LIMS laboratory workflows | Laboratory orders, sample status, results, and diagnostic review linked to the patient visit. | Connected work remains tied to the patient, facility responsibility, and operating process. |
| PACS-linked imaging workflows | Imaging orders, study references, reports, and linked clinical review. | Connected work remains tied to the patient, facility responsibility, and operating process. |
| Authorized data export | Facility-controlled export according to hospital policy and applicable obligations. | The facility retains an approved path to take its data out according to policy. |
Facility-specific connection work
A live capability still needs to fit the system it connects to.
The interoperability capabilities are live. Mapping and configuration ensure each connection reflects the facility's systems, approved data, access model, and staff responsibilities.
-
Define the operating workflow
Identify what staff need to send, receive, review, or report and who is responsible for each step.
-
Map the facility connection
Align the live HealthLedger capability with the facility's systems, data fields, access, and operating rules.
-
Configure and test
Verify the agreed connection and workflow before staff rely on it in live operation.
-
Train the teams involved
Prepare clinical, service, reporting, and administrative users for their responsibilities in the connected process.
-
Enable the workflow
Bring the connection into facility use with the agreed scope, ownership, and review process.
Data portability
Keep an authorized path to take facility data out.
HealthLedger supports authorized data export according to hospital policy and applicable legal obligations. The facility and implementation team confirm the approved scope and operating process.
Connection scope
Specific versions, data direction, authentication, terminology, and third-party compatibility are confirmed during technical scoping for the facility.
Integration questions
Clarify what is live and what is configured for the facility.
Are HealthLedger interoperability capabilities live today?
Yes. FHIR-based clinical exchange, DHIS2/NHMIS reporting, LIMS laboratory workflows, and PACS-linked imaging workflows are live capabilities. Facility-specific mapping and configuration establish how each connection works in that environment.
How is each facility connection configured?
The product capabilities are live. We map and configure each connection around the facility's systems, approved data, staff responsibilities, and operating workflow.
What can FHIR-based exchange cover?
HealthLedger supports approved workflows involving patient, visit, order, and observation information. The exact mapping, standard version, data direction, and connection scope are confirmed during technical scoping for the facility.
How does HealthLedger support laboratory and imaging work?
LIMS workflows can connect orders, sample status, results, and diagnostic review to the patient visit. PACS-linked workflows can connect imaging orders, study references, reports, and clinical review.
Can a facility export its data?
Yes. Authorized data export is supported according to hospital policy and applicable legal obligations. The implementation scope confirms the approved data and operating process.
Scope the workflow your facility needs connected.
Discuss the systems involved, the information staff need to exchange or report, and the roles responsible for the connected process.