Product Update Expands the #1 in KLAS® Corepoint Integration Engine’s intuitive features, including new configuration management and enhanced CDA capabilities
Dallas – May 2, 2012 – Corepoint Health announced its latest release of Corepoint Integration Engine, industry-leading software that allows healthcare organizations to easily connect different applications internally as well as to external providers or health information exchanges.
New features in the latest release of Corepoint Integration Engine include several user-requested features, most notably Mobile Monitor. This feature allows users to perform key interfacing functions on their smart phone or tablet, including the ability to oversee interfaces with the power to resolve alerts and to stop and restart interface connections.
Neal Haerich, integration analyst at Hays Medical Center, tested the new Mobile Monitor feature and found the flexibility to remotely monitor and restart interfaces gave him greater peace of mind that data is flowing within the hospital.
“It makes my job easier when I’m away from my desk because I’m able to ensure that patient data is properly flowing through the connections,” said Haerich. “Mobile Monitor can alert me to any problems that arise so I know to return to the Administration Console to further diagnose and correct the issue.”
Other major new features included:
- Advances in native version control that allow multiple repositories to account for different interfacing scenarios and for configuration sharing, features that make it easy to move the interface from the testing environment into production
- XML enhancements for intuitive handling of Continuity of Care Documents (CCD), using the Clinical Document Architecture (CDA) standard
Using the native version control features within Configuration Management, multiple repositories on a single server can be created easily. This enhancement allows users to:
- Keep different interfacing projects separate, efficiently maintaining and organizing development environments
- Develop new integration projects from a clean slate, creating a development sandbox that does not impact other test environments
- Develop new interfaces from a known starting point, pulling the production environment into a test repository, then making isolated changes without being impacted by other test scenarios
By using multiple repositories, interface developers have flexibility and more control over their healthcare interface environment.
Additionally, the new XML enhancements give interface developers the ability to process and transfer CDA documents in a more robust way. As part of Meaningful Use Stage 2 requirements, this is a key feature to meet the CMS (Centers for Medicare and Medicaid Services) proposed direction of using Consolidated CDA as the standard for the electronic transfer of patient care summary records. Similar to how Corepoint Integration Engine handles HL7 Version 2 messages, users can easily parse complex XML structures according to the CDA XML schema.
Dave Shaver, chief technology officer at Corepoint Health, said that each new feature is designed to enable healthcare IT professionals to have more control over their organization’s healthcare interoperability initiatives, including additional testing, version control, and healthcare standards capabilities.
“We continue to listen closely to our customers in how they need to adapt to the new demands of healthcare integration,” Shaver said. “The new enhancements available in Corepoint Integration Engine focus on how healthcare interfacing teams can scale their operations efficiently, handling new healthcare standards more effectively, and moving interfaces more cleanly between test and production environments.”
Shaver continued, “Meaningful Use is driving more interoperability and connectivity initiatives, and interface teams are being asked to do more without the corresponding resources. At Corepoint Health, we recognize this, and we are working diligently to support our customers to handle the new demands without adding more hours to their work day.”