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

Personne-ressource: Joel Francis

Administration: Joanie 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.

Retour à la Catégorie

À propos de nous

HL7 Canada Welcome 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)	Serve as a forum for all architectural questions about implemention of FHIR based solutions Discuss Canadian URI (incl. mapping to OIDs), profiles and extensions	Currently hosting governance calls for the FHIR Profiling Stream
eReferrals	Tim Berezny (CareDove) Caryn Harris (Orion Health)	Build eReferral use cases Prototype eReferral use cases Select Resources to include in Specifications Write preliminary Specifications for broader use	Assembled stakeholders from across the e-referral spectrum to build a community led e-Referral specification. 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.11.0/Index/Home/Introduction?version=0.11.0
Community Monthly Calls	Gavin Tong (Gevity Inc.) Yaron Derman (eHealth Ontario)	Share progress within the workstreams within the broader FHIR community Identify and promote FHIR education and implementation activities	Informative updates and discussions about FHIR globally and progress across the workstreams Average 17 participants per call.
Canadian Baseline Profiles & Governance	Sheridan Cook (Gevity Inc.) Michael Savage	Create of a set of national FHIR profiles that can be leveraged by implementers and jurisdictions to promote re-use and interoperability Establish a common baseline / starting point for Canadian FHIR Implementations	Organization of workstream into Profiling and Governance Streams, to allow for ample time to explore different types of issues Total of 78 proposed changes to draft Profiles received from FHIR Community Organization of Profiling Stream into sub-streams based on thematic groupings of FHIR Profiles: Entities, Medications, and Clinical Average 10 participants per call
SMART on FHIR Community of Practice	Paula Lee/Open	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é

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

Localization in ressource definition

I'd be extremely careful using something like OpenAI to perform translations. These tools are extremely vulnerable to bad input - eg people intentionally telling it incorrect values are correct. This means that the results can't be depended on. There was recently in the news a lawyer that had used ChatGPT to generate a briefing - and it returned fake case information that he didn't detect until after the judge he submitted to pointed out the issue. There is also the fact that you must be extremely careful to not include any identifiable information - these tools log everything they receive for ever...

Michael Savage a lancé une nouvelle discussion dans le groupe FHIR® Implementations

CA Baseline Governance Call - Friday June 9th 2-3pm EST Agenda

Hi all! The agenda for this Friday's Governance session is as follows: 1. Review the feedback provided to-date re: the proposal to remove MustSupport flags from the CA Baseline Implementation Guide (both the feedback provided via forum posts as well as provided during last week's profiling discussion) 2. Continue discussion in light of reviewed feedback 3. A reminder that due to the high amount of discussion from last week's call, we've decided to keep the window for feedback open until Friday June 16th to allow for more feedback to come in Thank you!

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

Patient.identifier.extension Health Number Version Code

PrescribeIT does have an extension (PHN-Version) on the identifier to capture the ON version.

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

Patient.identifier.extension Health Number Version Code

Lloyd beat me to it! The identifier actually identifies the health care system user. Theoretically, it stays the same for the entire lifetime of the user. The version code validates (against a central authority, not by any sort of calculation) that the identifier is currently valid for billing purposes within the billing system of the issuer.

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

Patient.identifier.extension Health Number Version Code

The identifier.value + system is globally unique and should always point to the same individual. The 'version' is used to verify that the credential they're displaying is current and to reduce chances of fraud.

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

Patient.identifier.extension Health Number Version Code

A couple thoughts... I'm thinking that it should not be limited to a number - it could be letters and digits. I do agree it makes sense to be attached to the identifier, but... Is the version code itself important? ie is "123456" plus "A12" different than "123456" plus "C32"? Or is just the identifier important? When the two components are important together, it almost implies that the version should be attached to the identifier.value - to make sure they are always kept together. If not always used together, then the version should be at the identifier level to allow identifer.value to not have the .version directly attached. We don't use version in Alberta, but we do have a counter tracking how many cards have been issued for a PHN. But this number is not used for identity management... Randy

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

Patient.identifier.extension Health Number Version Code

Identifier is definitely the right place for it. My inclination is to actually propose it for a standard extension because health cards aren't the only types of identifiers that have 'versions'. (It's a similar concept to credit card number security codes - a unique number issued with the identifier that is used to establish that this is the 'current' identifier.)

Événements à venir :

Ven Jui 16 @ 2:00PM - 03:00PM
CA Baseline Profiles Updates

Mar Jui 20 @11:00AM - 12:00PM
eReferral FHIR Working Group

Ven Jui 23 @ 2:00PM - 03:00PM
CA Baseline Profiles Governance

Forum

Randy Nonay

Déconnecté(e)

Localization in ressource definition 06/08/23

Michael Savage

Déconnecté(e)

CA Baseline Governance Call - Friday June 9th 2-3pm EST Agenda 06/07/23

Dean Matthews

Déconnecté(e)

Patient.identifier.extension Health Number Version Code 06/06/23

PrescribeIT does have an extension (PHN-Version) on the identifier to capture the ON version.

Peter Humphries

Déconnecté(e)

Patient.identifier.extension Health Number Version Code 06/06/23

Lloyd Mckenzie

Déconnecté(e)

Patient.identifier.extension Health Number Version Code 06/06/23

Randy Nonay

Déconnecté(e)

Patient.identifier.extension Health Number Version Code 06/06/23

Lloyd Mckenzie

Déconnecté(e)

Patient.identifier.extension Health Number Version Code 06/06/23

Ken Sinn

Déconnecté(e)

Patient.identifier.extension Health Number Version Code 06/06/23

Hi all, Are any implementers or jurisdictions (other than Ontario) that are using the Health Number Version Code extension for Patient.identifier slice? (as per https://simplifier.net/CanadianFHIRBaselineProfilesCA-Core/PatientProfile/~overview.)...

Joanie Harper

Déconnecté(e)

New Namespace OID request 06/06/23

The OID 2.16.840.1.113883.3.368.1022 has now been registered in the HL7 OID Registry. Best Regards, Joanie Harper

Linda Parisien

Déconnecté(e)

Localization in ressource definition 06/05/23

Hi, Just a reminder that any translation of SNOMED CT concepts must be approved by the Canadian National Release Center. The translations can be added to the Canadian Edition of SNOMED CT by submitting a request for change at Infoway.

Sheridan Cook

Déconnecté(e)

CA FHIR Baseline - MustSupport Modelling Decision - Feedback by June 16th 06/02/23

We had a great active discussion on today's profiling call - so much so that we're going to extend the discussion/feedback deadlines to account for another profiling session where the proposal can be discussed further. It seemed like folks want t...

Sheridan Cook

Déconnecté(e)

Localization in ressource definition 06/02/23

Erik - this doesn't speak to the translation extension but I did hear about some interesting tooling that is demonstrating resource text creation and translation: It's a proof of concept out of SNOMED to demonstrate how Large Language Model tools...

Tim Berezny

Déconnecté(e)

Localization in ressource definition 06/02/23

I believe the author is asking about a HealthcareService listing directory. So in particular service name and description need translating. A few value sets may need translating to (like for the HealthcareService.type field). Name an description...

Tim Berezny

Déconnecté(e)

Localization in ressource definition 06/02/23

Michael Savage

Déconnecté(e)

CA Baseline Profile Updates - Friday June 2nd 2-3pm EST Agenda 05/31/23

Hi all! The agenda for this Friday's Profiling Call is as follows: 1. Discuss the proposal to remove MustSupport from the CA Baseline iGuide, as raised during last week's Governance call 2. As part of above, discuss how we can best minimize im...

<< Début
< Précédent
1
2
3
4
5
6
7
8
9
10
...
105
Suivant >
Fin >>

Affichage #

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.