Standards & Interoperability
-
Where Imaging Data Fits in Clinical Data Integration
Imaging data does not move through clinical data integration the way a lab result or a medication order does. What breaks, and what a…
-
Integration Engines: Routing Clinical Messages Reliably
An integration engine receives, transforms, routes, and acknowledges every HL7 message, and queues what a downed destination cannot take until it returns.
-
What HL7 Is: The Standard Behind Clinical Messaging
HL7 names an organization and a messaging standard, not one thing. What a Version 2 message looks like, what ADT and ORM trigger, and…
-
A Field-by-Field Walkthrough of the HL7 MSH Segment
The MSH segment in HL7 carries routing, encoding, and message identity. What each field does, the field-numbering quirk, and what breaks when one is…
-
How HL7 SIU Messages Handle Scheduling
HL7 SIU is the message family that tells a RIS an appointment exists. What its trigger events, SCH segment, and resource segments carry, and…
-
How the FHIR Patient Resource Handles Identity
How the FHIR Patient resource handles identity: why identifier is a list, what system, use, and assigner mean, and why Patient.id is not the…
-
Securing a Medical Imaging Archive Server
Most DICOM services run with no authentication unless someone turns it on. What TLS, AE titles, segmentation, and audit logging cover, and where each…
-
Consolidating Studies Across Departments in One VNA Archive
Radiology is not the only department generating imaging. What a VNA archive has to consolidate: non-DICOM objects, patient identity, one retention policy.
-
FHIR in Plain Terms: How the Standard Models Clinical Data
FHIR models clinical data as linked resources exchanged over a RESTful API. What a resource is, where FHIR meets DICOM, and what a product…
-
Vendor Neutral Archive: Buying Storage That Outlives Your PACS
A vendor neutral archive is a description, not a certification: what makes migration lossy, and the questions that test for real neutrality before you…