Share this page:

Diagnostic Imaging
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.
Members: 150
Admins: Linda Monico
Type: Open
Access: Public
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.

About

LEADERS

Jason Nagels, CIIP, PMP - HDIRS, Manager Clinical Program

David Koff, MD FRCPC, Chair of The Department of Radiololgy at MacMaster University. Chief of Diagnostic Imaging at Hamilton Health Sciences. Professor of Radiology at MacMaster University.

KEY RESOURCES


XDS AFFINITY DOMAIN IMPLEMENTATION GUIDE

XRR-WD - Cross Enterprise Remote Read Work Flow Definition - FINAL Published Edition.

Activity

Jason Nagels created a new discussion in Diagnostic Imaging
Good Morning all - Today's meeting is cancelled. The next DI Community meeting will be the half-day face to face meeting on May 1st. Thx, J
Angela Brewer joined a group
Logo
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.
Jason Nagels created a new discussion in Diagnostic Imaging
Hi All - This is to inform you that the date for the half-day face to face meeting will be May 1st @ 9am - 1pm EST. An agenda will be posted by next week. Thx, J
Jason Nagels created a new discussion in Diagnostic Imaging
Hi All - Due to a few conflicts, this week's meeting will be cancelled. As a reminder, please try to submit your availability to the face 2 face poll as soon as possible: https://lettucemeet.com/l/z85pk Thx, K
Jason Nagels replied to a discussion in Diagnostic Imaging
Please try to respond to this poll before EOD Friday. The Canada room fills up fast, and we would like to book the room asap. https://lettucemeet.com/l/z85pk thx, J
Jason Nagels created a new discussion in Diagnostic Imaging
Good Morning All - Please use the link below to provide your availability on the proposed dates for a half day face to face meeting. https://lettucemeet.com/l/z85pk As suggested in the previous meeting, we're trying a new polling service. Click the link, and select 'add availability' to enter your availability for the date and times suggested. Thanks, J
Jason Nagels created a new discussion in Diagnostic Imaging
Hi All - The agenda for today's meeting is listed below: ... Thanks, J

Events



Upcoming events:
No events

Forum

***Cancelled Meeting - April 20th, 2018*** 04/20/18
Good Morning all - Today's meeting is cancelled. The next DI Community meeting will be the half-day face to face meeting on May 1st. Thx, J
Half Day - Face to Face Meeting: May 1st, 9am - 1pm EST 04/09/18
Hi All - This is to inform you that the date for the half-day face to face meeting will be May 1st @ 9am - 1pm EST. An agenda will be posted by next week. Thx, J
**Meeting Cancelled** - April 6, 2018 04/05/18
Hi All - Due to a few conflicts, this week's meeting will be cancelled. As a reminder, please try to submit your availability to the face 2 face poll as soon as possible: https://lettucemeet.com/l/z85pk Thx, K
Poll: Face to Face DI Working Group 04/04/18
Please try to respond to this poll before EOD Friday. The Canada room fills up fast, and we would like to book the room asap. https://lettucemeet.com/l/z85pk thx, J
Poll: Face to Face DI Working Group 04/04/18
Good Morning All - Please use the link below to provide your availability on the proposed dates for a half day face to face meeting. https://lettucemeet.com/l/z85pk As suggested in the previous meeting, we're trying a new polling service. C...
DI Community Meeting Agenda - Friday March 23rd 2018 03/23/18
Hi All - The agenda for today's meeting is listed below: ... Thanks, J
Meeting Cancelled **DI Community Meeting Agenda - Friday March 9th, 2018*** 03/08/18
Good Afternoon - This is to inform you that the tomorrow`s DI Community meeting is cancelled. We will meet next on March 23rd at 12pm EST. Thx, J
DI Community Meeting Agenda - Friday Feb 23rd 2018 02/23/18
Hi all - The Agenda for today's meeting is listed below. ... Thanks, J
**Meeting Cancelled*** DI Community - Friday Feb 9th 2018 02/08/18
Good Morning all - Please be advised that tomorrow's DI community meeting is cancelled. Thanks, J
IHE Profile Index and Opportunities of FHIR presentation 01/30/18
Here are the links to the IHE Profile Index document and Opportunities of FHIR presentation. ... Thanks, Kinson
DI Community Meeting Agenda - Friday January 12th 2018 01/26/18
Hi All - Please find the agenda for this week's DI meeting. ... Thanks, J
DI Community Meeting Agenda - Friday January 12th 2018 01/16/18
Meeting minuets for last week's meeting are listed below: ...
DI Community Meeting Agenda - Friday January 12th 2018 01/11/18
Happy New Year Everyone! Below is a link to this week's agenda. ... Thanks, J
Updated LOINC & RELMA now available for download from LOINC website 01/02/18
LOINC 2.63 and RELMA 6.22 are now available for download at loinc.org website. Here are some brief highlights for the update: 1660 new terms (including 736 laboratory, 558 clinical, and 366 new survey terms) Nearly 350 new radiology term...
DI Community Meeting Agenda - Friday December 15th 12/15/17
HI everyone, Please find ...the presentation I did today on the call. Thank you!

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.

DICOM ( 0 Document )

IHE ( 8 Documents )

DI Working Group Agenda: March 23, 2018 12pm-1pm EST

Published on Mar 23, 2018 by Jason Nagels

DI Working Group Agenda: Feb 23, 2018 12pm-1pm EST

Published on Feb 23, 2018 by Jason Nagels

DI Working Group Agenda: January 26, 2018 12pm-1pm EST

Published on Jan 26, 2018 by Jason Nagels

DI Working Group Minutes: January 12, 2018 - 12PM-1PM EST

Published on Jan 16, 2018 by Jason Nagels

DI Working Group Minutes: January 12 - 12PM-1PM EST

Published on Jan 16, 2018 by Jason Nagels

DI Working Group Agenda: January 12 2018 12pm-1pm EST

Published on Jan 11, 2018 by Jason Nagels

DI Working Group Agenda: December 15, 12pm-1pm EST

Published on Dec 14, 2017 by Jason Nagels

DI Working Group Minutes: December 1 - 12PM-1PM EST

Published on Dec 01, 2017 by Jason Nagels

DI Working Group Agenda: December 1, 2017 12pm-1pm EST

Published on Dec 01, 2017 by Jason Nagels

November 17, 2017- DI Community Meeting

Published on Nov 16, 2017 by Jason Nagels

DI Working Group Agenda: October 20, 12pm-1pm EST

Published on Oct 20, 2017 by Jason Nagels

DI Working Group Minutes: October 6, 12pm-1pm EST

Published on Oct 12, 2017 by Jason Nagels

DI Working Group Agenda: October 6, 12pm-1pm EST

Published on Oct 06, 2017 by Jason Nagels

DI Working Group Agenda: September 8, 12pm-1pm EST

Published on Sep 06, 2017 by Jason Nagels

DI Working Group Agenda: August 11, 12pm-1pm EST

Published on Aug 10, 2017 by Jason Nagels

DI Working Group Agenda: August 10,12pm-1pm EST

Published on Aug 10, 2017 by Jason Nagels

DI Working Group Agenda: July 28, 12pm-1pm EST

Published on Jul 28, 2017 by Jason Nagels

June 16/2017 Meeting Mins

Published on Jun 22, 2017 by Jason Nagels

CHI FEM Report Format, Conversion, and Transport Options

Published on Jun 20, 2017 by Teri Sippel Schmidt

DI Working Group Agenda: June 16,12pm-1pm EST

Published on Jun 15, 2017 by Jason Nagels

DI Working Group Mins: May 19th,12pm-1pm EST

Published on May 19, 2017 by Jason Nagels

IHE FEM Use Case 4 - ED Transfer

Published on May 19, 2017 by Teri Sippel Schmidt

IHE FEM Use Case 3 - Study Read at different facility

Published on May 19, 2017 by Teri Sippel Schmidt

DI Working Group Agenda: May 18,12pm-1pm EST

Published on May 18, 2017 by Jason Nagels

DI Community Meeting Mins: Friday May 5, 12pm-1pm EST

Published on May 09, 2017 by Jason Nagels

May 5/2017 - DI Community Agenda

Published on May 03, 2017 by Jason Nagels

April 21/2017 Meeting Mins

Published on May 03, 2017 by Jason Nagels

April 21 Meeting Agenda

Published on Apr 20, 2017 by Jason Nagels

April 3-17 Meeting Mins

Published on Apr 11, 2017 by Jason Nagels

April 7-2017 Meeting Mins

Published on Apr 11, 2017 by Jason Nagels

April 7 Meeting Agenda

Published on Apr 06, 2017 by Jason Nagels

March 24 Meeting Mins

Published on Mar 31, 2017 by Jason Nagels

April 3rd Face to Face Agenda

Published on Mar 30, 2017 by Jason Nagels

DI Working Group Agenda: Wed March 24,12pm-1pm EST

Published on Mar 22, 2017 by Jason Nagels

March 10 Meeting Mins

Published on Mar 15, 2017 by Jason Nagels

March 10 Meeting Agenda

Published on Mar 08, 2017 by Jason Nagels

DI Community Proposal Template

Published on Feb 27, 2017 by Jason Nagels

Feb 24 Meeting Minutes

Published on Feb 25, 2017 by Jason Nagels

DI Working Group Agenda: Wed Feb 24,12pm-1pm EST

Published on Feb 23, 2017 by Jason Nagels

Feb 8 Face to Face Meeting Minutes

Published on Feb 12, 2017 by Jason Nagels

IHE Rad Non-Urgent Critical Findings Follow-up Overview

Published on Feb 09, 2017 by Teri Sippel Schmidt

DI Working Group Agenda: F2F Wed Feb 8, 9am-12pm EST

Published on Feb 06, 2017 by Jason Nagels

DI Working Group Community Minutes: January 13, 2017

Published on Jan 13, 2017 by Jason Nagels

DI Working Group Agenda: Friday January 13, 12pm EST

Published on Jan 10, 2017 by Jason Nagels

DI Working Group Agenda: Friday November 18, 12pm EST

Published on Nov 16, 2016 by Laura Repchik

Remote Read Status - Presented by C. Lindop October 21, 2016

Published on Oct 26, 2016 by Laura Repchik

DI Working Group Community Minutes: October 21, 2016

Published on Oct 26, 2016 by Laura Repchik

DI Working Group Agenda: October 21, 2016

Published on Oct 19, 2016 by Laura Repchik

DI Working Group Agenda: September 23, 12pm EST

Published on Sep 22, 2016 by Laura Repchik

Clinical Division Support and the 2017 CMS Imaging Mandate

Published on Jun 10, 2016 by Laura Repchik

DI CS eHealth Update Presentation for DI WGC May 31 2016

Published on Jun 06, 2016 by Laura Repchik

DI Working Group Agenda: May 31, 2016

Published on May 30, 2016 by Laura Repchik

Diagnostic Imaging Community - Agenda for Friday May 6, 2016

Published on May 04, 2016 by Laura Repchik

Diagnostic Imaging Community - Agenda for Friday April 8, 2016

Published on Apr 07, 2016 by Laura Repchik

Remote Read Status - Next Steps

Published on Feb 16, 2016 by Ben Macerola

Meeting Agenda: DI Working Group Friday February 12, 2016

Published on Feb 11, 2016 by Laura Repchik

IHE Suppl XRR-WD Document

Published on Jan 15, 2016 by Laura Repchik

Remote Reporting for Imaging Dec 18, 2015 Meeting Agenda

Published on Dec 18, 2015 by Laura Repchik

Clinical Requirements Remote Read Radiologists Review v2

Published on Oct 09, 2015 by Diane Larwood

Detailed IHE Remote Read Proposal

Published on Sep 11, 2015 by Ben Macerola

DI RRI 2015 07 013

Published on Jul 13, 2015 by Chris Lindop

Remote Reading iGuide - KH

Published on Jul 05, 2015 by Kinson Ho

DI RRI 2015 05 08 revPeterP

Published on May 12, 2015 by Peter Popowycz

Diagnostic Imaging WG Meeting May 8, 2015

Published on May 07, 2015 by Laura Repchik

SCWG 10 Transition to DI Community

Published on Mar 26, 2015 by Diane Larwood

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.

!-

 Education

 Maintenance

-->

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

Andrea MacLean
Canada Health Infoway
OFFLINE
Contact
Linda Monico
Canada Health Infoway
OFFLINE
Admin
Angela Brewer
na
OFFLINE
Member
Elizabeth Stark
Leafsprout Technologies Inc.
OFFLINE
Member
Daniel Kuhn
Herr
OFFLINE
Member
Kjetil Nilsen
Sectra Canada Inc.
OFFLINE
Member
Desmond Guarin
BC Ministry of Health
OFFLINE
Member
Barinder Kaur
n/a
OFFLINE
Member
Harsh Sharma
Alberta Health Services
OFFLINE
Member
Debbie Onos
Alberta Health Services
OFFLINE
Member
Roberto Medaglia
NEODIN
OFFLINE
Member
Tyler England
Health Sciences North
OFFLINE
Member
Vipin Saini
n/a
OFFLINE
Member
RONKE OSATOHANMWEN
NA
OFFLINE
Member
Rejean Fortin
Biron Health Group
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