As Canada’s centre for Health Information Standards, Infoway is proud to support World Standards Day! 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: 139
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

Brian McGillis replied to a discussion in Diagnostic Imaging
Draft Use Case for call today. User case scenario for Peer Review One billion radiology studies are performed annually with an error rate of approximately 4%, which translates in 40 million errors per year. The leading cause of malpractice law suits against radiologists is the incorrect interpretation of studies. There has been a series of high profile ­reviews of radiologists in Canada, with media coverage, which resulted in loss of confidence in the profession and serious damages to the radiologists involved. This has raised awareness among radiologists that they have to engage actively in quality control to avoid situations where large scale reviews are mandated by local or regional authorities. The first peer review solution for radiologists was released in 2002 by the American College of Radiologists (ACR), as a retrospective, passive process where a radiologist reporting a study will review the previous study and score it on a scale from 1 to 4. In recent years, this approach has been challenged as it doesn’t answer to the requirements of effective patient care. Better suited are timed retrospective or ideally prospective peer review. The regulatory landscape has changed, after a large scale review in British Columbia . Following this review, the report released by Dr. Cochrane in 2011 has issued a number of recommendations, one of them, number 16, being the necessity to implement a standardized retrospective peer review process. Physician Peer-Review is a requirement for the American College of Radiology (ACR) - voluntary with no penalty other than refusal of accreditation. The Joint Commission on Accreditation of Healthcare Organizations (JCAHO) and the Accreditation Council for Graduate Medical Education (ACGME) require all staff to participate in peer review approximately 5% of cases. The radiologists expect that the peer review process: Reveals opportunities for quality improvement Is non-punitive Helps ensure competence Helps improve individual outcomes Is a fair, unbiased, consistent process Allows trends to be identified Ensures the opinions of both the reviewers and the radiologists being reviewed are recorded. Allow assessment of the agreement of the original report with subsequent review (or surgical or pathology findings). Allows easy participation The Canadian Association of Radiologists in a white paper released in September 2011 gave its recommendations for a peer-review electronic system: Include a reactive or proactive double reading with 2 physicians interpreting the same study. Allow for random selection of studies to be reviewed on a regularly scheduled basis. Examinations must be representative of each physician’s subspecialty. Approved classification of peer-review findings with regard to level of quality concern. Has minimal effect on workflow Fair, unbiased, consistent process ensuring confidentiality for all aspects of peer review and anonymity for reporting and reviewing radiologists when possible. Summary statistics can be generated and comparisons shown for each physician by modality to help the coordinator assess performance standards. Summary data for each facility or practice by modality can be obtained to aid the departmental QA program. There is a need for a standardized approach to electronic peer review within and between institutions, to ensure that implemented peer review programs provide essential functionality as listed above. This would also allow organizations that are engaging in a process to purchase or otherwise implement a peer review system to have a defined standard to require, so that they have confidence in the system that they will be selecting.
Jason Nagels created a new discussion in Diagnostic Imaging
Good Morning - To prepare ourselves for the next set of work activities for this group, we would like to arrange a half day face to face planning session to determine the next work activities to work on. Please complete the doodle poll listed below: https://doodle.com/poll/hv8ngzywnzzms6qz Thanks, J
Jason Nagels created a new discussion in Diagnostic Imaging
Hi All - The agenda for today's meeting is listed below: ... Thanks, J
Jason Nagels replied to a discussion in Diagnostic Imaging
Hi All - For next week's FEM/IDEP call, please refer to the WebEx and t-con listed below: https://infoway-inforoute.webex.com/meet/SPS21 Conference Call Info: 1-866-626-0833 Conference Code: 753 117 1082 Thanks, J
Teri Sippel Schmidt created a new discussion in Diagnostic Imaging
Hi all- We have decided to just hold the IDEP (FEM) use case/transaction sequence diagram and IHE Suppl Vol 1 review together on Tuesday, Oct 24th, from 10-11:30am Eastern. (as discussed on previous conference call...) Jason will reply here with the webex info shortly. I will add a link to view the transaction diagrams shortly also, but just want to be sure to get this onto everyone's calendar for now to reserve the time. Thanks, Teri
Jason Nagels created a new discussion in Diagnostic Imaging
Hi all - Please find a link to last week's meeting minutes. ... Thanks, J

Events



Upcoming events:
Fri Nov 03 @12:00PM - 01:00PM
DI Community Meeting (Bi-Weekly)
Fri Nov 17 @12:00PM - 01:00PM
DI Community Meeting (Bi-Weekly)
Fri Dec 01 @12:00PM - 01:00PM
DI Community Meeting (Bi-Weekly)

Forum

DI Community Meeting Agenda - Friday October 20th 10/20/17
Draft Use Case for call today. User case scenario for Peer Review One billion radiology studies are performed annually with an error rate of approximately 4%, which translates in 40 million errors per year. The leading cause of malpractice...
Doodle Poll: Face to Face Half Day Planning Session 10/20/17
Good Morning - To prepare ourselves for the next set of work activities for this group, we would like to arrange a half day face to face planning session to determine the next work activities to work on. Please complete the doodle poll listed bel...
DI Community Meeting Agenda - Friday October 20th 10/20/17
Hi All - The agenda for today's meeting is listed below: ... Thanks, J
Th, Oct 24th, 10am-11:30am ET - IDEP (FEM) Sequence diagram and IHE Vol 1 review 10/20/17
Hi All - For next week's FEM/IDEP call, please refer to the WebEx and t-con listed below: https://infoway-inforoute.webex.com/meet/SPS21 Conference Call Info: 1-866-626-0833 Conference Code: 753 117 1082 Thanks, J
Th, Oct 24th, 10am-11:30am ET - IDEP (FEM) Sequence diagram and IHE Vol 1 review 10/16/17
Hi all- We have decided to just hold the IDEP (FEM) use case/transaction sequence diagram and IHE Suppl Vol 1 review together on Tuesday, Oct 24th, from 10-11:30am Eastern. (as discussed on previous conference call...) Jason will reply here wi...
October 6 - Meeting Minutes 10/12/17
Hi all - Please find a link to last week's meeting minutes. ... Thanks, J
IHE Rad IDEP (FEM) pre-Tech Comm conference calls 10/10/17
Hi Stephen - The IHE F2F meeting is held at the following location: Meeting Location: Radiological Society of North America (RSNA) 820 Jorie Blvd., Oak Brook, IL 60523 Main Phone: 630-571-2670 Thanks, J
IHE Rad IDEP (FEM) pre-Tech Comm conference calls 10/10/17
Please forgive my ambiguity I was referring to the Oak Brook location.
IHE Rad IDEP (FEM) pre-Tech Comm conference calls 10/09/17
Hi- The venue will be webex. As soon as we pick a date and time (as soon as the doodle poll has a few more responses...), we will get a webex set up and I will post that to this Forums. It will probably only be a one hour webex, maybe 1.5 hours...
IHE Rad IDEP (FEM) pre-Tech Comm conference calls 10/09/17
Do you have venue information for this location?
IHE Rad IDEP (FEM) pre-Tech Comm conference calls 10/06/17
Hello CHI IDEP/FEM group- Please see doodle link near end of message! First, thanks again for being on the IHE Rad voting call such that we were able to get this profile approved in full! In review of the discussion this morning, the high le...
DI Working Group Agenda: October 6, 12pm-1pm EST 10/06/17
Good Morning Everyone - Apologies for not posting the agenda earlier. Please find today's agenda available below: ... Thanks, J
Webinar "Bundling Standards for Interoperability – ISO’s new Reference Standards Portfolio for Clinical Imaging" – October 26th 12:00-1:00pm ET 10/02/17
The ISO community will be hosting a Webinar on "Bundling Standards for Interoperability – ISO’s new Reference Standards Portfolio for Clinical Imaging" - October 26th 12:00-1:00pm ET. As the requirements for interoperability of healthcare informatio...
Congratulations on IHE Vote Results 09/22/17
Congratulations and thanks for to all members of the Infoway DI Community. Your effort and assistance helped us succeed as a group in having IDEP/FEM voted on for a maximum level of effort. Contributing your time to join these calls allowed us to...
Reminder: Final IHE Radiology Planning Committee Voting Call) - September 22nd 09/08/17
Good Afternoon Everyone - This post is to remind you that in two weeks, the DI Community call is cancelled as the Final IHE vote takes place September 22 @ 11:00am EST. It is very important that if you were on the previous IHE Radiology Planni...

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 )

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

Published on Oct 20, 2017 by Jason Nagels

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

Published on Oct 12, 2017 by Jason Nagels

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

Published on Oct 06, 2017 by Jason Nagels

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

Published on Sep 06, 2017 by Jason Nagels

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

Published on Aug 10, 2017 by Jason Nagels

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

Published on Aug 10, 2017 by Jason Nagels

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

Published on Jul 28, 2017 by Jason Nagels

June 16/2017 Meeting Mins

Published on Jun 22, 2017 by Jason Nagels

CHI FEM Report Format, Conversion, and Transport Options

Published on Jun 20, 2017 by Teri Sippel Schmidt

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

Published on Jun 15, 2017 by Jason Nagels

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

Published on May 19, 2017 by Jason Nagels

IHE FEM Use Case 4 - ED Transfer

Published on May 19, 2017 by Teri Sippel Schmidt

IHE FEM Use Case 3 - Study Read at different facility

Published on May 19, 2017 by Teri Sippel Schmidt

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

Published on May 18, 2017 by Jason Nagels

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

Published on May 09, 2017 by Jason Nagels

May 5/2017 - DI Community Agenda

Published on May 03, 2017 by Jason Nagels

April 21/2017 Meeting Mins

Published on May 03, 2017 by Jason Nagels

April 21 Meeting Agenda

Published on Apr 20, 2017 by Jason Nagels

April 3-17 Meeting Mins

Published on Apr 11, 2017 by Jason Nagels

April 7-2017 Meeting Mins

Published on Apr 11, 2017 by Jason Nagels

April 7 Meeting Agenda

Published on Apr 06, 2017 by Jason Nagels

March 24 Meeting Mins

Published on Mar 31, 2017 by Jason Nagels

April 3rd Face to Face Agenda

Published on Mar 30, 2017 by Jason Nagels

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

Published on Mar 22, 2017 by Jason Nagels

March 10 Meeting Mins

Published on Mar 15, 2017 by Jason Nagels

March 10 Meeting Agenda

Published on Mar 08, 2017 by Jason Nagels

DI Community Proposal Template

Published on Feb 27, 2017 by Jason Nagels

Feb 24 Meeting Minutes

Published on Feb 25, 2017 by Jason Nagels

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

Published on Feb 23, 2017 by Jason Nagels

Feb 8 Face to Face Meeting Minutes

Published on Feb 12, 2017 by Jason Nagels

IHE Rad Non-Urgent Critical Findings Follow-up Overview

Published on Feb 09, 2017 by Teri Sippel Schmidt

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

Published on Feb 06, 2017 by Jason Nagels

DI Working Group Community Minutes: January 13, 2017

Published on Jan 13, 2017 by Jason Nagels

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

Published on Jan 10, 2017 by Jason Nagels

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

Published on Nov 16, 2016 by Laura Repchik

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

Published on Oct 26, 2016 by Laura Repchik

DI Working Group Community Minutes: October 21, 2016

Published on Oct 26, 2016 by Laura Repchik

DI Working Group Agenda: October 21, 2016

Published on Oct 19, 2016 by Laura Repchik

DI Working Group Agenda: September 23, 12pm EST

Published on Sep 22, 2016 by Laura Repchik

Clinical Division Support and the 2017 CMS Imaging Mandate

Published on Jun 10, 2016 by Laura Repchik

DI CS eHealth Update Presentation for DI WGC May 31 2016

Published on Jun 06, 2016 by Laura Repchik

DI Working Group Agenda: May 31, 2016

Published on May 30, 2016 by Laura Repchik

Diagnostic Imaging Community - Agenda for Friday May 6, 2016

Published on May 04, 2016 by Laura Repchik

Diagnostic Imaging Community - Agenda for Friday April 8, 2016

Published on Apr 07, 2016 by Laura Repchik

Remote Read Status - Next Steps

Published on Feb 16, 2016 by Ben Macerola

Meeting Agenda: DI Working Group Friday February 12, 2016

Published on Feb 11, 2016 by Laura Repchik

IHE Suppl XRR-WD Document

Published on Jan 15, 2016 by Laura Repchik

Remote Reporting for Imaging Dec 18, 2015 Meeting Agenda

Published on Dec 18, 2015 by Laura Repchik

Clinical Requirements Remote Read Radiologists Review v2

Published on Oct 09, 2015 by Diane Larwood

Detailed IHE Remote Read Proposal

Published on Sep 11, 2015 by Ben Macerola

DI RRI 2015 07 013

Published on Jul 13, 2015 by Chris Lindop

Remote Reading iGuide - KH

Published on Jul 05, 2015 by Kinson Ho

DI RRI 2015 05 08 revPeterP

Published on May 12, 2015 by Peter Popowycz

Diagnostic Imaging WG Meeting May 8, 2015

Published on May 07, 2015 by Laura Repchik

SCWG 10 Transition to DI Community

Published on Mar 26, 2015 by Diane Larwood

Video

This Group has no videos.

Solutions

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

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.

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 (normally $100 USD fee per OID request).

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
Amanda Borecki
N/A
OFFLINE
Member
Sari Schapira
Canada Health Infoway
OFFLINE
Member
Zubair Usman
Sectra Canada Inc.
OFFLINE
Member
James Protz
Mayfair Diagnostics
OFFLINE
Member
Ryan Doherty
iamsick.ca
OFFLINE
Member
Thomas Zhou
Alberta Health
OFFLINE
Member
Abdullah Khan
-
OFFLINE
Member
Radhika Verma
eHealth Ontario
OFFLINE
Member
Daniel Pan
Ehealth ON
OFFLINE
Member
Parminder Dhillon
n/a
OFFLINE
Member
Eric Savoie
xrad technologie / Ministère de la santé et services sociaux du Québec
OFFLINE
Member
Brent McGaw
Canada Health Infoway
OFFLINE
Member

Join us at Partnership Conference on Nov. 14 for a keynote presentation on delivering meaningful at scale solutions… https://t.co/2Dous9Ue06

by Infoway

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