Corepoint Integration Engine DICOM Features

Automate order entry with Corepoint Health DICOM gear

Corepoint Integration Engine’s gear:

  • Eliminates manual entry of patient registration information associated with a DICOM study
  • Reduces processing time to referring practices and hospitals
  • Improves accuracy with electronic patient data transfer
  • Enhances service to referring physicians

Corepoint Integration Engine is the industry’s leading integration engine and has helped our radiology partners provide innovative interoperability and integration solutions that ensure future success in a rapidly changing marketplace.

Gaining efficiencies in workflows is vital for growing radiology practices. Different data formats and healthcare standards create bottlenecks that often require patient information to be manually updated, adding time and increasing the odds of data-entry error.

Additional workflow issues are created with unassociated images in the that do not automatically flow into work queues.

Corepoint Health delivers the flexibility to process every clinical data format and standard in healthcare, including , DICOM, and XML. With Corepoint Integration Engine, radiology workflows are automated and patient demographics, orders, and reports are processed without the need for a single keystroke.

Different approaches

Radiology groups may have unique operational approaches to their workflows. While one group may take the RIS-driven approach, another may be PACS-driven. In either case, Corepoint Integration Engine can easily process data, enhance workflows and provide peace of mind that patient data is moving from system to system as intended.

Corepoint Health’s role in each approach is displayed in the accompanying graphics.

Corepoint Integration Engine converts DICOM header information into an XML format. The engine uses this information to create a basic order or patient demographic message for the or PACS. From the XML format, the information can be converted to an HL7 message or other data formats. The study is handled by the PACS, but the associated vital patient information is communicated using Corepoint Integration Engine.

RIS workflow

  1. DICOM study is transmitted to the radiology group from a PACS or modality at a referring hospital or physician practice
  2. HL7 ORM is created from the DICOM header information and electronically sent to the RIS as an HL7 ORM
  3. With the incoming ORM, the patient is registered in the RIS, an accession number is assigned, and an updated ORM is sent to other applications as needed
  4. The PACS, the voice recognition (VR), and/ or dictation systems receive the ORM so the necessary patient information is available for the radiologist to complete the report in a timely manner

DICOM Workflow Example in Corepoint Integration Engine

PACS workflow

  1. DICOM study is transmitted to the radiology group from a PACS or modality at a referring hospital or physician practice
  2. HL7 ORM is created from the DICOM header and electronically sent to the PACS, VR, dictation, or other systems as an HL7 ORM. The necessary patient information is available for the radiologist to complete the report in a timely manner.

PACS Workflow Diagram

Download PDF

 Print Friendly