EP01.01 - Using Infoway Message Builder To Provide Proven Efficient Interoperability
e-Health ePoster Library. Lewis K. Jun 7, 2016; 131558; EP01.01
Mr. Kris Lewis
Mr. Kris Lewis
Login now to access Regular content available to all registered users.

You may also access this content "anytime, anywhere" with the Free MULTILEARNING App for iOS and Android
Rate & Comment (0)
Purpose/Objectives: To implement a standards-based interface for the Provider Registry System (PRS) used in BC, AB, SK, QC, and NL using Infoway Message Builder. Methodology/Approach: The Provider Registry System includes a messaging interface using a propriety specification. In the past, we supported HL7v3 messages by using XSLT based transformations. These transformations were effective but tedious to develop and test. From an ongoing maintenance perspective, it was expensive to keep-up with continuing standards development. We evaluated several options for a replacement design and chose to implement a new interface using the Infoway Message Builder library. To integrate with our existing data model and internal messaging formats, we created a design pattern for mapping and translation that isolates the Message Builder libraries from core PRS functionality Finding/Results: 1. By using Infoway Message Builder, our interface is more compliant with the standard. - We were able to focus effort on data semantics, mapping, and terminology translation rather than complex HL7v3 syntax and boilerplate XML. - Message Builder forces validation for data-types which is often overlooked by developers using other solutions. - We are able to force terminology validation where needed. 2. Our solution is easier to maintain and extend. - Using a plain-Java approach our code is easier to understand. - Our design allows for code re-use following standard Object-Oriented Programming concepts. - We are able to implement revisions and new standards releases with relatively low effort. - We are able to support jurisdictional variations by updating Message Builder with a jurisdictional version generated from Infoway ReMixer output. - We are able to use Infoway HL7 Explorer with content specific to our interface. - We can include HL7 Explorer content as a core component of our interface documentation. 3. Infoway was very attentive to our needs and development timelines. - They addressed defects and answered questions about usage, in a timely manner. - We included a number of jurisdictional model changes, and Infoway was able to add the changes and re-generate the Message Builder code in under two weeks. Conclusion/Implication/Recommendations: By using the Infoway Message Builder, our developers do not need to worry about the nuances of message formats. We can focus our effort where it matters most; on mapping, data semantics, and terminology. We are able to produce highly compliant messages with code that is easy to maintain or extend to support multiple jurisdictions or multiple versions of standards. Through tools like Message Builder; ReMixer; and HL7 Explorer, Infoway is becoming a better 'enabler', and adding significant value to implementations. 140 Character Summary: Using innovative Infoway tools to create a pan-Canadian Standard interface for the multi-jurisdictional Provider Registry System.
    This eLearning portal is powered by:
    This eLearning portal is powered by MULTIEPORTAL
Anonymous User Privacy Preferences

Strictly Necessary Cookies (Always Active)

MULTILEARNING platforms and tools hereinafter referred as “MLG SOFTWARE” are provided to you as pure educational platforms/services requiring cookies to operate. In the case of the MLG SOFTWARE, cookies are essential for the Platform to function properly for the provision of education. If these cookies are disabled, a large subset of the functionality provided by the Platform will either be unavailable or cease to work as expected. The MLG SOFTWARE do not capture non-essential activities such as menu items and listings you click on or pages viewed.

Performance Cookies

Performance cookies are used to analyse how visitors use a website in order to provide a better user experience.

Save Settings