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

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 currently has five streams of activity:
1. Topical workstreams
2. Monthly community calls to share workstream progress and other FHIR-related news
3. 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/eReferral-Ontario/Introduction
  3. Basecamp here: https://3.basecamp.com/3573371/projects/7773495
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

Sheridan Cook (Gevity Inc.)

Michael Savage (Ontario MD)

  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
Canadian FHIR Baseline Profiles – Individuals & Entities Sub Stream

Shamil Nizamov (BC MOH)

  1. Creation of a set of Patient, Practitioner, Organization, Location, PractitionerRole national profiles.

The work is based on US Core profiles with analysis of other existing profiles (Netherlands, Australian)The work is based on US Core profiles with analysis of other existing profiles (Netherlands, Australian)

Canadian FHIR Baseline Profiles - Immunization & Medication Sub Stream

Igor Sirkovich

  1. Creation of a set of Immunization, Medication, MedicationRequest, MedicationStatement national profiles

The work is based on US Core profiles with analysis of other existing profiles (Netherlands, Australian)The work is based on US Core profiles with analysis of other existing profiles (Netherlands, Australian)

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.

Canadian Core Profiles

Activité

Michael Savage a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Attendees Michael Savage Sheridan Cook Anne Belford Joanie Harper Harsh Sharma Joel Francis Kenneth Sinn Randy Nonay Rita Pyle Shamil Nizamov Thomas Zhou • Shamil updated the group on the progress of the Clinical Profiles Sub-stream o 3 profiles remaining o clinical profile sessions are 2-3pm EST • Sheridan took the group through Patient Profiles for DHIR Due Diligence Review • General note (not specific to DHIR review); for CA Baseline Patient Profile, need to edit the note on the profile page in the iGuide, one of the bullets needs to be updated to reflect a recent change • General note; for feedback on CA Baseline Profile decisions that are outside the scope of comparing the CA Baseline and the chosen iGuide (DHIR in this case), please direct those comments via the GitHub Repository Issue log • General note; Mike will restart the posting of the meeting purpose / agenda prior to each call, to clarify meetings for newer members • CA Baseline Profile of Patient o .identifer > for the ‘all slices’, would expect to see the .type element supported o The need for this .type depends on whether the system being used for the identifier can be counted on to be known o Taking this away for future discussion, but can expect relaxation of cardinality of .type from 1..1 to 0..1 o Will be circulating this question
Michael Savage a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hi all! Is there any ongoing work within the Canadian FHIR community on utilizing Clinical Quality Language (CQL) or electronic Clinical Quality Measures (eCQM) to represent clinical measures or healthcare indicators in Canada? If anyone is involved with work relevant to this, please feel free to reply to this thread; the question comes from a colleague of mine who is eager to hear the extent to which the FHIR Community is leveraging these! Thank you! -Mike
Michael Savage a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hi all, Apologies for the late notice, but following all of FHIR North 2020 action this week we require some extra bandwidth to get caught up on work duties, and will not be hosting the Governance call today. The bi-weekly meetings will of course continue though. While we will not be having a meeting today, Sheridan has put together some great clear + thorough updates to keep everyone visible to the CA Baseline work that continues to progress: Update on Due Diligence Review • Reviewing baseline profiles against profiles in the DHIR R4 Point of Care Implementation Guide (see forum for notes on discrepancies flagged by the DDR) o Completed reviews of Immunization profile against DHIR Immunization Submission & Immunization Retrieval o Completed review of ImmunizationRecommendation against DHIR ImmunizationRecommendation o Nearly completed review of Patient profile against DHIR Patient (Imm Submission) Profile – will pick up where we left off next week o Next up is DHIR Patient (Imm Retrieval) Profile then we’ll look at the 3 DHIR Practitioner profiles • Both the IPS Immunization Profile and PrescribeIT guide have been proposed as next up after the review against the DHIR completes • Attracting new attendees (2 new vendors have joined us or reached out in the last month) • New attendees that have previously submitted change requests out of sequence of the substream reviews re-emphasized the need for an email account for the Canadian baseline like other implementation guides have Update on request for external support • We previously compiled work items and estimates for a request for paid SME support to expedite the due diligence reviews and produce DDR comparison artifacts to build confidence and alignment in the implementor community • The request has been shared with Infoway for SME support is making its way through the internal process • Derek will provide updates as he gets them Update on Template • As part of our maturity process we are conducting implementation guide clean up to get it ready for external exposure • Github project created, Russ is working this month to port over the work into the new Githhub project so we can update it with the newest templates, expunge reference to scratch profiles, bring more clarity between core and baseline Thanks everyone and apologies again for the late notice.
Tim Berezny a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Lloyd Mackenzie has brought to my attention that it would be more appropriate for the MesagerHeader.focus to point to the Task resource instead of the ServiceRequest. "The Task.focus is the ServiceRequest. The MessageHeader.focus would be what's happening to the ServiceRequest (seeking fulfillment, accepting, rejecting, updating fulfillment status, etc.) - and that's communicated by the Task." This sounds like it would be a sensible update to make to the specification
Tim Berezny a lancé une nouvelle discussion dans le groupe FHIR® Implementations
This is the first entry in the "Questionnaire" topic. This topic is an offshoot of the eReferral working group. Ongoing discussions regarding Questionnaires can occur within this topic. Thanks -Tim Berezny, CTO Caredove | tim@caredove.com | 705-717-6359
Tim Berezny a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hello Conversations regarding FHIR eReferral, Healthcareservice, and Questionnaire specification development are being moved from Basecamp to the Infoway/InfoCentral collaboration space. This transition is being done to align collaboration spaces with other FHIR development work being done across Canada. This space will host a discussion forum, meeting event details, and document storage. The new forum can be found at: https://infocentral.infoway-inforoute.ca/en/collaboration/wg/fhir-implementations If you don't have an account at InfoCentral already, you will need to sign up. Watch this 3 minute video for a quick introduction on how to use the collaboration space: https://www.screencast.com/t/kjERke6rSd Please take a few minutes to sign up to the new space and look around - as the basecamp space will be inactivated in the near future. Thanks -Tim Berezny
Tim Berezny a créé un événement dans le groupe FHIR® Implementations
eReferral FHIR Working Group
Mardi, Octobre 13, 2020 11:00am - 12:00pm
Biweekly meeting regarding the development of an eReferral FHIR specification. Other releated topics addressed include HealthcareService directory and Questionnaire. Participation is open to anybody who is interested in the development of this stadard, across Canada.

Événements



Événements à venir :
Lun Oct 26 @ 2:00PM - 03:00PM
Canadian Core Profiles: Clinical Profiles Stream
Mar Oct 27 @11:00AM - 12:00PM
eReferral FHIR Working Group
Ven Oct 30 @ 2:00PM - 03:00PM
FHIR Solution Architecture & Governance

Forum

Canadian FHIR Baseline Profiles - Profiling Updates + DDR - Oct 23 Notes 10/23/20
Attendees Michael Savage Sheridan Cook Anne Belford Joanie Harper Harsh Sharma Joel Francis Kenneth Sinn Randy Nonay Rita Pyle Shamil Nizamov Thomas Zhou • Shamil updated the group on the progress of the Clinical Profiles Sub-stream...
Clinical Quality Language (CQL) or electronic Clinical Quality Measures (eCQM) in the FHIR Community 10/22/20
Hi all! Is there any ongoing work within the Canadian FHIR community on utilizing Clinical Quality Language (CQL) or electronic Clinical Quality Measures (eCQM) to represent clinical measures or healthcare indicators in Canada? If anyone is involv...
CANCELLED - Oct 16 2pm CA Baseline Governance Call (read for updates) 10/16/20
Hi all, Apologies for the late notice, but following all of FHIR North 2020 action this week we require some extra bandwidth to get caught up on work duties, and will not be hosting the Governance call today. The bi-weekly meetings will of course...
eReferral Spec Development work stream 10/15/20
Lloyd Mackenzie has brought to my attention that it would be more appropriate for the MesagerHeader.focus to point to the Task resource instead of the ServiceRequest. "The Task.focus is the ServiceRequest. The MessageHeader.focus would be what's...
Questionnaire spec development work stream 10/13/20
This is the first entry in the "Questionnaire" topic. This topic is an offshoot of the eReferral working group. Ongoing discussions regarding Questionnaires can occur within this topic. Thanks -Tim Berezny, CTO Caredove | tim@caredove.com | 705-7...
HealthcareService spec development work stream 10/13/20
Hello Conversations regarding FHIR eReferral, Healthcareservice, and Questionnaire specification development are being moved from Basecamp to the Infoway/InfoCentral collaboration space. This transition is being done to align collaboration spaces...
Canadian FHIR Baseline Profiles - Oct 9th Due Diligence Review Notes 10/13/20
Hi, In Alberta, we use the following rules for 1 name persons: - One name (Last Name only) Clients with only a last name (i.e. family name) should have the last name entered in both the last name and first name fields, e.g. Mauli Mauli. - O...
Canadian FHIR Baseline Profiles - Oct 9th Due Diligence Review Notes 10/09/20
Attendees Michael Savage Sheridan Cook Igor Sirkovich Anne Belford Harsh Sharma Karl Stroetmann Kenneth Sinn Kristina Garrels Randy Nonay Rita Pyle Shamil Nizamov Thomas Zhou • Sheridan continued to lead the group through the Due Dil...
PCLOCD ValueSet URI 10/07/20
Hi Shamil, Just wanted to chime in here, I help with all authoring and maintenance of pCLOCD. pCLOCD is the Canadian constraint of the larger LOINC terminology and includes pan-Canadian unique XCA codes (65). We consider pCLOCD to be a Code System...
PCLOCD ValueSet URI 10/06/20
The binding strength in CA Core profiles is almost always "preferred". There might be few cases where we decided to make it required but I cannot recall it.
PCLOCD ValueSet URI 10/06/20
Hi Shamil, What we could try is to set the binding on the Coding element to be a fixed value and have it point to https://fhir.infoway-inforoute.ca/CodeSystem/pCLOCD Example: This will ensure that the Coding.system...
PCLOCD ValueSet URI 10/06/20
Hi Joanie, for the profile element binding I need to provide ValueSet URI, not CodeSystem URI. Can we consider that pCLOCD value set uri is - https://fhir.infoway-inforoute.ca/ValueSet/pCLOCD
PCLOCD ValueSet URI 10/06/20
Hi Shamil, We do not have a ValueSet URI for pCLOCD, however there is a CodeSystem URI that can be found at: https://build.fhir.org/ig/HL7/UTG/CodeSystem-pclocd.html. You can use the Defining URL found on that page. Please let us know if you...
PCLOCD ValueSet URI 10/05/20
Is there any registered pCLOCD ValueSet URI, I cannot find any?
Type 4 OID for ATLAS Alliance 10/04/20
OID Description: ATLAS Alliance EPIC Identifier - Six health-care organizations, from Hawkesbury to Ottawa and Renfrew to Barry’s Bay Full Name: ATLAS Alliance OID Symbolic name: caAtlas Existing OID to be registered : 2.16.840.1.113883.3.239.23.9...

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.

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

OAuth2, OpenID and SAML2 overview

An overview of these specifications and technologies and how they relate to SMART on FHIR.

01/19/18
FHIR in Canada

Infoway Partnership Conference 2017. Presented by Yaron Derman, Manager, eHealth Standards, eHealth Ontario, and Attila Farkas, Director, FHIR Strategy and Implementation, Canada Health Infoway

01/03/18

Solutions

  • Webhook Notifications
  • TermManager
  • FHIR Uniform Resource Identifier (URI)
  • Object Identifier (OID)
  • 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

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 TermManager is a web-based data mapping solution which is provided by request for free to individuals who have Standards Access. It provides comprehensive mapping capability to SNOMED CT® and the Canadian Edition of SNOMED CT with multi-user work flow options and flexible output formats.

 Implementation Guidelines & Resources

  • Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. - Email your request to Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. with the following information:
    • Your InfoCentral username.
    • Is this a new request or are you renewing your access to use TermManager?
    • Intended Use: Please describe the project and mapping requirements. Please Note: TermManager is limited to mapping with SNOMED CT. As more terminologies are available, they will be added.
    • Local Terms: Please describe the source of your local terms (EMR, LIS, etc.).
    • Please describe your requirements/project if they don't fit the above.
  • TermManager Release Notes

knowing Learn More

  • Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.
  • Apelon Mapping Tool Presentation
  • SNOMED CT Education
  • TermManager User Guide
  • How TermManager Works
  • TermManager FAQs

A Uniform Resource Identifier (URI) is a globally unique string of characters that provides a simple and extensible means for identifying a resource. URIs are used to identify a namespace or the location of a resource. URIs are human-readable and offer the potential for resolvability. The HL7 FHIR® specification recommends using URIs to have all resources resolvable and to comply with the FHIR RESTful paradigm.

URI Registration Process

  1. Requestor shall first check that the URI does not already exist in the Canadian URI Project, Jurisdictional Registry (if exists) or HL7 FHIR Specification
  2. FHIR URIs must not be proposed for Subsets to be published on the Terminology Gateway as they will be generated automatically.
  3. Requestor shall contact the owner or respresentative for either:
  4. Forum posts shall have the following format:

    Subject: New URI Request
    • Description: “A description of the URI”
    • Responsible Body & Contact Information
    • Proposed FHIR URI: URI as per URI Guidelines
    • Existing OID (if exists)
    • To be published (optional): Jurisidictional repository/ Canadian URI Registry
  5. There will be a wait period of five business days for the communities to react to the forum post with comments, questions or requests for clarification.
  6. Update Forum post will be updated with the new URI.
  7. Publishing the URI in the Canadian URI Registry and Jurisdictional Registry. This is highly recommended to prevent any misuse or duplication of URIs but it is optional.

See a flowchart of the FHIR URI Registration Process (pdf).

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. for all Non-jurisdictional and Infoway owned subsets. All other requests must be sent to Jurisdictional Representatives for OIDs following these guidelines listed:

  1. Jurisdictional Teams will require 5-7 business days to process each request. It will be incumbent on the requestor to reply within this time frame to any questions or make any follow ups as required. Any failure to do so will result in an automatic rejection and require resubmitting the request.

  2. The Requestor must post the OID Requests on the following forums ONLY after consulting with the Jurisdiction/Infoway SME:

    a. HL7 International and FHIR Implementation WG (Jurisdictional/Non-Jurisdictional OID Requests)
    b. Public Health Surveillance and Health Terminologies (Subset OID Requests)

    TIP How to upload and link a document to an InfoCentral Forum

  3. Forum posts shall have the following format:

    Subject: New Namespace/CodeSystem/Subset OID Request
    • OID Description: “A description of the OID”
    • OID Symbolic name: Symbolic name guidelines
    • Responsible Body & Contact Information
    • Proposed FHIR URI: URI as per URI Guidelines
    • To be published: Canadian URI Registry/Terminology Gateway

  4. There will be a wait period of 5 business days for the communities to react to the forum post with comments, questions or asks for clarification.

  5. FHIR URIs must be proposed for all Jurisdictional and Non-jurisdictional OID requests according to the URI Guidelines and must be published in the Canadian URI Registry. Publishing the URI is an optional but highly recommended step. The requestor will submit a validated FHIR® NamingSystem resource object based on the NamingSystem profile to their jurisdictional representative who will then upload it.

  6. FHIR URIs must not be proposed for Subsets to be published on the Terminology Gateway as they will be generated automatically.

  7. The Forum post will be updated with the new OID.

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

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

Service Level Agreement and Business Continuity

Simplifier.net should not be used in a production setting, as 24/7 support is not provided by Infoway or Firely®.

A project created in the Canadian FHIR Registry can be linked to an existing GitHub account. GitHub serves as a secondary backup and can sync the content in the project accordingly. Read details on how to set this up

Users of the Canadian FHIR Registry on the Simplifier platform can expect the following response time from the Firely team for any issue encountered.

Issue Premium Support Description
High Priority
  • Response time < 4 hours
  • Resolution time < 8 hours
Work halts and affects a large number of users
Medium Priority
  • Response time < 4 hours
  • Resolution time < 16 hours
Able to continue working but affects a small number of users
Low Priority
  • Response time < 4 hours
  • Resolution time < 24 hours
Able to continue work and affects a couple of users
Tickets
  • Unlimited
Able to influence the product’s road map

Read an overview of the Service Level Agreement between Infoway and Simplifier.net.

All project artifacts are backed up weekly at midnight on Sundays. 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..

Forge License Agreement

As per the statement issued on the Firely blog,  Securing the future of Forge, as of January 1, 2020, the free version of Forge will be licensed for non-commercial use only. To continue using Forge, users will need to be part of a paid plan on Simplifer.net. The current contract between Infoway and Firely for Simplifier.net allows for an unlimited number of users of Forge. Infoway has received confirmation from Firely that this will remain unaffected until December 31, 2021. As long as the authors in Simplifier.net belong to projects that are part of the Canadian FHIR Registry, they will be given rights through the administration processes of the platform conducted by Infoway.

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

  Message ReMixer retired November 29, 2019

Message ReMixer retired on November 29, 2019 and is no longer accessible.

Please contact Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. if you have any questions or concerns.

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

 

  HL7 Explorer retired November 29, 2019

HL7 Explorer retired on November 29, 2019 with no further updates or maintenance. Access will continue “as is”.

Please contact Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. if you have any questions or concerns.

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

  Message Builder retired November 29, 2019

Message Builder retired November 29, 2019 and is no longer supported. The source code and all supporting documentation is available as-is on GitHub:

Please contact Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. if you have any questions or concerns.

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

Infoway Request Management System (InfoRMS) is Infoway's request for change (RFC) 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 SNOMED CT

In order to ensure that SNOMED CT RFCs are addressed in an efficient and timely manner, it is the requestor's responsbility to:

  1. Ensure that the content does not exist in either the International or Canadian editions of SNOMED CT;
  2. Ensure that the request conforms with the most recent Editorial Guidelines;
  3. Provide the date of implementation;
  4. Provide reference material that is publicly available, authoritative, recent and relevant to the request (Wikipedia is not considered appropriate);
  5. Support the request with a clear justification for the change and an appropriate use case for context;
  6. Ensure all mandatory InfoRMS fields have been completed prior to submission.

Login to submit or follow requests to SNOMED CT 

 

pCLOCD leaf symbol pCLOCD/LOINC

Prior to submitting a pCLOCD/LOINC request, it is the requestor's responsibility to:

  1. Ensure that the content does not exist in LOINC or the pCLOCD;
  2. Ensure that a similar or equivalent term has not already been requested, by way of searching the online LOINC Submissions Queue;
  3. Ensure that a similar or equivalent term has not already been accepted and under development for the next official release, by way of searching LOINC Pre-release terms;
  4. Comply with Regenstrief Editorial Guidelines (note: login required)

Login to submit or follow requests to pCLOCD/LOINC 

 

subsets magnifying glass on monitor 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

Login to 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

Joel Francis
Canada Health Infoway
Déconnecté(e)
Personne-ressource
Joan Harper
Canada Health Infoway
Déconnecté(e)
Admin
Linda Monico
Canada Health Infoway
Déconnecté(e)
Admin
khush sekhon
BC Provincial Government
Déconnecté(e)
Membre
Mohamad Kassem
Allscripts
Déconnecté(e)
Membre
Sharilyn Kmech
Alberta Health Services
Déconnecté(e)
Membre
Amélie Tremblay
msss
Déconnecté(e)
Membre
Jeff Poy
Canadian Institute for Health Information
Déconnecté(e)
Membre
Dwayne Pickering
Ontario Health - Digital Services
Déconnecté(e)
Membre
Elisa Zapata
BID
Déconnecté(e)
Membre
YARON DERMAN
COGNISANTMD
Déconnecté(e)
Membre
Donghui Yin
N/A
Déconnecté(e)
Membre
Piers Hollott
NTT DATA/Sierra Systems
Déconnecté(e)
Membre
Mark Hewko
National Research Council
Déconnecté(e)
Membre
Shweta Munshi
N/A
Déconnecté(e)
Membre

L’enregistrement de la séance du 13 octobre de l’Événement de l’automne du Partenariat d’Inforoute est maintenant e… https://t.co/dQra0PLSY4

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