Partager :

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

Integrating the Healthcare Enterprise (IHE)
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Membres: 149
Personne-ressource: Derek Ritz
Administration: Andrea MacLean, Linda Monico
Type: Ouvert
Accès: Public
Health care and health information professionals collaborating to improve information sharing between health care technology systems.

À propos de nous

What is IHE?

Unlike HL7 (or ISO, or SNOMED, or WHO, etc.), IHE is not a health informatics standards development body. Rather, IHE is a standards profiling body. IHE Profiles are implementation guides – they make standards digestible, usable, and implementable. They describe, at a conformance-testable level of detail, how a portfolio of underlying standards will be employed to address the ecosystem-wide interoperability issues associated with a specific set of healthcare use cases. IHE Profiles create re-usable, digital health building blocks by “packaging up” the 5C’s:

  • Care context
  • Content specs
  • Coding specs
  • Communications specs
  • Confidentiality and security specs

The target audience for an IHE profile is the entire care delivery network. This especially includes the jurisdictional governance entities that are tasked with operationalizing plug-and-play interoperability between disparate network participants. IHE is focused on taking digital health interoperability to scale and to mitigating the risks inherent in such an effort.

What is the IHE Community?

The IHE Community is a place where health care professionals and the health information industry collaborate to improve the way health care technologies and systems share information.

To become a member of this community select Join Group in the Group Menu.

If you have an idea for a community, working group or project that will drive interoperability forward, let us know! Send your suggestions

LEADER

Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.

KEY RESOURCES

IHE Resources

Activité

James Mitchell s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Laurence Chiu s'est joint(e) à un groupe
Logo
Health care and health information professionals collaborating to improve information sharing between health care technology systems.
Derek Ritz a répondu au cours d'une discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Thanks, Alex, for the reply. :) In section 3.2 where I suggest there is a potential opportunity for collaboration regarding the IHE testing platform I was thinking that the collaborators would be Canada Health Infoway (which is the home for both Canada's HL7 and IHE national committees) and IHE International, which is the IP holder for the Gazelle test platform that underpins Connectathons. In Europe and in the US, there are national initiatives that leverage the IHE test infrastructure to support "projectathons"; these are basically project-specific (or national-extension specific) conformance-testing Connectathons. I was thinking it would be something similar (although I live in hope for a permanent national conformance test centre). The webinars referenced in section 3.3 will be targeted to our IHE Canada community. I have every expectation that the subject matter will be of interest to others -- but the purpose of the webinars will be to look at topics of interest to us, domestically, even if they originate from outside. As an example -- I thought a recent webinar related to the FHIR profile of the International Patient Summary was fantastic, and relevant, even though it was not directly targeted to a Canadian context. Also of note -- I'm hoping that we will do collaborative webinars with others (e.g. the FHIR working group, the ISO committee, DICOM, CAP, etc.); IHE is a profiling organization, after all, so there are always Standards Development Organizations (and their standards) that are implied partners in our work. I hope this is helpful. In your view, Alex -- would the document benefit from including some of these clarifications? Warmest regards, Derek
Alexander Goel a répondu au cours d'une discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Hi Derek, Really appreciate the work that went in to this paper. It's a great summary of all the great work that has been done this year. On page 4 in Section 3.2 who would be the collaborators referred to? "This is expected to lead to a need for a CA-Core conformance-testing capability and this challenge could also be a potential opportunity for collaboration regarding the IHE testing platform." On page 6 in Section 3.3 "IHE Canada will host 3-5 webinars in 2019 to review IHE activities (current and future)" Are these IHE activities, International, North American, European, Canada, USA, or all of the above?
Derek Ritz a créé un événement dans le groupe Integrating the Healthcare Enterprise (IHE)
IHE Canada 2019 report plus new IHE Profiles for public comment
Mercredi, Mai 08, 2019, 12:00pm - 01:00pm
This webinar will be used to get feedback on the IHE Canada 2019 draft annual report and to introduce a new set of IHE Profiles being released for public comment -- some of which are important to Canada's adoption of FHIR. Join Zoom Meetinghttps://zoom.us/j/889030334 Dial by your location +1 646 558 8656 US (New York) +1 669 900 6833 US (San Jose) 855 880 1246 US Toll-free 877 853 5257 US Toll-freeMeeting ID: 889 030 334Find your local number: https://zoom.us/u/ac9mnEmsew
Derek Ritz a créé un événement dans le groupe Integrating the Healthcare Enterprise (IHE)
IHE Canada 2019 report plus new IHE Profiles for public comment
Mercredi, Mai 08, 2019, 12:00pm - 01:00pm
This webinar will be used to get feedback on the IHE Canada 2019 draft annual report and to introduce a new set of IHE Profiles being released for public comment -- some of which are important to Canada's adoption of FHIR. Join Zoom Meetinghttps://zoom.us/j/889030334 One tap mobile+16475580588,,889030334# Canada8557038985,,889030334# Canada Toll-free Dial by your location +1 647 558 0588 Canada 855 703 8985 Canada Toll-freeMeeting ID: 889 030 334Find your local number: https://zoom.us/u/ac9mnEmsew
Derek Ritz a lancé une nouvelle discussion dans le groupe Integrating the Healthcare Enterprise (IHE)
Hi teammates -- please can I ask you to review the .... Every year, we present a national deployment committee report to the IHE Board and our turn is coming up again, soon. This year, we want to have community review of and input into this annual report. We will have a webinar on May 8 to discuss comments and inputs on the 2019 report and to arrive at a consensus document. Also -- we'll use the meeting to introduce new IHE Profiles (including a number of FHIR Profiles important to our Canadian context) that are being released for public comment. Although we don't need to develop an IHE Canada consensus position on these (each IHE member can individually submit comments), it will be useful to garner inputs from the community and find a way to ensure they are taken into account by the respective IHE technical committees. :) The webinar details are below. I hope we can have broad attendance! Topic: Review IHE Canada 2019 report and new IHE profiles up for public comment Time: May 8, 2019 12:00 PM Eastern Time (US and Canada) Join Zoom Meeting https://zoom.us/j/889030334 One tap mobile +16475580588,,889030334# Canada 8557038985,,889030334# Canada Toll-free Dial by your location +1 647 558 0588 Canada 855 703 8985 Canada Toll-free Meeting ID: 889 030 334 Find your local number: https://zoom.us/u/ac9mnEmsew

Événements



Événements à venir :
Aucun événement

Forum

IHE Canada 2019 draft report plus new IHE Profiles out for public comment 04/27/19
Thanks, Alex, for the reply. :) In section 3.2 where I suggest there is a potential opportunity for collaboration regarding the IHE testing platform I was thinking that the collaborators would be Canada Health Infoway (which is the home for bot...
IHE Canada 2019 draft report plus new IHE Profiles out for public comment 04/26/19
Hi Derek, Really appreciate the work that went in to this paper. It's a great summary of all the great work that has been done this year. On page 4 in Section 3.2 who would be the collaborators referred to? "This is expected to lead to a need...
IHE Canada 2019 draft report plus new IHE Profiles out for public comment 04/23/19
Hi teammates -- please can I ask you to review the .... Every year, we present a national deployment committee report to the IHE Board and our turn is coming up again, soon. This year, we want to have community review of and input into this annual re...
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/20/19
i sure do agree with your last points, Lloyd. Leadership is everything!
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/18/19
Thanks, Lloyd, for the very thoughtful and thorough reply. There's a lot to think about, as we continue to progress Canada's digital health agenda. I genuinely appreciate these ideas and suggestions and clarifications. All very helpful! :)
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/18/19
Hi Derek, The risk in proliferation of extensions really comes from two places: 1. Systems that choose to stick their data into extensions rather than conveying it in standard elements. For example, "I use a SNOMED code for gender, so I'll send...
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/18/19
Lloyd -- thank you for these thoughtful responses! And yes, I'm happy to see that we separately teased out some nearly identical points regarding governance. I wonder if you could clarify a few of your points, please. I'm especially unclear reg...
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/18/19
It's good that we're aligned on some key aspects of the governance piece. FHIR isn't trying to diverge from a model-based approach. What it is diverging from is two parts of the v3 methodology: 1. Having the modeling be part of the learning cur...
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/18/19
David -- thank you for this! You're right, of course... ideally we would all love to be able to get all 3 at once and it does feel, a bit, like we're being asked to make a false choice. I fear there is a bit of persistent naivete, though, around...
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/18/19
Hi Derek, Some thoughts on your post 1. FHIR extensions have several important differences from v2 Z-segments: FHIR extensions are named in a globally unique way by a URI, so you don't have to wonder whether my ZPA.2.5 means the same as yo...
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/18/19
Interoperability needs to be priority #1. Flexible is a nice to have. Cheap is a reality. That being said, we need to look at the balancing of interoperability and flexibility. We may have higher flexibility and lower interoperability if we can sh...
Cheap... Flexible... Interoperable... choose 2. YIKES!! 04/18/19
This is meant as a spark-a-conversation piece... please, let's DISCUSS this very important topic. Recently, I heard a presenter cite, with some reverence, Grahame Grieve's "..." which basically posits that there is a trade-off between having digit...
Updating IHE's FHIR Profiles to R4... and more details about Project Gemini 04/11/19
Derek thanks for sharing this update and for promoting the FHIR education session at the HL7 International working group meeting in Montreal next month. I wanted to let folks know that Infoway is hosting a free Introduction to FHIR webinar next...
Updating IHE's FHIR Profiles to R4... and more details about Project Gemini 04/10/19
IHE is working its way through the portfolio of FHIR-based Profiles and refreshing these to conform to Release 4. In parallel -- IHE and HL7 and moving forward with their FHIR-centric collaboration: the Gemini Project. Updates regarding both of these...
IHE International and SNOMED International announce global license agreement 04/10/19
From the IHE newsletter... here's a hot-off-the-press joint announcement related to operationalizing global interoperability. ... Agreements such as this are examples of how IHE Profiles make standards-based digital health more digestible and...

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.

Archive ( 2 Documents )

Vidéo

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)

    TIP How to upload and link a document to an InfoCentral Forum

  3. Forum posts shall have the following format:

    Subject: New Namespace/CodeSystem/Subset OID Request
    • OID Description: “A description of the OID”
    • OID Symbolic name: Symbolic name guidelines
    • Responsible Body & Contact Information
    • Proposed FHIR URI: URI as per URI Guidelines
    • To be published: Canadian URI Registry/Terminology Gateway

  4. There will be a wait period of 5 business days for the communities to react to the forum post with comments, questions or asks for clarification.

  5. FHIR URIs must be proposed for all Jurisdictional and Non-jurisdictional OID requests according to the URI Guidelines and must be published in the Canadian URI Registry. Publishing the URI is an optional but highly recommended step. The requestor will submit a validated FHIR® NamingSystem resource object based on the NamingSystem profile to their jurisdictional representative who will then upload it.

  6. FHIR URIs must not be proposed for Subsets to be published on the Terminology Gateway as they will be generated automatically.

  7. The Forum post will be updated with the new OID.

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

Derek Ritz
ecGroup Inc.
Déconnecté(e)
Personne-ressource
Andrea MacLean
Canada Health Infoway
Déconnecté(e)
Admin
Linda Monico
Canada Health Infoway
Déconnecté(e)
Admin
James Mitchell
Royal Victoria Regional Health Centre
Déconnecté(e)
Membre
Laurence Chiu
Google
Déconnecté(e)
Membre
Céline Veilleux
CreativAxion IT inc.
Déconnecté(e)
Membre
Laura Bright
LJB Consulting
Déconnecté(e)
Membre
Parul Sinha
n/a
Déconnecté(e)
Membre
Sean Murray
Box
Déconnecté(e)
Membre
Beverly Knight
Canada Health Infoway
Déconnecté(e)
Membre
Deepti Razdan
cd-ed
Déconnecté(e)
Membre
Katie Williams
NSHA
Déconnecté(e)
Membre
Ron Parker
Parker Digital Health Consulting Inc.
Déconnecté(e)
Membre
Tracy Wutzke
CD-ED
Déconnecté(e)
Membre
Ovidiu Girlan
MOHLTC
Déconnecté(e)
Membre

« Ça semble toujours étrange qu’on n’ait pas accès à notre information médicale. » Faites connaissance avec Mark, l… https://t.co/blN9nlmN0J

par Inforoute,

Logo d'InfoCentral

La santé numérique à votre service

 

Transformer les soins de santé au Canada grâce aux technologies de l'information sur la santé.



Login Register