Interfaces developed and operated using the Ensemble enterprise interface engine provide data integration services between patient care and business applications within the Medical Center as well as between Medical Center applications and affiliated organizations.
To provide information about Interface Standards, Environment, Development and Support.
The scope of this document is to describe standards applicable to interfaces developed and operated using the eGate enterprise interface engine.
The current standard supported is HL7 version 2.3 unless otherwise noted.
Ensemble is used for enterprise interfacing. It supports real time TCPIP and batch interfacing. Interfaces to hosts outside of the secure clinical subnet are supported via VPN, SSL/HTTPS or sftp. There are approximately 270 interfaces in production. We operate separate Production and Test systems.
New Interfaces - Requests for new interfaces should be sent to the Manager of Integration, Waddill Stewart, for review. Every effort is made to support new interface requests within our existing standards.
- Vendors are expected to implement custom logic or filtering within their interface processes in an effort to maintain consistency and standards across all applications.
- It is the standard of the UVa Health System to first implement an ADT interface to a new system before implementing outbound orders, results, documents or charges to other Health System applications. The goal of this is to minimize errors by using electronic synchronization of patient data via ADT.
- Department users are requested to thoroughly test how interfaced data is working within their system prior to implementing a production interface. It is expected that Unit, Functional and Scenario/Scripted testing efforts are employed and documented.
- Established test systems and test interfaces are needed to support testing and future changes.
Changes to Existing Interfaces - Requests for interface customizations should be sent to the Manager of Integration, Waddill Stewart, for review. Every effort is made to support changes within our existing standards.
- Changes require testing prior to be implementing in production. The requesting department should drive the testing, including coordinating the data entry activities required of others and validating the desired results within their application.
- A formal Change Control procedure is used by the interface engine support staff. All changes are to be documented including documentation about the type and scope of testing that took place and acceptance by the requesting department.
Interface Operational Support
Engine Support - HIT provides the application and infrastructure support of the interface engine. This includes server support, system patches, upgrades and other required maintenance. Planned maintenance activities will be communicated to designated interface contacts so departments can employ downtime procedures as needed.
Interface Monitoring - Interface connections to other systems are monitored on a 24x7 basis. Alerts are configurable and sent to designated support contacts.
Designated Support Contacts - This must be a Health System staff member or team capable of understanding the impact of the interface problem and able to coordinate the appropriate resolution. They should have a cell phone capable of receiving text messages. The designated contact can not be a vendor, although the UVa designated contact may contact the vendor as needed to resolve the problem.
Reconnection Configuration - Interfaces on vendor systems should be configured to automatically attempt to reconnect to the interface engine should they become disconnected for any reason. This can happen for any number of reasons including server reboot, network issue and planned/unplanned maintenance. Configuring to reconnect reduces the need for technical support staff to become involve and makes the overall environment more robust.
- New systems requesting interfaces must have the capability to apply filtering rules to HL7 messages
- New systems requesting interfaces must have the capability to edit fields or change format in accordance with system data requirements
- Must support both batch and real time message processing