Vous avez jusqu'au 27 juin 2018 pour présenter des candidatures au tout nouveau rôle de responsable de la nouvelle communauté Terminologies de la santé. 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: 173
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

Attila Farkas (Infoway)

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
Tooling

Attila Farkas (Infoway)

Frederic Laroche (Gevity Inc.)

Main focus of the working group is the discovery, identification, implementation and education surrounding tooling and best practices for FHIR development in Canada
  1. Identified a logical capability model that enables collaborative FHIR development, support digital integration and sharing
  2. Concluded discovery phase for the core component of the model - the FHIR Registry
  3. Launched the Canadian FHIR Registry at the September 2017 FHIR Community meeting
Client & Provider Registries

Kris Lewis (Sierra Systems)

Natalya Pogrebetsky (eHealth Ontario)

Define FHIR PR and CR use cases
  1. Ontario shared PR and CR specs with the working stream and provided business and technical overview
  2. PR/CR working group working on Canadian FHIR use cases
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.
Business Case for FHIR

Attila Farkas (Infoway)

Shamil Nizamov (BC MoH)

Creation of reference material for those new to FHIR on the benefits of its adoption
  1. Concluded a storming phase identifying aspects relevant to a business case
  2. Collected community feedback and published a baseline of best practices.
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 lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hi everybody, Ontario will be launching an HL7 FHIR query option for its provincial client registry in the near future. In case you are interested, below are details for an upcoming webinar that will provide a detailed review of the contents of the iGuide. (NOTE: unfortunately, the webinar conflicts with the next FHIR community call :-( ) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To assist with the review of the PCR HL7 FHIR Implementation Guide (iGuide), a second in-depth walkthrough and live feedback session is being offered. The purpose of the second webinar to offer an in-depth walkthrough of the PCR FHIR iGuide. The goals of this walkthrough are to offer participants an opportunity to receive a ‘guided tour’ of the new online format for Ontario’s FHIR iGuide, gain exposure to how FHIR is profiled and to collect ‘real-time’ comments and feedback from participants for inclusion in the open review. The PCR HL7 FHIR material includes: • PCR HL7 FHIR Implementation Guide • Terminology value sets • Sample messages The open review comment period will take place from June 20-July 19. Information on how to provide comments will be included in the webinar. The link to access the PCR HL7 FHIR Specification can be found here: https://www.ehealthontario.on.ca/en/standards/view/provincial-client-registry-fhir/ Please circulate this email with your stakeholders. Contact us at architecture@ehealthontario.on.ca for questions. Presenters: Fang Cao, Senior Standards Analyst, eHealth Ontario Yaron Derman, Manager Standards, eHealth Ontario Wednesday, June 27, 11:30 - 1:00 ET Teleconference & WebEx: https://ehealthontario.webex.com/ehealthontario/j.php?MTID=m400c47d1dd10b909e8023b4a16dc9629 Local:416-212-8011 TFN#1 866-602-5461 Conference ID:6302256#
Michael Savage a lancé une nouvelle discussion dans le groupe FHIR® Implementations
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/monthly-calendar/month.calendar/2018/06/21/1268 Draft Agenda: 1.Agenda & Action Items Review a.Action Item Progress 2.Updates: a.Update on FHIR versioning b.Feedback on iGuide 3.Updates From Stream Leads a.eReferral b.Tooling c.Solution Architecture d.SMART on FHIR
Igor Sirkovich a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Randy, I'm glad to see you back. We had assigned an URI https://fhir.infoway-inforoute.ca/NamingSystem/ca-ab-health-service-provider-id to HSPID a few weeks ago (it was posted on this forum for comments back then) and I just wanted to confirm that this URI is fine with you. Harsh, I think we should assign an URI to MINC, but we cannot mandate the use of MINC and the reality is that so far, it's rarely been used by eHealth projects across Canadian jurisdictions. Ken, I'm not convinced we should stick to the colleges' definitions. I would rather reflect in the URI name the real meaning of these URIs to FHIR consuming systems. Also, colleges might change their definitions over time, but we would need to keep these URIs stable unless the numbering system changes as well.
Randy Nonay a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Hi all, I'm back after a 3 month absence. Sorry for not being able to participate... In Alberta, we use the term "License Number" or more completely "College License Number" for the various college's licenses. We also have "Health Service Provider Identifier" (HSPID) which is a number assigned " to each person of interest to the health industry, irrespective of their health service role." So in keeping with the discussion, I'd think that using eg. "ca-ab-license-occupational-therapist" would be the expected URI for our license numbers, and "ca-ab-Identifier-health-service-provider" for our HSPID. I'm not sure using MINC is viable because I don't think we record this at present in Alberta Provider registry. (I'll have to confirm this). Maybe as a future alternate identifier, but I wouldn't use it as the main identifier in Alberta (yet). One problem I see with MINC is that it conveys no information at all about a persons' currently active license(s). Most usage we have is concerned with the license being active, and that the person is allowed to perform the service. Randy
Harsh Sharma a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Hello, I agree with Igor. We should look at this from a consumer of information standpoint. In Canada, based on the jurisdiction, the identifiers could be managed differently with provincial customization. In order to achieve a semantic standardization, Can we use Medical Identification Number for Canada (MINC) instead of License #/Registration # ? Reason: Its a unique identifier assigned to every individual entering the Canadian medical education or practice system. An individual's MINC will not change throughout their entire medical career. It stays the same if they leave Canada and return, or move between Canadian jurisdiction, or change registration status. Even after they pass away, an individual's MINC will not be reassigned. Sample: CAMD-1234-5679 CA - Canada MD - MD for Physicians Next 7 digit serial number with no encoding info. 8th digit is a Check digit. Thanks so much! Harsh
Ken Sinn a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Under the Ontario Regulated Health Professions Act (1991), members are licensed for the Royal College of Dental Surgeons, CPSO, College of Optometrists, and Ontario College of Pharmacists. Since then, other colleges have members that are registered under their respective acts, e.g. members are registered to the College of Chiropodists under the Chiropody Act, College of Massage Therapists under the Drugless Practitioners Act, College of Psychologists under the Psychologists Registration Act. I think the general idea of "licenced" providers is because we usually focus on members of the CPSO, who are traditionally licenced. That said, for the purposes of URIs, we should really use the official terminology from each Ontario college, as they are the authoritative source. We can add "licensed/registered" within the description for clarity, but we should defer to the legal definitions.
Igor Sirkovich a répondu au cours d'une discussion dans le groupe FHIR® Implementations
Thank you Peter. I'm wondering if you can post a link to a web page that describes how Health Canada differentiates between the license number and the registration number. This would be important for our discussion.

Événements



Événements à venir :
Mer Jui 27 @12:00PM - 01:00PM
FHIR Community - monthly tcon
Ven Jui 29 @ 2:00PM - 03:00PM
FHIR Solution Architecture
Ven Juil 06 @ 2:00PM - 03:00PM
SMART on FHIR four-weekly call

Forum

Ontario Provincial Client Registry HL7 FHIR Implementation Guide In-depth review 06/21/18
Hi everybody, Ontario will be launching an HL7 FHIR query option for its provincial client registry in the near future. In case you are interested, below are details for an upcoming webinar that will provide a detailed review of the contents of t...
FHIR Implementers' Community Call - June 27, 12-1 EST 06/21/18
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/monthly-calendar/month.calendar/...
Solution Architecture work stream 06/15/18
Randy, I'm glad to see you back. We had assigned an URI https://fhir.infoway-inforoute.ca/NamingSystem/ca-ab-health-service-provider-id to HSPID a few weeks ago (it was posted on this forum for comments back then) and I just wanted to confirm that th...
Solution Architecture work stream 06/15/18
Hi all, I'm back after a 3 month absence. Sorry for not being able to participate... In Alberta, we use the term "License Number" or more completely "College License Number" for the various college's licenses. We also have "Health Service Pr...
Solution Architecture work stream 06/15/18
Hello, I agree with Igor. We should look at this from a consumer of information standpoint. In Canada, based on the jurisdiction, the identifiers could be managed differently with provincial customization. In order to achieve a semantic stand...
Solution Architecture work stream 06/15/18
Under the Ontario Regulated Health Professions Act (1991), members are licensed for the Royal College of Dental Surgeons, CPSO, College of Optometrists, and Ontario College of Pharmacists. Since then, other colleges have members that are registere...
Solution Architecture work stream 06/15/18
Thank you Peter. I'm wondering if you can post a link to a web page that describes how Health Canada differentiates between the license number and the registration number. This would be important for our discussion.
Solution Architecture work stream 06/15/18
Good Morning, I have verified that there are cases where Health Canada differentiates between the license number and the registration number. I am aware that the answer does not relates specif icily to the question below, but wanted to make you awar...
Solution Architecture work stream 06/14/18
Hello Everyone, We are seeking feedback of the group on a few UR-related topics. In Ontario we have a notion of LHINs (Local Health Integration Networks), which are essentially 14 regional health authorities with sequential identifiers ranging...
Cross Posting: HL7 International collecting data on FHIR Usage Worldwide 06/14/18
Is there a closing date of the survey?
Cross Posting: HL7 International collecting data on FHIR Usage Worldwide 06/14/18
In order to better serve you and the greater FHIR community, HL7 is gathering information about FHIR usage worldwide. Your responses to a brief survey will help us guide the development of the FHIR standard in the coming years to ensure that your nee...
SMART on FHIR - CDS Hooks workstream 06/13/18
Hey everyone, In line with our decision last Friday, I have updated the calendar and zoom meeting for SMART Friday. You may want to go and download the new calendar item into your own to have them up to date.
eReferral Spec Development work stream 06/12/18
Hello all, A friendly reminder of Tuesday's eReferral call at 11am. Here is the agenda: 1) updates on service directory 2) Invitation to do video demos of integration from FHIR North see existing demos here: https://simplifier.net/guide/eReferr...
SMART on FHIR - CDS Hooks workstream 06/08/18
Hi, Here's the notes from today's call: SMART on FHIR WG – 2018-06-08 Attendees: Gavin Tong, Attila Farkas, Igor Sirkovich, Joel Francis, Luis Pizarro, Shamil Nizamov, Tim Berenzy, Dustin Doan. Regrets: Mike Savage Notes Welcome and agend...
SMART on FHIR - CDS Hooks workstream 05/25/18
Hi all, Please see below for the minutes/highlights from the May 25th SMART on FHIR - CDS Hooks workstream call: Attendees: Michael Savage Attila Farkas Dustin Doan John Wills Tim Berezny Alan Leung Alex Goel Ben Macerola Igor Sirkov...

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
  • TermWorks
  • Registre FHIR Canadien
  • InfoScribe
  • 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.

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

Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.

infoscribeSupporting the Standards Selection Framework, InfoScribe enables teams to collaboratively create, discuss, and publish digital health solutions from clinical requirements to specifications. Featuring templates, versioning, PDF export, inline commenting and HL7 Explorer integration, InfoScribe improves productivity and accelerates the development of healthcare solutions.

Des exigences cliniques aux spécifications

Le Cadre de sélection des normes permet à ses utilisateurs de planifier, de choisir et de documenter des solutions d’interopérabilité depuis l’étape du concept jusqu’à celle de l’implantation. À partir des exigences cliniques établies par les cliniciens jusqu’aux exigences administratives, en passant par les normes et les spécifications techniques, le Cadre se veut un guide complet sur toutes les étapes de la création de solutions d’interopérabilité.

Le Cadre donne aussi à la communauté d’InfoCentral une occasion d’échanger sur les projets d’implantation fructueux, le choix des normes effectué à un moment précis d’un projet et les spécifications qui en ont résulté. La publication des solutions à cet endroit permettra la mise sur pied d’un répertoire de référence canadien.

clinical requirements

Exigences Cliniques décrivent les besoins en information et en déroulement du travail du clinicien pour une situation clinique particulière et pour l’échange de données cliniques. À partir des principes de l’interopérabilité clinique, on utilise un ensemble d’exigences exprimées par les cliniciens pour mettre sur pied une solution d’interopérabilité bien conçue.

business requirements

Exigences Administratives sont établies d’après les exigences cliniques et procurent une image complète de la solution à mettre au point. Des cas d’utilisation, des règles administratives et des conseils sont aussi donnés en référence pour permettre une modélisation complète de la solution.

standards selection

Sélection des Normes désigne le processus établi pour guider les équipes dans les diverses étapes de la sélection de la terminologie et des normes de messagerie. À l’aide du sujet de la requête et des diverses considérations contenues dans les formulaires fournis, les équipes d’implantation peuvent évaluer les normes accessibles et déterminer le meilleur choix ponctuel. Le processus permet aussi à la communauté d’InfoCentral d’échanger sur les projets d’implantation fructueux, ce qui favorise la normalisation par la réutilisation.

standards

Normes afont partie intégrante de la solution d’interopérabilité; elles touchent tant la terminologie, qui définit les données envoyées, que les structures de messagerie, qui définissent comment ces données sont envoyées. Le cadre fournit les critères d’accès aux normes internationales et canadiennes, ainsi que les critères d’examen en vue de faciliter l’implantation.

specifications

Spécifications procurent les détails de la solution à implanter. Ces détails comprennent : un examen des éléments de données utilisés, des échantillons des messages transférés, l’architecture du système et les spécifications de sécurité, dont l’autorisation et l’authentification.

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
Halina Labikova
Evinance
Déconnecté(e)
Membre
Greg Peres
Identos Inc.
Déconnecté(e)
Membre
Attila Farkas
Canada Health Infoway
Déconnecté(e)
Membre
Ivan Yuen
Health Quality Ontario
Déconnecté(e)
Membre
Ben Macerola
OntarioMD
Déconnecté(e)
Membre
Peter Bomberg
Health Canada
Déconnecté(e)
Membre
Saurav Bhardwaj
Future Idea Group Inc.
Déconnecté(e)
Membre
Daniel Heo
TELUS
Déconnecté(e)
Membre
A Mehta
N/A
Déconnecté(e)
Membre
Dustin Doan
CognisantMD
Déconnecté(e)
Membre
Mark VanRietschoten
QHR Technologies
Déconnecté(e)
Membre
Andrew Cummings
Regional Muncipality of York / McMaster
Déconnecté(e)
Membre
Jason Etherington
N/A
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