[01]
LIS via HL7 v2 MLLP
HL7 v2 message exchange (ORM orders, ORU results) with the hospital's analyzers/LIS over MLLP — the de facto standard for laboratory interoperability.
[Integration] Laboratory & Radiology
LIS & PACS Integration.
Lab results flow automatically into the medical record via HL7 v2 MLLP, and radiology links to the hospital's PACS through a DICOM worklist. Vendor-neutral — the hardware and servers remain the hospital's.
Capabilities
Lab & radiology interoperability.
Built on real standards — HL7 v2 and DICOM — not proprietary connectors that lock the hospital in.
[02]
Auto-ingest results into the EMR
Lab results flow automatically into the patient's medical record, complete with critical-value alerts — reducing manual entry and the risk of transcription errors.
[03]
PACS via DICOM worklist
DICOM modality worklist + webhook integration into the hospital's PACS, so each modality receives its worklist and images link back to the exam.
[04]
PACS vendor-neutral
Works with the hospital's PACS of choice — Orthanc, dcm4chee, or others. No lock-in to a single imaging provider.
Lab and radiology results neatly linked in the EMR also strengthen readiness for sending data to SATUSEHAT.
FAQ
LIS & PACS integration questions.
HL7 v2 over MLLP — ORM messages for test orders and ORU for results. This is the standard most widely supported by analyzers and laboratory information systems (LIS).
No. To be straightforward: the analyzer hardware, LIS software, PACS server, and image storage are provided by the hospital. Adievia provides the integration layer — HL7 v2 MLLP for the lab and DICOM worklist for radiology.
Vendor-neutral. We integrate with the hospital's PACS such as Orthanc, dcm4chee, or other products via DICOM worklist + webhook — whichever the hospital chooses.
Next step