Lyniate Team

DICOM and Web Services Features Used to Achieve Interoperability Success

November 20, 2014

Central Illinois Radiological Associates (CIRA), headquartered in Peoria and serving Illinois communities from Kankakee to Springfield, is one of the top 10 private practice radiology groups in the nation. They serve a variety of hospital locations including numerous outlying tertiary care facilities. With over 100 reporting locations, their expanded service area and disparate reading environments challenge CIRA’s IT team to provide an efficient workflow for its radiologists.

Serving a geographically dispersed area with a quality-driven business model presents a wide spectrum of technology challenges. To address current and future needs of the radiology market in Illinois, the CIRA team began developing an IT Business Plan in 2009 led by Eric Weber, CFO, and Pat Ward, CIO.

Nate Anderson and Steve McHenry discuss using Corepoint Integration Engine Web Services and DICOM Gear

After final approval from CIRA’s physician-led executive committee, the plan’s implementation began in September 2010 and has successfully solved workflow deficiencies across several areas of the practice.

Leading the creative problem solving of each unique environment, CIRA’s  Systems Engineer Nate Anderson and Software Engineer Steve McHenry have dedicated their time and efforts to finding unique solutions for delivering quality, focused imaging services to all customers. The team has used the Corepoint Integration Engine DICOM gear and Web Services capabilities to solve these interesting challenges.

The following scenarios were developed by Nate and Steve.

Scenario 1: Using the Corepoint Health DICOM Gear to Achieve Interoperability in Smaller Clinics

As most in the radiology space would know, budget strapped tertiary care facilities typically do not have the technical resources to provide or build HL7 enable RIS or EHR interfaces.  CIRA’s workaround for these technical deficiencies is a DICOM driven workflow using the facilities PACS or modalities.  To solve these situations CIRA has adopted a customized workflow utilizing Corepoint Health DICOM Gear connection.  CIRA’s logic in this environment is as follows:

  • Create a standard DICOM connection with Corepoint Integration Engine
  • The clinic (our customer) scans the patient and the image will exist on their PACS or other modality
  • That scan is then uploaded to Corepoint Integration Engine through the DICOM gear via TCP/IP
  • The Corepoint DICOM Gear connection parses the header data
  • Corepoint Integration Engine converts the header data into XML and maps it into an HL7 message which provides for a normalized order message into PS360 and variety of other destinations such as CIRA’s billing provider and VNA.

CIRA DICOM Solution Using Corepoint Integration Engine

CIRA has connected 15 rural clinics to its PS360, billing provider and VNA using this methodology.

Scenario 2: Using Corepoint Integration Engine Web Services to Enable Interoperability for Customers

Some facilities don’t have the resources or ability to send a digital DICOM because they are still using plain film. The solution CIRA developed involved the Web Services capabilities of Corepoint Integration Engine to enable a web-based order entry system through which HL7 order message can be generated.

  • A web server is deployed which utilizes PHP to generate a SOAP request.
  • Corepoint Integration Engine receives the SOAP request and maps out all the fields for use in an action list, which is very similar to the action list utilized to support the DICOM scenario stated above.
  • From there, Corepoint Integration Engine accepts the SOAP and parses it into an order message and sends the data to a variety of systems (PS360, PACS…etc) to accomplish the centralized work list.

CIRA Web Services Solution Using Corepoint Integration Engine

These solutions reduce the number of support calls from physicians working in disparate reading environments and provides for a common worklist solution for physicians who would otherwise have to travel to outlying locations. Lastly, CIRA’s mission to provide greater access to subspecialty care is improved through the integration of disparate workflows with Corepoint Integration Engine.

Related Blogs

Shelley Wehmeyer

Introducing Lyniate HealthTerm version 15.2: powerful new features to support the evolution of mappings

With this release, you can take advantage of better visibility mapping history.

Read more

Jesse Eichhorn

Introducing Lyniate EMPI by NextGate 11.2: powerful new tools to drive identity data trust

Listen to my colleague and identity data management veteran Rico Garcia talk about what makes this new version special.

Read more
The number 1 integration engine is now available in the cloud

Shelley Wehmeyer

The Best-in-KLAS® healthcare integration engine, Lyniate Corepoint, deployed in the cloud

Rolling out now... the integration engine you know and love, Lyniate Corepoint, is deployed on AWS to provide optimal business continuity, system resiliency, and security.

Read more