Corepoint Integration Engine Technical Features

Scale Smarter with Corepoint Integration Engine

Corepoint Health’s customers have experienced many benefits of using Corepoint Integration Engine, including:

  • Reduced time in developing healthcare interfaces through menu-driven, graphical builds
  • Improved quality of interfaces by checking conformance and testing interfaces as they are developed
  • Increased productivity in building and maintaining interfaces with powerful, simple-to-use tools
  • Enhanced management of interface workflows through intelligent logging, monitoring, and alerting features within the interactive Monitor

Corepoint Integration Engine is an effective solution for healthcare organizations that are updating first-generation interface technology or adding a supplemental or departmental interfacing solution.

Communication: send and receive

  • Send or generate outbound messages
  • Manage dynamic behavior profiles to deal with inbound acknowledgements
  • Manage inbound messages and generate acknowledgements
  • Handle HL7 resends
  • Manage communication with multiple applications
  • Support unrestricted data flow
  • Resolve Minimum Layer Protocol (MLP) implementation and communication problems
  • Use pre-configured sender and receiver logic
  • Read, write, query, insert, and/or delete data in any ODBC Database
  • Support for and
  • Easily send large batch files with streaming technology

Meaningful Use compliant

  • Corepoint Integration Engine was the first Meaningful Use Stage 1-certified interface engine for Modular Ambulatory and Modular Inpatient EHR
  • Corepoint Integration Engine has continued certification throughout all three stages of Meaningful Use
  • Corepoint Integration Engine certifies to the same privacy and security criteria as EHR vendors
  • Satisfy your Public Health Reporting requirements for Immunizations, Electronic Lab Reporting, and Syndromic Surviellance

Message: map and route

  • Use preloaded definitions of messages, segments, fields and data types for all HL7 2.x versions
  • Support for XML messages created using HL7 version 3, custom XSDs, and standards including HL7 Clinical Document Architecture (), Consolidated CDA, and Continuity of Care ()
  • Support for , and
  • Include ASCII or UNICODE character sets
  • Process repeating fields, repeating segments, groups of segments, etc.
  • Handle one input message to produce 0-to-n output messages through dynamic, contentbased routing
  • Transform XML documents into HL7 messages
  • Run HL7 conformance checks using sample messages, testing the HL7 derivative configuration; reinforce the HL7 objective of keeping compatible versions and ensuring data integrity
  • Pass messages through as unparsed objects
  • Build, process, or route batch files

Interface: configure and test

  • Review the history of any configuration object, and edit configuration objects without impacting the running engine service
  • Leverage the entire HL7 standard as the starting point for each interface
  • Allow user-defined variations in messages (e.g., making segments or fields optional, required or rearranging)
  • Configure and leverage vendor-specific HL7
  • Configure messages easily to reduce integration work
  • Create Z segments and custom messages
  • Validation check on user-defined HL7 messages
  • Summary view and HL7 message filtering available
  • Process HL7 documents, such as CDA, C-CDA, CCD, and more
  • Create resources to exchange data via Web Services and FHIR

Health data workflow using Corepoint Integration Engine

 

interface workflow

 

Message and document definition

  • Configure message mapping easily to reduce integration work
  • Define filter criteria such as ‘Only send A04 and A08’ and ‘Remove all outpatients from data stream’ through GUI-based tool
  • Adjust coded values such as replacing “M” to “1” for Male
  • Point-and-click GUI to move data from point A to B in a message
  • Print and save HL7 message definitions and configuration files for clear documentation
  • Completely reformat interface message or document without writing any code or interpreted scripts
  • Test mapping operations in GUI testing screen prior to implementation
  • Export interface configuration

Alert configuration

  • Configure alerts flexibly according to time and severity thresholds, including:
    • By day
    • Time of day
    • Type of day (e.g., weekday, weekend, holiday)
    • Thresholds (seconds, minutes, hours)
    • Who receives alert
  • Receive alerts based on:
    • Queue depth
    • Message error
    • Connection activity
    • Connection status
  • Assign unique alert configurations to different interfaces
  • Set escalation of alerts if no change in status or new threshold is met
  • Store and view alert and resolution log

Alert: view and resolve

  • Automatically monitor connection states and related conditions, and raise alerts when problems occur
  • Display alerts in an administration console
  • Send alerts via email to mobile devices, cell phones, etc.
  • Support for quick resolution of alerts

Archive: review and resubmit

  • Search messages using an intuitive search utility
  • Search for messages by message content, history, and metadata attached to the message
  • Edit and re-send messages easily, especially useful in testing
  • View the message lineage across connections with a single click

Connection: monitor and control

  • One-click access to search logs, review alerts, and review the details of each interface in the Monitor
  • View and manage connection status in HTML5
  • Tailor display and easy control of the conn – ections’ view in the Monitor
  • Filter HL7 messages by content (e.g., find all ADT for patient #127451)
  • Examine:
    • Connection state (Is the connection working?)
    • Idle time (Is there any issue with the message flow on a connection?)
    • Message queue depth (Is there a delay in message processing?)
    • Centralize interface connection management

Web-based administration console

  • Determine access to interface environment with user roles
    • Corepoint Integration Engine logon credentials stored in Corepoint Integration Engine
    • Windows user: authentication is carried out using Windows username and domain name credentials
    • Windows group: authentication is carried out using Windows local groups
    • User profiles: provide added security in determine permissions
    • Engine: start and stop service, view engine log, manage licenses
    • Configuration: view and export configuration objects, modify and import configuration objects, manage users, configure and monitor Corepoint Integration Engine
    • Connections: view connection status, start and stop connections, view alerts, resolve alerts, view connection log, view message log, resend messages
  • Graphical views:
    • Quick view: Get high level monitoring and see all of your connections via Connection Central. The drill-down color display provides status of your connections in real-time
    • Alert view: See alerts as they happen for quick action and resolution
  • View and manage logs conveniently within the management console. Filter messages based on message content and or time of day

Ensure high availability

  • Assured Availability (A2) for Corepoint Integration Engine simplifies high availability and enables an easy-to implement solution that constantly delivers run-time confidence
  • Delivered natively
  • Ensures continuous processing of critical patient data exchanges without the need to setup complex, maintenance-intensive clustering environments
  • Disaster Recovery for Corepoint Integration Engine enables remote backup capabilities in the event of a disaster

Download PDF

 Print Friendly