Insights
Implementation guides for HL7, FHIR, patient identity and clinical data exchange.
Inventory of interfaces for a French-speaking HIS: ADT/ORM/ORU, HPRIM Santé, INS overlay, and the HL7 v2-to-FHIR 1.0.0 STU 1 guide as a mapping contract — not a replacement for v2.
How to structure NextGen Connect (formerly Mirth Connect) channels — source, filter, transformer, destination, configuration maps, error queues versus retry, and Git export of channel XML.
DEP FHIR Implementation Guide: CH EPR FHIR 5.0.0, EPR-SPID identifier, MHD / PIXm / PDQm transactions, languageCode metadata, and what is prohibited from storing.
A practical breakdown of HIPAA requirements as they apply to healthcare integration — the Privacy Rule, Security Rule, minimum necessary standard, BAAs, audit logging, and how integration engines like Mirth Connect enforce compliance at the message level.
A deep dive into the clinical workflows that integration engineers support — the radiology order-to-report cycle, laboratory result routing, billing charge capture, and the HL7 message choreography that makes it all work.
How to run an HL7 v2 migration to FHIR without breaking clinical workflows: interface inventory, coexistence through an interface engine, a FHIR façade, the HL7 V2-to-FHIR mapping guide, historical data loads, validation and the retirement of v2 feeds.
Showing 19–24 of 30 articles
Talk through your integration, data or software delivery needs.
Allow analytics cookies to help understand site visits and enquiries? Optional analytics stays off until you accept.