Insights
Practical guides to healthcare interoperability, clinical workflows, health-data regulation and software delivery.
A playbook for projecting HL7 v2 ADT A01, A04, A08 and A03 onto FHIR Patient and Encounter — PID-3 versus identifier.system, PV1-19 visit numbers, and de-identified test fixtures.
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.
What the development team should map before code: medical destination, MDCG 2019-11 rev.1, branches of rule 11, IEC 62304 and SOUP inventory — separate from the English-speaking MDR guide.
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.
NIS2 operational evidence pack for a health IT team: Art. 21 and 23 of Directive (EU) 2022/2555, 24/72/one-month clocks, ANSSI and CERT-FR, and the dual-channel GDPR.
Implement SMART App Launch 2.2.0 against Epic and other EHRs — EHR launch versus standalone, iss and aud, the launch token, PKCE S256, and why the Epic sandbox is not production.
Showing 37–42 of 68 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.