Share this page:

Diagnostic Imaging
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.
Members: 165
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

Raqia Hazam created a new discussion in Diagnostic Imaging
Hello DI Community, Please see comment request from DICOM regarding CP-1850. Please submit any feedback you may have by end of day December 19 so I can comment on your behalf. Thank you, Raqia To: DICOM Community Cc: Chair of WG-06 – Bjorn Nolte, Siemens Healthineers DICOM Editor – David Clunie, PixelMed From: DICOM Secretariat Office Lisa Spellman, General DICOM Secretary Luiza Kowalczyk, Senior Manager, DICOM Operations Subject: Soliciting Public Comments on CP-1850 Change old RT-style SNOMED IDs to CT-style Concept IDs. ATTENTION: This Change Proposal may have a significant impact on your implementations. The DICOM Standard Committee is circulating this CP for special public comment due to its scope and content. Please read the rationale section of the CP carefully. We encourage commenters to perform risk assessments (an example is shown in the rationale) and communicate the results back to the Committee. The more detail you provide (specific codes, specific consequences) the better we will be able to help mitigate those risks. Thank you for your attention. ‘Download’ links: CP-1850_pc_replacingsrtwithsct.pdf- PDF Document ... Please click on the following link to submit comments on CP-1850_pc_replacingsrtwithsct ... PLEASE NOTE: The CP-1850 Change old RT-style SNOMED IDs to CT-style Concept IDs is also uploaded on the DICOM website and the ftp server: •... •...
Raqia Hazam replied to a discussion in Diagnostic Imaging
Hello DI Community, A vote of abstention was registered with DICOM on behalf of the Canadian DI community. Kind regards, Raqia Hazam
Helena Nutakor joined a group
Logo
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.
Raqia Hazam created a new discussion in Diagnostic Imaging
Hello DI Community, Please see this request from DICOM regarding Correction Package #99 . Please submit your response by end of day January 4, 2019 so I can vote on your behalf. If I don't receive any feedback by the deadline, Canada will abstain. Kind regards, Raqia Hazam To: Members of the DICOM Standard Committee Voting and Alternate Voting Representatives From: DICOM Secretariat Luiza Kowalczyk, Senior Operations, DICOM Manager Lisa Spellman, General DICOM Secretary Subject: Letter Ballot for Proposed DICOM Correction Package #99 (CPack-99) Following is a letter ballot seeking DICOM Standard Committee approval of proposed DICOM Correction Proposals (CPs). Note: only the officially designated voting representatives (or alternates) of the Members of the DICOM Standards Committee (....) are invited and entitled to cast a ballot. Others in the DICOM Community receive a copy of this ballot as a courtesy so that all will be apprised of anticipated revisions or extensions to the DICOM Standard. The DICOM Standard, which addresses image communication and related data management functions, was first published in 1993. DICOM Working Group Six regularly reviews and approves extensions (Supplements), clarifications and error fixes (Correction Proposals) to the Standard. Requests for such fixes or clarifications or general questions and comments may be submitted by anyone to the Secretariat (dicom@dicomstandard.org). CPs are batched into C-Packs for balloting to the DICOM Standard Committee members. Approved corrections are incorporated into the next edition of the DICOM Standard, which is now released 5 times a year, following each WG-06 meeting. Correction Proposals may address: •Ambiguities – standard text that is not precise or leads to various interpretations. •Clarifications – to facilitate the interpretation of the Standard but not change the spec •Errata – correction of normative and informative errors. •Inconsistencies – sections of the Standard that contain conflicting definitions. •Omissions – Obvious text was not included in the Standard. The following Correction Proposals, approved by WG-06, are included in this ballot: CP# Title 1626 Correct Attribute Types in Text Style 1674 Add Dermatology Anatomic Site Context Group and BYU Numbering System Coding Scheme 1714 Add last release to PS 3.6 tag registry 1736 Add Visible Light Photography Attributes corresponding to EXIF 2.31 and TIFF/EP 1764 More quantitative image features 1779 Update AIM to DICOM SR TID 1500 mapping with model revisions 1793 Harmonize the description of the DICOM Communication Model across the parts 1797 Update definition of SOP Class, inclusion of Media Storage Service and Web Services 1807 Corrections of Performed Storage Module 1810 Make the sections on definitions consistent and complete 1811 Key measurements in Encapsulated PDF 1812 Add calculation comments for intraocular lens calculations to Intraocular Lens Calculations IOD 1813 Add concept of Toric Intraocular Lenses to Intraocular Lens Calculations IOD 1814 Add corneal measurement values sequence to Intraocular Lens Calculations IOD (IOL) 1815 Add new Intraocular Lens Formulas and Lens Constants to DICOM Content Mapping Resource 1816 Update JPEG-LS and RLE Media Types for web services to use registered rather than experimental media types 1817 Replace uses of “data set” that don’t refer to the PS3.5 defined meaning 1818 Large compressed images may have more frames than fit in the Basic Offset Table 1819 Add 64 bit binary VRs 1820 InConcatenationTotalNumber must be greater than one if present 1821 Acquisition Duration need not be mandatory for WSI 1822 Remove Dimension Index Sequence requirement for WSI when Dimensions implicitly defined by TILED_FULL 1823 Add more PET Radiopharmaceuticals for Alzheimer’s Disease 1824 Add more PMSA Targeting Radiopharmaceuticals 1825 Decision result context groups should not be extensible 1826 Specimen De-identification 1827 Correct code meaning for Formalin 1828 Add Barcode Value to Modality Worklist for WSI 1829 Clarify what slide label images contain and add overview image type 1830 Use of Segmentation and Parametric Maps with Whole Slide Imaging 1833 CP 1304 accidentally introduced restriction on PS format for MPEG-2. 1834 Add RT Dose Measurement Devices to CID 7193 1836 Remove instance attributes from QIDO series includeall 1837 Add Reason for Visit 1838 Additions to Breast Imaging Report 1840 Make Code Meaning consistent Each proposal specifies the type of correction, the rationale for the correction, the sections of the DICOM Standard that will be changed, and the correction wording. In voting, you may vote on the complete package or vote on the individual Correction Proposals. All of the balloted Correction Proposals may be found at: ... In addition, some of the Correction Proposals can be found in other formats at: ...
Sean Murray 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
Good Morning all - Due to some scheduling conflicts, this week's DI Community meeting will be canceled. We will re-group on December 14th. Thx, J
Raqia Hazam created a new discussion in Diagnostic Imaging
Hello DI Community, Please see this request from DICOM regarding Correction Package #98 . Please submit your response by end of day December 17, 2018 so I can vote on your behalf. If I don't receive any feedback by the deadline, Canada will abstain. Kind regards, Raqia Hazam To:Members of the DICOM Standard Committee Voting and Alternate Voting Representatives From: DICOM Secretariat Luiza Kowalczyk, Senior Operations, DICOM Manager Lisa Spellman, General DICOM Secretary Subject: Letter Ballot for Proposed DICOM Correction Package #99 (CPack-99) Following is a letter ballot seeking DICOM Standard Committee approval of proposed DICOM Correction Proposals (CPs). Note: only the officially designated voting representatives (or alternates) of the Members of the DICOM Standards Committee (....) are invited and entitled to cast a ballot. Others in the DICOM Community receive a copy of this ballot as a courtesy so that all will be apprised of anticipated revisions or extensions to the DICOM Standard. The DICOM Standard, which addresses image communication and related data management functions, was first published in 1993. DICOM Working Group Six regularly reviews and approves extensions (Supplements), clarifications and error fixes (Correction Proposals) to the Standard. Requests for such fixes or clarifications or general questions and comments may be submitted by anyone to the Secretariat (dicom@dicomstandard.org). CPs are batched into C-Packs for balloting to the DICOM Standard Committee members. Approved corrections are incorporated into the next edition of the DICOM Standard, which is now released 5 times a year, following each WG-06 meeting. Correction Proposals may address: •Ambiguities – standard text that is not precise or leads to various interpretations. •Clarifications – to facilitate the interpretation of the Standard but not change the spec •Errata – correction of normative and informative errors. •Inconsistencies – sections of the Standard that contain conflicting definitions. •Omissions – Obvious text was not included in the Standard. The following Correction Proposals, approved by WG-06, are included in this ballot: CP# Title 1626 Correct Attribute Types in Text Style 1674 Add Dermatology Anatomic Site Context Group and BYU Numbering System Coding Scheme 1714 Add last release to PS 3.6 tag registry 1736 Add Visible Light Photography Attributes corresponding to EXIF 2.31 and TIFF/EP 1764 More quantitative image features 1779 Update AIM to DICOM SR TID 1500 mapping with model revisions 1793 Harmonize the description of the DICOM Communication Model across the parts 1797 Update definition of SOP Class, inclusion of Media Storage Service and Web Services 1807 Corrections of Performed Storage Module 1810 Make the sections on definitions consistent and complete 1811 Key measurements in Encapsulated PDF 1812 Add calculation comments for intraocular lens calculations to Intraocular Lens Calculations IOD 1813 Add concept of Toric Intraocular Lenses to Intraocular Lens Calculations IOD 1814 Add corneal measurement values sequence to Intraocular Lens Calculations IOD (IOL) 1815 Add new Intraocular Lens Formulas and Lens Constants to DICOM Content Mapping Resource 1816 Update JPEG-LS and RLE Media Types for web services to use registered rather than experimental media types 1817 Replace uses of “data set” that don’t refer to the PS3.5 defined meaning 1818 Large compressed images may have more frames than fit in the Basic Offset Table 1819 Add 64 bit binary VRs 1820 InConcatenationTotalNumber must be greater than one if present 1821 Acquisition Duration need not be mandatory for WSI 1822 Remove Dimension Index Sequence requirement for WSI when Dimensions implicitly defined by TILED_FULL 1823 Add more PET Radiopharmaceuticals for Alzheimer’s Disease 1824 Add more PMSA Targeting Radiopharmaceuticals 1825 Decision result context groups should not be extensible 1826 Specimen De-identification 1827 Correct code meaning for Formalin 1828 Add Barcode Value to Modality Worklist for WSI 1829 Clarify what slide label images contain and add overview image type 1830 Use of Segmentation and Parametric Maps with Whole Slide Imaging 1833 CP 1304 accidentally introduced restriction on PS format for MPEG-2. 1834 Add RT Dose Measurement Devices to CID 7193 1836 Remove instance attributes from QIDO series includeall 1837 Add Reason for Visit 1838 Additions to Breast Imaging Report 1840 Make Code Meaning consistent Each proposal specifies the type of correction, the rationale for the correction, the sections of the DICOM Standard that will be changed, and the correction wording. In voting, you may vote on the complete package or vote on the individual Correction Proposals. All of the balloted Correction Proposals may be found at: ... In addition, some of the Correction Proposals can be found in other formats at: ...

Events



Upcoming events:
No events

Forum

PUBLIC COMMENT REQUIRED ON CP-1850 Change old RT-style SNOMED IDs to CT-style Concept IDs, Deadline December 19, 2018 12/11/18
Hello DI Community, Please see comment request from DICOM regarding CP-1850. Please submit any feedback you may have by end of day December 19 so I can comment on your behalf. Thank you, Raqia To: DICOM Community Cc: Ch...
Letter Ballot seeking DICOM Standard Committee (DSC) approval of the Proposed DICOM Supplement: Deadline December 2018 12/11/18
Hello DI Community, A vote of abstention was registered with DICOM on behalf of the Canadian DI community. Kind regards, Raqia Hazam
DICOM Ballot CPack-99 - Submit your votes by Monday, January 4, 2019 12/03/18
Hello DI Community, Please see this request from DICOM regarding Correction Package #99 . Please submit your response by end of day January 4, 2019 so I can vote on your behalf. If I don't receive any feedback by the deadline, Canada will abstain...
**Cancelled Meeting** November 30th, 2018 11/28/18
Good Morning all - Due to some scheduling conflicts, this week's DI Community meeting will be canceled. We will re-group on December 14th. Thx, J
Vote required for DICOM Ballot CPack-99 deadline by December 17, 2018 11/21/18
Hello DI Community, Please see this request from DICOM regarding Correction Package #98 . Please submit your response by end of day December 17, 2018 so I can vote on your behalf. If I don't receive any feedback by the deadline, Canada will absta...
DICOM WG-06 Base Standard-Actions after November 2018 meeting 11/16/18
Hello DI Community, Please see details below from DICOM regarding last week's WG-06 Base Standard Meeting. Please note, next meeting is scheduled for Monday January 7 and Friday January 11, 2019– MITA HQ, Arlington, VA. Raqia Hazam...
DI Community Agenda - November 16, 2018 11/14/18
Hi All - Please find the Agenda for this week's meeting available below: ... One of the agenda items this week is related to DIR best practices and learning opportunities. We would love to have as much participation from the DIR community a...
Letter Ballot seeking DICOM Standard Committee (DSC) approval of the Proposed DICOM Supplement: Deadline December 2018 11/12/18
Hello DI Community, Please see below request seeking approval for Supplement 183: PS3.18 Web Services Re-Documentation. Please submit your responses by December 6 so I can vote on your behalf. If I don't receive any feedback by the deadline, Canad...
Letter Ballot seeking DICOM Standards Committee (DSC) approval of the Proposed DICOM Supplement: Supplement 206: CRYPTREC TLS Profile, October 18 Deadline 11/07/18
Hello DI Community, A vote of abstention was registered with DICOM on behalf of the Canadian DI community. Kind regards, Raqia Hazam
Infoway Event: IHE's Important Role: Turning HYPE into VALUE 11/06/18
Good Morning all - As discussed in the last meeting, .Derek Ritz - IHE Canada Liaison to IHE International - Will be hosting a call related Infoway IHE community. Details are listed below: Wednesday, November 21, 2018, 12:00pm - 01:00pm ET...
Diagnostic Imaging Repository - Discussion and Exchange 11/06/18
Hi Ibou - Welcome again to the Infoway DI Community group. The discussion points you bring up are very appropriate for this group. I will add this as an item to the November 16th Agenda. I encourage all DI Community members that are involved wit...
Letter Ballot for Proposed DICOM Correction Package #98 (CPack-98) 11/05/18
Hello DI Community, A vote of abstention was registered with DICOM on behalf of the Canadian DI community. Thank you. Kind regards, Raqia Hazam
Diagnostic Imaging Repository - Discussion and Exchange 11/01/18
I am the responsible of Diagnostic Imaging Repository (DIR) Laval-Sherbrooke. I wanted to get in touch with those persons responsible for the diagnostic imaging repository in other provinces to exchange and talk about each other realities. • schedu...
DI Community Agenda - November 2, 2018 10/30/18
Hi All - Please find the agenda for this week's DI Community call listed below. ... Thx, J
DICOM Meetings Schedule-RSNA 2018 10/26/18
Dear DI Community, Please see below for upcoming DICOM meetings. Kind regards, Raqia To: DICOM COMMUNITY The DICOM meetings at RSNA are scheduled on Monday-Thursday as follows. o All interested persons are invited to all...

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 ( 2 Documents )

IHE ( 8 Documents )

Meeting & Materials ( 81 Documents )

DI Community Agenda - July 20, 2018

Published on Jul 18, 2018 by Jason Nagels

Video

This Group has no videos.

Solutions

  • Canadian FHIR Registry
  • Canadian URI Registry
  • FHIR Terminology Service API
  • HAPI FHIR
  • HAPI v2
  • HL7 Explorer
  • InfoRMS
  • 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.

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

Organization projects can be viewed without logging in. To edit or request a new project, This email address is being protected from spambots. You need JavaScript enabled to view it. with the details.

View projects in the Canadian FHIR Registry

The Canadian URI Project is a repository of identifier and code system namespaces. Capturing key metadata as FHIR® NamingSystem resources provides an automatic mapping of OIDs to URIs or vice versa.

To make the discovery of these artifacts more flexible, the Canadian URI Registry (alpha) was developed to allow artifacts to be queried via plain text, OID, URI or their respective identifiers. These identifiers are created according to the URI guidelines and posted to the FHIR Solution Architecture Workstream for approval.

It is important to note that all searchable artifacts are to be curated via the Canadian URI Project in Simplifier. There are ongoing discussions with the FHIR Solution Architecture Stream to have a single representative manage data for their respective jurisdictions.

A scheduled task is run periodically, making all new or modified artifacts searchable after a 20 minute window.

Search the Canadian URI Registry (alpha)

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

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

 

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

  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.

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
Helena Nutakor
CENTRE FOR DISTANCE EDUCATION
OFFLINE
Member
Sean Murray
Box
OFFLINE
Member
Katie Williams
NSHA
OFFLINE
Member
Amanda Morgan
Horizon Health Network
OFFLINE
Member
Sandra Colavecchia
NSHA
OFFLINE
Member
Leo Arhanic
n/a
OFFLINE
Member
Kevin McConomy
Ontario Ministry of Health & Long Term Care
OFFLINE
Member
Amira Alameldin
CD-ED
OFFLINE
Member
Dorrell Metcalfe
Nova Scotia Health Authority
OFFLINE
Member
Shimi Das
Tertiary Care Hospital
OFFLINE
Member
Deepti Razdan
cd-ed
OFFLINE
Member
saulat aamer
n/a
OFFLINE
Member
Raqia Hazam
Canada Health Infoway
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