Perhaps the greatest additional advantage of having an integration platform in the middle of your health IT environment is the creativity it offers above and beyond HL7 v2 interfaces. While approximately 90% of healthcare provider interfaces are comprised of v2 interfaces, many Corepoint customers are getting exciting results using other standards, such as C-CDA.
For example, Meaningful Use requires providers to have the ability to produce a C-CDA document and make that available to the patient after discharge or the visit. To qualify, providers have to prove that it is available for patients to view, download and transmit their summary of care.
Corepoint users can build C-CDA documents in the engine. Each month we hold a free webinar for our customer base that includes product or industry education or, occasionally, customer presentations. A customer gave a demonstration of how they were populating a mobile app with summary of care information. Here’s are the specifics:
- When the patient is discharged an HL7 AO3 message is triggered by the EHR, which in this case was Paragon.
- When that discharge AO3 message hits the engine (trigger event), the engine the Paragon database and retrieves the XML for the C-CDA.
- The engine then performs a PIX query, which is a web services call, out to Mobile MD, the patient portal provider and developer of the mobile app.
- When a patient logs into the portal/app they’re actually logging into a Mobile MD site in the cloud.
- The engine performs a PIX query out to Mobile MD to get their identifier for the patient. When located the engine creates a provided register transaction and posts the C-CDA with the Mobile MD patient identifier to Mobile MD so that they can display it on a webpage/app.
- Curveball: Radiologists are not required to sign off on a chart until seven days after discharge. Meaning, the summary of care record is not finalized until it is signed by the radiologist.
- In the engine, they created an event in a work list. After the designated number of days it is triggered. The engine again queries Paragon to get the updated summary of care info and again posts it to the Mobile MD.
That’s a fairly complex workflow. The only thing that Paragon can do is show the patient’s record at this moment in time. The ability to have a timed trigger event with the engine allowed the customer to present a complete result to their patients.
This is just one of many creative ways Corepoint Health customers are using the engine to connect data to care.