Webinar: Results from the 2018 Canadian Physician Survey: Use of Digital Health Technology in Practice, Monday December 10, 2018, 1 - 2 P.M. more >

Share this page:

Integrating the Healthcare Enterprise (IHE)
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Members: 145
Contact: Derek Ritz
Type: Open
Access: Public
Health care and health information professionals collaborating to improve information sharing between health care technology systems.

About

What is IHE?

Unlike HL7 (or ISO, or SNOMED, or WHO, etc.), IHE is not a health informatics standards development body. Rather, IHE is a standards profiling body. IHE Profiles are implementation guides – they make standards digestible, usable, and implementable. They describe, at a conformance-testable level of detail, how a portfolio of underlying standards will be employed to address the ecosystem-wide interoperability issues associated with a specific set of healthcare use cases. IHE Profiles create re-usable, digital health building blocks by “packaging up” the 5C’s:

  • Care context
  • Content specs
  • Coding specs
  • Communications specs
  • Confidentiality and security specs

The target audience for an IHE profile is the entire care delivery network. This especially includes the jurisdictional governance entities that are tasked with operationalizing plug-and-play interoperability between disparate network participants. IHE is focused on taking digital health interoperability to scale and to mitigating the risks inherent in such an effort.

What is the IHE Community?

The IHE Community is a place where health care professionals and the health information industry collaborate to improve the way health care technologies and systems share information.

To become a member of this community select Join Group in the Group Menu.

If you have an idea for a community, working group or project that will drive interoperability forward, let us know! Send your suggestions

LEADER

Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.

KEY RESOURCES

IHE Resources

Activity

Umberto -- I completely agree. I made a FHIR joke in a meeting yesterday when I said: "it's like riding a hype-cycle... once you learn how, you never forget". (with apologies to bicycle-riders everywhere...) ;-)
Ready, set… Check out two NEW exciting opportunities happening at the IHE North American Connectathon 2019 this January in Cleveland, Ohio! ... | Wednesday, January 23rd, 8:30am – 6:00pm ET Advancements in health information exchange and the characteristics of interoperability are being shaped through a variety of organizations and initiatives. Achieving interoperability of health information within and among healthcare organizations requires dedicated focus not only on the people and the processes but also on the organization’s vision, strategy, and business model capabilities. Join IHE USA and HIMSS for a highly interactive conference comprised of educational sessions, demonstrations, a hands-on workshop and an exclusive tour of the IHE North American Connectathon testing floor and HIMSS Innovation and Conference Center, and will begin with a keynote presentation describing the national vision for achieving interoperability presented by Steven Posnack, Executive Director of the Office of the National Coordinator for Health IT. ... | Thursday, January 24th, 8:00am – 5:30pm ET & Friday, January 25th, 8:00am – 12:00pm ET Health IT developers and implementers at healthcare organizations across the country will soon be required to know how to leverage Fast Healthcare Interoperability Resources (FHIR®). Michigan Health Information Network (MiHIN) and IHE USA are hosting a collaborative interoperability testing event based on HL7 FHIR® specifications and the MiHIN FHIR PIT and Ring of FHIR implementation, consisting of tutorial material and face to face testing at the IHE NA Connectathon 2019. The tutorial will be presented as part of the Innovations in Interoperability - Connectathon 2019 Conference on Wednesday, January 23 (separate registration required), and the Ring of FHIR Interoperability testing event will take place the following days. Take advantage of this exciting opportunity to get hands-on experience and learn, develop, and test the exchange of health information using MiHIN’s FHIR Pilot Interoperability Testbed! Interested? Find out more by clicking the links above! …GO! Ready to register? ...! More information at ....
Sean Murray joined a group
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
After the great presentation that Derek did I asked few questions regarding information vs data models, how FHIR fits into this picture and what to use to manipulate data (data analytics, big data and other popular terms). Instead of having 1:1 email conversation we decided to move this over the IHE Canada thread. Please feel free to express your thoughts. I also think it may be useful to bring someone from OHDSI to present OMOP data model, i.e., what advantages it has over FHIR model, practical use, etc. With Derek’s permission his answer is below: ============ RE: the information model / data model distinction – I think it’s important to reiterate that FHIR is a data model (it is a message model intended to traverse the wire). Information models are more conceptual in nature. OpenEHR archetypes, for example, are based on an underlying Reference Model (RM)… and this RM is an information model. The HL7 RIM is a conceptual/information model, too. To successfully support big data analytics – the content must be in a computable format and it must be “understandable” what that content represents. This is one of the strengths of the OHDSI initiative (and its adoption of OMOP) – there is an agreed, underlying information model that each participating entities’ data model… and data… can be mapped to. I know there are some who are leveraging FHIR as such an information model. The problem with this is – what happens when the FHIR spec changes? (think of Apple… which has wedded its HealthKit information model to FHIR DSTU 2… and which now finds that this information model is out of step with the latest version of the FHIR spec). Is this related to what IHE does? To be honest… that depends. IHE’s core focus is on interoperability – so it very much finds itself concerned with the “wire formats” that describe message formats and data exchange patterns. But if you look at the arc of IHE’s work over time – there have been multiple IHE profiles that address the same underlying workflow and which are, in fact, harmonious with each other’s underlying information models (e.g. PDQ, PDQv3, PDQm). One of the things that came up last week during the F2F IHE meetings in Chicago was the premise that, going forward, IHE profiles should be behaviourly compatible with each other – regardless of whether they are HL7v2 based, or CDA-based, or FHIR-based… or whatever. So there is, potentially, a role that IHE profiles can and will play in collecting big data assets that can drive broad-scale analytics. This topic is very much in-scope for the new Computable Care Guidelines work item, for example. ============
Hi all -- a hearty thanks to everyone who attended today's webinar and especially to those who contributed their very-helpful comments and questions. Much appreciated!! Since some of you have asked, I've uploaded a copy of the slide deck from today's webinar to my GDRIVE; it can be found .... I also managed to find the ZOOM recording on my hard drive and convert it into a viewable video format that I could upload to Vimeo. The video of the webinar is here (and sorry for how goofy I sound during the first few minutes... it took me a bit of time to get sorted out with Zoom): .... As a word of caution... my slides don't always make as much sense without the voice-over as they do with the voice-over... so please, if you're re-using any of the content, do try to preserve the "context" and associated meaning they were intended to convey. Of course... if it doesn't make sense no matter how many times you listen to the ZOOM recording, please post a comment or suggestion to the thread that will help clear things up for us all (especially me!). It takes a village... ;)
Beverly Knight joined a group
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Deepti Razdan joined a group
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.

Events



Upcoming events:
No events

Forum

Turning HYPE into VALUE -- DISCUSSION THREAD 11/29/18
Umberto -- I completely agree. I made a FHIR joke in a meeting yesterday when I said: "it's like riding a hype-cycle... once you learn how, you never forget". (with apologies to bicycle-riders everywhere...) ;-)
News from our IHE USA colleagues regarding Connectathon 2019 11/29/18
Ready, set… Check out two NEW exciting opportunities happening at the IHE North American Connectathon 2019 this January in Cleveland, Ohio! ... | Wednesday, January 23rd, 8:30am – 6:00pm ET Advancements in health information exchange and the...
Turning HYPE into VALUE -- DISCUSSION THREAD 11/29/18
Hello Derek, great article (unfortunately I discovered it just now). I agree with the idea of turning hype into value, but you missed a part of it in my opinion: IHE shall act as a sort of hype filter as well. Because we all know: hype is quite of...
Turning HYPE into VALUE -- DISCUSSION THREAD 11/23/18
After the great presentation that Derek did I asked few questions regarding information vs data models, how FHIR fits into this picture and what to use to manipulate data (data analytics, big data and other popular terms). Instead of having 1:1 e...
Turning HYPE into VALUE -- DISCUSSION THREAD 11/21/18
Hi all -- a hearty thanks to everyone who attended today's webinar and especially to those who contributed their very-helpful comments and questions. Much appreciated!! Since some of you have asked, I've uploaded a copy of the slide deck from toda...
Turning HYPE into VALUE -- DISCUSSION THREAD 11/14/18
Thanks, Mike -- these are very insightful comments. Your point is well-taken; IHE profiles can and do reference multiple underlying standards (not just FHIR). This is, I think, one of the key strengths -- an IHE profile of FHIR can draw in and includ...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/14/18
Thanks, Shanil. The effort right now is to develop a standards-based specification (a "grammar") that may be used to express a computable care guideline. Is this what the company had? If you'd like to connect them into this forum -- that'd be great!...
Turning HYPE into VALUE -- DISCUSSION THREAD 11/13/18
Thanks for the blog post, Derek. You reminded us all of the importance of IHE in the digital health ecosystem. A couple of comments: This article focuses around FHIR, but it should be pointed out that IHE profiles work with many other standard...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/13/18
Hello All, I was at American Heart Association couple days back and I met with a company who has the experience of integrating all kinds of data not limiting to EHR/EMR, genetics, wearables, and so on. This is all HL7. Also, they have the capabili...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/13/18
Yup -- we'll be progressing the "official" work, there, regarding the new profile. Ron -- there may also be a general "call for participants" regarding the WHO's own internal project as this moves to a prototyping phase around antenatal care and immu...
Turning HYPE into VALUE -- DISCUSSION THREAD 11/13/18
Hey David -- I think you've raised a number of really good points! As a first, most obvious observation -- I completely agree with you... the whole purpose of this blog post is to "reach out proactively to the industry beyond current committee member...
WHO as an IHE Deployment Committee 11/13/18
Hey Ron -- our next step is to wait for the "launch" meeting to take place between the IHE board co-chairs and the WHO reps. This first meeting has been delayed because of trying to find a suitable time between the very-busy schedules of these partie...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/13/18
Derek, I would very much like to be a part of this. I presume this involves signing up for QRPH Technical Committee?
Turning HYPE into VALUE -- DISCUSSION THREAD 11/13/18
This is an interesting blog entry. To date, IHE ITI and other Domain have mostly focused on creating Implementation Guides for using FHIR with existing Document Sharing or other established profiles. These are needed as there are many DS implement...
WHO as an IHE Deployment Committee 11/13/18
Hey Derek. This is a great idea, and I have my particular reasons to participate. How does one get engaged? Rp

Tasks


Tasks


Time Tracking


Gantt

Documents

Click Manage documents to:

  • view the complete list of documents or documents grouped by folder
  • upload a new document

Note: Group members are not currently notified when new documents are added. To notify others, you must post the URL to the new document in the forum. (Notification of document uploads is a feature in development.)

Manage documents You may need to login and/or be a member of the group to access this content.

Archive ( 4 Documents )

IHE Canada Liaison Role Description

Published on Jul 19, 2018 by Andrea MacLean

Video

Solutions

  • Canadian FHIR Registry
  • Canadian URI Registry
  • FHIR Terminology Service API
  • HAPI FHIR
  • HAPI v2
  • HL7 Explorer
  • InfoRMS
  • Message Builder
  • Message ReMixer
  • Object Identifier (OID)
  • SNOMED CT Browser
  • Terminology Gateway
  • Terminology Service API
  • TermWorks
  • WebHook Notifications

The Canadian FHIR® Registry supports collaborative development in an effort to accelerate sustainable growth of FHIR, locally and internationally. The registry will be the home of national FHIR profiles recommended for use in Canada, including extensions, value sets, URIs and other useful, commonly used components. It is also host to a growing number of national, jurisdictional and locally shared FHIR projects, and is open to all Canadian implementers.

The Canadian FHIR Registry offers:

  • seamless integration of profile editing using Forge (free FHIR profile editor)
  • designated project space
  • supports project teams of up to 100 individuals
  • online authoring of implementation guides
  • integration with source control tools such as GitHub
  • version controlled environment

The Canadian FHIR Registry blends software development best practices with the requirements of modelling in FHIR, essential to delivering successful project requirements while having continuous access to structure validation, rendering and publishing.

All project artifacts are backed up weekly, on Sunday nights. Each snapshot will be retained for 10 days. The project owner can request an as-is snapshot containing all the necessary artifacts such as text, xml, json, md and image files by contacting This email address is being protected from spambots. You need JavaScript enabled to view it..

Organization projects can be viewed without logging in. To edit or request a new project, This email address is being protected from spambots. You need JavaScript enabled to view it. with the details.

View projects in the Canadian FHIR Registry

The Canadian URI Project is a repository of identifier and code system namespaces. Capturing key metadata as FHIR® NamingSystem resources provides an automatic mapping of OIDs to URIs or vice versa.

To make the discovery of these artifacts more flexible, the Canadian URI Registry (alpha) was developed to allow artifacts to be queried via plain text, OID, URI or their respective identifiers. These identifiers are created according to the URI guidelines and posted to the FHIR Solution Architecture Workstream for approval.

It is important to note that all searchable artifacts are to be curated via the Canadian URI Project in Simplifier. There are ongoing discussions with the FHIR Solution Architecture Stream to have a single representative manage data for their respective jurisdictions.

A scheduled task is run periodically, making all new or modified artifacts searchable after a 20 minute window.

Search the Canadian URI Registry (alpha)

FHIR web services used to access terminology data

FHIR Terminology Service APIs enable automated exchange of clinical terminology content and resources. It allows developers to easily implement healthcare applications that programmatically consume codes and subsets without requiring in-depth expertize in the fine details of terminology.

terminology gateway APIFHIR Terminology Service API

 

Open source integration tools useful for health IT integration projects

HAPI FHIR® is a simple-but-powerful library for adding FHIR messaging to applications. It is pure Java compatible and licensed under the business-friendly Apache Software License, version 2.0.

HAPI FHIR

 

External Solutions for API integration

Open source integration tools useful for health IT integration projects.

HAPI v2
 

HAPI for HL7 v2 messages is an open-source, object oriented HL7 v2.x parser developed for the Java platform

HAPI FHIR
 

HAPI FHIR is a simple-but-powerful library for adding FHIR messaging to your application. It is pure Java compatible and licensed under the business-friendly Apache Software License, version 2.0.

Open source integration tool useful for health IT integration projects

HAPI for HL7 v2 messages is an open-source, object oriented HL7 v2.x parser developed for the Java platform.

HAPI v2

Enhanced browsing of HL7 v3

Infoway HL7 Explorer is a powerful browser for HL7 v3 structures, vocabulary and references. Used in conjunction with the pan-Canadian releases, HL7 Explorer makes locating details and information more efficient.

In November 2017, the Canadian HL7 InfoCentral community determined that there was no longer any need to do further updates to the pan-Canadian Version 3 messages. As a result, the December 2012 releases of MR02.06.01 and CeRx 4.4.2 are the latest pan-Canadian publications of these standardized messages.

The HL7 Explorer, the Master Terminology Worksheet (MTW) and all other messaging related artifacts are aligned with the latest releases.

Overview
 

Learn about the features HL7 Explorer: search once, graphical representation, quick hints, etc.

MR 02.06
 

HL7 Explorer applied to the MR 02.06 HL7 v3 maintenance release

CeRx 4.4.2
 

HL7 Explorer applied to the CeRx 4.4.2 HL7 v3 maintenance release

 

 

Standards versions available for viewing in HL7 Explorer

Standard URL 
CA MR 02.06 https://infocentral.infoway-inforoute.ca/extra/ca/mr0206-html/html/search.html
CA MR 02.05.01 https://infocentral.infoway-inforoute.ca/extra/ca/mr020501-html/html/start.html
CA MR 02.05 https://infocentral.infoway-inforoute.ca/extra/ca/mr0205-html/html/start.html
CA MR 02.04.03 https://infocentral.infoway-inforoute.ca/extra/ca/mr020403-html/html/start.html
CA CeRx 4.4.2 https://infocentral.infoway-inforoute.ca/extra/ca/cerx442-html/html/search.html
CA CeRx 4.4.1 https://infocentral.infoway-inforoute.ca/extra/ca/cerx441-html/html/start.html 
CA CeRx 4.4 https://infocentral.infoway-inforoute.ca/extra/ca/cerx44-html/html/start.html
BC V02R04 https://infocentral.infoway-inforoute.ca/extra/bc/v02r04-html/html/start.html
NS CeRx 4.3 https://infocentral.infoway-inforoute.ca/extra/ns/cerx43-html/html/start.html
NS R02.04.03 https://infocentral.infoway-inforoute.ca/extra/ns/r020403-html/html/start.html
AB MR2007 https://infocentral.infoway-inforoute.ca/extra/ab/mr2007-html/html/start.html
AB R02.04.03 https://infocentral.infoway-inforoute.ca/extra/ab/r020403-html/html/start.html
AB R02.04.00 SHR https://infocentral.infoway-inforoute.ca/extra/ab/r020400-shr-html/html/start.html
AB R02.04.03 Imm https://infocentral.infoway-inforoute.ca/extra/ab/r020403-imm-html/html/start.html

Request Management Solution

InfoRMS (Infoway Request Management System) is Infoway's Request for Change Tool for SNOMED CT, pCLOCD/LOINC and pan-Canadian Subsets. Not sure if you have access to InfoRMS? Manage your InfoRMS Access in your user profile.
SNOMED CT
 

Prior to submitting a SNOMED CT request, it is the requestor's responsibility to:

  1. Validate that the content does not exist in either the International or Canadian editions of SNOMED CT
  2. Comply with the appropriate Editorial Guidelines

Submit or follow requests to SNOMED CT

pCLOCD/LOINC
 

Prior to submitting a pCLOCD/LOINC request, it is the requestor's responsibility to:

  1. Validate that the content does not exist in LOINC or the pCLOCD
  2. Comply with Regenstrief Editorial Guidelines (note: login required)

Submit or follow requests to pCLOCD/LOINC

pan-Canadian Subsets
 

Prior to submitting a Subset request, it is the requestor's responsibility to:

  1. Validate the content against the subsets in Terminology Gateway
  2. Comply with the appropriate proper terminology Editorial Guidelines

Submit or follow requests to pan-Canadian Subsets

 

Solution for API integration

Infoway Message Builder allows developers to focus on the business challenges of integrating their solutions with each electronic health record implementation by abstracting the differences between different versions of pan-Canadian HL7 messaging and supporting current implementation constraints. Developers can build interfaces in a familiar development environment, using the programming language of their choice*, while the Message Builder API fosters quick and easy creation, population and access to HL7v3 requests and responses.

Infoway Message Builder v2.0 and later is enhanced to generate JAVA APIs to create, validate, marshal/unmarshal CDA documents.

 Implementation and Exchange

 

Key features and benefits

Message Builder offers a number of key features and benefits:

  1. Abstracts the complexity of HL7v3 messages and greatly simplifies the work of the developer when implementing them;
  2. Reduces the impact on developers from implementation variations;
  3. Enables companies to achieve Infoway product certification with greater confidence and reduced time;
  4. Enables developers to incorporate future message versions without re-writing their products;
  5. Can be embedded in software applications due to its open source distribution under a commercial-friendly Apache 2.0 license.

Out of the box support

Infoway Message Builder comes with built-in runtime APIs that support a number of pan-Canadian specifications:

  • MR2009 (R02.04.02)
  • MR2007 (V02R02)
  • MR 2007 (V02R01)
  • CeRx (V01R04.3)

In addition, while developers can easily build custom transport mechanisms without affecting the core, Message Builder includes native support for SOAP and RESTful message transports. Developers can configure and extend the transport as desired.

Detailed product features

  • Provides the capability to configure and populate message values that are common to all messages—this allows developers to reuse common message data, shortening the time to configure and create an interoperable system.
  • Uses simplified data types that are natural and familiar to the programming language (e.g. String for ST) rather than directly exposing the sometimes complicated HL7v3 data types—yet still allowing access to HL7v3 data types when necessary.
  • Allows developers to focus on the business-aspect of a request/response, avoiding many of the complexities of HL7v3.
  • Code-generation algorithms merge identical and similar classes together to simplify the generated API—meaning less confusion in the resulting code and an increased ability to write generic handlers for certain types.
  • Converts populated objects into HL7v3 XML requests, and converts HL7v3 responses into populated objects.
  • Provides flexibility in configuring and performing terminology-code lookups, including code set and database-backed lookups (can mix and match).
  • Associations and attributes are strongly typed, given business names when provided, and contain code docs directly from the MIFs (see wiki.hl7.org/index.php?title=MIF).
  • The algorithms inline most classes that only have a small number of properties, further simplifying the API.
  • Offers both permissive and strict modes—permissive allows many common errors and generates appropriate error comments in the XML or result object.
  • A separate validation tool is provided to test ad-hoc messages—this tool reuses the same validation components that are executed during message marshaling and unmarshalling, ensuring consistent processing of the message whether during processing or during conformance validation.

Forward looking

The power of the Message Builder architecture is in its MIF-based generation of the specification API. With Message Builder, any MIF is supported—whether a future release of the pan-Canadian specifications or a modified (constrained) jurisdiction-specific release of an existing specification. 

 

How it works

Message Builder comprises two parts:

  1. Message Builder Generator—a tool used by Infoway to take input MIFs and create Message Sets for use by Message Builder Runtime;
  2. Message Builder Runtime—an API used by developers to allow their products to support multiple Message Sets without recoding.

Message Builder Generator

Used by Infoway, Message Builder Generator takes MIFs (as the source of truth for standards specifications) and converts them into a series of Java Classes. This is done by first converting the MIFs to an XML Message Set (a simplified representation of the information present in the original MIFs), then generating Java Classes that reference standard Java data types and use business-friendly names. In the process, groups of related elements are flattened and similar message parts are placed into a single class: these steps increase ease of use and reduce the complexity of the resulting Java Classes.

MBG process

Using Message Builder Generator, Infoway is able to create multiple Message Sets, each representing the MIFs used in a single jurisdiction, but all for the same HL7v3 version.

Message Builder Runtime

Message Builder Runtime allows developers to quickly adapt to implementations in multiple Jurisdictions: incoming messages are first examined to determine the corresponding source Message Set, once identified, a series of Java Objects that represent the message are instantiated. Next, the Java Objects are turned into an HL7 message for the HL7 version corresponding to the desired destination Message Set. 

MB process

Using Message Builder Runtime developers can accept messages over the wire and on-the-fly turn them into a different HL7 message version. Given the capability of Message Builder to support future versions of HL7 messages, developers can easily future proof their products with minimal effort.

 

*Developer friendly

The Message Builder libraries are available for Java and Microsoft .NET. In addition, a simplified XML message format is available with REST-based services for managing mapping to/from the simplified form to the target specification XML format.

 

CDA Support

Message Builder CDA API supports the following CDA and data type specifications:

Message Builder provides  JAVA and .NET APIs for CDA document creation, validation, marshalling/unmarshalling of the following CDA document types:

  • Continuity of Care Document (CCD) (Release 1.1)
  • Consultation Notes (Release 1.1)
  • Discharge Summary (Release 1.1)
  • Imaging Integration, and DICOM Diagnostic Imaging Reports (DIR) (Release 1)
  • History and Physical (H&P) (Release 1.1)
  • Operative Note (Release 1.1)
  • Progress Note (Release 1.1)
  • Procedure Note (Release 1)
  • Unstructured Documents (Release 1.1)
  • CDA documents using pan Canadian CDA header template

Clinical applications in JAVA or .NET can use the Message Builder CDA APIs to create, validate or parse above listed types of CDA documents. Potential use cases are document source or document consumer actors in IHE XDS profile, content creator/content consumer in any content module/profile, or report creator/viewer in RIS/PACS/EMR systems.

Message Builder is available for Java and .NET

Message Builder for Java

System Requirements

  • Java 1.5 or higher
  • Maven 3.0.3 or higher (can be removed after installing Message Builder if working with a non-Maven project)

Download

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder, you will need

  1. Message Builder Core and
  2. one or more Message Builder API release(s)—depending on your implementation requirements.

Select a Message Builder Version:

 

Select one or more Message Builder API releases:

 

Optional Message Builder components:

Terminology Database Resolver
Message Builder Example

Message Builder pom.xml file:

 

Message Builder for .NET

System Requirements

  • .Net Framework 3.5 or higher

Download

Message Builder v2.1 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder:

  1. Download Message Builder .NET Core 2.1.0 setup
  2. Unzip and pull out the dll files that you need:
     \ → root location of required Message Builder core assemblies (Mandatory - required all)
     \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
  3. Copy them to your .NET project 
  4. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

Message Builder v1.5.8.1 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder:

  1. Download Message Builder .NET Core 1.5.8.1 setup
  2. Unzip and pull out the dll files that you need:
     \ → root location of required Message Builder core assemblies (Mandatory - required all)
     \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
  3. Copy them to your .NET project 
  4. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

Message Builder v1.4.6 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder, you will need

  1. Download Message Builder .NET Core 1.4.6 setup
  2. Unzip and run SetupCore.msi file
  3. Choose a installation location <install dir>.  The setup execution should place the following directories in <install dir>:
     \lib\ → location of required Message Builder core assemblies (Mandatory - required all)
      \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
     \src\ → location of all source code and project files required to load them into visual studios
     \debug\ → location of debug symbol files
  4. Pull out files the dll files from the \lib\ and \releases\ folders, and copy them to your .NET project 
  5. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

Localization of pan-Canadian Standards

Infoway Message ReMixer is a web-based application that allows for the localization of pan-Canadian Standards (pCS) messages to meet jurisdictional requirements, all while maintaining the integrity of the original, standard message.

msg remixerAccess Message ReMixer Now

 Implementation and Exchange

Jurisdictional ReMixes

Pan-Canadian Standards use Object Identifiers (OIDs) to distinguish between objects by assigning a numeric string that enables other systems to understand the unique information that is being shared between various systems.

Canada Health Infoway has an arrangement in place with HL7 International that allows Infoway to submit OIDs to HL7 International on behalf of Canadian Implementers free of charge. There is a $250 USD fee per OID request if done directly with HL7 International.

To submit an OID, download the registration form that corresponds to your OID request. Email the completed form to This email address is being protected from spambots. You need JavaScript enabled to view it.

Browse International and Canadian Content

SNOMED International's SNOMED CT browser allows users to browse and search the SNOMED CT International Edition to explore concepts and relationships. It also provides access to browse national extensions from SNOMED International member countries including the Canadian Edition of SNOMED CT in English and French.

snomed browser Browse SNOMED CT Now

 General Documentation

Browse, download and leverage the terminology used in Canada

Terminology Gateway is a web based solution framework that enables the distribution and sharing of terminology concepts, subsets and concept maps, making them available for web browsing, download or real time query.

terminology gatewayBrowse Terminology Gateway Now

RESTful web services used to browse terminology data

Terminology Service RESTful APIs enable automated exchange of clinical terminology content and resources. It allows developers to easily implement healthcare applications that programmatically consume codes and subsets without requiring in-depth expertise in the details of terminology.

terminology gateway APITerminology Service API

 

Apelon’s TermWorks is an easy-to-use data mapping solution that is provided by request (free of charge) to individuals who have Standards Access. It brings powerful terminology capabilities directly to the desktop. TermWorks combines Microsoft® Excel® spreadsheet software with web services-based terminology processing to give organizations comprehensive mapping capability to SNOMED CT and the Canadian Edition of SNOMED CT.

 

knowing Learn More

  • This email address is being protected from spambots. You need JavaScript enabled to view it.
  • SNOMED CT Education
  • Apelon User Guide
  • Infoway User Installation Guide
  • How does TermWorks Work?
  • TermWorks FAQs

Automated notifications of new content in Terminology Gateway

A WebHook is an HTTP callback. When new content is published in the Terminology Gateway, a publishing event will be POSTed to each registered WebHook, notifying their respective owners about the publication.

WebHook registration

Individual users can register for WebHook notifications by sending an email to: This email address is being protected from spambots. You need JavaScript enabled to view it. and specifying the WebHook endpoint. Upon registration, a unique api_id will be assigned to the WebHook. Each notification POSTed by the Terminology Gateway will contain the api_id, allowing the endpoint to verify that the notification was indeed issued by the Terminology Gateway. The api_id must be echoed back by the WebHook endpoint in the body of the notification response.

WebHook interface

The WebHook endpoint must serve HTTP requests conforming to the following interface:

HTTP Request

{
  "api_id": "cb570e5a2748f349f9119431db836b3a23fdb6571afee34c0432d87220f2431b",
  "base_url": "https://termapi.infoway-inforoute.ca/rest/v1/",
  "notification_time": "2017110711:07:00",
  "targets": [
    {
      "id": "2.16.840.1.113883.2.20.6.1",
      "name": "Canadian Clinical Drug Data Set (CCDD)",
      "type": "package",
      "version": "20171016",
      "effective_date": "20171016",
      "publication_time": "2017103015:20:23",
      "message": "Monthly CCDD update for October 2017"
    },
    {
      "id": "2.16.840.1.113883.2.20.3.443",
      "name": "PrescribeIT",
      "type": "package",
      "version": "LPR2",
      "effective_date": "20171103",
      "publication_time": "2017110309:37:22",
      "message": "PrescriptionMedicinalCode version reflecting the October 2017 CCDD update"
    }
  ]
}
				
  • api_id: as previously mentioned, each notification POST contains the api_id granted at registration.
  • base_url: the base URL for the native REST API endpoint of the originating system. This can be used to call back the Terminology Gateway via APIs in order to programmatically download updated content.
  • notification_time: the timestamp of the WebHook notification in yyyyMMddHH:mm:ss format.
  • targets: list of updated targets. Each entry in this array corresponds to a Terminology Gateway artifact (subset, codesystem, map, package) that was updated and is therefore subject to the notification. The target list will only include artifacts for which the user has registered to receive notifications. Users can register to receive notifications about content updates using the Terminology Gateway User Interface or by invoking the native REST APIs.

    Each of the notification targets contains the following fields:
    • id: the artifact id, typically an OID
    • name: the artifact name
    • type: the artifact type: subset, codesystem, package or map
    • version: the published version id
    • effective_date: the effective date associated to the artifact version, in yyyyMMdd format
    • publication_time: the publication time in yyyyMMddHH:mm:ss format
    • message: optional message describing the published artifact version

HTTP Response

HTTP Response code: 200 for success, any other response code will be interpreted as an error
Sample HTTP Response Body:

{
  "api_id": "cb570e5a2748f349f9119431db836b3a23fdb6571afee34c0432d87220f2431b",
  "result": "success",
  "message": "Successful processing of the WebHook notification"
}
  • api_id: as previously mentioned, each notification response must echo back the api_id granted at registration.
  • result: success if the web hook notification was successful, any other value will be interpreted as an error.
  • message: optional response message.


Error handling

When receiving an error as a result of a WebHook notification, the Terminology Gateway will retry the notification four times at 15 minutes intervals. If still unsuccessful after four notification attempts, the system will drop the notification and will notify the user by email that the WebHook couldn't be invoked.

Sample code

Demo code for a sample WebHook endpoint can be found here: 

https://github.com/CanadaHealthInfoway/tgateway-webhook

Web Conference

Please login to acquire access to the InfoCentral web conferencing.

Members

Derek Ritz
ecGroup Inc.
ONLINE
Contact
Andrea MacLean
Canada Health Infoway
OFFLINE
Admin
Linda Monico
Canada Health Infoway
OFFLINE
Admin
Sean Murray
Box
OFFLINE
Member
Beverly Knight
Canada Health Infoway
OFFLINE
Member
Deepti Razdan
cd-ed
OFFLINE
Member
Katie Williams
NSHA
OFFLINE
Member
Ron Parker
Parker Digital Health Consulting Inc.
OFFLINE
Member
Tracy Wutzke
CD-ED
OFFLINE
Member
Ovidiu Girlan
MOHLTC
OFFLINE
Member
Melody Scory
n/a
OFFLINE
Member
Melvy Sanchez
CDED
OFFLINE
Member
Deborah Schmidt
Classic Care Pharmacy
OFFLINE
Member
Lorraine Constable
Constable Consulting Inc
OFFLINE
Member
Shanil Keshwani
BI
OFFLINE
Member

How can consumers ensure their personal data is being protected? Our chief privacy officer offers some insights int… https://t.co/ZLTxlqVkEM

by Infoway

logo 1

Improving the quality of patient care through the effective sharing of clinical information among health care organizations, clinicians and their patients.



Login Register