The Integration Engine for Paragon Hospitals
Native High Availability.
Continuous processing of messages without expensive third party solutions.
Modern, improved system performance.
Proactive alerts, mobile interface monitoring, and custom user profiles.
Interoperability refers to the ability of two or more systems or components to exchange information and to use the information that has been exchanged., faster.
Develop, test, deploy, and manage interfaces in less time.
Office of the National Coordinator for Health Information Technology (ONC) – Located within the Office of the Secretary for the U.S. Department of Health and Human Services (HHS), the Office of the National Coordinator (ONC) coordinates nationwide ... More and IHE certified.
Exceed interoperability requirements and meaningful use specifications.
Paragon® customer case studies
Mary Lanning Memorial Hosptial
“We don’t find ourselves in the middle of a conversation where ‘product a’ says it’s ‘product b’s’ problem, and ‘product b’ says it’s ‘product a’s’ problem. Corepoint Integration Engine gives us the flexibility and power to make things work, resolve problems, and really speed things up.”
Ridgeview Medical Center
“It’s reassuring to know i can pick up the phone and receive excellent support, but to receive a proactive call from a Corepoint representative asking me what i need–that’s something extra special.”
“From a technical perspective, Corepoint Integration Engine is an absolute home run. It is extremely stable and easy to use. From an operational perspective, Corepoint Integration Engine delivers real value every day. In a Paragon environment, an interface engine will save money”
Oakbend Medical Center Paragon and Corepoint Integration Engine discussion
Paragon Interfacing Faqs
Do we need an FTE dedicated solely to the interface engine in order to manage it?
A number of factors come into play when determining the right staffing model for a hospital in supporting their interface environment. These factors include:
- Size of the hospital
- Number of interfaces planned
- Number of interfaces in production
- Complexity of the workflows
In general, building, testing, and deploying interfaces does not take a full-time employee. Ongoing management and maintenance is typically incorporated into the network or IT operations functions. For Corepoint Health customers, a mid-sized hospital may have a half FTE assigned to interface development.
Would an interface engine give me the capability to search for messages and resend? What about interface monitoring?
Within our administration console, there is a robust log management solution which makes it easy to filter, search, and re-send messages with a few clicks. Finding and re-sending messages is done in less than a minute.
Complete interface monitoring is achieved through a web-based console, complete with robust alerting. With Corepoint Integration Engine, customized alerts can be routed to the appropriate people if issues with any of the interfaces arise. If the alert is not addressed within the defined time period, it can be automatically escalated to the right individual or group of individuals.
Additionally, the Audit Logging and Log Search features provide key insights into your organization’s health data. Audit Logging allows engine users to record and view events such as any additions, deletions, changes, queries, printing, and copying of protected health information. Log Search allows users to perform Google-like searches for specific message types across multiple connections, including the complete history of a message’s lineage.
Do we have to be proficient in a programming language to have an interface engine?
The short answer is “no.” In most hospitals using our interface engine, an application or systems analyst is the skill level used in building, testing, and deploying interfaces. Building the interface is done in an environment that is menu-driven and easy-to-understand.
The approach is one of test-as-you-build so that you see the intended results immediately. Additionally, there is context-sensitive on-line help to assist with using the features of the interface engine.
Can we use your interface engine to connect to EMRs?
Yes. Electronic Medical Record (EMR), 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 can be... More connectivity is a growing area of demand as hospitals and clinics implement tightly connected communities of care. An interface engine plays a key role in the exchange of patient data between the different providers. Each EMR or hospital information system has a slightly different data format or communication requirement, and an interface engine delivers the flexibility to handle the exchanges efficiently and securely.
Corepoint Health has experience in working with various EMR interfaces. Although there are too many to mention, a few examples include eClinicalWorks, Greenway, Sage, eMDs, Allscripts, etc.
What health care standards and protocols does Corepoint Integration Engine handle?
- 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... More
- An HL7 standard that is short for Fast Healthcare Interoperability Resources and pronounced “Fire”. The standard defines a set of “Resources” that represent granular clinical concepts. The resources provide flexibility for a range of healthca... More
- Continuity of Care Document (CCD) The HL7 CCD is the result of a collaborative effort between the Health Level Seven and American Society for Testing Materials (ASTM) to “harmonize” the data format between ASTM’s Continuity of Care Record (CCR)... More
- Continuity of Care Record (CCR) is an XML-based standard for the movement of “documents” between clinical applications. Furthermore, it responds to the need to organize and make transportable a set of basic information about a patient’s health ... More
- X12 provides for electronic exchange of business transactions-electronic data interchange (EDI). The American National Standards Institute (ANSI) chartered the Accredited Standards Committee (ASC) X12 to develop uniform standards.
- The National Council for Prescription Drug Programs (NCPDP) creates and promotes the transfer of data related to medications, supplies, and services within the healthcare system through the development of standards and industry guidance. Visit the NC... More
- Transmission Control Protocol/Internet Protocol (TCP/IP) is a low-level communications protocol used to connect hosts on the Internet or a network. TCP/IP connections are established between clients and servers via sockets. TCP/IP is stream-oriented ... More
- Secure FTP
- Web services are a standardized way of integrating applications. Using open standards, businesses can communicate without in-depth knowledge of one another’s systems, beyond the communication protocol. Because all communication is XML-based, web se... More (SOAP (Simple Object Access Protocol) is a web services protocol used heavily in healthcare to implement IHE profiles. SOAP is an enterprise standard that is typically used by business applications to exchange information across the enterprise. See al... More, REST (Representational State Transfer) is a web services approach used heavily in social media sites. Uses HTTP in conjunction with GET, POST, PUT, and DELETE.)
- Microsoft SQL
- ODBC-compliant databases
- The Direct Project was launched by the ONC within Health and Human Services (HHS) on March 1, 2010. It was initially called NHIN Direct. The object of the Direct Project is to replace the use of faxes, phones, and paper transactions with a simple and... More
Isn’t an interface engine just another point of failure in my healthcare IT environment?
It is true that your patient data will be flowing through a central point and then routed to another defined application. Many hospitals—large and small—use this hub-and-spoke approach to exchange data.
With the help of an interface engine, robust monitoring and alerting is in place for all interfaces. If the data is not flowing as intended, then the right people will immediately receive alerts. Service levels are maintained while potential problem areas are quickly addressed.
With point-to-point interfaces, however, monitoring rarely exists. Managing 5, 10, 15 or 20 interfaces individually is far more challenging and risky than managing them centrally. Moreover, the right interface engine can deliver native high availability that provides additional protection and peace of mind.
Do you have 24×7 support available?
Corepoint Health delivers on our customer support promises. We have 24×7 support available, and our support receives the highest rating in KLAS®. Customers are central to everything that we do, and we work hard to demonstrate that every day in our interactions with our customers.