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: 151
Personne-ressource: Attila Farkas
Administration: Andrew Liu, 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 & CDS Hooks

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

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/01/10/1268 Draft Agenda: 1. Agenda & Action Items Review a. Action Item Progress 2. Updates: a. FHIR North 3. Updates From Stream Leads a. eReferral b. Tooling c. Solution Architecture d. SMART on FHIR / CDS Hooks If there are any additional items, please comment in this thread in advance of the meeting (Wednesday January 24th, 12-1)
Attila Farkas a répondu au cours d'une discussion dans le groupe FHIR® Implementations
The SMART on FHIR track resumes this year with a look at OAuth2 and OpenID. Make sure not to miss this very important topic this upcoming Friday. Event details available here: .... See you on Friday at 2pm EDT.
Josh Haskins 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.
D S 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.
Attila Farkas a lancé une nouvelle discussion dans le groupe FHIR® Implementations
Hi everyone, I am creating a new thread for the FHIR Registry where we can list the enhancements that are implemented to the Simplifier.NET platform that is powering our registry. These updates are coming on a monthly basis so knowing about them can help you work smarter. Here are the highlights for the January release 17.7: Implementation Guide Editor The new IG Editor includes two new features. You can now export your IG to static HTML pages, which can be hosted anywhere. This is useful when publishing milestones and to comply with organizational publishing policies. The IG Editor's intellisense feature displays projects and resources on Simplifier.net on the fly. Diff Viewer The Diff Viewer 2.0 displays differences between two versions of a resource. Go to the history tab of a resource, select two versions and click the compare button to see the renewed Diff Viewer in action. Validate We added a new way to validate your profiles and instances. Next to validating snippets or resources in your project, you can use the validator without needing to log in or upload resources. Copy and paste FHIR content here. The Profiling Academy We added a terminology module to the Profiling Academy, the free online learning platform on FHIR profiling. Includes exercises.
Christopher Parisien 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.
Doug Allan 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.

Événements



Événements à venir :
Ven Jan 19 @ 2:00PM - 03:00PM
SMART on FHIR bi-weekly call
Mar Jan 23 @11:00AM - 12:00PM
FHIR eReferral Spec Working Group
Mer Jan 24 @12:00PM - 01:00PM
FHIR Community - monthly tcon

Forum

FHIR Implementers' Community Call - January 24, 12-1 EST 01/17/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/...
SMART on FHIR - CDS Hooks workstream 01/17/18
The SMART on FHIR track resumes this year with a look at OAuth2 and OpenID. Make sure not to miss this very important topic this upcoming Friday. Event details available here: .... See you on Friday at 2pm EDT.
Canadian FHIR Registry - updates 01/12/18
Hi everyone, I am creating a new thread for the FHIR Registry where we can list the enhancements that are implemented to the Simplifier.NET platform that is powering our registry. These updates are coming on a monthly basis so knowing about them c...
eReferral Spec Development work stream 01/09/18
Hello, a reminder for todays FHIR eReferral working group meeting. Today we will be discussing the /task resource. Tuesday, November 28, 2017, 11:00am - 12:00pm ET Previous RepeatNext Repeat by Tim Berezny Biweekly meeting regarding the de...
Webinar: Advancing FHIR in Canada 01/08/18
hi Everyone, Happy 2018! I'm looking forward to working together with you to make this a big year for FHIR collaboration and implementation. Attila and I will be co-presenting a webinar this Wednesday (noon - 1PM ET) about the past, present an...
Upcoming HL7 Community Call on January 9th at 12pm Eastern 01/05/18
Please join us for the next HL7 Community Call on Tuesday, January 9th at 12pm Eastern. Here is the current agenda: 1) HL7 Ballot Review 2) January HL7 Working Group Meeting (including CDA Implementation-A-Thon and FHIR Connect-A-Thon) 2a) Wh...
Reminder - FHIR Implementers' Community Call - December Cancelled 12/20/17
Hi all, Just a reminder that the community-wide FHIR Implementers' Community Call for December is cancelled. The next call is scheduled for Wednesday January 24th 2018, 12-1 EST. Thank you! - Michael Savage
SMART on FHIR - CDS Hooks workstream 12/15/17
The SMART on FHIR Architecture deeper dive meeting just concluded. The recording is posted in the Video tab and the agreement was to resume in the new year with leg #two of the journey, an overview of the OAuth2 specification, OpenID and investigate...
Solution Architecture work stream 12/12/17
Hello All, We take a break from the meetings for the winter holidays. Our meetings will resume on Friday, January 12 at 2 pm and from there, will be scheduled to every other week, alternating Fridays with the Smart on FHIR stream. Please join t...
eReferral Spec Development work stream 12/12/17
Hello, a reminder for todays FHIR eReferral working group meeting. Today we will be discussing REST vs. messaging, OAuth, the /subscription resource, and possibly /task resource. Tuesday, November 28, 2017, 11:00am - 12:00pm ET Previous RepeatN...
Dec 1 & 8: FHIRbase/AidBox and OntarioMD Hospital Report Manager Presentations 12/08/17
Hello Everyone, Please join the FHIR Solution Architecture stream call today at 2:00 pm EST for a presentation by Chris Mota from OntarioMD of the Ontario FHIR-based Hospital Report Manager (HRM) solution. Join from PC, Mac, Linux, iOS or And...
Tooling work stream 12/08/17
Hi everyone, don't forget about the Tooling stream demo of Simplifier today at 11:00am. Coordinates here: ...
Upcoming HL7 Community Call on December 5th 11/30/17
Our next HL7 Community Call will be on December 5th at noon eastern. Please join us as we will be having a presentation from Attila Farkas of Infoway on FHIR. This is the FHIR presentation that Attila made at the recent Partnership Conference....
Dec 1 & 8: FHIRbase/AidBox and OntarioMD Hospital Report Manager Presentations 11/28/17
I would like to invite all FHIR Implementation community members to join the FHIR Solution Architecture stream on December 1st at 2:00 pm EST for a presentation by Pavel Smirnov and Nikolai Ryzhikov of FHIRbase (http://fhirbase.github.io), an open so...
eReferral Spec Development work stream 11/28/17
Hello, a last minute reminder for today's eReferral EG meeting. Tuesday, November 28, 2017, 11:00am - 12:00pm ET Previous RepeatNext Repeat by Tim Berezny Biweekly meeting regarding the development of an eReferral FHIR specification https://...

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 )

Client Registry ( 0 Document )

Consent Management ( 0 Document )

eReferral ( 0 Document )

Meeting Materials ( 0 Document )

Provider Registry ( 0 Document )

Tooling ( 0 Document )

Vidéo

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
SMART on FHIR - Architecture

A deeper dive into the SMART on FHIR architecture

12/15/17

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 (normally $100 USD fee per OID request).

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 which is provided by request for free 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.

 Education

  • Introduction to SNOMED CT (English)
  • Introduction to SNOMED CT (French)
  • Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.

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 IHTSDO 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 what HL7 Explorer can do for you with this brief online presentation.

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

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
 

Submit or follow requests to SNOMED CT

pCLOCD/LOINC
 

Submit or follow requests to pCLOCD/LOINC

pan-Canadian Subsets
 

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

Attila Farkas
Canada Health Infoway
Connecté(e)
Personne-ressource
Andrew Liu
Canada Health Infoway
Déconnecté(e)
Admin
Linda Monico
Canada Health Infoway
Connecté(e)
Admin
Josh Haskins
Northern Health Authority
Déconnecté(e)
Membre
D S
n/a
Déconnecté(e)
Membre
Christopher Parisien
NexJ Health
Déconnecté(e)
Membre
Doug Allan
eHealth Ontario
Déconnecté(e)
Membre
Asiya Shams
The Ottawa Hospital
Déconnecté(e)
Membre
Terry Waldron
Kingston General Hospital
Déconnecté(e)
Membre
Cassiano Moralles
PUCRS
Déconnecté(e)
Membre
Jason Lin
TELUS Health
Déconnecté(e)
Membre
Debbie Onos
Alberta Health Services
Déconnecté(e)
Membre
Paul Tagl
McKesson
Déconnecté(e)
Membre
Maria Sauco
Canada Health Infoway
Déconnecté(e)
Membre
Tib Onu
Canada Health Infoway
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