Partager :

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

Health Level Seven International (HL7)
Keep up to date and get involved in the latest from HL7 International, the HL7 Canada Constituency, the HL7 Canada Council, and the pan-Canadian messaging standards.
Membres: 213
Personne-ressource: Jean Duteau
Administration: Linda Monico, Andrea MacLean
Type: Ouvert
Accès: Public
Keep up to date and get involved in the latest from HL7 International, the HL7 Canada Constituency, the HL7 Canada Council, and the pan-Canadian messaging standards.

À propos de nous

What is the HL7 Community?

The HL7 Community is a place to share lessons learned and learn about new and existing HL7 Standards implemented in Canada, such a version 2, version 3, CDA and FHIR.

This community is where requests to make changes to any of the pan-Canadian messages occur and where implementers come for OID requests in Canada or find Canadian OIDs in the HL7 OID Registry.

Canada is proud to have a thriving HL7 Canada Constituency and actively participates in HL7 Ballots.

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

If you have an idea for

LEADER

Melva Peters - Chair, HL7 Canada

Industry Leader, Medication Management, Gevity Consulting

FACILITATOR

Jean Duteau - Facilitator, pan-Canadian Standards discussions and RFCs

Canada Health Infoway, HL7 Subject Matter Expert

KEY RESOURCES

HL7 Artifacts (Standards, Release notes, Education etc)

Activité

Attila Farkas a lancé une nouvelle discussion dans le groupe Health Level Seven International (HL7)
Don't miss the upcoming meeting discussing OAuth2 matters as they relate to SMART on FHIR. The meeting is on Friday, at 2pm EDT details available here: ...
Ken Sinn a répondu au cours d'une discussion dans le groupe Health Level Seven International (HL7)
... Ballot Comments from eHealth Ontario for FHIR R4, for the 2018JAN Ballot. eHealth Ontario will be on the Ballot Review Call on Wednesday.
Andrea MacLean a répondu au cours d'une discussion dans le groupe Health Level Seven International (HL7)
Added. Glad you have you on board Rita.
Rita Pyle a répondu au cours d'une discussion dans le groupe Health Level Seven International (HL7)
Can you add me to your list too Please? Thank you
Andrea MacLean a répondu au cours d'une discussion dans le groupe Health Level Seven International (HL7)
Added Sisira. Thank you. I will be compiling a list up until the deadline and then convening a call to discuss so that we can determine the best way to proceed for all concerned. It is great to see such interest. I also have interest to learn more from some implementers in BC and ON that contacted me by email, so it should be a great discussion.
Sisira De Sliva a répondu au cours d'une discussion dans le groupe Health Level Seven International (HL7)
Hi Andrea, I am interested in this pathology work. Could you please add me to your list? Thanks, Sisira. Newfoundland & Labrador Centre for Health Information
Andrea MacLean a répondu au cours d'une discussion dans le groupe Health Level Seven International (HL7)
Andrea, great news. I have added you to my growing list. :) Stay tuned. Andrea

Événements



Événements à venir :
Mar Fév 06 @12:00PM - 01:00PM
HL7 Community Call
Mar Mar 06 @12:00PM - 01:00PM
HL7 Community Call

Forum

Upcoming FHIR Implementer's WG meeting - SMART on FHIR - OAuth2 and OpenID 01/18/18
Don't miss the upcoming meeting discussing OAuth2 matters as they relate to SMART on FHIR. The meeting is on Friday, at 2pm EDT details available here: ...
HL7 (Health Level Seven) International January 2018 Ballot is now open for comments 01/12/18
... Ballot Comments from eHealth Ontario for FHIR R4, for the 2018JAN Ballot. eHealth Ontario will be on the Ballot Review Call on Wednesday.
Cancer Pathology Reporting: Standards Selection 01/11/18
Added. Glad you have you on board Rita.
Cancer Pathology Reporting: Standards Selection 01/11/18
Can you add me to your list too Please? Thank you
Cancer Pathology Reporting: Standards Selection 01/11/18
Added Sisira. Thank you. I will be compiling a list up until the deadline and then convening a call to discuss so that we can determine the best way to proceed for all concerned. It is great to see such interest. I also have interest to lea...
Cancer Pathology Reporting: Standards Selection 01/11/18
Hi Andrea, I am interested in this pathology work. Could you please add me to your list? Thanks, Sisira. Newfoundland & Labrador Centre for Health Information
Cancer Pathology Reporting: Standards Selection 01/11/18
Andrea, great news. I have added you to my growing list. :) Stay tuned. Andrea
Cancer Pathology Reporting: Standards Selection 01/11/18
Hi Andrea, I am a EHR Informatics Consultant and I have done extensive work with LOINC standardization, I am also very familiar with SNOMED CT and I have a background in Anatomic Pathology so I would be very interested in participating. Thanks,...
Cancer Pathology Reporting: Standards Selection 01/10/18
Absolutely. Stay tuned.
Cancer Pathology Reporting: Standards Selection 01/10/18
HI Andrea Could you please also add me to your list? I have done work on both LOINC and SNOMED CT mapping and would be very interested in participating. Thanks! Diane Gutiw
Cancer Pathology Reporting: Standards Selection 01/10/18
Daniela, this is great news. There is an active work going on right now. I am just in the process of confirming the exact work group. Stay tuned. Andrea
Cancer Pathology Reporting: Standards Selection 01/10/18
Hi Andrea, I am a Clinical Terminologist primarily using SNOMED CT for coding, and I am interested in this pathology work if there is a working group in the future. Thank you, Daniela
Cancer Pathology Reporting: Standards Selection 01/10/18
As discussed at the January 9 HL7 community meeting: Infoway has received a request to support the SNOMED CT encoding of the ... in support of .... The CAP checklists and protocols represent the clinical content standard for cancer pathology repo...
HL7 (Health Level Seven) International January 2018 Ballot is now open for comments 01/09/18
As per the January 9th HL7 Community call, here are the links for getting to the HL7 Ballot site: If you are NOT a member of HL7 International, then you can only get there via the following links: https://infocentral.infoway-inforoute.ca/en/sta...
HL7 Canada Ballot Review Call - January 17, 2017 1pm Eastern Standard Time 01/09/18
I have just updated the corresponding event, but here are the details for the call on January 17th where we will be discussing all of the comments received on the current ongoing HL7 Ballot. HL7 January 2018 Ballot Review Wednesday, January 17, 2...

Tâches


Tâches


Suivi du temps


Gantt

Documents

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.

Implementation ( 0 Document )

Documents for implementers of HL7 v3. For context, see HL7 standards page.

Vidéo

Ce groupe n'a pas de video.

Solutions

  • 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
  • HAPI FHIR
  • 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 (normally $100 USD fee per OID request).

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": "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 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: 

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

Apelon’s TermWorks is an easy-to-use data mapping solution which is provided by request for free 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.

 Education

  • Introduction to SNOMED CT (English)
  • Introduction to SNOMED CT (French)
  • Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.

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.

standards

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.

specifications

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.

HAPI v2

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 IHTSDO 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.

Overview
 

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 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

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.

HAPI FHIR

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
 

Submit or follow requests to SNOMED CT

pCLOCD/LOINC
 

Submit or follow requests to pCLOCD/LOINC

pan-Canadian Subsets
 

Submit or follow requests to pan-Canadian Subsets

 

Conférence Web

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

Membres

Jean Duteau
Duteau Design Inc
Déconnecté(e)
Personne-ressource
Linda Monico
Canada Health Infoway
Déconnecté(e)
Admin
Andrea MacLean
Canada Health Infoway
Déconnecté(e)
Admin
Joel Francis
Canada Health Infoway
Déconnecté(e)
Membre
Debbie Onos
Alberta Health Services
Déconnecté(e)
Membre
febisola Ayodeji
Center for distance education
Déconnecté(e)
Membre
RONKE OSATOHANMWEN
NA
Déconnecté(e)
Membre
Tue Hoang
Caredove
Déconnecté(e)
Membre
Lydia Akiru
Centre for distance education
Déconnecté(e)
Membre
naomi beaulieu
cd-ed
Déconnecté(e)
Membre
Iris Batalli
N/A
Déconnecté(e)
Membre
Kelsey Li
Blue Skies Pharmacy
Déconnecté(e)
Membre
Cindy Jiang
eHealth Ontario
Déconnecté(e)
Membre
Danna Dobson
Ontario Ministry of Health
Déconnecté(e)
Membre
Sari Schapira
Canada Health Infoway
Déconnecté(e)
Membre
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