ViaExchange
TreVia’s comprehensive interoperability engine utilizes the latest technology and state-of-the-art architecture
ViaExchange is an interoperability engine that allows for the seamless sharing of healthcare information between disparate systems. ViaExchange connects external systems using standard messaging protocols, like HL7. It is built on an Enterprise Service Bus (ESB), giving it enterprise scope and scalability. ViaExchange can be used to connect to anything, from legacy practice management systems, to modern electronic medical record systems, to cloud-based billing systems.
Architecture
ViaExchange is a service oriented architecture (SOA) that allows for the complexities of external systems to be isolated at the “edge,” enabling down stream systems to operate on a canonical message, unaware of the original sourcing system. Transformation of HL7 messages is handled by using Mirth Connect channels. Mirth Connect is an open source healthcare transformation engine that is attached to the ESB. Using this connection the Mirth Connect channels get their input messages, transform them into a canonical form, and publish them back onto the ESB for downstream processing.
The edge adapters are typically services created for specific external systems communication and protocol exchange. An example would be an MLLP adapter for HL7, or an http (REST/SOAP) adapter using web services for cloud based systems.
The architecture supports both inbound and outbound messaging. In this context, the direction is with respect to ViaExchange, so an inbound message is a message coming from an external system into ViaExchange. A typical example of an inbound message would be patient demographics and insurance to insert or update patient information in the patient directory. In the HL7 context, these would be ADT messages. Further, outbound messages from ViaExchange to other systems would be to send out patient exam results that could be inserted into the patients electronic medical record. Again, in the HL7 context, this would be an ORU message. Additionally, bi-directional support is included in ViaExchange whereby request/reply messaging is supported. A good example of this type of messaging involves the ViaExchange system asking an external system if a patient exists and if so to send patient demographic and insurance information back.
Custom formats and specifications
ViaExchange is simple to extend and to support custom message formats and protocols. Using our “at the edge” technology, customization and special message handling is accomplished easily and at a point where downstream processing is not effected. ViaExchange utilizes the concept of channeling as well, meaning each specific interface to an external system is connected using a dedicated channel. Each channel encapsulates all the needed information within it to communicate directly with the external system and in-turn interact with the other TreVia digital health systems.
Operations
As is the case with any interfacing/integration system, there must be an operational component included that allows for the manual ability to manage exceptions that naturally happen between external systems exchanging information. These operations are typically centered on what to do with patient demographics and duplication checking. A patient directory containing many duplicate patient records quickly becomes fractured and records become isolated. ViaExchange detects any duplicates and places the exception in a hold area that allows ViaExchange support personal to manually examine the exception and either correct any issues with the exception or allow it to be processed directly.
All operations are accomplished through our standard management console which is completely browser based and works anywhere there is an internet connection, making ViaExchange easy to monitor and manage.
