Partager :

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

SNOMED CT
Sharing information, lessons learned and discussion between SNOMED International, Infoway's Canadian stakeholders and implementers.
Membres: 174
Personne-ressource: Linda Parisien
Administration: Linda Monico, Andrea MacLean
Type: Ouvert
Accès: Public
Sharing information, lessons learned and discussion between SNOMED International, Infoway's Canadian stakeholders and implementers.

À propos de nous

What is the SNOMED CT Community?

The SNOMED CT Community is a place to share lessons learned and learn about new and existing implementations and updates to both the International version and Canadian English and French Extensions of SNOMED CT. Canada Health Infoway is the National Release Centre (NRC) for SNOMED CT in Canada.

Whether you are looking to add new content to SNOMED CT, consult editorial guidelines, browse the content or want to map your local terminology to SNOMED CT, this is the place to be.

Implementations of SNOMED CT are growing by leaps and bounds in Canada and so is the wealth of International and Canadian knowledge to share.

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

LEADERS

Sharilyn Kmech, Director, Provincial Terminology Services, Health Information Management, Alberta Health Services

Shelley Lipon, Customer Relations Lead Americas, SNOMED International

KEY RESOURCES

SNOMED CT Artifacts (Standard, Release Notes, Maintenance, Education, etc.)

Activité

Chris Heale s'est joint(e) à un groupe
Logo
Sharing information, lessons learned and discussion between SNOMED International, Infoway's Canadian stakeholders and implementers.
Linda Parisien a répondu au cours d'une discussion dans le groupe SNOMED CT
Bonjour Dr Beauchemin, Nous espérons que ces sessions seront utililes et pourront permettre une meilleur interaction entre les participants. Préparez vos questions, nous allons y répondre!
Pierre Beauchemin a répondu au cours d'une discussion dans le groupe SNOMED CT
Bonjour Linda, excellente idée de présenter ce type de session. Pierre Beauchemin md
Linda Parisien a lancé une nouvelle discussion dans le groupe SNOMED CT
I am very happy to announce that new Hands-on sessions have been scheduled and are offered to different audiences for increasing the knowledge of the SNOMED CT terminology and related tools. One session per month will be dedicated to a new topic. If you want to learn more about the resources that are available to support you and your team in your Terminology Projects, you are welcome to attend these sessions, where you will have the opportunity to share your challenges and screen so we can solve your issues! Refer to this document for the schedule: ... Note that the sessions are also in the InfoCentral Events Calendar.
Linda Parisien a lancé une nouvelle discussion dans le groupe SNOMED CT
Thank you to Alan Stein for the great presentation, and to all participants in yesterday Community monthly Meeting. . The presentation can be found here: .... If you have questions, you are encouraged to post them on the Forum. Thank you!
Andrea MacLean a lancé une nouvelle discussion dans le groupe SNOMED CT
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 reporting in Canada. Canada is now working cooperatively to adopt standardized encoded data elements with ...to align these data elements with the next update to the WHO Blue books. In Canada, we have historically used ... to encode the questions in checklists such as these and SNOMED CT to encode the answers. The Regenstrief Institute has recently made great strides in terms of creating LOINC codes for the “questions” in this clinical content standard. (LOINC codes ... and... are two great examples). There is also work being led in the USA with various pathology organizations, SNOMED International and other SNOMED CT member countries to SNOMED CT encode these checklists and protocols. The encoding of Pathology reports to this level is a relatively new endeavour in Canada and Infoway is seeking interest in this work. We are also interested to understand if the current model (LOINC for the question and SNOMED CT for the answer) is relevant for the discrete reporting of cancer pathology. We would like to hear from you before March 1, 2018 regarding potential interest in the work and the preferred model (using LOINC and SNOMED CT) for the coding. Thank you. Regards, Andrea
Linda Parisien a lancé une nouvelle discussion dans le groupe SNOMED CT
On behalf of SNOMED International Dear SNOMED CT Users, The SNOMED International Editorial Advisory Group is undertaking a review of the permitted modifications in the SNOMED CT national extensions. The draft policy "Allowance of Extension to Modify Core Content v.2.1" has been developed and reviewed by the representatives of SNOMED International member countries. We are now seeking input from SNOMED CT users and implementers on the suitability of proposed policy for national and international SNOMED CT implementation. We would like to invite your feedback and comments on the draft policy for "Allowance of Extension to Modify Core Content v.2.1" (link enclosed below) before 30.March 2018. https://confluence.ihtsdotools.org/pages/viewpage.action?pageId=50594085 Please note a suggested approach to submitting your review comments is by commenting on the Google sheet provided at: https://docs.google.com/spreadsheets/d/1ngJky4ZLKIh0cDusbcB3IjGY5RC-Gc5vrCL7LLPJgds/edit?usp=sharing Thank you! Yours Sincerely, Jim Case Head of Terminology SNOMED International

Événements

Forum

Coming Hands-on Sessions 01/18/18
Bonjour Dr Beauchemin, Nous espérons que ces sessions seront utililes et pourront permettre une meilleur interaction entre les participants. Préparez vos questions, nous allons y répondre!
Coming Hands-on Sessions 01/18/18
Bonjour Linda, excellente idée de présenter ce type de session. Pierre Beauchemin md
Coming Hands-on Sessions 01/17/18
I am very happy to announce that new Hands-on sessions have been scheduled and are offered to different audiences for increasing the knowledge of the SNOMED CT terminology and related tools. One session per month will be dedicated to a new topic....
January Monthly call 01/17/18
Thank you to Alan Stein for the great presentation, and to all participants in yesterday Community monthly Meeting. . The presentation can be found here: .... If you have questions, you are encouraged to post them on the Forum. Thank you!
Cancer Pathology Reporting: Standards Selection 01/10/18
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 reporting in Canada. Canada is now working cooperatively to...
Invitation to review the policy for Allowance of Extension to Modify Core Content 01/05/18
On behalf of SNOMED International Dear SNOMED CT Users, The SNOMED International Editorial Advisory Group is undertaking a review of the permitted modifications in the SNOMED CT national extensions. The draft policy "Allowance of Extension to...
Thank You Sharilyn!! 01/04/18
Recently, Sharilyn Kmech has communicated her decision to step down as our Community Co-Leader due to competing demands on her time. I would like to thank Sharilyn for all her volunteer efforts to lead this community from its inception! Her support t...
SNOMED CT for Data Analysts Pilot is now available for feedback 01/02/18
Hi Monica, Yes sure SNOMED CT is of value for most healthcare related domains. In the drug space we have developed SNOMED CT immunization content and subsets for Canadian specific purposes. The drugs that are in scope for e-Prescribing are encoded u...
Feedback requested on Substance use, misuse, abuse 01/01/18
Please tell me how I can help! Thanks.
SNOMED CT for Data Analysts Pilot is now available for feedback 01/01/18
Dear Madam: I'm a pharmacist and nuts over SNOMED CT. Are there any benefits to learn SNOMED ? Most pharmacist have not got a clue as to what SNOMED is. Thank You
SNOMED CT Description Logic Enhancements - Consultation 12/21/17
Proposal to Enhance SNOMED CT's Logic Capabilities SNOMED International is proposing enhancements to SNOMED CT's logic features, both to enable improvements to the quality and analytics capabilities of SNOMED CT and to increase productivity in co...
Mark you calendar for the December Community meeting! 12/20/17
Hi Mukesh, No worries... if you have any questions or comments you are welcome to post them on the Forum. Linda
Mark you calendar for the December Community meeting! 12/19/17
Sorry I missed today's conference call as there was power outage in our area due to snow storm. Wish you a happy holidays as well. Connect in new year. Thank you
Mark you calendar for the December Community meeting! 12/19/17
Many thanks to our guest speaker Jon Zammit for providing us with a great update on SNOMED International education and information material as well as on the eLearning courses. The presentation can be found .... Thank you all for your participatio...
Topic added to the DI Community Dec 15 meeting Agenda: planned changes to the DI Editorial Guidelines for the SNOMED CT CA Edition 12/15/17
HI everyone, Please find ...the presentation I did today on the call. Thank you!

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 ( 14 Documents )

TermWorks ( 6 Documents )

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

Linda Parisien
Canada Health Infoway
Déconnecté(e)
Personne-ressource
Linda Monico
Canada Health Infoway
Déconnecté(e)
Admin
Andrea MacLean
Canada Health Infoway
Déconnecté(e)
Admin
Chris Heale
Applied Informatics for Health
Déconnecté(e)
Membre
Rachel Guthrie
Enthrall Inc
Déconnecté(e)
Membre
Alana Lane
Canadian Institute for Health Information
Déconnecté(e)
Membre
Sharon Baker
Canadian Institute for Health Information
Déconnecté(e)
Membre
Mukesh Kashyap
BC Ministry of Health
Déconnecté(e)
Membre
Debbie Onos
Alberta Health Services
Déconnecté(e)
Membre
Jean Manuel De Bane
Softway Medical
Déconnecté(e)
Membre
David Rocha
Rocha Medical Clinic
Déconnecté(e)
Membre
Kelly Kuru
SNOMED International
Déconnecté(e)
Membre
Ashraf Iqbal
Nova Scotia Health Authority
Déconnecté(e)
Membre
Tue Hoang
Caredove
Déconnecté(e)
Membre
Sanford Kong
BC Renal Agency - PROMIS
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