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: 191
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 three 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.

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é

Yaron Derman a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Draft Meeting Notes Attendees: 1. Gavin Tong 2. John Wills 3. Attila Farkas 4. Finnie Flores 5. Igor Sirkovich 6. Ken Sinn 7. Shamil Nizamov 8. Janice Spence 9. Ben Macerola 10. Yaron Derman ACTION ITEM 11:28:1: Michael to close the 2nd and 3rd action items ACTION ITEM 11:28:2:Report back to group when R4 will be published API Toolchain - Ontario exploring if a collection of tools can be 'knitted' together so that the output of one is the input of the next to minimize the amount of 'handcrafting' from profile definition to functional API Infoway was moving in this direction two years ago. Wrote a utility to convert the from Simplifier to SWAGGER but not at production grade - Graham Grieve has been promoting this tool to convert FHIR to SWAGGER - https://github.com/bobby-brennan/fhir-swagger - Suggestion to ask James Agnew in his experience with HAPI - CIHI has implemented FHIR for IRIS - Shamil has used Touchstone and found the UI may take time to learn Value Set Creation Tool ○ To enable creation of locally developed value sets ○ Graham mentioned a tool but it hasn't been updated since 2017 http://healthintersections.com.au/FhirServer/ ○ Terminology Gateway API is not an editor - it's a presentation layer and version control ACTION ITEM 11:28:3: Finnie to connect eHealth Standards with CIHI team (COMPLETED) ACTION ITEM 11:28:4: Gavin will contact colleagues working at MU conformance testing centers to see if they have experience with testing tools Canadian FHIR Baseline Profiles - Thanks to everyone that commented and reached out on the topic - Value to have a set of read-only profiles of the data that one could expect to receive back (query rather than put) - Would be an accelerator for vendors/jurisdictions when defining profiles by providing guidance on what/how to handle Canadian data needs - No mandate or restriction - Attila proposed working together towards a Canadian version/update to the Argonaut profiles - Infoway Access Health project will be first Canada-wide scope of production FHIR APIs - 4 RFPs to be released, some to include 'connectors' from jurisdictional E H R to Access - As the project progresses, there will be paid resources to help move this forward; this group provides guidance to this at that point - Need a 'project initiator', 'project manager' and 'core development team' roles ○ Project initiator - Attila ○ Project manager - Michael Savage (pending his acceptance) ○ Hands on keyboard - Shamil, Igor, Ken, Finnie ○ ACTION ITEM 11:28:5: Gavin will ask Michael and/or others around project manager role No meeting in December
Yaron Derman a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Dear FHIR Community Colleagues Starting December 12, 2018 – January 17, 2019, we will be launching an open review for the Ontario Laboratory Information System (OLIS) HL7 FHIR Consumer Query implementation guide V1.0 Scope OLIS is a cornerstone information system that connects hospitals, community laboratories, public health laboratories, practitioners and patients to facilitate the secure electronic exchange of laboratory test orders and results. The OLIS FHIR Implementation Guide provides consumers application developers with an interface specification to query OLIS using the FHIR STU3 standard. Delivery of this interface is a key milestone towards FHIR based interoperability in the province of Ontario. The current OLIS FHIR Consumer Query interface is designed for consumer application use and supports view-only laboratory data. A webinar will be hosted for the open review: • An introductory webinar will be hosted on December 18 to review the material and explain the process for submitting feedback. Webinar materials and recordings will be made available on basecamp. Anticipated Key Dates: 1. December 18: Webinar Session 2. Dec 12, 2018 – Jan 17, 2019: Provincial Review 3. Jan 18 – Feb 13: Comment reconciliation period 4. Feb 20: BTC Meeting to recommend for SC approval 5. March 21: SC Meeting to approve Please circulate this email with your stakeholders. Contact us at architecture@ehealthontario.on.ca for questions about how you can participate in this provincial review.
Michael Savage a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hi all! The draft agenda for the FHIR Implementations Community Call is below. As a reminder, the calendar invite with connection details can be found on the event calendar here: https://infocentral.infoway-inforoute.ca/en/news-events/event-calendar/month.calendar/2018/11/28/1268 Draft Agenda: 1.Agenda & Action Items Review a.Action Item Progress 2.Updates: a.Community Direction(s) for the New Year b.FHIR Baseline Profile Discussion(s) Synopsis c.Meeting Frequency 3.Updates From Stream Leads a.eReferral b.Tooling c.Solution Architecture d.SMART on FHIR If there are any additional items, please comment in this thread in advance of the meeting (Wednesday Nov 28th, 12-1)
Deepti Razdan 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.
Sophia Wong 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.
Sean Mikalson 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.
Joel Francis a répondu au cours d'une discussion dans le groupe FHIR® Implementations
The OIDs have now been deprecated

Événements



Événements à venir :
Ven Déc 14 @ 2:00PM - 03:00PM
FHIR Solution Architecture
Ven Déc 21 @ 2:00PM - 03:00PM
SMART on FHIR four-weekly call
Mer Déc 26 @12:00PM - 01:00PM
FHIR Community - monthly tcon

Forum

FHIR Implementers' Community Call - November 28, 12-1 EST 11/28/18
Draft Meeting Notes Attendees: 1. Gavin Tong 2. John Wills 3. Attila Farkas 4. Finnie Flores 5. Igor Sirkovich 6. Ken Sinn 7. Shamil Nizamov 8. Janice Spence 9. Ben Macerola 10. Yaron Derman ACTION ITEM 11:28:1: Michael to...
OLIS HL7 FHIR Consumer Query - Open Review 11/23/18
Dear FHIR Community Colleagues Starting December 12, 2018 – January 17, 2019, we will be launching an open review for the Ontario Laboratory Information System (OLIS) HL7 FHIR Consumer Query implementation guide V1.0 Scope OLIS is a cornerston...
FHIR Implementers' Community Call - November 28, 12-1 EST 11/21/18
Hi all! The draft agenda for the FHIR Implementations Community Call is below. As a reminder, the calendar invite with connection details can be found on the event calendar here: https://infocentral.infoway-inforoute.ca/en/news-events/event-cal...
More Duplicated OIDs for deprecation 11/15/18
The OIDs have now been deprecated
General Canadian FHIR Baseline Feedback 11/12/18
Maybe Ontario could use FHIR as a face-saving excuse to drop the version code and expiring health cards, altogether. ;)
General Canadian FHIR Baseline Feedback 11/12/18
The is an issue with merging the version number. In Ontario the Health Card Expires every 5 years and when a new card is issued you get a new Version Code. There is a need to track the expiration date of the Health Number as well.
General Canadian FHIR Baseline Feedback 11/12/18
... The Ontario "version code" is a simple billing validation check and has nothing at all to do with identifying the client. The identifier is the numeric health card number; the version code is changed every time a new health card is issued (On...
General Canadian FHIR Baseline Feedback 11/12/18
Agree that the use of extensions should be minimized and that systems should be expected to support the core address elements. (If they want discrete components too, that's ok, but that shouldn't be part of pan-Canadian core and doesn't replace the...
General Canadian FHIR Baseline Feedback 11/12/18
A few thoughts: 1. eReferrals can be a really big application for base profiles, both for direct transmission and for SMART on FHIR methods. 2. Ontario version code seems to cause all manner of discussions and headaches. Why not just merge vers...
General Canadian FHIR Baseline Feedback 11/11/18
That's true when the PHN is sent for coverage purposes, but not when it's sent as a general purpose identifier - as is often the case. An extension on identifier (possibly one that's also used for credit card verification numbers) would be fully app...
General Canadian FHIR Baseline Feedback 11/11/18
Hi Gavin: the 'health card number version code' would go in Coverage.class (.type=sequence, .value=version code/number). Regards Paul
General Canadian FHIR Baseline Feedback 11/10/18
I'd limit it to human medicine with primary focus on information relevant to outpatients as part of a cross-practitioner shared record. In addition to SMART, I'd list CDS Hooks. So standardizing terminologies where we can (reflecting existing pan-C...
Editor to build resource 11/09/18
Hi, Please see an editor to easily create FHIR Resources: http://docs.smarthealthit.org/fred/ This might be useful for those without much experience using JSON or XML. Thanks, Joel
General Canadian FHIR Baseline Feedback 11/09/18
Hi, If you have use cases for Canadian Baseline profiles can you please share them here? We'd like to frame the next FHIR WG call about assessing the value of creating national FHIR profiles. There is concern that if the scope is too broad, then...
Report suggests US health IT approaching FHIR tipping point 11/08/18
A very interesting read: https://www.digitalhealth.net/2018/11/report-suggests-us-health-it-approaching-fhir-tipping-point/ New US analysis suggests the country is approaching a “turning point” in the implementation of interoperability standards f...

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)
  • 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)

  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.

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 Sunday nights. 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
Deepti Razdan
cd-ed
Déconnecté(e)
Membre
Sophia Wong
Vancouver General Hospital
Déconnecté(e)
Membre
Sean Mikalson
QHR Technologies
Déconnecté(e)
Membre
Stefanie Pranoto
PHSA
Déconnecté(e)
Membre
Fowzia Mahamed
EduCare
Déconnecté(e)
Membre
Bryan Bergen
QHR Technologies
Déconnecté(e)
Membre
Michel Boivin
CGI
Déconnecté(e)
Membre
Moazzam Khan
Alberta Health
Déconnecté(e)
Membre
Abdullah Khan
-
Déconnecté(e)
Membre
Ross Shnaper
CIHI
Déconnecté(e)
Membre
Lentic Li
University of Victoria
Déconnecté(e)
Membre
Brian Vuyk
TouchIntel
Déconnecté(e)
Membre
Ovidiu Girlan
MOHLTC
Déconnecté(e)
Membre
No tweets found.

logo inv fr

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