Share this page:

FHIR® Implementations


Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.
Members: 337
Contact: Joel Francis
Type: Open
Access: Public
Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.

About

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.11.0/Index/Home/Introduction?version=0.11.0
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

Activity

Sheridan Cook replied to a discussion in FHIR® Implementations

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 like OpenAI could be used to generate an initial summarized text for a resource using the details in the elements in the style of a clinician summary and it also has some translation prompts that could be expanded. https://ihtsdo.github.io/openai-demo/ You need to get an OpenAI key to run it but it's free to sign up for a key and there is a link in the demo. It goes without saying that use of this type of technology is really new in our industry - so how it works in production (e.g., localized instances, segmentation of data in queries for privacy, etc) is something that isn't well defined. But I bring it up to see if there is interest in exploring the proof of concept further at future IPS connectathon tracks (e.g., have an outside app pass resources for summarization and request additional translations be included in resource.text).

Tim Berezny replied to a discussion in FHIR® Implementations

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 would usually be translated by a human, the .type valueset would be pre-defined.

Tim Berezny replied to a discussion in FHIR® Implementations

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 would usually be translated by a human, the .type valueset would be pre-defined.

Michael Savage created a new discussion in FHIR® Implementations

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 impact of this change Thank you!

Lloyd Mckenzie replied to a discussion in FHIR® Implementations

There's been a fair bit of effort that's gone into trying to land on the MS assertions, so it'd be a shame to throw all of that away. However, the new "obligation" framework that allows more specific SHALL/SHOULD/MAY assertions specific to particular types of apps (and that can be maintained separately from the base profiles) is definitely where we should go with this. Perhaps, for now, move the MS notion into a parallel spreadsheet pre profile with rows for each element that we can eventually migrate into Obligations?

Sheridan Cook created a new discussion in FHIR® Implementations

As part of our recent efforts to make the CA FHIR Baseline profiles more use case agnostic - we are considering the removal of the MustSupport flags on the current profiles and using a section in the guide to indicate which elements that implementers should consider for MustSupports in their respective profiles. Given what we've learned from other National bases recently + the efforts that are coming forward for the alternative to MustSupport (particularly for bases and cores) + the work that is occurring with the pan-Canadian data models and CA Core+, we believe now is the right time to modify the approach we've been using (applying MustSupports on items we see are MS across implementation guides and removing the flag during Due Diligence Reviews that identify evidence that the element isn't MS for a use case). We will have a discussion on the proposed change on the next CA FHIR Profiling call - June 2nd. We're asking for feedback to be provided during that call and through this forum thread by June 9th 1pm ET. We will collect any feedback received and discuss how it should be dispositioned during our June 9th CA FHIR Baseline Governance Call. Afterwards a decision will be posted to this forum thread and reiterated on the subsequent CA FHIR Baseline call.

sean vogel created a new discussion in FHIR® Implementations

OID Description: OID to identify Collaborative Health Record as a vendor OID Symbolic name: CHR Responsible Body & Contact Information: Telus Health Solutions | Sean Vogel Proposed FHIR URI: URI as per URI Guidelines To be published: Canadian URI Registry/Terminology Gateway Telus Oid Request for CHR Could we have 2.16.840.1.113883.3.368.1022... We are looking to have 2.16.840.1.113883.3.368.1022 as a child of 2.16.840.1.113883.3.368 (which i what I have in column G)

Events



Upcoming events:

Fri Jun 02 @ 2:00PM - 03:00PM
CA Baseline Profiles Updates
Fri Jun 09 @ 2:00PM - 03:00PM
CA Baseline Profiles Governance
Fri Jun 16 @ 2:00PM - 03:00PM
CA Baseline Profiles Updates

Forum

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

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

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

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

CA FHIR Baseline - MustSupport Modelling Decision - Feedback by June 9th 05/26/23

There's been a fair bit of effort that's gone into trying to land on the MS assertions, so it'd be a shame to throw all of that away. However, the new "obligation" framework that allows more specific SHALL/SHOULD/MAY assertions specific to particula...

CA FHIR Baseline - MustSupport Modelling Decision - Feedback by June 9th 05/26/23

As part of our recent efforts to make the CA FHIR Baseline profiles more use case agnostic - we are considering the removal of the MustSupport flags on the current profiles and using a section in the guide to indicate which elements that implementers...

New Namespace OID request 05/26/23

OID Description: OID to identify Collaborative Health Record as a vendor OID Symbolic name: CHR Responsible Body & Contact Information: Telus Health Solutions | Sean Vogel Proposed FHIR URI: URI as per URI Guidelines To be published: Canadian URI...

Localization in ressource definition 05/25/23

I think it's important to understand what you are looking for in a translation. Are you hoping for code display values in one of a choice of languages, or available in multiple languages? Are you expecting one instance of a resource to be in one lang...

CA Baseline Profiles - Governance Call - Fri May 26th 2-3pm EST Agenda 05/24/23

Hi all! Our agenda for this Friday's CA Baseline Governance Call from 2-3pm EST is as follows: 1. Continue the discussion on processes and what other methods we can leverage toward bringing about more Use Case Agnosticism in our Profiles 1a. S...

Localization in ressource definition 05/24/23

There's actually a bunch of work underway sponsored by the WHO to add publication support for multiple languages in IGs using industry standard translation files. However, those features aren't fully defined anywhere yet.

Localization in ressource definition 05/24/23

HI Erik, In FHIR R4, the Translation extension had a status of draft: https://www.hl7.org/fhir/R4/extension-translation.html In R4B, the extension was still in draft status: https://hl7.org/fhir/r4b/extension-translation.html In FHIR R5, the T...

Localization in ressource definition 05/24/23

You could consider using designation in your value set definitions

Localization in ressource definition 05/24/23

Hi! I was looking for any references on ressource definitions that would support multiple languages. For instance, a HealthcareService that would be defined in multiple locales (fr-CA and en-CA). Are there any guidelines identified on using the FHIR...

Links to Simplifier / Forge May 16 Webinar 05/23/23

Hello FHIR Implementers, For anyone who missed the Simplifier.net and Forge Webinar last week, here are the links to the recordings and slide deck: Recording: https://www.youtube.com/playlist?list=PLAPVWVA2xKFhFCPuwrbj7FOsCAO3-6Xo4 Slides: https...

FHIR Implementers Community Call - Weds May 24th 12-1pm EST 05/19/23

Hi all! For our quarterly FHIR Implementers Community Call coming up on Wednesday May 24th 12-1pm EST, the draft agenda is as follows: 1. Intro to any new attendees (may have some!) 2. Updates from the Community a. Sun Life Canada embarking...

Documents

Click Manage documents to:

  • view the complete list of documents or documents grouped by folder
  • upload a new document

Note: Group members are not currently notified when new documents are added. To notify others, you must post the URL to the new document in the forum. (Notification of document uploads is a feature in development.)

Manage documents You may need to login and/or be a member of the group to access this content.

Architecture ( 2 Documents )

BusinessCase ( 6 Documents )

CDS Hooks ( 1 Document )

Client Registry ( 2 Documents )

Consent Management ( 0 Document )

eReferral ( 68 Documents )

Meeting Materials ( 9 Documents )

Provider Registry ( 1 Document )

Questionnaire ( 3 Documents )

SMART on FHIR ( 3 Documents )

Tooling ( 9 Documents )

HL7 OID for Quebec - clarification of .56 and .100

Published on Jun 07, 2022 by Anibal Jodorcovsky

Canada Type 3 OIDS - Professional Colleges

Published on Nov 23, 2021 by Joanie Harper

Identifier OID Registration Form OmniMed

Published on Aug 05, 2021 by Vania Granese

ca-NamingSystem screenshot

Published on Nov 16, 2020 by Joanie Harper

Identifier OID Registration Form_ShoppersDrugMart_Type4

Published on Oct 07, 2020 by Vania Granese

Identifier OID Registration Form for ATLAS Alliance

Published on Oct 04, 2020 by Vania Granese

Identifier OID Registration Form Aware MD

Published on Sep 03, 2020 by Vania Granese

FHIR NamingSystem Template 2020

Published on Jul 21, 2020 by Joel Francis

HL7 Canada Pres to FHIR Community 2020-03-25

Published on Mar 25, 2020 by Michael Savage

Identifier OID Registration Form QHR

Published on Mar 06, 2020 by Vania Granese

Canadian Core Project Deck - as of Nov 6 2019

Published on Nov 06, 2019 by Michael Savage

Alberta Pharmacy License Number

Published on Nov 04, 2019 by Randy Nonay

Life of Lamberts Consolidated Stories

Published on Oct 25, 2019 by Michael Savage

SDC on FHIR by Joel Francis and Alex goel

Published on Sep 06, 2019 by Alexander Goel

ACCESS Atlantic Discovery Phase B Presentation - July 2019

Published on Jul 24, 2019 by Michael Savage

Alberta Delivery Site Identifier OIDS

Published on Jul 04, 2019 by Randy Nonay

Canadian Core Profile - Template for Review / Proposed Changes

Published on Jun 21, 2019 by Michael Savage

Vendor OID Form IntraHealth EMR

Published on Jun 11, 2019 by Vania Granese

Alberta Prescription Monitoring Protocol OID request

Published on Mar 29, 2019 by Randy Nonay

OID registration form for Microquest Canada

Published on Mar 29, 2019 by Randy Nonay

OID Registration Form for Input Health

Published on Mar 22, 2019 by Vania Granese

Identifier OID Registration Form for Indivica

Published on Mar 05, 2019 by Vania Granese

Joel Francis' HL7 WGM Update

Published on Jan 23, 2019 by Yaron Derman

New OIDs Request Process

Published on Dec 05, 2018 by Joel Francis

Terminology Gateway - Overview

Published on Dec 05, 2018 by Joel Francis

Why FHIR, Why Now?

Published on Dec 14, 2017 by Tasha Shaw-Verbic

Pourquoi utiliser FHIR et pourquoi maintenant

Published on Dec 13, 2017 by Tasha Shaw-Verbic

Video

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

Members

Joel Francis
Picture of Joel Francis
Canada Health Infoway
OFFLINE
Contact
Joanie Harper
Picture of Joanie Harper
Canada Health Infoway
OFFLINE
Admin
Linda Monico
Picture of Linda Monico
Canada Health Infoway
ONLINE
Admin
sean vogel
Picture of sean vogel
Telus Health
OFFLINE
Member
Jessica MacDougall
Picture of Jessica MacDougall
NS Department of Health
OFFLINE
Member
john forbes
Picture of john forbes
health region (BC)
OFFLINE
Member
Andrew Hebert
Picture of Andrew Hebert
eHealth Saskatchewan
OFFLINE
Member
Desmond Guarin
Picture of Desmond Guarin
BC Ministry of Health
OFFLINE
Member
Tom Servaes
Picture of Tom Servaes
Dept. Of Health and Wellness
OFFLINE
Member
Clark Van Oyen
Picture of Clark Van Oyen
Cortico Health Technologies
OFFLINE
Member
Madison Kaskiewicz
Picture of Madison Kaskiewicz
Canada Health Infoway
OFFLINE
Member
Yongjian Yang
Picture of Yongjian Yang
Novari Health
OFFLINE
Member
Valérie Beauchamp
Picture of Valérie Beauchamp
CHUM
OFFLINE
Member
Philip John Sales
Picture of Philip John Sales
OntarioHealth
OFFLINE
Member
Rachel Barker
Picture of Rachel Barker
Provincial Health Services Authority
OFFLINE
Member
Twitter response: "Could not authenticate you."

InfoCentral logo

Improving the quality of patient care through the effective sharing of clinical information among health care organizations, clinicians and their patients.



Login Register