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

Shelley Lipon, Customer Relations Lead Americas, SNOMED International

KEY RESOURCES

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

Activité

Dat Nguyen 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 lancé une nouvelle discussion dans le groupe SNOMED CT
SNOMED International has released the January 2018 General Practitioner/Family Practitioner (GP/FP) SNOMED CT® Reference Sets and SNOMED CT® to ICPC-2 Map package. The Production release of the GP/FP SNOMED CT® Reference Sets and SNOMED CT® to ICPC-2 Map package is dependent upon, and should therefore be consumed in conjunction with the January 2018 SNOMED CT® International Edition. All files distributed are available from the “January 2018 v1.0” version in the “GP/FP SNOMED CT Refset and SNOMED CT to ICPC2 Map package. The GP/FP SNOMED CT® Reference Sets and SNOMED CT® to ICPC-2 Map package contains SNOMED CT files in Release Format 2 (RF2) only, distributed in a zipped file archive: SnomedCT_GPFPICPC2_PRODUCTION_20180416T120000Z.zip. The Release Notes have been separated from the release package: • doc_SnomedCT-GPFP-Production-ReleaseNotes_Current-en-US_INT_20180131.pdf • doc_SnomedCT-ICPC2-Production-ReleaseNotes_Current-en-US_INT_20180131.pdf The Release Notes can also be accessed online from the following pages: • ... • ... If you are interested in any of the above files, please sent an email to the Standards Helpdesk at: Standards@infoway-inforoute.ca
Kelly Kuru a lancé une nouvelle discussion dans le groupe SNOMED CT
Hello all, Due to overwhelming request from those among the SNOMED CT Community of Practice, we have issued an extension to the SNOMED CT Expo Call for Abstracts period to this Friday April 20th. If you're thinking about submitting an abstract, there's still time to showcase your implementation experiences in Vancouver this fall. Submit your abstract at: http://www.snomedexpo.org/call-for-abstracts Looking forward to welcoming you to Vancouver, - Kelly Kuru
Gennine Roberts s'est joint(e) à un groupe
Logo
Sharing information, lessons learned and discussion between SNOMED International, Infoway's Canadian stakeholders and implementers.
Marie-alexandra Lambot a répondu au cours d'une discussion dans le groupe SNOMED CT
I've a outsider's view but here is my feeling on your topic. I would not use "group" as this projects a mind-image of a small number of persons, maybe a closed circle, something that does not project openness. You need to apply to be member of a group, to get accepted by the group. Community has a more "loose connotation". It brings up in the mind communautary life, sharing, something open and more welcoming, a big to huge number of persons also, like a web forum. As to the choice between proposition 1 and 3, I'd say the first is easier to remember and the first thing you read is what it's about, the health terminology, while in the other, you're putting forward the community aspect before the terminology aspect. Again it's a question of mind image, which certain persons will feel and other not, but Community for X, brings as first image the community and then, makes the purpose of the community secondary to the fact that you are a community. At least to my non-native english speaking mind. I would not make e-something jokes because you'll be dealing in terminologies. Meaning your goal is to make people used correct words. Starting this by misspelling terminlogy is somewhat sending a first contact message at odds with your final goal. Plus it'll make you more difficult to find on google or such because only those already knowing the joke will find you. The rest will type "terminology community" and find nothing. What you want is, I suppose, that many poeple can stumble across the community pages while browsing terminology related topics and form that point wish to participate in your community. Hope this helps. Best regards
Linda Parisien a lancé une nouvelle discussion dans le groupe SNOMED CT
There is a proposal at the Content Manager Advisory Group (CMAG) to inactivate concepts with the pattern of: Under care of For example the below concepts and their subtypes: Under care of team (finding) Under care of person (finding) Under care of service (finding) The meaning of the term used to represent the clinician or service may vary between countries. Please let me know if you are using these concepts, so we can provide feedback to SNOMED International CMAG. Thank you!
Linda Parisien a lancé une nouvelle discussion dans le groupe SNOMED CT
SNOMED International has released the SNOMED CT® General Dentistry Diagnostic refset package. All files distributed are available from the “January 2018 v1.0” version in the “SNOMED CT General Dentistry Diagnostic refset package - SNOMED International” project. The SNOMED CT® General Dentistry Diagnostic refset package contains SNOMED CT files in Release Format 2 (RF2) only, distributed in a zipped file archive: SnomedCT_GeneralDentistry_PRODUCTION_20180331T120000Z.zip The Release Notes have been separated from the Release package: doc_SnomedCT-GeneralDentistry-ReleaseNotes_Current_en-US_INT_20180131.pdf ... If you are interested in any of the above files, please sent an email to the Standards Helpdesk at: Standards@infoway-inforoute.ca

Événements



Événements à venir :
Lun Avr 30 @ 8:00AM -
Subset Maintenance Annual Release
Lun Avr 30 @ 8:00AM -
Canadian Edition Release of SNOMED CT
Mer Mai 02 @ 1:00PM - 02:00PM
Subset Maintenance Annual Release Webinar

Forum

January 2018 GP/FP SNOMED CT Reference Sets and SNOMED CT to ICPC-2 Map Production release 04/18/18
SNOMED International has released the January 2018 General Practitioner/Family Practitioner (GP/FP) SNOMED CT® Reference Sets and SNOMED CT® to ICPC-2 Map package. The Production release of the GP/FP SNOMED CT® Reference Sets and SNOMED CT® to ICP...
SNOMED CT Expo 2018 in Vancouver - Call for Abstracts extended to this Friday April 20th 04/16/18
Hello all, Due to overwhelming request from those among the SNOMED CT Community of Practice, we have issued an extension to the SNOMED CT Expo Call for Abstracts period to this Friday April 20th. If you're thinking about submitting an abstrac...
Request for name ideas: New terminology community 04/11/18
I've a outsider's view but here is my feeling on your topic. I would not use "group" as this projects a mind-image of a small number of persons, maybe a closed circle, something that does not project openness. You need to apply to be member of a grou...
Are you using «Under care of » SNOMED CT concepts? 04/10/18
There is a proposal at the Content Manager Advisory Group (CMAG) to inactivate concepts with the pattern of: Under care of For example the below concepts and their subtypes: Under care of team (finding) Under care of person (finding)...
January 2018 SNOMED CT General Dentistry Diagnostic refset package Production release 04/10/18
SNOMED International has released the SNOMED CT® General Dentistry Diagnostic refset package. All files distributed are available from the “January 2018 v1.0” version in the “SNOMED CT General Dentistry Diagnostic refset package - SNOMED Internat...
Reminder: Introduction to SNOMED CT Webinar on Wednesday, April 18, 2018 04/10/18
We are pleased to invite you to this revamped «Introduction to SNOMED CT» session. This is the third of the Standards webinar series targeting a beginner's audience. It has been designed for anyone interested in becoming acquainted with SNOMED CT...
Canceled: SNOMED CT Community April Monthly Meeting 04/10/18
Please note that the April 17 monthly meeting is canceled. Thank you! Linda
Request for name ideas: New terminology community 04/10/18
Hi all, great discussion on names so far. I have a simpler view of health and healthcare. To me health is the state of wellness, being free from illness or injuries, whereas healthcare is the maintenance and improvement of health through provision of...
Request for name ideas: New terminology community 04/10/18
Hi, I like what you have proposed Harsh, since it seems to provide recognized boundaries to what we are all trying to achieve in enhancing healthcare outcomes. I would have liked to add a little ludic piece to this new name by enforcing the fact...
Request for name ideas: New terminology community 04/10/18
Hello Andrea, I believe a slight change to the proposed name will make a huge impact on stakeholders. "Healthcare Terminologies Community" Reason for "Healthcare": There is huge difference between Health and Healthcare. Our focus (within H...
Request for name ideas: New terminology community 04/10/18
Great suggestions, Francis. To take a slight twist on your suggestion, adding "Health Terminologies Community". This broadens inclusion covering multiple terminologies. Also, fine with Health Terminology Community, if that is the preferred. Sue Schn...
Request for name ideas: New terminology community 04/10/18
Health Terminology Community seems a good fit. Thanks Alison Morra.
Request for name ideas: New terminology community 04/10/18
On April 3, a number of members of the InfoCentral community came forward to discuss the idea of amalgamating the pCLOCD and SNOMED CT communities along with all HL7 code system discussions into one central location. This discussion was in response...
Terminology Community Discussion: Should InfoCentral support one terminology community to better reflect implementation realities and needs? 04/05/18
Thank you everyone who participated in the One Terminology Community discussion on April 3, 2018. I have posted the presentation here: https://infocentral.infoway-inforoute.ca/en/resources/docs/snomedct/meetings/2521-discussion-deck-moving-all-ter...
Webinar: Connected Health Information in Canada: A Benefits Evaluation Study 03/29/18
With investment from Canada Health Infoway (Infoway) and its partners in electronic health records, clinicians are beginning to have better access to patient information across the health care system continuum. Join Infoway and Gartner to discuss...

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.

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

!-

 Education

 Maintenance

-->

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

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

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
Dat Nguyen
OntarioMD
Déconnecté(e)
Membre
Gennine Roberts
eHealth Saskatchewan
Déconnecté(e)
Membre
divya raini
cd ed college
Déconnecté(e)
Membre
Shannon Bernard
Cadham Provincial Laboratory
Déconnecté(e)
Membre
Tyler Dickson
Alberta Health Services
Déconnecté(e)
Membre
Thierry Klein
-
Déconnecté(e)
Membre
Sasha Smith
NSCC Health Information Management
Déconnecté(e)
Membre
RONKE OSATOHANMWEN
NA
Déconnecté(e)
Membre
Karen Kovach
eHealth Saskatchewan
Déconnecté(e)
Membre
Cathy Skubisz
Manitoba eHealth
Déconnecté(e)
Membre
Kathy Giannangelo
KGC
Déconnecté(e)
Membre
Chris Heale
Applied Informatics for Health
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