Corepoint Integration Engine runs essential health information exchange tests with 28 vendors
Dallas, Texas – Feb. 11, 2014 – Corepoint Integration Engine successfully completed testing in 14 Integrating the Healthcare Enterprise (IHE) profiles with 28 partners at the 2014 North American IHE Connectathon in Chicago, Jan. 27-31. Passing testing criteria shows that Corepoint Integration Engine can help healthcare organizations successfully exchange data with external applications and providers.
Corepoint Integration Engine demonstrated its proficiency with critical profiles used to securely share patient health information, both within enterprises and across communities. Meaningful Use embraces the use of Integrating the Healthcare Enterprise (IHE) is an initiative by healthcare professionals and industry to improve the way computer systems in healthcare share information. Visit the IHE website. Synonyms: Integrating the Healthcare Enterprise profiles for query-based exchange of health data with external organizations.
“The 2014 IHE Connectathon marked a new high for Corepoint Health because we were able to test Corepoint Integration Engine with 28 partners,” said Rob Brull, Corepoint Health product manager. “This is vitally important to our customers to ensure they will have a positive experience when connecting to these partners in a live setting.”
The IHE Connectathon, now on its 15th year, brings together approximately 500 healthcare IT professionals representing the industry’s leading IT vendors to demonstrate how applications can work together to effectively exchange health data. Participants choose to qualify, or test, for specific IHE Integration Profiles, which provide a data programming framework organizations use to exchange health data.
Corepoint Integration Engine tested a set of profiles that are commonly utilized for 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...) connectivity. Profiles tested included:
- ATNA: Defines basic auditing, secure communication, access and authentication controls.
- CT: Ensures that system clocks and time stamps are synchronized.
- PDQ (HL7 V2 and V3): Allows querying for a list of patients based on patient demographics.
- Patient Identifier Cross Referencing (PIX) What it is used for: Cross-referencing multiple local patient ID‘s between hospitals, sites, health information exchange networks, etc. Used when local patient ID’s have been registered with a PIX manage... (HL7 V2 and V3): Allows querying for patient identity cross-references between facilities.
- Cross-enterprise Document Reliable Interchange (XDR) – What it’s used for: The exchange of health documents between health enterprises using a web-based, point-to-point push network communication, permitting direct interchange between EHRs, PHRs ...: Allows point-to-point direct document interchange.
- Cross-enterprise Document Sharing What it’s used for: The sharing of documents between any health care enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility, through a common registry. Medical document...: Standard for registering and sharing 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... documents between healthcare enterprises.
- XDS-SD: Defines how to couple legacy formats within a structured 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... 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,... document.
- XCA (Initiating and Responding): Queries and retrieves patient records held across communities.
- XCPD (Initiating and Responding): Supports the translation of patient identifiers across communities.
- C-CDA (Create and Consume): Document standard required by Meaningful Use Stage 2.
About Corepoint Health
Corepoint Health delivers a simplified approach to internal and external health data integration and exchange for hospitals, radiology centers, laboratories, and clinics. Corepoint Integration Engine has been named the #1 interface engine for five consecutive years, 2009-2013, in the Best in KLAS: Software & Services report. Our software solutions help healthcare providers achieve interoperability goals and create operational leverage within their care organization.
Contact: Chad Johnson at 214-618-7028 | Email: firstname.lastname@example.org