Radiology Interoperability

Utilizing their integration engine, MD Link, MDI Solutions’ integration team provides software and services to manage the complex HL7 tasks required by Diagnostic Imaging Workflow.

MDI offers a cost effective option to manage interface requirements and customization.  Often, determining the suite of HL7 messages designed and available for testing is the critical first step that ensures support among all stakeholders.  These messages types are often required to support Diagnostic Imaging operations and include ADT, ORM, ORU and SIU.

There is now increased demand for ‘study’ results from outside of the traditional hospital based radiology department and these include:  other hospital/acute departments, ambulatory care, soliciting 3rd party expertise, use of Computer Assisted Diagnoses and Primary Care that has continuous stewardship of a patient.

MD Link is routinely used to develop HL7 interfaces that can support radiology workflow including:  Schedule an Appointment, Order a Test and Produce a Result.  This level of integration is also used to support Primary Care Physician Clinics (using EMR-based software) as physician offices can easily exchange data with radiology departments and get ‘real time’ Diagnostic Imaging Lab Results, which is particularly beneficial when the physician is the referral source.

MDI Solutions and MD Link makes short work of this task by asking the right questions of vendors involved, designing a solution, testing it, gaining acceptance and continuously monitoring its progress.

MDI Solutions services a wide range of clients including:

  • Hospital Information Systems
  • Diagnostic Imaging Departments
  • Primary Care Physicians and EMR vendors
  • RIS PACS vendors

Common RIS Messaging Requirements to Support Multi-Disciplinary Imaging Strategy


Converts MDI’s integration team are able to convert repeating HL7 segments within a data stream to a discreet HL7 message.  For example, repeating segments in an ORU message that reflect multiple studies can easily be converted to a discreet unsolicited HL7 ORU (lab order result) message.

Updating Multiple Databases MDI can update multiple tables in databases simultaneously from a RIS source.

For example, more than one table is updated from a PID segment:

  • personal information such as name, surname, addresses, birth date
  • for patient’s external codes such as MPI
  • for town’s descriptions
  • {ORC-OBR} segments (a table each for exam’s description, order & doctor’s information)

Multi-Threading MD Link can process multiple HL7 Query messages concurrently; this is an advantage over HL7 SDKs that are restricted to processing a single query message at a time.

One example of this feature is individual researchers each generating multiple HL7 queries from a RIS to a PACS or other application; they do not have to wait for the HL7 server to process the query in a series of first come first served, which allow each researcher to get near immediate system response.

HL7 Create HL7 messages can be created from other HL7 messages; for example, a RIS updating an EMR that requires an ADT (Demographics) message extracted from an SIU (Scheduling) message.

RIS to EMR – HL7/ORU Conversion A RIS that routinely generates an HL7 ORU message to report a test result of a study completed by a radiologist may need to be converted to an HL7 MDM as a Medical Document Message in an EMR – MD Link can be used for this conversion.

This is often required for EMRs such as: Allscripts, GE Centricity, XWave, EMIS, In Practice Vision, TPP System One, Cattails MD, NextGen & Practice Solutions.