During a recent monthly user group session held for current Corepoint Health customers, Mike Stockemer presented the most common ways customers are using web services to exchange documents via Corepoint Integration Engine, the most common being using web services for public health reporting.
The five real-world scenarios in which Corepoint Health customers are most often exchanging health data using web services include:
- Deliver HL7 is a Standards Developing Organization accredited by the American National Standards Institute (ANSI) to author consensus-based standards representing a board view from healthcare system stakeholders. HL7 has compiled a collection of message form... More messages to a state agency
- Deliver Clinical Document Architecture (CDA) HL7 CDA uses XML for encoding of the documents and breaks down the document in generic, unnamed, and non-templated sections. Documents can include discharge summaries, progress notes, history and physical reports,... More documents to a health information exchange (Health Information Exchange (HIE) focuses on the mobilization of healthcare information electronically across organizations within a region or community. HIE provides the capability to electronically move clinical information between disparate health... More)
- Receive CDA from an Electronic Health Record (EHR), as defined in Defining Key Health Information Technology Terms (The National Alliance for Health Information Technology, April 28, 2008): An electronic record of health-related information on an individual that conform... More
- Standard and custom web services
- HL7 v2 to CDA via The Direct Project was launched by the ONC within Health and Human Services (HHS) on March 1, 2010. It was initially called NHIN Direct. The object of the Direct Project is to replace the use of faxes, phones, and paper transactions with a simple and... More
The interesting component of using web services are the workflow challenges that are being solved using Corepoint Integration Engine. Let’s take a look at the first scenario in this post. For the sake of brevity, we’ll describe the other scenarios in future posts.
Deliver HL7 messages to the state via web services
Typical actions involved with public health reporting:
- EHR sends HL7 message over Transmission Control Protocol/Internet Protocol (TCP/IP) is a low-level communications protocol used to connect hosts on the Internet or a network. TCP/IP connections are established between clients and servers via sockets. TCP/IP is stream-oriented ... More interface into Corepoint Integration Engine
- “Fix” the HL7 message into a format the state can receive (despite Meaningful Use certification, several EHR vendors do not completely adhere to the CDA standard)
- Create a web service message (XML) from the new HL7 message per the state’s requirements
- Sends the new web service message to the web service sender interface and make a web service request of the state repository, transmitting the XML message to the state.
- Receive the response from the state that indicates successful transmission or any error codes that occurred, indicating a problem with the content of the XML file.
- Processes responses from the state so the interface team can become aware of any issues that need to be resolved.
Stage 2 meaningful use requires caregivers to send syndromic surveillance and reportable lab results to their state’s department of public health. To read what HL7 information is required, read syndromic surveillance and reportable labs in meaningful use.
if you’re a corepoint health customer, you can view the complete presentation in the user community.Tags: Corepoint Integration Engine, meaningful use, radiology, web services