Partager :

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

FHIR® Implementations


Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.
Membres: 308
Personne-ressource: Joel Francis
Administration: Joan Harper, Linda Monico
Type: Ouvert
Accès: Public
Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.

À propos de nous

HL7 CanadaWelcome to the Canadian FHIR implementation community forum. The purpose of this forum is to collaborate on areas of FHIR implementation that will advance implementations across Canada, while contributing to the global adoption of FHIR. The objective is to develop pan-Canadian approaches to constraining and extending FHIR. The community has been active since January 2016 and has been growing ever since!

The community has several streams of activity:

  • Topical workstreams
  • Monthly community calls to share workstream progress and other FHIR-related news
    A general forum to ask questions and share information

The table below provides more details on the workstream activity:

Workstream Co-Chairs Objective Progress to date
Solution Architecture

Igor Sirkovich (OMHLTC)

Ken Sinn (Ontario Health Team)

  1. Serve as a forum for all architectural questions about implemention of FHIR based solutions
  2. Discuss Canadian URI (incl. mapping to OIDs), profiles and extensions
  1. Currently hosting governance calls for the FHIR Profiling Stream
eReferrals

Tim Berezny (CareDove)

Caryn Harris (Orion Health)

  1. Build eReferral use cases
  2. Prototype eReferral use cases
  3. Select Resources to include in Specifications
  4. Write preliminary Specifications for broader use
  1. Assembled stakeholders from across the e-referral spectrum to build a community led e-Referral specification.
  2. Published an e-referral implementation guide that has been adopted by various integrations across Ontario: https://simplifier.net/guide/ca-on-eReferral-r4-iguide-v0.10.1/Introduction
Community Monthly Calls

Gavin Tong (Gevity Inc.)

Yaron Derman (eHealth Ontario)

  1. Share progress within the workstreams within the broader FHIR community
  2. Identify and promote FHIR education and implementation activities
  1. Informative updates and discussions about FHIR globally and progress across the workstreams
  2. Average 17 participants per call.
Canadian Baseline Profiles & Governance

Sheridan Cook (Gevity Inc.)

Michael Savage

  1. Create of a set of national FHIR profiles that can be leveraged by implementers and jurisdictions to promote re-use and interoperability
  2. Establish a common baseline / starting point for Canadian FHIR Implementations
  1. Organization of workstream into Profiling and Governance Streams, to allow for ample time to explore different types of issues
  2. Total of 78 proposed changes to draft Profiles received from FHIR Community
  3. Organization of Profiling Stream into sub-streams based on thematic groupings of FHIR Profiles: Entities, Medications, and Clinical
  4. Average 10 participants per call
SMART on FHIR Community of Practice

Paula Lee/Open

  1. Develop Canadian specific SMART on FHIR guidance and specification documentation and best practices

This group has been recently established and is beginning with business use cases around which to develop an implementation guide and specification. Current SMART on FHIR implementers from across Canada are welcome to join.

The FHIR community forum is a great place to learn, share and collaborate, whether you are new to FHIR or are already have deep FHIR experience.

Key Resources

Canadian Core Profiles

Activité

Joan Harper a répondu au cours d'une discussion dans le groupe FHIR® Implementations

Hi Anibal, I have updated the OID registry as requested, however for 2.16.840.1.113883.4.56, I have left the note about existing usage at the top of the description. Please review and let me know if you have any concerns. Joanie

Anibal Jodorcovsky a répondu au cours d'une discussion dans le groupe FHIR® Implementations

Hi Joan, Is there an update on this? I wanted to follow-up just to see when the appropriate changes would have been posted to HL7: http://www.hl7.org/oid/index.cfm?Comp_OID=2.16.840.1.113883.4.56 http://www.hl7.org/oid/index.cfm?Comp_OID=2.16.124.10.101.1.60.100

Dean Matthews a répondu au cours d'une discussion dans le groupe FHIR® Implementations

You also need to be careful how detailed you get in the description. In your example of using the College of Nursing and calling it ab-rn-identifier means it also includes the person's role. What happens if the RN upgrades their education and becomes a Nurse Practitioner? They still have the same Identifier as given by their college, so nothing should need to change as far as their identifier goes

Lloyd Mckenzie a répondu au cours d'une discussion dans le groupe FHIR® Implementations

The reality is that both business identifiers and descriptive names can change over time. For most situations, implementers are going to have an easier time with names. Even if the organization renames, using the 'old' name will still make more cognitive sense than using a random identifier. That said, part of the question is "what do systems typically have?" If existing systems identify an organization by a particular identifier rather than a descriptive URL, then use a descriptive URL as the 'system' for that identifier and send the identifier in the value. If you're dealing with a URL for an identifier rather than an organization, it's best to have the name focus on the credential and not the organization that gives it. "ab-rn-identifier" is better than "ab-college-of-nursing-rn-id", for example, just in case the Alberta College of Nursing (or whatever they call themselves) changes their name.

Fang Cao a lancé une nouvelle discussion dans le groupe FHIR® Implementations

We have a question in regards to the identifier management and appreciate if you could shed some lights on. In our current URL naming convention we include the organization name to make the URL human readable, e.g. http://ehealthontario.ca/fhir/NamingSystem/id-university-health-network-mrn As we are supporting more and more healthcare service providers, we are concerned about the sustainability of issuing URL based on organization name – see below for a few examples of the organizations. • Reconnect Community Health Services • Dilico Anishinabek Family Care • Carizon Family and Community Services • Community Counselling Centre of Nipissing • Catholic Family Services of Simcoe County • K-W Counselling Services • Family Service Thames Valley • Counselling Centre of East Algoma • Service familial catholique Ottawa/Catholic Family Service Ottawa • Women's Shelter, Second Stage Housing and Counselling Services of Huron We are contemplating if we should consider revisiting the naming convention to move away from using organization name but to use business identifiers such as MOH generated unique identifier to form the URI. See examples of the two flavors below. URL using organization name: http://ehealthontario.ca/fhir/NamingSystem/id-reconnect-community-health-services-mrn URL using business identifier: http://ehealthontario.ca/fhir/NamingSystem/id-ohfs-facility-385-mrn We'd like to know how the other jurisdictions are handling this. Do you use the organization name or a business identifier, or another approach? If you are using the organization name, how do you manage long organization names and organization name changes? Your feedback is greatly appreciated.

Tarek Kadoura s'est joint(e) à un groupe

FHIR® Implementations Logo
Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.

Sheridan Cook a lancé une nouvelle discussion dans le groupe FHIR® Implementations

The newest CA FHIR Baseline package (...) has been published on Simplifier, meaning its available for selection in Simplifier (or through direct download). Claiming a dependency on the CA FHIR Baseline package means that your IGuides and profiles can leverage a point-in-time version of the CA Baseline content (e.g., profiles, extensions, valuesets) without having to recreate any of it in your own guides! Packages are also usable by folks who are validating examples/instances using https://validator.fhir.org/ or the validation built into IG Publisher/FHIR Validator tools. We put out a 1.0 package in January, but as we've had more and more folks in our community asking to utilize it, we wanted to make it even easier for IGuides that publish through a variety of tools & mechanisms (e.g., Simplifier, IGPublisher, FHIR Shorthand). So this version includes Snapshots for every profile in addition to the differentials. It also reflects some of the refinements we've been making to our profiles since the new year based on community review & feedback. You can read instructions for how to use packages in the .... As more communities begin using the CA Baseline and suggesting refinements (i.e., our process for maturing the CA FHIR Baseline profiles), we'll continue to make more package releases and announce them on this thread. Please reach out if you questions, we're happy to provide some pointers on how to best use packages and options for staying up to date with new releases. Subscribe to this topic to stay tuned for new releases & announcements.

Événements



Événements à venir :

Ven Juil 01 @ 2:00PM - 03:00PM
CA Baseline Profiles Updates
Ven Juil 08 @ 2:00PM - 03:00PM
CA Baseline Governance Stream
Ven Juil 15 @ 2:00PM - 03:00PM
CA Baseline Profiles Updates

Forum

Change to the meaning of an OID for Quebec patient identifier 06/21/22

Hi Anibal, I have updated the OID registry as requested, however for 2.16.840.1.113883.4.56, I have left the note about existing usage at the top of the description. Please review and let me know if you have any concerns. Joanie

Change to the meaning of an OID for Quebec patient identifier 06/21/22

Hi Joan, Is there an update on this? I wanted to follow-up just to see when the appropriate changes would have been posted to HL7: http://www.hl7.org/oid/index.cfm?Comp_OID=2.16.840.1.113883.4.56 http://www.hl7.org/oid/index.cfm?Comp_OID=2.1...

FHIR Uri naming convention - seeking input from other jurisdictions 06/10/22

You also need to be careful how detailed you get in the description. In your example of using the College of Nursing and calling it ab-rn-identifier means it also includes the person's role. What happens if the RN upgrades their education and become...

FHIR Uri naming convention - seeking input from other jurisdictions 06/10/22

The reality is that both business identifiers and descriptive names can change over time. For most situations, implementers are going to have an easier time with names. Even if the organization renames, using the 'old' name will still make more cog...

FHIR Uri naming convention - seeking input from other jurisdictions 06/10/22

We have a question in regards to the identifier management and appreciate if you could shed some lights on. In our current URL naming convention we include the organization name to make the URL human readable, e.g. http://ehealthontario.ca/fhir/Namin...

CA FHIR Baseline - Newest Package 06/09/22

The newest CA FHIR Baseline package (...) has been published on Simplifier, meaning its available for selection in Simplifier (or through direct download). Claiming a dependency on the CA FHIR Baseline package means that your IGuides and profiles can...

Change to the meaning of an OID for Quebec patient identifier 06/07/22

Thanks! I uploaded the document here: https://infocentral.infoway-inforoute.ca/en/resources/docs/fhir/3947-hl7-oid-for-quebec-clarification-of-56-and-100

Change to the meaning of an OID for Quebec patient identifier 06/07/22

Thank you Anibal. You can add a document by going to the Documents section of the FHIR Implementations Group. Click Manage Document and then you will see an option to add a document. Once you do so, you will need to create another post to let pe...

Change to the meaning of an OID for Quebec patient identifier 06/07/22

Hello everybody, Daniel did a lot of work on getting consensus between key people in MSSS (Ministere) and RAMQ (Regie d'Assurance Maladie). He prepared a document, which he alludes it in the previous post and since then the UCNI (Unité de coordin...

Implementer FYI - Resource ID Data Type Constraints 06/06/22

Additional implication: - All FHIR R4 profiles will show MyMedication.id, MyImmunization.id, MyPatient.id, etc as "String" type in the snapshot view, in both Simplifier and HL7 Publisher formats. They all inherit the base FHIR R4 definitions, whic...

Implementer FYI - Resource ID Data Type Constraints 06/06/22

To put this in a more concrete example: For all resources except for the base "Resource", FHIR R4 (4.0.1) incorrectly defined their logical id defined as "string" type , - Medication.id, Immunization.id, Patient.id, Organization.id, etc are define...

Implementer FYI - Resource ID Data Type Constraints 06/06/22

This is a PSA regarding namedresource.id data type that one of our Canadian FHIR Implementers recently ran into. We felt it was helpful to raise in case others in our community weren't aware of it and are starting to work with vendors to generate and...

CA Baseline Profiles Governance Stream Agenda - Friday May 27th 2-3pm EST 05/25/22

Hi all, PLEASE first note that, once again, we have needed to update the zoom links in our calendar invites for the CA Baseline Profiles meetings (both Profiles and Governance streams). Please refer to the calendar invites for the updates registra...

Call for Agenda Items - Community Quarterly Call - Weds June 1st 12-1pm EST 05/24/22

Hi all, Apologies, we've needed to push the scheduled Quarterly Community Call by 1 week - it will be planned for Weds June 1st 12-1pm EST. As well, this is an open call for Agenda items, so please reply in this thread with any suggested agenda it...

Should URI to a ValueSet resolve to a valid end-point? 05/21/22

The goal is that the canonical url is a unique identifier for that ValueSet (or CodeSystem, or profile StructureDefinition, etc.). By "unique" I mean that the same url identifies the ValueSet regardless of what local FHIR server it is copied onto....

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.

Architecture ( 0 Document )

BusinessCase ( 0 Document )

CDS Hooks ( 0 Document )

Client Registry ( 0 Document )

Consent Management ( 0 Document )

eReferral ( 0 Document )

Meeting Materials ( 0 Document )

Provider Registry ( 0 Document )

Questionnaire ( 0 Document )

SMART on FHIR ( 0 Document )

Tooling ( 0 Document )

Vidéo

FHIR testing with Crucible and Synthea Patient generator

A look at an open source FHIR testing platform (Crucible) and a synthetic patient generator (Synthea) - aired Nov. 3rd, 2017

11/29/17
FHIR Solution Architecture - Smile CDR

A demo of a system built on FHIR - Smile CDR given by James Agnew author of HAPI FHIR server - aired October 20, 2017

11/29/17

Membres

Joel Francis
Photo de Joel Francis
Canada Health Infoway
Déconnecté(e)
Personne-ressource
Joan Harper
Photo de Joan Harper
Canada Health Infoway
Déconnecté(e)
Admin
Linda Monico
Photo de Linda Monico
Canada Health Infoway
Déconnecté(e)
Admin
Tarek Kadoura
Photo de Tarek Kadoura
Canada Health Infoway
Déconnecté(e)
Membre
Mairead Fitzsimmons
Photo de Mairead Fitzsimmons
TELUS
Déconnecté(e)
Membre
Katherine McMillan
Photo de Katherine McMillan
Telfer School of Management
Déconnecté(e)
Membre
Emmanuel Liossis
Photo de Emmanuel Liossis
Lifeaccount Inc.
Déconnecté(e)
Membre
Mathieu Tougas
Photo de Mathieu Tougas
Akinox Solutions Inc.
Déconnecté(e)
Membre
eric savoie
Photo de eric savoie
msss
Déconnecté(e)
Membre
Sam Donaldson
Photo de Sam Donaldson
Gevity Inc
Déconnecté(e)
Membre
Pascal St-Onge
Photo de Pascal St-Onge
CHUM
Déconnecté(e)
Membre
Florin Negoita
Photo de Florin Negoita
n/a
Déconnecté(e)
Membre
Sarabjit Singh
Photo de Sarabjit Singh
Ontario Health
Déconnecté(e)
Membre
Duane Bender
Photo de Duane Bender
Digital Health Partners
Déconnecté(e)
Membre
Edmond Chiu
Photo de Edmond Chiu
Canada Health Infoway
Déconnecté(e)
Membre

Dernier message Twitter

Dans l’article paru sur notre blogue, nous explorons l’interopérabilité et analysons certains des résultats du réce… https://t.co/k0flB1QY07

par Inforoute,

Logo d'InfoCentral

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