Partager :

Le contenu créé par les communautés et les groupes de travail est accessible dans la version originale seulement.

Enterprise Solution and Integration Architecture
Focusing on the structuring of business processes, information assets, and digital technologies to meet the needs of individual and organizational health care providers and patient communities across Canada
Membres: 103
Personne-ressource: Ron Parker
Administration: Linda Monico
Type: Ouvert
Accès: Public
Focusing on the structuring of business processes, information assets, and digital technologies to meet the needs of individual and organizational health care providers and patient communities across Canada

À propos de nous

Activité

Pakizah Kozak s'est joint(e) à un groupe
Logo
Focusing on the structuring of business processes, information assets, and digital technologies to meet the needs of individual and organizational health care providers and patient communities across Canada
Mike Gifford a lancé une nouvelle discussion dans le groupe Enterprise Solution and Integration Architecture
Accessibility needs to be baked into this solution. It needs to be accessible by default, which means that solutions need to be thinking about this now. Citizens with all abilities need to be able to perceive, operate and understand this technology in a robust framework. This needs to be built into both the technology chosen as well as the the procurement process itself. I've got some best practices listed here: https://github.com/mgifford/a11y-contracting/ What is being done to see that we can meet WCAG 2.0 on both the front-end & back-end of the the digital interface? What can be done to ensure that it meets WCAG 2.1 and is future compatible?
Mike Gifford a lancé une nouvelle discussion dans le groupe Enterprise Solution and Integration Architecture
We've got a lot of catching up to do if we are able to have Canadian's trust in a centralized system. It really needs to be based on principles like they have implemented in Estonia http://estonianworld.com/security/right-mix-estonia-ensures-privacy-access-e-services-digital-age/ Health Care is central to Canadian governments. We need to ensure that we have Canadian's trust with their data. Privacy has to be built in by default.
Mike Gifford s'est joint(e) à un groupe
Logo
Focusing on the structuring of business processes, information assets, and digital technologies to meet the needs of individual and organizational health care providers and patient communities across Canada
Robin Dilawri s'est joint(e) à un groupe
Logo
Focusing on the structuring of business processes, information assets, and digital technologies to meet the needs of individual and organizational health care providers and patient communities across Canada
Poonam Khanna s'est joint(e) à un groupe
Logo
Focusing on the structuring of business processes, information assets, and digital technologies to meet the needs of individual and organizational health care providers and patient communities across Canada
Bill Gordon s'est joint(e) à un groupe
Logo
Focusing on the structuring of business processes, information assets, and digital technologies to meet the needs of individual and organizational health care providers and patient communities across Canada

Forum

WCAG 2.0 & ATAG 2.0 Standards 04/05/18
Accessibility needs to be baked into this solution. It needs to be accessible by default, which means that solutions need to be thinking about this now. Citizens with all abilities need to be able to perceive, operate and understand this technol...
A secure X-road to Estonia's the central health information system 04/05/18
We've got a lot of catching up to do if we are able to have Canadian's trust in a centralized system. It really needs to be based on principles like they have implemented in Estonia http://estonianworld.com/security/right-mix-estonia-ensures-privacy...
Participate in the pilot course: SNOMED CTfor Developers 10/19/17
SNOMED International has developed a new crash course for software developers. This course is available to those who need to learn quickly about SNOMED CT and leverage the capabilities of the terminology. For more information on this course pilot...
Ontario’s EHR Interoperability Plan |Open review April 19 – May 18 | Your Input Requested 04/28/17
Ontario’s EHR interoperability plan has now been developed and is ready for provincial review. Its purpose is to summarize the current state of EHR interoperability in the province, anticipate where and when further interoperability should be enable...
Barcoding and RFID 02/27/17
Island Health has just launched a working group to help support development of a regional barcoding and RFID strategy. We are assembling current state right now. The scope of our analysis at the current time is broad with an ultimate focus on wo...
Worlds Standards Day – October 14 , 2016 10/11/16
In less than a week, the agency will be celebrating “Worlds Standards Day – October 14” and this year is shaping up to be another spectacular event! The eHealth Standards Program is very excited, for the sixth year, to be hosting an event on behalf o...
Your Input Wanted – review the refreshed information view of Ontario's eHealth Blueprint 04/08/16
Open review runs April 7 to May 9, 2016 Ontario’s Ehealth Blueprint is the key to electronic health record (EHR) planning and delivery. Developed in collaboration with stakeholders across the province, it is comprised of three “views” – business,...
Reminder for Today's Webex 12/09/15
Hey Everyone... Just a reminder that were is a ... for the ESIA Community where Eric will be presenting on Ontario's Consent Model. In this presentation, Eric will be discussing: Ontario's strategic objectives for consent Current Ontario co...
Kickoff Webex for ESIA on Dec 9th 11/24/15
Hey Everyone... thanks for signing up or the Enterprise Solution and Integration Architecture group. Eric Labadie and Ron Parker are hosting a WebEx on Dec 9th to introduce some topics of interest to this group, as well as to solicit your feedbac...
eHealth Ontario CDR Input specification review 10/23/15
Hello, Starting October 26, eHealth Ontario will be hosting an open review for the ConnectingOntario Clinical Data Repository (CDR) Input Specification. The ConnectingOntario CDR supports patients by providing care teams with a central point of...
Please Introduce Yourself 07/31/15
Hi everyone, I am an Enterprise Architect working with the BC Ministry of Health and Rick Connoly is our Director. Amen
BC Health Segmentation Model 07/31/15
Hi everyone I am an Enterprise Architect with the BC MoH. I am interested to see how other provinces and health jurisdictions have depicted their Health Landscape within a segmentation model. We are working on a model and would like to collaborate...
Help shape this year's Partnership program 07/21/15
The date is set and the Infoway Partnership Conference 2015 is planned for November 24th-25th in Vancouver, BC. Respond to this ..., or reply to this post to tell us your thoughts on how you’d like to see clinical interoperability featured at this ye...
Federated provider identifiers 07/17/15
I get an Error 404 when trying to access the reports
eHealth Ontario Connectivity Strategy 07/06/15
On July 1st, 2015 eHealth Ontario launched the province’s EHR Connectivity Strategy, which describes how health care information will be connected to create a safe, cost-effective, provincially-integrated electronic health record (EHR). Based on...

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.

Federated Identity in Health Care Presentation

Publié le 26 Jui, 2015 par Ron Parker

Vidéo

Ce groupe n'a pas de video.

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.

!-

 Education

 Maintenance

-->

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

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

Ron Parker
Canada Health Infoway
Déconnecté(e)
Personne-ressource
Linda Monico
Canada Health Infoway
Connecté(e)
Admin
Pakizah Kozak
SKH
Déconnecté(e)
Membre
Mike Gifford
OpenConcept Consulting Inc.
Déconnecté(e)
Membre
Robin Dilawri
Manitobs eHealth
Déconnecté(e)
Membre
Bill Gordon
Applied Informatics for Health Society
Déconnecté(e)
Membre
Cheryl Ulmer
Fraser Health Authority
Déconnecté(e)
Membre
Lydia Akiru
Centre for distance education
Déconnecté(e)
Membre
Andrew Cummings
Regional Muncipality of York / McMaster
Déconnecté(e)
Membre
Sheng Fang
eHealth Ontario
Déconnecté(e)
Membre
Mike Krasnay
eHealthOntario
Déconnecté(e)
Membre
Annick Arrand
CD-ED
Déconnecté(e)
Membre
Tue Hoang
Caredove
Déconnecté(e)
Membre
Anna Morrison
-
Déconnecté(e)
Membre
John Breakey
Fivel Systems
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