Today’s high-quality, sustainable health IT systems depend on an integration layer that serves as the health data platform to interoperate between applications. While much attention has been placed on the 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... system, the integration layer serves as the catalyst for all health data activities and allows IT departments to break free from EHR databases and gain full control of their patients’ health data.
That’s the role Corepoint Integration Engine plays for hundreds of healthcare providers.
The demand for population health, precision medicine, mobile applications, and home health applications has highlighted the need for rapid and more lightweight digital integration. This need will be met through FHIR -based web APIs (application programmer interface) technology—which gives applications simple and fast access into other applications’ data.
As a software company, we are always looking at the changing needs in the marketplace to ensure our software stays ahead of the curve so our customers can stay on the cutting edge of health data exchange. FHIR, RESTful web services , and evolved data monitoring features are all present in Corepoint Integration Engine.
While we get excited about future trends and possibilities, it’s important to remain focused on the basics of current healthcare data exchange, which remains 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... v2.
HL7 is part of the foundation in which any healthcare interface, integration, or interoperability initiative can begin. There are no “out-of-the-box” HL7 templates between two or more applications, since each application is implemented a little differently and HL7 is used with just a little modification. This is what creates the joy and opportunity for many healthcare interfacing teams in the essential work they do.
If you want to review some of the basics, below are links to the common HL7 message types and an overview of what is really involved in an HL7 interface. You can visit our HL7 Resource Page  for a comprehensive list. This page remains a valuable reference source for interface teams (and consistently one of the most visited on our website).
- What is an HL7 ADT message?  (Patient demographics)
- What is an HL7 ORM message?  (Patient orders)
- What is an HL7 ORU message?  (Patient test results)
- What is an HL7 DFT message?  (Patient billing)
HL7 will remain a key ingredient for data exchange even as the industry adopts new methods and protocols. Current and future customers can be assured that Corepoint Integration Engine will continue to provide a high performing data platform for all healthcare organizations.