Coming Soon: Standards Releases, SNOMED CT International and pCLOCD, July 31 more >

Share this page:

Diagnostic Imaging
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.
Members: 175
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
Dear DI Community, Please see following post from DICOM. Thank you! **** Dear members of DSC, WG-10, and WG-29 Could you please kindly inform me LKowalczyk@dicomstandard.org , if you are going to attend DICOM meetings in Thailand? We need a headcount. In addition, I created a spreadsheet to track the details of peoples’ arrival. This sheet will help us gather information on flights, hotels, dates and times of your arrival. All your travel information will be in one place to make the communication easier. There might be people who arrive to Thailand/Bangkok during similar times. If that’s the case, they can always share a cab from the airport to the hotel/s. REMINDER: If you reserve a hotel room at the Chatrium hotel, the hotel provides a transportation service for its guests from the airport to the hotel. • ... Please enter your travel information in the spreadsheet below. Link: ... It is posted on the ftp server: ... • 2019-Bangkok Thailand/ o DICOM WG-10-29-DSC MTGS IN THAILAND-SEPT_ARRIVAL LIST.docx Please let me know if you have any questions. Sincerely, Luiza
Raqia Hazam created a new discussion in Diagnostic Imaging
Hello everyone, Please see following post from DICOM regarding DICOM Conference in Thailand. Thank you ********** Dear DICOM Community, Registration is open! DICOM® is going on the road to Thailand this year! As a globally-adopted standard, DICOM® holds meetings worldwide to support our current stakeholders and to meet new people and organizations that are interested to learn more. 2019 DICOM Conference Registration: ... We are meeting in Bangkok, Thailand at the Chatrium Hotel Riverside Bangkok, Thursday-Friday, October 3-4, 2019 – details below and on the .... Please visit the links below to see the program, highlights and venue information. We would love to see a full house, so please feel welcome to forward this email to others that you think may be interested to join us. Please note that DICOM meetings are open to all. DICOM Working Group (WG) Meetings Dates: Monday-Wednesday, Sept. 30-Oct. 2, 2019 Times: 9:00-16:00 local time Place: ... Fee: No fee required. Monday, September 30, 2019, 9:00-16:00 • WG-10, Strategic Advisory Tuesday, October 1, 9:00-16:00 • WG-29, Education, Communication & Outreach Wednesday, October 2, 9:00-16:00 • DICOM Standard Committee DICOM® welcomes new members and our WG meetings are open to all. To learn more about DICOM and how to participate, please visit http://www.dicomstandard.org/participate/ 2019 DICOM Educational Conference Dates: Thursday-Friday, Oct. 3-4, 2019 Times: 8:00/8:30-16:50 local time Place: ... Fee: • Early-bird ends on July 31: Fee: 3,500 Baht (Approx.: $114 US USD) • Regular registration: August 1-September 15, 2019: Fee: 4,000 Baht (Approx.: $130 US USD) • On-site registration: October 3-4, 2019 Fee: 4,500 Baht (Approx.: $147 US USD) 1. Home page | ... 2. 2019 DICOM Conference Program | ... 3. 2019 DICOM Conference Meetings Schedule | ... 4. 2019 DICOM Conference Venue | ... 5. 2019 DICOM Conference Registration | ... 6. DICOM Conference Speakers – Coming soon
Arielle Fuller joined a group
Logo
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.
Jason Nagels replied to a discussion in Diagnostic Imaging
Good Morning Everyone - Thanks to all that were able to attend the Webinar on Terminology Management last Friday. Here is a link to download the .... The link will expire after 7 days. Let me know if you have any issues accessing the download. Thx, J
Raqia Hazam created a new discussion in Diagnostic Imaging
This is a cross post from the HL7 FHIR Implementers Group as requested by Gavin Tong Hi, We just wanted to give the community a heads up that on the July 24th FHIR WG meeting there will be a presentation on the findings from the ACCESS Atlantic Discovery Phase B project that examined mapping between provincial interfaces and FHIR resources. The focus for the analysis was on citizen access to lab results, and citizen and clinician access to medication profile information. The presentation will include an overview of the methodology used, some of the key findings from the mapping work and the draft resource profiles and supporting implementation guidance. Thanks, Gavin
Cezary Klimczak replied to a discussion in Diagnostic Imaging
Hi David, I think your concern is justified: what SNOMED has just done is a rather frivolous semantic adjustment for the meaning of 113345001. It has been a common understanding, also in Canada, that abdomen is separate from pelvis and they are both children of "abdomen and pelvis". This indeed seems like a tough one for the DICOM standard, with no obvious path out of this, unless you resort to updating all prior instances (not sensible/possible). I am puzzled by the SNOMED decision, to say the least. This results in a BREAKING CHANGE for those in the DICOM world who naively though that "abdomen" meant "abdomen" ?!. I hope SNOMED-CT gives that breaking change some consideration as this is certainly not the greatest marketing campaign they've embarked on. In Canada (or to be more specific in BC), we have always assumed that procedure codes would change at some point (including breaking changes), or the semantics of certain codes would change. Consequently, in BC, we decided to take an approach where we map imaging procedures codes coming from local enterprises to the provincial set (and back) and we do not rely on what has been embedded in the datasets. We have realized that imaging terminologies cannot be considered on their own merit but rather in the context of the environment where they are being used. As a precaution and insurance against "floating" imaging terminologies, we have resorted to explicit terminology mappings between LOCAL and PROVINCIAL sets. For example, if a local enterprise were to follow the lead of SNOMED-CT and start treating the code "CT of abdomen" to mean "CT of abdomen and pelvis" we would expect the chief radiologist there (or whoever is in charge of mappings) to adjust the mappings between this enterprise's terminology and the provincial terminology to "CT of abdomen" --> "CT of abdomen and pelvis" . The reverse mappings would also need to be adjusted accordingly so when we brought in a foreign prior coded "CT of abdomen and pelvis" it would end up as "CT of abdomen" . Some other institution could be different. Similarly, if the meaning of a procedure code were to change at the provincial level, e.g., "CT of abdomen" were to start meaning "CT of abdomen and pelvis", we would need to adjust the affected translation tables to/from local enterprises. The above decoupling of local and global/provincial terminologies, combined with the management of codes (procedures, body parts, coarse body parts, modalities, actionable findings, clinical findings, etc) inside a metadata registry allows us to: 1) maintain a consistent meaning of all codes at the provincial level even when a contributing enterprise that happens to use the same terminology has a different meaning for that code 2) perform the search for relevant priors against the metadata registry using the authoritative/PROVINCIAL set of codes (with authoritative semantics) rather than against the codes and semantics that are enterprise-specific and time-specific (this year's or last year's meaning?) which end up embedded in the DICOM datasets. Cezary P.S. In BC we are not using SNOMED-CT for identifying imaging procedures at the provincial level, but the problem of "floating semantics of codes" is occurring in other terminology universes as well, including those home-grown. The mapping approach insulates us from this problem. The province decided against forcing a single imaging terminology onto all healthcare enterprises there due to viability concerns.
Monief Eid joined a group
Logo
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.

Events



Upcoming events:
No events

Forum

DICOM WG-10, -29, DSC, Mtgs in Thailand-Please confirm your attendance 07/19/19
Dear DI Community, Please see following post from DICOM. Thank you! **** Dear members of DSC, WG-10, and WG-29 Could you please kindly inform me LKowalczyk@dicomstandard.org , if you are going to attend DICOM meetings in Thailand? We...
Registration is open, 2019 DICOM Educational conference in Thailand, October 3-4, 2019 07/19/19
Hello everyone, Please see following post from DICOM regarding DICOM Conference in Thailand. Thank you ********** Dear DICOM Community, Registration is open! DICOM® is going on the road to Thailand this year! As a globally-adopted...
Webinar: July 12th - 12pm - 1pm EST - Terminology mappings with application to Foreign Exam Management (and analytics, AI, etc.) 07/16/19
Good Morning Everyone - Thanks to all that were able to attend the Webinar on Terminology Management last Friday. Here is a link to download the .... The link will expire after 7 days. Let me know if you have any issues accessing the download....
HL7 FHIR WG Presentation on ACCESS Discovery Phase 07/15/19
This is a cross post from the HL7 FHIR Implementers Group as requested by Gavin Tong Hi, We just wanted to give the community a heads up that on the July 24th FHIR WG meeting there will be a presentation on the findings from the ACCESS Atlant...
Terminology: Does the abdomen include the pelvis? 07/12/19
Hi David, I think your concern is justified: what SNOMED has just done is a rather frivolous semantic adjustment for the meaning of 113345001. It has been a common understanding, also in Canada, that abdomen is separate from pelvis and they are bo...
Terminology: Does the abdomen include the pelvis? 07/12/19
SNOMED CT has recently been doing major work on cleaning up their anatomy. One of the changes is to redefine the current code for "abdomen" (113345001) to mean "abdominopelvic", i.e., to include the pelvis. This has procedure code consequence...
Webinar: July 12th - 12pm - 1pm EST - Terminology mappings with application to Foreign Exam Management (and analytics, AI, etc.) 07/11/19
Hi All - Just a reminder that tomorrow's scheduled DI Community meeting will be a webinar providing an experiential look at how terminology mappings have been managed in the province of British Columbia. Event Info: https://infocentral.info...
DICOM News & New DICOM Working Group for Dermatology 07/09/19
Hello everyone, Please see below post from DICOM. ************ Dear DICOM Community DICOM News New Edition published– suitable for updating management on DICOM developments! The status of CPs and Supplements, following the June 2019...
Webinar: July 12th - 12pm - 1pm EST - Terminology mappings with application to Foreign Exam Management (and analytics, AI, etc.) 07/03/19
Hi All - Sorry for any confusion from the previous title on the last post. The Webinar is July 12th @ 12pm - 1pm EST. Thx, J
Webinar: July 12th - 12pm - 1pm EST - Terminology mappings with application to Foreign Exam Management (and analytics, AI, etc.) 07/03/19
Good Afternoon All! Next week's DI Community Group Meeting, will feature a presentation/demo of how British Columbia is managing terminology mappings with their VNA solution. The details for the webinar are listed below. Please forward this along...
Call for Participation: Pathology Visions 2019 Connectathon 06/27/19
Hello, Knowing all of the interest and success of Connectathons, please see the note below from DICOM We are announcing a Connectathon to be held at the Pathology Visions 2019 Conference (...) at the Hyatt Regency Orlando. We have a documen...
exam room naming convention 06/24/19
Hi there, does anyone know of a current standard in naming diagnostic imaging acquisition units (exam rooms)? We are looking into standardizing the naming convention of acquisition units in both the RIS and PACS and ideally having the name of the e...
Update: Collecting ideas for the new DICOM logo by Monday July 1 06/21/19
Dear members of DICOM Community, We are extending the deadline for submission ideas for the new DICOM logo, which is now July 1, 2019. Meeting folder: ... Next steps: •After July 1, 2019, an official ballot will go out to voting members of...
DICOM WG-29 ECO Minutes posted-June 18, 2019 06/20/19
Hello everyone, Please see below post from DICOM regarding WG-29 ECO. *************************** Hello WG-29 ECO Cc: WG-10 & DSC rosters The minutes of the June 18, 2019 WG-29 ECO t-con have been approved by the Legal Counsel of the D...
DICOM 2019c Release 06/20/19
Hello everyone, Please see below post from DICOM regarding 2019c release: *************** Dear DICOM Community The 2019c release of the DICOM standard is now available from the NEMA site: ... It is also indexed from the status page a...

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

IHE ( 8 Documents )

Meeting & Materials ( 88 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
  • TermManager
  • TermWorks
  • WebHook Notifications

The Canadian FHIR® Registry supports collaborative development in an effort to accelerate sustainable growth of FHIR, locally and internationally. The registry is 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 at midnight on Sundays. 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 (Inofway) 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.

  • For all non-jurisdictional and Infoway owned subsets, email the completed form to This email address is being protected from spambots. You need JavaScript enabled to view it.
  • All other requests must be sent to the Jurisdictional Representatives for OIDs
.

OID submission guidelines

  1. Jurisdictional Teams 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 and follow up 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:
  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 requests 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 TermManager is a web-based data mapping solution which is provided by request for free to individuals who have Standards Access. It provides comprehensive mapping capability to SNOMED CT and the Canadian Edition of SNOMED CT with multi-user work flow options and flexible output formats.

 Implementation Guidelines & Resources

  • This email address is being protected from spambots. You need JavaScript enabled to view it. - Email your request to This email address is being protected from spambots. You need JavaScript enabled to view it. with the following information:
    • Your InfoCentral username.
    • Is this a new request or are you renewing your access to use TermManager?
    • Intended Use: Please describe the project and mapping requirements. Please Note: TermManager is limited to mapping with SNOMED CT. As more terminologies are available, they will be added.
    • Local Terms: Please describe the source of your local terms (EMR, LIS, etc.).
    • Please describe your requirements/project if they don't fit the above.
  • TermManager Release Notes

knowing Learn More

  • This email address is being protected from spambots. You need JavaScript enabled to view it.
  • Apelon Mapping Tool Presentation
  • SNOMED CT Education
  • TermManager User Guide
  • How TermManager Works
  • TermManager FAQs

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
Jason Nagels
HDIRS
OFFLINE
Admin
Arielle Fuller
London Health Sciences Centre
OFFLINE
Member
Monief Eid
Ministry of Health
OFFLINE
Member
Akram Mohammed
Philips Healthcare
OFFLINE
Member
Mark Cicero
16 Bit Inc.
OFFLINE
Member
Bryan Dearlove
GE Healthcare
OFFLINE
Member
Laurence Chiu
Google
OFFLINE
Member
Jeremy Robertson
Vancouver Coastal Health
OFFLINE
Member
Gary Yao
GE Healthcare Digital Canada
OFFLINE
Member
Luiz Aizawa
London Health Science Centre
OFFLINE
Member
Josee Patenaude
CIUSS Centre sud de Montréal
OFFLINE
Member
ashley smith
n/a
OFFLINE
Member
Helena Nutakor
CENTRE FOR DISTANCE EDUCATION
OFFLINE
Member

InfoCentral logo

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



Login Register