Webinaire: Donner toute sa valeur à la saveur du jour - l’importance du rôle d’IHE , le 21 novembre 2018, de midi à 13 h HE. 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: 143
Personne-ressource: Derek Ritz
Administration: Andrea MacLean, 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 IHE?

Unlike HL7 (or ISO, or SNOMED, or WHO, etc.), IHE is not a health informatics standards development body. Rather, IHE is a standards profiling body. IHE Profiles are implementation guides – they make standards digestible, usable, and implementable. They describe, at a conformance-testable level of detail, how a portfolio of underlying standards will be employed to address the ecosystem-wide interoperability issues associated with a specific set of healthcare use cases. IHE Profiles create re-usable, digital health building blocks by “packaging up” the 5C’s:

  • Care context
  • Content specs
  • Coding specs
  • Communications specs
  • Confidentiality and security specs

The target audience for an IHE profile is the entire care delivery network. This especially includes the jurisdictional governance entities that are tasked with operationalizing plug-and-play interoperability between disparate network participants. IHE is focused on taking digital health interoperability to scale and to mitigating the risks inherent in such an effort.

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

Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.

KEY RESOURCES

IHE Resources

Activité

Deepti Razdan s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Katie Williams s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Derek Ritz a répondu au cours d'une discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Thanks, Mike -- these are very insightful comments. Your point is well-taken; IHE profiles can and do reference multiple underlying standards (not just FHIR). This is, I think, one of the key strengths -- an IHE profile of FHIR can draw in and include complementary specifications that are "out of scope" of the FHIR standard. Importantly, an IHE profile can also be leveraged to provide a functionally equivalent FHIR option alongside legacy options that are already widely deployed in our digital health landscape. In this way, IHE profiles can provide the long on-ramp that any new technology will need as it diffuses and is broadly taken up over time. In my view, Mike -- this FHIR uptake will happen; I really do think that FHIR has a momentum that HL7v3 (or v2, or OpenEHR) did not ever achieve. Equally... I'm convinced this diffusion will happen in ecosystem time... not technology time. The former tends to be comparatively geologic while the latter (with all its hype) is often measured in dog-years. ;-) Regarding the blog graphic's LMIC flavour -- you caught me! The example care pathways all denote WHO or UNICEF as the underlying guideline source. We could just as easily imagine the Canadian Diabetes Association or the Canadian Partnership Against Cancer along that top row. Of course, I'd point out that our immunization guidelines here in Canada (and everywhere else in the world) are based on the global EPI guideline. This is generally true for evidence-based care pathways -- they are remarkably consistent with each other, country to country. Mike -- I hope you can join the webinar next week. Yours is an important, experienced voice on the topic of IHE and its role!
Derek Ritz a répondu au cours d'une discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Thanks, Shanil. The effort right now is to develop a standards-based specification (a "grammar") that may be used to express a computable care guideline. Is this what the company had? If you'd like to connect them into this forum -- that'd be great! Whether it is the right approach for WHO, I know it will be informative to us all. As John Kennedy said: "a rising tide lifts all ships". :-)
Shanil Keshwani a répondu au cours d'une discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Hello All, I was at American Heart Association couple days back and I met with a company who has the experience of integrating all kinds of data not limiting to EHR/EMR, genetics, wearables, and so on. This is all HL7. Also, they have the capabilities to do AI/ML on those data as well. Please let me know if you want to connect. Currenlty, I am also working on various smartcity healthcare projects as well where I am helping the seniors and frail populations. Please let me know if I could be of any help.
Derek Ritz a répondu au cours d'une discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Yup -- we'll be progressing the "official" work, there, regarding the new profile. Ron -- there may also be a general "call for participants" regarding the WHO's own internal project as this moves to a prototyping phase around antenatal care and immunization workflows. Will post to this thread if those opportunities come up, too. :)
Derek Ritz a répondu au cours d'une discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Hey David -- I think you've raised a number of really good points! As a first, most obvious observation -- I completely agree with you... the whole purpose of this blog post is to "reach out proactively to the industry beyond current committee members". One place where I'd differ with you, though, is the degree to which FHIR is solving new problems that didn't exist before. That's perhaps true if we consider the rise of apps -- but this doesn't (in my view, at least) obviate the need to connect the digital health solutions that operationalize day-to-day care continuity (EMRs, EPRs, lab systems, pharmacy systems, DI, and the shared registries and repositories that help them interoperate). FHIR has a role to play in this, too -- today, and on into the future as the spec grows and matures. In fact, I'd argue that the true innovation is that, with FHIR, easy things are easy. (This is different from CDA over XDS, in my experience, where even easy things can be hard). I hope you'll agree: FHIR's current market hype is not our friend. It sometimes seems the key lesson we will all have to learn, again, is that hard things are still hard. They're hard because ecosystem-wide interoperability is more of a sociotechnical problem than a technical problem. Interoperability at scale relies on consistent digital health behaviour across a whole array of disparate systems -- and the governance and operationalization of this is beyond the scope of an over-the-wire message protocol... even a really clever one. David -- I sure hope you can attend the webinar next week. Yours is a seasoned and experienced voice that I'd love to hear in the call's Q&A. B) We've got a really important job to succeed at, here; this time (unlike last time), we need to turn the technology hype into actual health value.

Événements



Événements à venir :
Mer Nov 21 @12:00PM - 01:00PM
IHE's Important Role: Turning HYPE into VALUE

Forum

Turning HYPE into VALUE -- DISCUSSION THREAD 11/14/18
Thanks, Mike -- these are very insightful comments. Your point is well-taken; IHE profiles can and do reference multiple underlying standards (not just FHIR). This is, I think, one of the key strengths -- an IHE profile of FHIR can draw in and includ...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/14/18
Thanks, Shanil. The effort right now is to develop a standards-based specification (a "grammar") that may be used to express a computable care guideline. Is this what the company had? If you'd like to connect them into this forum -- that'd be great!...
Turning HYPE into VALUE -- DISCUSSION THREAD 11/13/18
Thanks for the blog post, Derek. You reminded us all of the importance of IHE in the digital health ecosystem. A couple of comments: This article focuses around FHIR, but it should be pointed out that IHE profiles work with many other standard...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/13/18
Hello All, I was at American Heart Association couple days back and I met with a company who has the experience of integrating all kinds of data not limiting to EHR/EMR, genetics, wearables, and so on. This is all HL7. Also, they have the capabili...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/13/18
Yup -- we'll be progressing the "official" work, there, regarding the new profile. Ron -- there may also be a general "call for participants" regarding the WHO's own internal project as this moves to a prototyping phase around antenatal care and immu...
Turning HYPE into VALUE -- DISCUSSION THREAD 11/13/18
Hey David -- I think you've raised a number of really good points! As a first, most obvious observation -- I completely agree with you... the whole purpose of this blog post is to "reach out proactively to the industry beyond current committee member...
WHO as an IHE Deployment Committee 11/13/18
Hey Ron -- our next step is to wait for the "launch" meeting to take place between the IHE board co-chairs and the WHO reps. This first meeting has been delayed because of trying to find a suitable time between the very-busy schedules of these partie...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/13/18
Derek, I would very much like to be a part of this. I presume this involves signing up for QRPH Technical Committee?
Turning HYPE into VALUE -- DISCUSSION THREAD 11/13/18
This is an interesting blog entry. To date, IHE ITI and other Domain have mostly focused on creating Implementation Guides for using FHIR with existing Document Sharing or other established profiles. These are needed as there are many DS implement...
WHO as an IHE Deployment Committee 11/13/18
Hey Derek. This is a great idea, and I have my particular reasons to participate. How does one get engaged? Rp
Turning HYPE into VALUE -- DISCUSSION THREAD 11/13/18
I recently posted a ... on the Infoway site. Hopefully... it's a bit provocative. ;) Let's use this thread to start a discussion on the timely topic of IHE's role in a digital health market that seems to have caught on FHIR. Comments welcome!!
WHO as an IHE Deployment Committee 11/13/18
I had a chance, last week in Geneva, to progress the ongoing discussions with WHO about a super-cool IHE-WHO initiative to improve support for digital health infrastructure projects within the 130+ low and middle-income countries (LMIC) that, today,...
WHO Computable Care Guidelines project - CALLING ALL INNOVATORS 11/13/18
I had the great pleasure to attend a working group "kick-off" meeting last week in Geneva regarding a new WHO-led global initiative focused on computable care guidelines and the associated AI/ML innovations that could be supported by such an effort....
IHE Connectathon 2019 -- "Ring of FHIR" event registration 11/13/18
OK... I must admit that I don't always understand marketing-speak. For example, is Ring of FHIR supposed to invoke Johnny Cash... or lava-spewing, island-creating Pacific tectonic shifts... or ghost pepper day-after misery... or what, exactly?...
IHE Meeting: Nov 21 at noon ET and supporting blog 11/12/18
Dear IHE Community members. In advance of the upcoming IHE community meeting on November 21 at noon ET, Derek has posted a great blog that certainly sets expectations for this meeting and the great work ahead. The blog can be found here: https:...

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
  • Canadian URI Registry
  • TermWorks
  • Registre FHIR Canadien
  • 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

Le registre canadien d'identificateurs uniformes de ressources (URI) a été créé pour regrouper l'information concernant les espaces de noms des identificateurs et des systèmes de codes. L'utilisation des ressources NamingSystem de FHIR® rend la saisie des métadonnées propice à la consultation et au traitement informatique. Elle permet aussi le mappage bidirectionnel automatique entre les identificateurs d'objets (OID) et les URI.

Afin de rendre la recherche de ces artéfacts plus souple, le registre d'URI canadien (alpha) permet d'effectuer des recherches via du texte en clair, des OID ou des URI. Les identificateurs URI sont créés à l'aide des lignes directrices URI et affichés sur la page du groupe de travail sur l'architecture de solutions FHIR en vue d'être approuvés.

Tous les artéfacts NamingSystem sont organisés par le Canadian URI Project dans Simplifier et peuvent faire l’objet de recherches après une période de 20 minutes.

Consultez le registre d’URI canadien(alpha)

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.

All project artifacts are backed up weekly, on Sunday nights. Each snapshot will be retained for 10 days. The project owner can request an as-is snapshot containing all the necessary artifacts such as text, xml, json, md and image files by contacting Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser..

Organization projects can be viewed without logging in. To edit or request a new project, Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. with the details.

View projects in the Canadian FHIR Registry

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

Derek Ritz
ecGroup Inc.
Déconnecté(e)
Personne-ressource
Andrea MacLean
Canada Health Infoway
Déconnecté(e)
Admin
Linda Monico
Canada Health Infoway
Connecté(e)
Admin
Deepti Razdan
cd-ed
Connecté(e)
Membre
Katie Williams
NSHA
Déconnecté(e)
Membre
Ron Parker
Parker Digital Health Consulting Inc.
Déconnecté(e)
Membre
Tracy Wutzke
CD-ED
Déconnecté(e)
Membre
Ovidiu Girlan
MOHLTC
Déconnecté(e)
Membre
Melody Scory
n/a
Déconnecté(e)
Membre
Melvy Sanchez
CDED
Déconnecté(e)
Membre
Deborah Schmidt
Classic Care Pharmacy
Déconnecté(e)
Membre
Lorraine Constable
Constable Consulting Inc
Déconnecté(e)
Membre
Shanil Keshwani
BI
Déconnecté(e)
Membre
Kinson Ho
McKesson
Déconnecté(e)
Membre
David Kwan
Cancer Care Ontario
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