La période de renouvellement de l’accès aux normes d’HL7 International pour 2018-2019 est commencée. Veuillez renouveler votre accès d’ici le 3 avril 2017. plus >

Partager :

Le contenu créé par les communautés et les groupes de travail est accessible dans la version originale seulement.

Interoperability Solutions
Discuss and learn about technical solutions used to accelerate interoperability.
Membres: 131
Personne-ressource: Ron Parker
Administration: Linda Monico
Type: Ouvert
Accès: Public
Discuss and learn about technical solutions used to accelerate interoperability.

À propos de nous


Jason Roberts, Technical Architect at Intelliware Development Inc


Messaging Solutions:

Message Builder

Message Remixer


HL7 Explorer

Terminology Solutions:


Common Terminology Services 2

Clinical Document Solutions:

Trifolia Template Editor


Open Health Model Drive Health Tools


Cheryl Ulmer s'est joint(e) à un groupe
Discuss and learn about technical solutions used to accelerate interoperability.


Événements à venir :
Aucun événement


A New Graduate Certificate Program in Health Terminology Standards at UVic 04/10/17
The School of Health Information Science at the University of Victoria is launching a new Graduate Certificate Program in Health Terminology Standards. This 1-year part-time blended delivery program is now accepting applications for its first cohort...
Monday March 20 - Deadline to Register for FHIR Fundamentals! 03/16/17
HL7® FHIR® Fundamentals 4-week Online Course (April 6 - May 4) If you're looking for an in-depth overview of HL7’s newest standard, Fast Healthcare Interoperability Resources (FHIR®), plan to join the April offering of the HL7 FHIR Fundamentals c...
Standards Selection Framework, Guidance and Registry - webinar slides 10/12/16
As a follow up to the September 29, 2016 webinar presenting the new Standards Selection Framework, the slide deck is now available in the Documents section of the community page. You can retrieve it from here: .... provides a great opportunity for ou...
Webinar: Infoway Terminology Gateway feature update and FHIR Terminology Service 10/11/16
Terminology Gateway continues to expand its value and utility for Canadian health technology implementers. Please come and join us to get an update on the new features and terminology content that have been made available by Canada Health Infoway’s C...
Webinar: Sierra Systems: Using innovative Infoway tools to Provide Proven Efficient Interoperability 09/29/16
Hi All, Sorry I couldn't attend the webinar due to schedule conflict. My colleague let me know that there were a couple of questions on Infoway tool MessageBuilder/HL7Explorer - what is the source for code generation, is that XML Schema or le...
Webinar: Sierra Systems: Using innovative Infoway tools to Provide Proven Efficient Interoperability 08/26/16
Please find event details ...
Using consumer-mediated personal health records to enable interoperability across the health sector-- cross-posting from the Public Health Surveillance forum 03/14/16
A very interesting article describing an alternate approach to sharing health records that puts the client at the centre: A neat immunization example...
Webinar: Ontario's Care Coordination Tool 11/23/15
This webinar on the Care Coordination Tool recently deployed in Ontario is hosted by Orion Health. The Care Coordination Tool (CCT) contains the functionality to support an enhanced approach to patient-centred care planning, by communicating quick...
Presentation from Orion Health: Information and care coordination in support of patient transitions across continuum of care 11/20/15
Title: Information and care coordination in support of patient transitions across continuum of care Presenters: Dr. Chris Hobson, Chief Medical Officer, Orion Health Susan Anderson, Managing Director, Orion Health Date: Tuesday, December 1...
Webinar: Infoway Terminology Gateway and APIs 08/31/15
For those of you who have missed the webinar in August, there is another session in September: Terminology Gateway and API webinar Thursday, September 17, 2015 12:00 pm | Eastern Daylight Time (New York, GMT-04:00) | 1 hr ... Meet...
Webinar: Infoway Terminology Gateway and APIs 08/05/15
Thank you to those who participated in the webinar. Please find the presentation here: .... For your reference, we have a demo video on YouTube to show you the key features of the Terminology Gateway: .... Try out the new tools here! ... To l...
Webinar: Infoway Terminology Gateway and APIs 07/29/15
Dear all, As you might have seen in InfoCentral News, Infoway has released the Beta version of Terminology Gateway and APIs. Please come and join us in a Webinar for a walk through of this new service, the coordinates of the Webinar can be foun...
Help shape this year's Partnership program: how should clinical interoperability be featured? 07/21/15
The date is set and the Infoway Partnership Conference 2015 is planned for November 24th-25th in Vancouver, BC. Share your suggestions in this ... or reply to this post to tell us your thoughts on how you’d like to see clinical interoperability feat...
Webinar: Process to handle discussions and proposed changes to pan-Canadian HL7 standard artifacts 06/29/15
The HL7 Community is hosting a short general webinar for all communities to go over a pilot process to handle discussions and proposed changes to pan-Canadian HL7 standards artifacts including OIDs. The webinar will be on July 8 at 12:15 – 12:45...
Clinical Interoperability Action Plan Available for Public Comment 05/25/15
The Clinical Interoperability Action Plan, endorsed by the Pan-Canadian Clinical Interoperability Steering Committee, has been made available for public comment. Your feedback is needed to ensure the Action Plan captures the right elements needed...



Suivi du temps



Cliquez sur « Gérer des documents » pour :

  • voir la liste complète des documents ou les dossiers regroupant les documents
  • téléverser un nouveau document

N. B. : Les membres des groupes ne sont actuellement pas avisés de l'ajout d'un nouveau document. Pour aviser d'autres membres, vous devez en afficher l'adresse électronique dans le forum. (La fonction d'avis de téléversement des nouveaux documents est en préparation.)

Gérer des documents Vous devez peut-être ouvrir une session et/ou être déjà membre du groupe pour accéder à ce contenu.


Ce groupe n'a pas de video.


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

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 Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.





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: Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. 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": "",
  "notification_time": "2017110711:07:00",
  "targets": [
      "id": "2.16.840.1.113883.",
      "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.",
      "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 Request

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:

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

  • Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.
  • SNOMED CT Education
  • Apelon User Guide
  • Infoway User Installation Guide
  • How does TermWorks Work?
  • TermWorks FAQs

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.

Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.

infoscribeSupporting the Standards Selection Framework, InfoScribe enables teams to collaboratively create, discuss, and publish digital health solutions from clinical requirements to specifications. Featuring templates, versioning, PDF export, inline commenting and HL7 Explorer integration, InfoScribe improves productivity and accelerates the development of healthcare solutions.

Des exigences cliniques aux spécifications

Le Cadre de sélection des normes permet à ses utilisateurs de planifier, de choisir et de documenter des solutions d’interopérabilité depuis l’étape du concept jusqu’à celle de l’implantation. À partir des exigences cliniques établies par les cliniciens jusqu’aux exigences administratives, en passant par les normes et les spécifications techniques, le Cadre se veut un guide complet sur toutes les étapes de la création de solutions d’interopérabilité.

Le Cadre donne aussi à la communauté d’InfoCentral une occasion d’échanger sur les projets d’implantation fructueux, le choix des normes effectué à un moment précis d’un projet et les spécifications qui en ont résulté. La publication des solutions à cet endroit permettra la mise sur pied d’un répertoire de référence canadien.

clinical requirements

Exigences Cliniques décrivent les besoins en information et en déroulement du travail du clinicien pour une situation clinique particulière et pour l’échange de données cliniques. À partir des principes de l’interopérabilité clinique, on utilise un ensemble d’exigences exprimées par les cliniciens pour mettre sur pied une solution d’interopérabilité bien conçue.

business requirements

Exigences Administratives sont établies d’après les exigences cliniques et procurent une image complète de la solution à mettre au point. Des cas d’utilisation, des règles administratives et des conseils sont aussi donnés en référence pour permettre une modélisation complète de la solution.

standards selection

Sélection des Normes désigne le processus établi pour guider les équipes dans les diverses étapes de la sélection de la terminologie et des normes de messagerie. À l’aide du sujet de la requête et des diverses considérations contenues dans les formulaires fournis, les équipes d’implantation peuvent évaluer les normes accessibles et déterminer le meilleur choix ponctuel. Le processus permet aussi à la communauté d’InfoCentral d’échanger sur les projets d’implantation fructueux, ce qui favorise la normalisation par la réutilisation.


Normes afont partie intégrante de la solution d’interopérabilité; elles touchent tant la terminologie, qui définit les données envoyées, que les structures de messagerie, qui définissent comment ces données sont envoyées. Le cadre fournit les critères d’accès aux normes internationales et canadiennes, ainsi que les critères d’examen en vue de faciliter l’implantation.


Spécifications procurent les détails de la solution à implanter. Ces détails comprennent : un examen des éléments de données utilisés, des échantillons des messages transférés, l’architecture du système et les spécifications de sécurité, dont l’autorisation et l’authentification.

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

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.


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

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


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

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


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.


Learn about what HL7 Explorer can do for you with this brief online presentation.

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
CA MR 02.05.01
CA MR 02.05
CA MR 02.04.03
CA CeRx 4.4.2
CA CeRx 4.4.1 
CA CeRx 4.4
BC V02R04
NS CeRx 4.3
NS R02.04.03
AB MR2007
AB R02.04.03
AB R02.04.00 SHR
AB R02.04.03 Imm

Solution for API integration

Infoway Message Builder allows developers to focus on their business problem by providing APIs that foster quick and easy creation, population and access to HL7v3 requests and responses and CDA documents.

 Implementation and Exchange

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.


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.

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


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


Conférence Web

Veuillez ouvrir une session pour accéder à la conférence web d'InfoCentral.


Ron Parker
Canada Health Infoway
Linda Monico
Canada Health Infoway
Cheryl Ulmer
Fraser Health Authority
Kathy Giannangelo
Jignesh Rathod
Bonnie Chandler
Holland College
Tue Hoang
Rejean Fortin
Biron Health Group
Prasanth Joseph
Niagara Health
naomi beaulieu
Ryan Doherty
Elizabeth Barclay
Circa Information Corporation
Abdullah Khan
Daniel Pan
Ehealth ON
No tweets found.

logo inv fr

La santé numérique à votre service


Transformer les soins de santé au Canada grâce aux technologies de l'information sur la santé.

Login Register