Using Web Services for Public Health Reporting

public health reporting

As part of August’s monthly online user group session for Corepoint Health customers, Mike Stockemer presented the most common ways customers are using web services to exchange documents via Corepoint Integration Engine.

Mike presented five different real-world scenarios in which Corepoint Health customers are exchanging health data using web services:

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 second scenario in a future post.

Deliver HL7 Messages to the State

Typical actions involved with public health reporting:

  • EHR sends HL7 message over TCP/IP 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.

To illustrate:

HL7 Public Health Reporting

Stage 2 of Meaningful Use requires caregivers to send syndromic surveillance and reportable labs 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, along with several other previous sessions.