Bientôt: Nouvelles versions de SNOMED CT International et de pCLOCD, juillet 31 plus >

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: 221
Personne-ressource: Joel Francis
Administration: 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
Smart on FHIR

Gavin Tong (Gevity)

  1. Investigate these emerging FHIR technologies for applicability to the Canadian market
  2. Create reference material to support and promote national adoption
  3. Identify the need and kick-off activities needed to create necessary FHIR elements that support Canadian implementations
  1. Drafted core objectives and initial action items
  2. Presented a Business Case overview for SMART on FHIR (video here)
  3. Conducted a review of architectural considerations
  4. Analyzed usable OAuth2 grant schemes for SMART applications
  5. Created a demo application shared on GitHub
  6. Start creating a marketing engagement strategy to educate, promote and invite more industry participation. Doc here.
Solution Architecture

Igor Sirkovich (OMHLTC)

Kris Lewis (Sierra Systems)

  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. Review FHIR URI strategy
  2. Full list of provincial Patient ID URIs
  3. Partial list of provincial Org URIs
  4. Started work on provincial provider URIs
  5. Started discussion paper on IG publisher
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. Overall use case flows combined into a single modular flow diagram: diagram and video.
  2. A demo video of some of eReferral workflows in action in a pilot environment: simple, SMART, advanced business logic
  3. Primary Resources have been identified. Identifying the role of the Task Resource.
  4. FHIR Resources applied in pilot environment, Specification writing still pending, outsanding: authentication mechanisms.
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 FHIR Baseline Profiles

Michael Savage (Ontario MD)

  1. Formulation of an apporach to initiate and govern the baseline work
  2. Creation of a set of national profiles that can be leveraged by implementers and jurisdictions to promote re-use and interoperability
  1. An analysis of the work that is currently available such as - Argonaut Project
  2. Average 30 participants per call.

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.

Activité

Michael Savage a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Hi all, In advance of tomorrow's call, if interested Community members can consult the current list of Patient profile proposed changes in the GitHub issue log (https://github.com/scratch-fhir-profiles/CA-Core/issues) and indicate their support / disagreement with the proposed changes by giving either a thumbs-up or thumbs-down emoticon for the issue (it's pretty straightforward, but email me if you're unclear how to do this), that would be great. This will really help us demonstrate how we can prioritize which proposed changes get discussed in meetings. A side-note, if you choose to give a thumbs-down for a proposed change it is expected that you provide a comment which explains why. Thank you!
Greg Violette s'est joint(e) à un groupe
Logo
Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.
Michael Savage a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Thanks for posting this Gavin. As this presentation will take the majority of the meeting, I think it's just safe to state the rest of the meeting agenda here as Updates from Stream Leads, in the remaining time following the presentation. As always, the Zoom meeting details can be accessed from the events calendar: https://infocentral.infoway-inforoute.ca/en/monthly-calendar/month.calendar/2019/07/17/1268
Gavin Tong a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hi, If you're interested in presenting at FHIR North please complete the call for speakers application by August 12: https://docs.google.com/forms/d/1wINSB1iBYMuYFZe1064EdLkYruJUq_aj-LDRGrzHnmI/viewform?edit_requested=true There will be two opportunities to present at FHIR North this year: FHIR Academy and CodeCamp. Both presentation types will focus on how FHIR can/has been applied in Canadian and international healthcare communities, however the CodeCamp presentations are expected to be more hands-on practicum focused. FHIR Academy: Presenters are invited to give a scheduled 10 minute oral presentation with 5 minutes for audience questions. If the content you’re presenting on requires more time, there will also be an option of a 30 minute presentation slot (20 minutes with 10 minutes for audience questions). CodeCamp: Presenters are invited to give a 20 minute deep dive into a particular application of FHIR. In previous years, topics of CodeCamp presentations have been focused on deepening a technical audience’s understanding of: SMART-on-FHIR, FHIR-enabled eReferral, CDS Hooks, etc.
Michael Savage a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hi all, For this Friday's Profiling Stream Meeting (Friday July 19th, 2-3pm EST) the draft agenda is to look at the proposed changes that have been submitted by reviewers for the current draft of the Canadian Core Patient Profile. The issue log can be found here: https://github.com/scratch-fhir-profiles/CA-Core/issues Just to set expectations for the call, we will not be able to go through every proposed change for the Patient Profile during the call (there are around 20 of them); we will have to look at managing the volume of proposed changes (i.e. how to vote on all of them) as a work-in-progress. Please keep in mind that, rather than waiting for the calls, you are always welcome and encouraged to email me at michael.savage@ontariomd.com if you have any questions. Thank you! The Zoom meeting details for joining the meeting can be found on the relevant calendar invite here: https://infocentral.infoway-inforoute.ca/en/monthly-calendar/month.calendar/2019/07/16/1268
Ken Sinn a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Thanks to Joel for reaching out to Firely regarding our request for project key/name/description recommendation. While Firely has no recommended approaches and suggest that organizations develop their own nomenclature, they did suggest taking a look at FHIR package naming conventions as documented at http://wiki.hl7.org/index.php?title=FHIR_NPM_Package_Spec#Package_name for ideas and considerations. We will follow up in the next few days, giving people in this workgroup some time to review the content at the link above.
Gavin Tong a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hi, We just wanted to give the community a heads up that on the July 24th FHIR WG meeting there will be a presentation on the findings from the ACCESS Atlantic Discovery Phase B project that examined mapping between provincial interfaces and FHIR resources. The focus for the analysis was on citizen access to lab results, and citizen and clinician access to medication profile information. The presentation will include an overview of the methodology used, some of the key findings from the mapping work and the draft resource profiles and supporting implementation guidance. Thanks, Gavin

Événements



Événements à venir :
Mar Juil 23 @11:00AM - 12:00PM
E-Referral Work Stream
Mer Juil 24 @12:00PM - 01:00PM
FHIR Community - Monthly Update Call
Ven Juil 26 @ 2:00PM - 03:00PM
FHIR Solution Architecture

Forum

Canadian FHIR Baseline Profiles - Profiling Stream Meeting - July 19th, 2-3pm EST 07/18/19
Hi all, In advance of tomorrow's call, if interested Community members can consult the current list of Patient profile proposed changes in the GitHub issue log (https://github.com/scratch-fhir-profiles/CA-Core/issues) and indicate their support /...
July 24 FHIR WG Meeting: ACCESS Atlantic Discovery Phase B 07/17/19
Thanks for posting this Gavin. As this presentation will take the majority of the meeting, I think it's just safe to state the rest of the meeting agenda here as Updates from Stream Leads, in the remaining time following the presentation. As alway...
FHIR North - Call for Speakers 07/17/19
Hi, If you're interested in presenting at FHIR North please complete the call for speakers application by August 12: https://docs.google.com/forms/d/1wINSB1iBYMuYFZe1064EdLkYruJUq_aj-LDRGrzHnmI/viewform?edit_requested=true There will be two op...
Canadian FHIR Baseline Profiles - Profiling Stream Meeting - July 19th, 2-3pm EST 07/16/19
Hi all, For this Friday's Profiling Stream Meeting (Friday July 19th, 2-3pm EST) the draft agenda is to look at the proposed changes that have been submitted by reviewers for the current draft of the Canadian Core Patient Profile. The issue log ca...
FHIR Implementation Community - Solution Architecture Call (2019-07-12 2pm-3pm EST) Minutes 07/16/19
Thanks to Joel for reaching out to Firely regarding our request for project key/name/description recommendation. While Firely has no recommended approaches and suggest that organizations develop their own nomenclature, they did suggest taking a look...
July 24 FHIR WG Meeting: ACCESS Atlantic Discovery Phase B 07/15/19
Hi, We just wanted to give the community a heads up that on the July 24th FHIR WG meeting there will be a presentation on the findings from the ACCESS Atlantic Discovery Phase B project that examined mapping between provincial interfaces and FHIR...
FHIR Implementation Community - Solution Architecture Call (2019-07-12 2pm-3pm EST) Minutes 07/12/19
Attendees: Ken Sinn Joel Francis Anne Belford Natalya Pogrebetsky Randy Nonay (Alberta) Alex Goel Rita Pyle Thomas Zhou Finnie Flores Janice Spence Iryna Roy Sisira De Silva (NLCHI) Agenda: Review/C...
FHIR Implementation Community - Solution Architecture Call (2019-06-14 2pm-3pm EST) 07/12/19
I can chair the meeting for July 12th, and run through the agenda. Current Agenda Items: * Review/Confirm proposal for Simplifier project naming conventions * Answer any questions on the URI Registry Process * Update on FHIR CA-Core (Canadian B...
FHIR Implementation Community - Solution Architecture Call (2019-06-14 2pm-3pm EST) 07/12/19
The meeting scheduled for today July 12th is cancelled? I wanted to add the URI Registry process discussed on the HL7 call to the agenda in case they were any pending questions.
FHIR Implementation Community - Solution Architecture Call (2019-06-14 2pm-3pm EST) 07/12/19
Unfortunately, I will be traveling on July 12th with no or limited access to Internet. The Project Name/Description Proposal of eHealth Ontario is the only item on our agenda. Ken, if you are able to attend, please lead the discussion. Otherwise,...
Canadian FHIR Baseline Profiles - Governance Stream Meeting - July 5th, 2-3pm EST 07/10/19
Also on the call: - Francis Lau - Joel Francis - Craig Anderson - Radhika Verma - Sisira De Silva There was concern raised about overall workload to review the significant number of resources/profiles, particularly as a volunteer activity....
Canadian FHIR Baseline Profiles - Governance Stream Meeting - July 5th, 2-3pm EST 07/08/19
Attendees • Michael Savage • Andrea MacLean • Finnie Flores • Ben Macerola • Alan L • Harsh Sharma • Igor Sirkovich • Sheridan Cook • John Wills • Ken Sinn • Laura • Randy Nonay • Smita Kachroo • Fariba Behzadi Key Links: • Sim...
OID request - Alberta Delivery Site Identifiers 07/04/19
We are requesting that OID 2.16.840.1.113883.4.289 be deprecated, and 2 new OIDs to represent delivery site identifiers be created to replace it. This is because implementers have used the existing OID for two different identifier sets and we need to...
Canadian FHIR Baseline Profiles - Governance Stream Meeting - July 5th, 2-3pm EST 07/03/19
Hi all! Just posting this as a reminder re: the agenda for this Friday's Governance meeting (see prior post in this thread). I had sent it out Friday afternoon so just want to make sure it doesn't get buried in people's inboxes. -Mike
Cross Post - Innovation Lab webinar: Innovation in Consumer Health 07/02/19
Hello, Are you interested in building digital health applications and/or learning about the exchange of health care information? If so, you may benefit from attending our next Innovation Lab webinar! Join us on July 16th at noon for a walk-through...

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 )

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

  • Object Identifier (OID)
  • TermManager
  • 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. 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.

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

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 Sundays at midnight. 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

Joel Francis
Canada Health Infoway
Déconnecté(e)
Personne-ressource
Linda Monico
Canada Health Infoway
Déconnecté(e)
Admin
Greg Violette
Accreon Inc.
Déconnecté(e)
Membre
Anil Patel
n/a
Déconnecté(e)
Membre
Scott Prior
n/a
Déconnecté(e)
Membre
Michelle O'Keefe
Sierra Systems
Déconnecté(e)
Membre
Pennylane MacDonald
n/a
Déconnecté(e)
Membre
James Mitchell
Royal Victoria Regional Health Centre
Déconnecté(e)
Membre
Ramandeep Dhanoa
Northern Health
Déconnecté(e)
Membre
Jorge Alejandro Pichardo
Island Health
Déconnecté(e)
Membre
Amaria Wachanga
Clinic
Déconnecté(e)
Membre
Maher Salah
CGI
Déconnecté(e)
Membre
steven wong
McMaster University
Déconnecté(e)
Membre
Patrick Pyette
Perimind Corporation
Déconnecté(e)
Membre
Kinson Ho
McKesson
Déconnecté(e)
Membre

Au rythme où les technologies de santé numériques sont adoptées, les Canadiens obtiennent collectivement des avanta… https://t.co/7YdWTbUbRt

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