Partager :

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

pCLOCD
Probing the latest on pCLOCD/LOINC and UCUM from Regenstrief, Infoway and implementers.
Membres: 98
Personne-ressource: Lorie Carey
Administration: Linda Monico, Andrea MacLean
Type: Approbation
Accès: Public
Probing the latest on pCLOCD/LOINC and UCUM from Regenstrief, Infoway and implementers.

À propos de nous

As suggested by community members, the SNOMED CT and pCLOCD communities have merged into a new Health Terminologies community that will host all updates, discussions, presentations and work items related to the various terminologies and classifications used in health in Canada.

On May 16, 2018, the SNOMED CT and pCLOCD communities stoped accepting new members. All current members are now members of the new Health Terminologies community and are subscribed to receive forum notifications. Current members of SNOMED CT and pCLOCD communities will continue to have access to those communities and their forums until June 29, 2018.

Documents related to the SNOMED CT and pCLOCD communities will be available in an Archive folder within the Health Terminologies documents.

Forum postings from the pCLOCD and SNOMED CT communities will not be migrated to the new community. These posts are available as read-only until June 29, 2018.

The first meeting of the Health Terminology community will be on May 30 to determine the scope, leadership and direction of this new and exciting community. Be sure to join us and add your voice to determine the direction of health terminologies in Canada.

If you have any questions or concerns, please contact us at standards@infoway-inforoute.ca.

What is the pCLOCD Community?

The pCLOCD Community is a great place to ask questions (like what does pCLOCD stand for?), share lessons learned in pCLOCD implementations and learn more about the growth and development of pCLOCD and LOINC in Canada.

Meetings provide an opportunity to keep up on the latest releases of the pCLOCD, LOINC and UCUM, discuss requests for new content and share support for implemetation challenges. Exchange ideas and ask questions about implementation options, units of measure challenges or documentation ontology concerns using the community forum.

The pCLOCD is the most implemented standard in Canada and is poised to be implemented in the CIHI MIS statistics in the future. Community participants have a wealth of knowledge to share. Currently, it is in use or under review in 9 or 10 provinces and 1 of 3 territories.

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

If you have ideas for a community discussion or topic, working group or project that will drive interoperability forward, let us know! Send your suggestions.

CO-LEADERS

Karen Kovach, Laboratory Standards Analyst with eHealth Saskatchewan

Gennine Roberts, Clinical Informatics Specialist, MLT with eHealth Saskatchewan

KEY RESOURCES

pCLOCD Artifacts (Standard, Release Notes, Maintenance, Education, etc.)

Activité

Lorie Carey a lancé une nouvelle discussion dans le groupe pCLOCD
To all members of the pCLOCD Community: As suggested by SNOMED CT and pCLOCD community members and their leaders, these two communities will be merging into a new Health Terminologies community that will host all updates, discussions, presentations and work items related to the various terminologies and classifications used in health in Canada. The new Health Terminologies community will be launched on May 16th! All members of SNOMED CT and pCLOCD communities on May 16, 2018 will automatically be added to the membership of the new Health Terminologies community and will be subscribed to receive forum notifications. SNOMED CT and pCLOCD communities will no longer be able to accept new members after May 16th and these communities will be closed on June 29, 2018. Documents related to the SNOMED CT and pCLOCD communities will be available in an Archive folder within the Health Terminologies Documents Tab. Forum postings from the pCLOCD and SNOMED CT communities will not be migrated to the new community. These posts will be available as read-only until June 29, 2018. This new community will be hosting the first Kick-off meeting on May 30th. Many things such as scope, leadership and direction of this new and exciting community will need to be determined. Be sure to join in and add your voice to determine the direction of health terminologies in Canada. Watch the new forum for more information! I would personally like to thank the current leaders of this community, Karen Kovach and Gennine Roberts for their volunteer time and leadership. I would also like to thank the members of this community who have participated in the various forms, meetings, postings and general discussions. I look forward to seeing all of you in the new community! Regards, Lorie Carey Standards SME Canada Health Infoway

Événements



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

Forum

Important Notice about this Community 05/14/18
To all members of the pCLOCD Community: As suggested by SNOMED CT and pCLOCD community members and their leaders, these two communities will be merging into a new Health Terminologies community that will host all updates, discussions, presentation...
Terminology Community Discussion: Should InfoCentral support one terminology community to better reflect implementation realities and needs? 04/05/18
Dear pCLOCD community, Our thanks to everyone who particpated in the one community discussion. The deck and all next steps will now be communicated from the SNOMED CT community, so please do subscribe to that forum to keep yourself looped in an...
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 C...
Terminology Community Discussion: Should InfoCentral support one terminology community to better reflect implementation realities and needs? 03/02/18
Canada Health Infoway has received a request to host all terminology related discussions in one community that is more reflective of real-life project implementations that often need to implement more than one terminology to meet their clinical and b...
Cancer Pathology Synoptic Reporting: March 1 meeting results available 03/02/18
Good morning. I wanted to make everyone aware the Cancer Pathology Synoptic Meeting discussion and notes have been posted and shared on InfoCentral. All of the details can be found here: https://infocentral.infoway-inforoute.ca/en/forum/221...
LOINC/pCLOCD Code for Serotype determination of Streptococcus pneumoniae by Quellung reaction 02/20/18
Hi Shannon, Thank you for sending this inquiry. Could you please review LOINC 73674-4 (see attributes below)? LOINC_NUM COMPONENT PROPERTY TIME_ASPCT SYSTEM SCALE_TYP METHOD_TYP CLASS 73674-4 Streptococcus pneumoniae serotype Type Pt Isolate Nom...
LOINC/pCLOCD Code for Serotype determination of Streptococcus pneumoniae by Quellung reaction 02/20/18
Hello, I'm trying to find an appropriate code for the above analysis, performed at the National Microbiology Lab. From what I've read, this is the 'gold standard' test for epidemiological typing of Streptococcus pneumoniae. The specimen is an is...
Cancer Pathology Reporting: Standards Selection 02/08/18
Good morning, Please see InfoCentral events for the WebEx/Teleconfernce information for this session. https://infocentral.infoway-inforoute.ca/en/news-events/event-calendar/icalrepeat.detail/2018/03/01/2529/142/pathology-webinar March 1 at 1...
Cancer Pathology Reporting: Standards Selection 02/07/18
Good afternoon everyone, In advance of our meeting to discuss the encoding of the cancer pathology protocols and checklists, I have added some additional supporting documentation from Dr. Scott Campbell of the University of Nebraska who has been l...
pCLOCD Community Meeting - pCLOCD Release Feb 6/18 02/06/18
A kind thanks to all who were able to join today's pCLOCD Community Meeting for updates on the latest release. If there are any questions you didn't get to ask, we are happy to connect with you. Feel free to post in the forum or email us at stand...
The new version of the pan-Canadian LOINC Observation Code Database (pCLOCD) is now available 01/31/18
Access the latest release files on our ... Content highlights for the January 2018 release of pCLOCD include: 70 new codes have been added as a result of requests from Quebec & Saskatchewan Changes are based on the December 2017 Internatio...
pCLOCD Community Meeting - pCLOCD Release Feb 6/18 01/17/18
Linda Monico will be discussing the pCLOCD January 2018 release. See link below to add details to your calendar. https://infoway-inforoute.webex.com/infoway-inforoute/j.php?MTID=m82127fb1521df3fd8632483fb6a3fb01 Gennine
Regenstrief discouraging existing ^pre dialysis terms 01/16/18
The Regenstrief LOINC team put forward a proposal to discourage (not deprecate) the ^pre dialysis chemistry set and map them to the existing general concepts. This request is driven by potential increase in number of requests for “pre-dialysis” ter...
LOINC December 2017 Release Updates - January 11/18 01/11/18
Thanks to everyone who joined today's pCLOCD Community Meeting. We would really like to hear any feedback you may have or if there are any questions you didn't get to ask, we are happy to connect with you. The presentation from the meeting can be...
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...

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.

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.

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

Lorie Carey
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
Shelby Christenson
chima
Déconnecté(e)
Membre
steven wong
McMaster University
Déconnecté(e)
Membre
Cathy Skubisz
Manitoba eHealth
Déconnecté(e)
Membre
Mark Devries
Service New Brunswick
Déconnecté(e)
Membre
Claude Ouellette
Public Health Agency of Canada
Déconnecté(e)
Membre
Debbie Onos
Alberta Health Services
Déconnecté(e)
Membre
Lesley Eckstrand
n/a
Déconnecté(e)
Membre
Dr. Peter Samu
Rad-Logic Inc.
Déconnecté(e)
Membre
Sarah Wilson
Alberta Health Services
Déconnecté(e)
Membre
Ryan Doherty
iamsick.ca
Déconnecté(e)
Membre
Thomas Zhou
Alberta Health
Déconnecté(e)
Membre
Nicole Jaster
eHealth Saskatchewan
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