Voter pour l’agent de liaison canadien d'Integrating the Healthcare Enterprise IHE, août 13 à 24, 2018 plus >

Partager :

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

Integrating the Healthcare Enterprise (IHE)
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Membres: 134
Personne-ressource: Andrea MacLean
Administration: Linda Monico
Type: Ouvert
Accès: Public
Health care and health information professionals collaborating to improve information sharing between health care technology systems.

À propos de nous

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

TBD: Election in progress

KEY RESOURCES

IHE Resources

IHE CANADA LIAISON ELECTION, August 13 - 24, 2018

You must be logged in and a member of the IHE community to vote. Read more details on the election process.

Activité

Ilana Sirkovich s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Yaron Derman s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Andrea MacLean a lancé une nouvelle discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Dear IHE community members. As we prepare for the new leadership under the soon to be elected IHE Canada Liaison, I wanted to take this opportunity to clean up the IHE documents section of the community, so that we can start off on a “fresh page”. There were only 4 documents: 2 from 2015, and one each from 2016 and 2017. They can all be found in the new archive folder: https://infocentral.infoway-inforoute.ca/en/resources/docs/ihe/archive-ihe I just wanted to make everyone aware. Thank you. Regards, Andrea
Andrea MacLean a lancé une nouvelle discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Dear IHE community members. As we prepare for the new leadership under the soon to be elected IHE Canada Liaison, I wanted to take this opportunity to clean up the forum a bit, and provide a "fresh page" so-to-speak. There is now an archive folder (https://infocentral.infoway-inforoute.ca/en/forum/ihe-archive) added to the IHE community forum. Over the next little while, I am going to move older postings about webinars or meetings that are now expired to this archive folder. Nothing will be deleted. I just wanted to make everyone aware. Thank you. Regards, Andrea
Patti Foran s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Rod Thurber s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Lloyd Mckenzie s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.

Événements



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

Forum

IHE Documents Folder Clean-up 08/14/18
Dear IHE community members. As we prepare for the new leadership under the soon to be elected IHE Canada Liaison, I wanted to take this opportunity to clean up the IHE documents section of the community, so that we can start off on a “fresh page”....
IHE Forum Posting Clean-up 08/14/18
Dear IHE community members. As we prepare for the new leadership under the soon to be elected IHE Canada Liaison, I wanted to take this opportunity to clean up the forum a bit, and provide a "fresh page" so-to-speak. There is now an archive fol...
IHE Canada Liaison Election Announcement 08/13/18
The poll to vote for the IHE Canadian Liaison role is now open. To vote, you must be logged into InfoCentral and be a member of the IHE Community. There is no charge to obtain an InfoCentral account or join the IHE community. All are welcome....
IHE Canada Liaison Election Announcement 08/07/18
The nominations for the IHE Canada Liaison role are now closed. IHE Canada is delighted to have candidates of the caliber of Michael and Derek running for this position. We are just in the process of creating the election poll. Voting will...
IHE Canada Liaison Election Announcement 08/03/18
The nomination period for the IHE Canada Liaison role closes today, so if you were thinking about “throwing your name into the hat” please do not delay. For ease of reference, the election timelines are as follows: • Nominations: July 23, 2018 –...
Derek Ritz nomination for position of IHE Canada Liaison 08/01/18
It's time for something different... My name is Derek Ritz. Please accept my nomination for the position of IHE Canada Liaison. I need to be upfront with IHE community members who might vote for me -- please make no mistake: my intention is to be...
IHE Canada Liaison Election Announcement 07/27/18
Just a gentle reminder that nominations for the IHE Canada Liaison role close on Friday August 3, 2018, so there is still time to “throw your name into the hat”. The description of the role can be found here: https://infocentral.infoway-inforoute....
IHE Canada Liaison Election Announcement 07/23/18
Please accept my nomination for the position of IHE Canada Liaison. Below is a brief bio that outlines my IHE and IHE Canada experience. Michael H. Nusbaum, BASc, MHSA, FHIMSS I am honored to submit my name for nomination for the position IH...
IHE Canada Liaison Election Announcement 07/19/18
Canada Health Infoway is proud to support IHE and to be the home of IHE Canada. Infoway is delighted to host an election for the IHE Canada Liaison position representing the IHE Canada Community internationally for the term of two years. A do...
Oct 26th Webex - presentation & recording: Bundling Standards for Interoperability – ISO’s new Reference Standards Portfolio for Clinical Imaging 10/27/17
Hi everyone, Thank you so much to those of you who were able to participate in yesterday’s webex on Bundling Standards for Interoperability – ISO’s new Reference Standards Portfolio for Clinical Imaging. Please not that I have posted the presentat...
IHE Blog reflects on FHIR 08/30/17
A number of very useful facts on IHE and FHIR collected in ... blog. Useful reference material.
IHE IT Infrastructure Technical Framework Supplements Published 07/21/17
IHE IT Infrastructure Technical Framework Supplements Published The IHE IT Infrastructure Technical Committee has published the following supplements for Trial Implementation as of July 21, 2017: New Supplement • Remove Metadata and Document (RM...
IHE Radiology Technical Framework Supplements Published for Trial Implementation 07/14/17
The IHE Radiology Technical Committee has published the following supplements to the IHE Radiology Technical Framework for trial implementation as of July 14, 2017: • Imaging Object Change Management Extension (IOCM Extension) - Rev. 1.6 • Manage...
ITAC Health releases position paper calling for IHE integration profiles 12/20/16
Canadians following IHE will be interested in the recent ITAC Health position paper on interoperability standards. Read it here: .... Please post your comments to this forum...
Pitch for IHE International Membership 09/28/15
to: members of the IHE Community in Canada from: Lynne Zucker (in my role as a board member of IHE International) As I posted a few months ago, IHE International is asking organizations to pay modest membership fees to help to support the great w...

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.

Archive ( 2 Documents )

Vidéo

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

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

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

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

 

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.

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

 

Conférence Web

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

Membres

Andrea MacLean
Canada Health Infoway
Déconnecté(e)
Personne-ressource
Linda Monico
Canada Health Infoway
Déconnecté(e)
Admin
Ilana Sirkovich
Xperterra
Déconnecté(e)
Membre
Yaron Derman
eHealth Ontario
Déconnecté(e)
Membre
Patti Foran
Central Health
Déconnecté(e)
Membre
Rod Thurber
Gevity Consulting Inc.
Déconnecté(e)
Membre
Lloyd Mckenzie
LM&A Consulting Ltd.
Déconnecté(e)
Membre
Lisa Hayes
Canada Health Infoway
Déconnecté(e)
Membre
Linda Hamilton
Health Informatics
Déconnecté(e)
Membre
Bruce Forde
Cambian Business Services
Déconnecté(e)
Membre
Martin Desmarais
s.o.
Déconnecté(e)
Membre
Nitin Gupta
Manitoba eHealth
Déconnecté(e)
Membre
Barbara Podtepa
n/a
Déconnecté(e)
Membre
Jason Nagels
HDIRS
Déconnecté(e)
Membre
Kayla Self
Center for Distance Education
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