Share this page:

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

Brent McGaw joined a group
Logo
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.
Emilie Brisson 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
Just a reminder that tomorrow (April 25) at 10am EST is the first FEM Bi-Weekly Call. https://infoway-inforoute.webex.com/meet/SPS21 Conference Call Info: 1-866-626-0833 Conference Code: 753 117 1082 See you there! Thanks,
Jason Nagels created a new discussion in Diagnostic Imaging
Hi All - As brought up on today's call, here are the dates for the FEM sub-group meetings. All meetings will take place 10am-11am EST. April 25, May 9, May 23, June 6, June 20 https://infoway-inforoute.webex.com/meet/SPS21 Password: Infoway10 Conference Call Info: 1-866-626-0833 Conference Code: 753 117 1082 Thanks, J
Babette Macrae joined a group
Logo
Exploring Diagnostic Imaging topics to accelerate interoperability , such as Foreign Exam Management, Remote Reading and Radiology Synoptic Reporting.
Kinson Ho created a new discussion in Diagnostic Imaging
Hi All, The upcoming Radiology Face-to-Face meeting will be on May 9 - 12. The draft agenda is available at http://wiki.ihe.net/index.php/Rad_Tech_Agenda_2017-05-09_to_2017-05-12 Thanks, Kinson
Jason Nagels created a new discussion in Diagnostic Imaging
Hi All - Please find the agenda for tomorrow's t-con. ... Thanks, J

Events



Upcoming events:
No events

Forum

FEM Sub-Group Meetings - Starting April 25 10am-11am EST (bi-weekly) 04/24/17
Just a reminder that tomorrow (April 25) at 10am EST is the first FEM Bi-Weekly Call. https://infoway-inforoute.webex.com/meet/SPS21 Conference Call Info: 1-866-626-0833 Conference Code: 753 117 1082 See you there! Thanks,
FEM Sub-Group Meetings - Starting April 25 10am-11am EST (bi-weekly) 04/21/17
Hi All - As brought up on today's call, here are the dates for the FEM sub-group meetings. All meetings will take place 10am-11am EST. April 25, May 9, May 23, June 6, June 20 https://infoway-inforoute.webex.com/meet/SPS21 Password: Infow...
IHE Radiology Face-to-Face meeting in May 04/21/17
Hi All, The upcoming Radiology Face-to-Face meeting will be on May 9 - 12. The draft agenda is available at http://wiki.ihe.net/index.php/Rad_Tech_Agenda_2017-05-09_to_2017-05-12 Thanks, Kinson
DI Community Meeting Agenda - Friday April 21th 04/20/17
Hi All - Please find the agenda for tomorrow's t-con. ... Thanks, J
Meeting Mins - April 3rd and April 7th 2017 04/11/17
The meeting mins for the April 3 face to face and April 7th t-con are available below. ...
April 7 Meeting Agenda 04/06/17
Hi All - Here is the agenda for tomorrow's meeting. ... Thanks, J
Very early version: IHE Rad Foreign Exam Mngt (FEM) supplement template 03/31/17
Hello CHI DI Community, I have uploaded (in MS Word format) a very initial version of the IHE Rad FEM supplement template. ... There are only two things that you should bother to review yet. (Also, please ignore the massive quantities of it...
Use of Google Docs for co-development 03/31/17
Hello CHI Diagnostic Imaging Community: re-opening topic... Google Drive worked great for co-developing extremely complex and long profiles. But, we are now learning that it is much more difficult to re-convert from Google Drive back to MS Wor...
March 24 Meeting Mins 03/31/17
Hi All - Please find the Meeting Mins available below: ... Thanks, J
April 3rd Face to Face Agenda 03/30/17
Hi All - Please find attached the agenda for Monday's face to face meeting. ... As well, I apologize for not having last week's meeting minutes out yet. I hope to have those posted EOD tomorrow. Thanks, J
MIIT 2017 03/27/17
Hi All - Seeing as the participants in this group have an interest in all things related to DI... I thought I would send a quick FYI regarding a related educational opportunity coming up in Ontario at the end of April. Here are the details:...
"Coarse" Body Parts / Anatomy 03/27/17
The ON DICS terminology project applies 2 mappings where coarse body parts are use: (1)local to provincial, and also (2) provincial to DICOM CID to support FEM. (1) All ON DI procedure terms should have a target site for imaging (i.e. more granular...
"Coarse" Body Parts / Anatomy 03/27/17
When I mentioned ‘relevancy’ on the call with respect to foreign priors my intention wasn’t to go down the rabbit hole of terminology. My thoughts were more along the lines of how systems that use disparate terminology dictionaries but want to ingest...
"Coarse" Body Parts / Anatomy 03/27/17
Hello, To clarify, my comments on Friday's call was not from the perspective of CCO. CCO is does not currently have any specifications in regards to body parts for Cancer Imaging. I was speaking from experiences during work on creating the standar...
"Coarse" Body Parts / Anatomy 03/27/17
Hi, The codes are coming from SNOMED CT International. I suggest that a validation of the codes should be done to make sure they are all active in the latest SNOMED CT version which is January 2017, and membership be adjusted according to usage and...

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

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

  • FHIR Terminology Service API
  • HAPI FHIR
  • HAPI v2
  • HL7 Explorer
  • InfoRMS
  • InfoScribe
  • Message Builder
  • Message ReMixer
  • Object Identifiers (OIDs)
  • SNOMED CT Browser
  • Terminology Gateway
  • Terminology Service API
  • TermWorks

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.

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, pan-Canadian Subsets and pan-Canadian HL7 artifacts. Not sure if you have access to InfoRMS? Manage your InfoRMS Access in your user profile.
SNOMED CT
 

Submit or follow requests to SNOMED CT

pCLOCD/LOINC
 

Submit or follow requests to pCLOCD/LOINC

pan-Canadian Subsets
 

Submit or follow requests to pan-Canadian Subsets

HL7
 

Follow requests to pan-Canadian HL7 messaging

 

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.

  • OIDs are intended to be globally unique and never re-used
  • OIDs in the pan-Canadian standards identify terminology code systems and are transmitted in HL7 messages
  • OIDS used to identify terminology subsets are not transmitted in HL7 messages, rather these OIDs are used for vocabulary maintenance and Terminology Services
  • OIDs are used to qualify local identifiers (e.g. patient identifiers) such that the combination of an OID (assigning authority) and a local identifier remains globally unique

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 which is provided by request for free 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.

 Education

  • Introduction to SNOMED CT (English)
  • Introduction to SNOMED CT (French)
  • This email address is being protected from spambots. You need JavaScript enabled to view it.

Web Conference

Please login to acquire access to the InfoCentral web conferencing.

Members

Ben Macerola
Canada Health Infoway
OFFLINE
Contact
Linda Monico
Canada Health Infoway
OFFLINE
Admin
Tasha Shaw-Verbic
Canada Health Infoway
OFFLINE
Admin
Brent McGaw
Canada Health Infoway
OFFLINE
Member
Emilie Brisson
Ministère de la Santé et des Services sociaux
OFFLINE
Member
Babette Macrae
Accusys Solutions
OFFLINE
Member
Stephen Winnett
Carestream Health
OFFLINE
Member
Janice Spence
eHealth Ontario
OFFLINE
Member
Arif Kotadia
PHSA (Provincial Health Services Agency) British Columbia
OFFLINE
Member
Becki VanderWal
MHA and LHSC
OFFLINE
Member
Brian McGillis
Realtime Medical
OFFLINE
Member
Rob McGuffin
London Health Sciences Centre
OFFLINE
Member
Hamid Neshat
Agfa Healthcare
OFFLINE
Member
Alexander Goel
Cancer Care Ontario
OFFLINE
Member
Don Dennison
Don K Dennison Solutions Inc.
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