Share this page:

Coordination of Care
Facilitates discussion and supports efforts to develop and implement effective clinical interoperability solutions to improve the coordination of care including consult, referral, case and transfer management.
Members: 181
Contact: Finnie Flores
Admins: Linda Monico
Type: Open
Access: Public
Facilitates discussion and supports efforts to develop and implement effective clinical interoperability solutions to improve the coordination of care including consult, referral, case and transfer management.

About

LEADERS

Finnie Flores, Program Lead, Architecture & Standards, CIHI

Diane Gutiw, Director, Consulting, CGI

KEY RESOURCES

Pan-Canadian CDA - includes CDA references lists, pan-Canadian CDA Header Implementation Guide, Guidance document and Dashboard of projects.

Primary Health Care EMR Content Standard

Primary Health Care EMR Reference Set

interRAI implementation Toolkit - CIHI's new online interRAI Implementation toolkit contains useful tips, tools and resources to support organizations and jurisdictions as they explore or emabark on implementing an interRAI assessment system. The toolkit is organized into several sections and covers many topics including:

  • Understanding the interRAI/CIHI partnership
  • Choosing a vendor
  • Training Staff
  • Submitting data
  • Using the information

Activity

Linda Parisien created a new discussion in Coordination of Care
We invite you to participate in this survey conducted by SNOMED International. The complete information and link to the survey can be found on the new Health Terminologies Community forum at: https://infocentral.infoway-inforoute.ca/en/forum/254-health-terminologies/2231-global-survey-of-snomed-ct-use#3958 We look forward to working with you and helping to meet your terminology needs. Thank you!
Linda Parisien joined a group
Logo
Facilitates discussion and supports efforts to develop and implement effective clinical interoperability solutions to improve the coordination of care including consult, referral, case and transfer management.
Finnie Flores created a new discussion in Coordination of Care
Hello all, I think this movie is something that will resonate to the members of this community. Falling Through the Cracks: Greg’s Story is a short film on Greg Price’s journey through the healthcare system. The film gives a glimpse of who Greg was and focuses on the events of his healthcare journey that ended in his unexpected and tragic death. In spite of the sadness of Greg’s Story, the message of the film is intended to inspire positive change and improvement in the healthcare system. We believe the film will resonate with the audience and create a platform for further dialogue. We hope people will feel empowered and challenge the status quo of the current healthcare system so we all end up with better care and outcomes. There is public screening in Calgary tonight (May 17) at 7:00 PM. Dates and times of public screening in other cities, and other information are available here: http://gregswings.ca/fttc-gregsstory/ Finnie
Anastazja Krawczyk joined a group
Logo
Facilitates discussion and supports efforts to develop and implement effective clinical interoperability solutions to improve the coordination of care including consult, referral, case and transfer management.
Finnie Flores replied to a discussion in Coordination of Care
Hello all, Here's further information on the presentations we will have from Alberta for this coming Tuesday (May 22). 1) The PaCT Care Plan Template: A broader and more patient centred approach to care planning in Alberta Overview: The Patients Collaborating with Teams care plan template in Alberta aims to broaden the definition of a complex patient, and to put the patients’ needs and wishes at the centre of the care planning process. Innovation Hubs across the province are currently testing this new tool in Patient’s Medical Home environments. Presenters: Sue Peters – Improvement Advisor, Toward Optimized Practice Chris Diamant – EMR Advisor, Toward Optimized Practice 2) Title: AHS Collaborative Care and the Integrated Care Suite Overview: Review of work to date in AHS through the CoACT Collaborative Care program which aimed to reduce redundancy in clinical documentation; promote the inclusion of the patient and family in care planning; enhance and support collaboration between and across the different disciplines on the care team; improve information transfer at transition. Presenter: Lisa Gordey, Alberta Health Services Looking forward to you joining the call. Regards, Finnie and Diane Co-Leads
Finnie Flores created a new discussion in Coordination of Care
Hello all, The Coordination of Care Community invites you to join us for our monthly meeting on May 22, 2018 at 1:00-2:00 PM EST The following is the draft agenda: - Care Plan initiatives presentation from 2 jurisdictions (to be confirmed) - Continuation of Care Plan Working Group discussion To add the meeting invite on your calendar, please follow this link: https://infocentral.infoway-inforoute.ca/en/?option=com_jevents&task=icalrepeat.detail&evid=2588&Itemid=2109&year=2018&month=05&day=22&title=coordination-of-care-may-2018-meeting&uid=f5c14717905105db330f041bd3a6f8a3 Regards, Finnie & Diane
Finnie Flores created an event in Coordination of Care
Coordination of Care - May 2018 Meeting
Tuesday, May 22, 2018, 01:00pm - 02:00pm
The Coordination of Care Community invites you to join us for our monthly meeting on May 22, 2018 at 1:00-2:00 PM EST The following is the draft agenda: - Care Plan initiatives presentation from 2 jurisdictions (to be confirmed) - Continuation of Care Plan Working Group discussion The following are the coordinates for the meeting: Join the call Call-in toll-free number: 1-866-626-0833 (US) Conference Code: 869 441 1152 Add to Calendar PLEASE DO NOT SEND A REPLY WHEN ACCEPTING THE MEETING INVITE

Events



Upcoming events:
Tue May 22 @ 1:00PM - 02:00PM
Coordination of Care - May 2018 Meeting

Forum

Global Survey of SNOMED CT use by SNOMED International 05/18/18
We invite you to participate in this survey conducted by SNOMED International. The complete information and link to the survey can be found on the new Health Terminologies Community forum at: https://infocentral.infoway-inforoute.ca/en/forum/254-hea...
Public Screening: Falling Through the Cracks: Greg's Story 05/17/18
Hello all, I think this movie is something that will resonate to the members of this community. Falling Through the Cracks: Greg’s Story is a short film on Greg Price’s journey through the healthcare system. The film gives a glimpse of who Gre...
Coordination of Care Community - May 22, 2018 Meeting 05/15/18
Hello all, Here's further information on the presentations we will have from Alberta for this coming Tuesday (May 22). 1) The PaCT Care Plan Template: A broader and more patient centred approach to care planning in Alberta Overview: The Pat...
Coordination of Care Community - May 22, 2018 Meeting 05/10/18
Hello all, The Coordination of Care Community invites you to join us for our monthly meeting on May 22, 2018 at 1:00-2:00 PM EST The following is the draft agenda: - Care Plan initiatives presentation from 2 jurisdictions (to be confirmed)...
Missed Today's Subset Presentation? 05/02/18
If you were not able to join us today, the presentation is available here .... Questions can be sent to standards@infoway-inforoute.ca Regards, Linda Parisien and Lorie Carey
The April 2018 Subset Release is now available 04/30/18
Infoway is pleased to announce the release of various subsets in support of stakeholder implementation requests. This release is aligned with the latest versions of the various reference terminologies used in each subset. The updated subsets conta...
Care Plan Workimg Group 04/13/18
I have sent an email to most of the members who requested to be included in this working group but not everyone had email contact information available. If you did not receive an email this morning please email me at diane.gutiw@cgi.com so I can add...
Coordination of Care Community - May 2018 Meeting 04/12/18
Hello all, Please note that our next community meeting will be May 1, 2018 at 1:00-2:00 PM EST (in lieu of April meeting) The following topics will be discussed: - Care Plan - eHealth Conference 2018 presentation Following is the link...
Webinar: Connected Health Information in Canada: A Benefits Evaluation Study 03/29/18
With investment from Canada Health Infoway (Infoway) and its partners in electronic health records, clinicians are beginning to have better access to patient information across the health care system continuum. Join Infoway and Gartner to discuss...
Coordination of Care Community - March 2018 Meeting 03/27/18
Hello all, Thanks again to our presenters at today's meeting. Below are the links to the materials used today. - Introduction slides: https://infocentral.infoway-inforoute.ca/en/resources/docs/coordofcare/2506-coordination-of-care-community-ma...
Kick Off for Care Plan Template Development 03/20/18
Hi Everyone We will be kicking off our Community Work on the Care Plan Development in our March 27th Community Meeting. Please join if you can! Details on the working group session that will follow will be sent to all those who expressed interes...
Call for Interest: Care Plan Template Development 03/20/18
Hi Everyone We will be kicking off the work on the Care Plan Template development in our Community Meeting - March 27 1ET. Please see the invitation details in the events and Forum post! Diane and Finnie
Coordination of Care Community - March 2018 Meeting 03/13/18
Hello all, The Coordination of Care community is pleased to host the following presentations on March 27, 2018 at 1-2 PM EST. - The ‘problem’: Data Sharing Agreements moving digital health initiatives forward by Abigail Carter-Langford, Executi...
eReferral Spec Work Stream 03/06/18
Here is the updated coordinates and agenda. Today we will be talking about the work the spec writing team accomplished this week, and the FHIR north connectathon. The new zoom meeting room info is as follows: =========================== Biwee...
eReferral Spec Work Stream 03/06/18
Hello all, I am cross posting here on the work that is happening on eReferral as this has been identified by the CoC Advisory Group as one of the priorities. If you are interested, there is a meeting today (March 6) at 11 - 12 EST. ... te...

Tasks


Tasks


Time Tracking


Gantt

Documents

Click Manage documents to:

  • view the complete list of documents or documents grouped by folder
  • upload a new document

Note: Group members are not currently notified when new documents are added. To notify others, you must post the URL to the new document in the forum. (Notification of document uploads is a feature in development.)

Manage documents You may need to login and/or be a member of the group to access this content.

Collaborative Care Planning (Fraser Health)

Published on Mar 27, 2018 by Finnie Flores

Data Sharing Agreements

Published on Mar 27, 2018 by Finnie Flores

Coordination of Care Community - March 2018 Meeting

Published on Mar 27, 2018 by Finnie Flores

eHealth Ontario Data Dictionary Presentation Feb 27 2018

Published on Feb 27, 2018 by Diane Gutiw

Patient-Reported Outcomes Measures (PROMs)

Published on Jan 30, 2018 by Finnie Flores

Patient-Oriented Discharge Summary (PODS)

Published on Jan 30, 2018 by Finnie Flores

Coordination of Care Community Update - Jan 2018

Published on Jan 30, 2018 by Finnie Flores

ISO_commenting_template (2017)

Published on Jan 05, 2018 by Finnie Flores

Infoway - Emerging Trends

Published on Dec 04, 2017 by Finnie Flores

Alberta - Community Information Integration (CII)

Published on Nov 01, 2017 by Finnie Flores

Transitions of Care and Care Planning

Published on Oct 02, 2017 by Finnie Flores

eHealth SK Initiatives: EMR Interoperability

Published on Oct 02, 2017 by Finnie Flores

Manitoba EMR Information Sharing and Data Extract

Published on Jun 30, 2017 by Finnie Flores

Ontario Coordinated Care Plan Presentation

Published on Jun 30, 2017 by Finnie Flores

CIHI - Acute and Ambulatory Care Data Content Standard

Published on Dec 20, 2016 by Peter Picton

ISO TC/215 Use Case Standard - Patient Summary - Nov3-16

Published on Nov 03, 2016 by Peter Picton

ISO - JIC Use Case & Patient Summary - CoC Sep27-16

Published on Oct 11, 2016 by Peter Picton

Clinical Document eXchange (BC CDX) Update - CoC Sep27-16

Published on Oct 11, 2016 by Peter Picton

CGI - CommunityCare360 - CoC Jun28-16

Published on Jun 30, 2016 by Peter Picton

CoC 2016-06-28 Teleconference Agenda

Published on Jun 27, 2016 by Peter Picton

Coordination of Care Community Insights Survey Summary

Published on Jun 03, 2016 by Peter Picton

CognisantMD and CMH - Ocean eReferrals - CoC May31-2016

Published on Jun 01, 2016 by Peter Picton

CoC 2016 03 29 Teleconference Agenda

Published on Mar 21, 2016 by Peter Picton

Coordination of Care Meeting - February 23rd 2016 Agenda

Published on Feb 22, 2016 by Peter Picton

Coordination of Care Meeting - January 26th 2016 Agenda

Published on Jan 25, 2016 by Peter Picton

2016 Interoperability Standards Advisory

Published on Jan 04, 2016 by Peter Picton

Alberta e Referral Portal CHT May 2015

Published on Nov 30, 2015 by Peter Picton

Case Study NLCHI May 2015

Published on Nov 30, 2015 by Peter Picton

CoC 2015 10 27 Teleconference Agenda

Published on Oct 27, 2015 by Peter Picton

Patient e-booking Infoway (CoC Meeting Sep29-2015)

Published on Oct 16, 2015 by Peter Picton

EHealth World Standards Day

Published on Sep 30, 2015 by Finnie Flores

Coordination of Care 2015/09/29 Teleconference Agenda

Published on Sep 24, 2015 by Peter Picton

Manitoba eReferral Presentation (CoC Meeting Jun23-2015)

Published on Jul 23, 2015 by Peter Picton

Ontario eReferral Presentation (CoC Meeting Jun23-2015)

Published on Jul 23, 2015 by Peter Picton

Alberta eReferral Presentation (CoC Meeting Jun23-2015)

Published on Jul 23, 2015 by Peter Picton

CoC 2015 07 28 Teleconference Agenda

Published on Jul 20, 2015 by Peter Picton

CoC 2015 06 23 Teleconference Agenda

Published on Jun 09, 2015 by Peter Picton

2015 May BC Discussion Document Provider Groups

Published on May 08, 2015 by Cynthia/Cindie Robertson

Video

This Group has no videos.

Solutions

  • Canadian FHIR Registry
  • FHIR Terminology Service API
  • HAPI FHIR
  • HAPI v2
  • HL7 Explorer
  • InfoRMS
  • InfoScribe
  • Message Builder
  • Message ReMixer
  • Object Identifier (OID)
  • SNOMED CT Browser
  • Terminology Gateway
  • Terminology Service API
  • TermWorks
  • WebHook Notifications

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.

This email address is being protected from spambots. You need JavaScript enabled to view it.

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

 

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.

-->

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

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

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

 

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.

Standards Selection Framework

The Standards Selection Framework provides users with the means to plan, choose and document interoperability solutions from concept through to implementation. Starting from the Clinical Requirements identified by clinicians through to business requirements, standards and technical specifications, the framework provides a comprehensive guide through the development of interoperability solutions.

The framework also provides an opportunity for the InfoCentral community to share successful implementation projects, the standards selections made at a point in time of the project and the specifications that result from the selections made. Publishing solutions in this space will help to establish a Canadian repository of references.

clinical requirements

Clinical Requirements describe the information and workflow needs of the clinician for a specific clinical context and clinical data exchange. Using the Clinical Interoperability Principles as a guide, a set of requirements expressed in the clinician’s voice will provide the foundation for a well-designed interoperability solution.

business requirements

Business Requirements are derived from clinical requirements and provide a full picture of the solution that needs to be developed. Use cases, business rules and guidance are used to fully outline the solution design.

standards selection

Standards Selection refers to the process that has been developed to help guide teams through the selection of terminology and messaging standards. Using the line of inquiry and considerations in the forms provided implementation teams may assess the standards available and determine the best option for the point in time. The process also provides an opportunity for the InfoCentral community to share successful implementation projects, promoting standardization through reuse.

standards

Standards are an integral piece of the interoperability solution, covering both the terminology that defines the data sent, and the messaging structures that define how the data is transferred. The framework provides the access and consideration criteria to the international and Canadian standards to facilitate implementation.

specifications

Specifications provide the details for the solution to be implemented. These details include: a review of the data elements used, samples of transferred messages, the system architecture as well as the security specifications including authorization and authentication.

Solution for API integration

Infoway Message Builder allows developers to focus on the business challenges of integrating their solutions with each electronic health record implementation by abstracting the differences between different versions of pan-Canadian HL7 messaging and supporting current implementation constraints. Developers can build interfaces in a familiar development environment, using the programming language of their choice*, while the Message Builder API fosters quick and easy creation, population and access to HL7v3 requests and responses.

Infoway Message Builder v2.0 and later is enhanced to generate JAVA APIs to create, validate, marshal/unmarshal CDA documents.

 Implementation and Exchange

 

Key features and benefits

Message Builder offers a number of key features and benefits:

  1. Abstracts the complexity of HL7v3 messages and greatly simplifies the work of the developer when implementing them;
  2. Reduces the impact on developers from implementation variations;
  3. Enables companies to achieve Infoway product certification with greater confidence and reduced time;
  4. Enables developers to incorporate future message versions without re-writing their products;
  5. Can be embedded in software applications due to its open source distribution under a commercial-friendly Apache 2.0 license.

Out of the box support

Infoway Message Builder comes with built-in runtime APIs that support a number of pan-Canadian specifications:

  • MR2009 (R02.04.02)
  • MR2007 (V02R02)
  • MR 2007 (V02R01)
  • CeRx (V01R04.3)

In addition, while developers can easily build custom transport mechanisms without affecting the core, Message Builder includes native support for SOAP and RESTful message transports. Developers can configure and extend the transport as desired.

Detailed product features

  • Provides the capability to configure and populate message values that are common to all messages—this allows developers to reuse common message data, shortening the time to configure and create an interoperable system.
  • Uses simplified data types that are natural and familiar to the programming language (e.g. String for ST) rather than directly exposing the sometimes complicated HL7v3 data types—yet still allowing access to HL7v3 data types when necessary.
  • Allows developers to focus on the business-aspect of a request/response, avoiding many of the complexities of HL7v3.
  • Code-generation algorithms merge identical and similar classes together to simplify the generated API—meaning less confusion in the resulting code and an increased ability to write generic handlers for certain types.
  • Converts populated objects into HL7v3 XML requests, and converts HL7v3 responses into populated objects.
  • Provides flexibility in configuring and performing terminology-code lookups, including code set and database-backed lookups (can mix and match).
  • Associations and attributes are strongly typed, given business names when provided, and contain code docs directly from the MIFs (see wiki.hl7.org/index.php?title=MIF).
  • The algorithms inline most classes that only have a small number of properties, further simplifying the API.
  • Offers both permissive and strict modes—permissive allows many common errors and generates appropriate error comments in the XML or result object.
  • A separate validation tool is provided to test ad-hoc messages—this tool reuses the same validation components that are executed during message marshaling and unmarshalling, ensuring consistent processing of the message whether during processing or during conformance validation.

Forward looking

The power of the Message Builder architecture is in its MIF-based generation of the specification API. With Message Builder, any MIF is supported—whether a future release of the pan-Canadian specifications or a modified (constrained) jurisdiction-specific release of an existing specification. 

 

How it works

Message Builder comprises two parts:

  1. Message Builder Generator—a tool used by Infoway to take input MIFs and create Message Sets for use by Message Builder Runtime;
  2. Message Builder Runtime—an API used by developers to allow their products to support multiple Message Sets without recoding.

Message Builder Generator

Used by Infoway, Message Builder Generator takes MIFs (as the source of truth for standards specifications) and converts them into a series of Java Classes. This is done by first converting the MIFs to an XML Message Set (a simplified representation of the information present in the original MIFs), then generating Java Classes that reference standard Java data types and use business-friendly names. In the process, groups of related elements are flattened and similar message parts are placed into a single class: these steps increase ease of use and reduce the complexity of the resulting Java Classes.

MBG process

Using Message Builder Generator, Infoway is able to create multiple Message Sets, each representing the MIFs used in a single jurisdiction, but all for the same HL7v3 version.

Message Builder Runtime

Message Builder Runtime allows developers to quickly adapt to implementations in multiple Jurisdictions: incoming messages are first examined to determine the corresponding source Message Set, once identified, a series of Java Objects that represent the message are instantiated. Next, the Java Objects are turned into an HL7 message for the HL7 version corresponding to the desired destination Message Set. 

MB process

Using Message Builder Runtime developers can accept messages over the wire and on-the-fly turn them into a different HL7 message version. Given the capability of Message Builder to support future versions of HL7 messages, developers can easily future proof their products with minimal effort.

 

*Developer friendly

The Message Builder libraries are available for Java and Microsoft .NET. In addition, a simplified XML message format is available with REST-based services for managing mapping to/from the simplified form to the target specification XML format.

 

CDA Support

Message Builder CDA API supports the following CDA and data type specifications:

Message Builder provides  JAVA and .NET APIs for CDA document creation, validation, marshalling/unmarshalling of the following CDA document types:

  • Continuity of Care Document (CCD) (Release 1.1)
  • Consultation Notes (Release 1.1)
  • Discharge Summary (Release 1.1)
  • Imaging Integration, and DICOM Diagnostic Imaging Reports (DIR) (Release 1)
  • History and Physical (H&P) (Release 1.1)
  • Operative Note (Release 1.1)
  • Progress Note (Release 1.1)
  • Procedure Note (Release 1)
  • Unstructured Documents (Release 1.1)
  • CDA documents using pan Canadian CDA header template

Clinical applications in JAVA or .NET can use the Message Builder CDA APIs to create, validate or parse above listed types of CDA documents. Potential use cases are document source or document consumer actors in IHE XDS profile, content creator/content consumer in any content module/profile, or report creator/viewer in RIS/PACS/EMR systems.

Message Builder is available for Java and .NET

Message Builder for Java

System Requirements

  • Java 1.5 or higher
  • Maven 3.0.3 or higher (can be removed after installing Message Builder if working with a non-Maven project)

Download

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder, you will need

  1. Message Builder Core and
  2. one or more Message Builder API release(s)—depending on your implementation requirements.

Select a Message Builder Version:

 

Select one or more Message Builder API releases:

 

Optional Message Builder components:

Terminology Database Resolver
Message Builder Example

Message Builder pom.xml file:

 

Message Builder for .NET

System Requirements

  • .Net Framework 3.5 or higher

Download

Message Builder v2.1 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder:

  1. Download Message Builder .NET Core 2.1.0 setup
  2. Unzip and pull out the dll files that you need:
     \ → root location of required Message Builder core assemblies (Mandatory - required all)
     \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
  3. Copy them to your .NET project 
  4. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

Message Builder v1.5.8.1 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder:

  1. Download Message Builder .NET Core 1.5.8.1 setup
  2. Unzip and pull out the dll files that you need:
     \ → root location of required Message Builder core assemblies (Mandatory - required all)
     \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
  3. Copy them to your .NET project 
  4. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

Message Builder v1.4.6 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder, you will need

  1. Download Message Builder .NET Core 1.4.6 setup
  2. Unzip and run SetupCore.msi file
  3. Choose a installation location <install dir>.  The setup execution should place the following directories in <install dir>:
     \lib\ → location of required Message Builder core assemblies (Mandatory - required all)
      \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
     \src\ → location of all source code and project files required to load them into visual studios
     \debug\ → location of debug symbol files
  4. Pull out files the dll files from the \lib\ and \releases\ folders, and copy them to your .NET project 
  5. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

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

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 This email address is being protected from spambots. You need JavaScript enabled to view it.

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

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

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

 

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

  • This email address is being protected from spambots. You need JavaScript enabled to view it.
  • SNOMED CT Education
  • Apelon User Guide
  • Infoway User Installation Guide
  • How does TermWorks Work?
  • TermWorks FAQs

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: This email address is being protected from spambots. You need JavaScript enabled to view it. 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 Response

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

Web Conference

Please login to acquire access to the InfoCentral web conferencing.

Members

Finnie Flores
Canadian Institute for Health Information
OFFLINE
Contact
Linda Monico
Canada Health Infoway
OFFLINE
Admin
Linda Parisien
Canada Health Infoway
OFFLINE
Member
Anastazja Krawczyk
n/a
OFFLINE
Member
Ron Parker
Independent
OFFLINE
Member
Mary Eileen MacPhail
Nova Scotia Health Authority
OFFLINE
Member
naomi monaster
PHSA - IMITS
OFFLINE
Member
ERIN MBUGUA
1980
OFFLINE
Member
divya raini
cd ed college
OFFLINE
Member
Mohammed Mahfooz
Centre for Distance Education
OFFLINE
Member
Andrew Cummings
Regional Muncipality of York / McMaster
OFFLINE
Member
Beverly Chan
Centre for Distance Education
OFFLINE
Member
Angela Brewer
na
OFFLINE
Member
Raymond Simkus
Brookswood Family Practice
OFFLINE
Member
Diana Trifonova
Doctors of BC
OFFLINE
Member

logo 1

Improving the quality of patient care through the effective sharing of clinical information among health care organizations, clinicians and their patients.



Login Register