Share this page:

FHIR® Implementations
Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.
Members: 106
Contact: Attila Farkas
Type: Open
Access: Public
Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.

About

NEW: visit the new FHIR page on InfoScribe!

Following an initial meeting hosted on the HL7 Community forum regarding the future of FHIR in Canada, there was a proposal made to start this working group. There are two interim co-chairs that volunteered to take this initiative off the ground:

Yaron Derman - Manager of Standards and Data Exchange at eHealth Ontario

Gavin Tong - Associate Partner at Gevity Consulting

Join the FHIR Implementations Working Group!

Please check the Forum to learn more about the Rules of Engagement, Tooling, Governance and other important information. Check back often as this will likely turn out to be a very active group. Better yet, subscribe for notifications.


There is no denying that HL7®, FHIR® is gaining momentum across the globe and this trend is certainly evident here in Canada. As this emerging standard promises a number of quick wins and benefits, it is tempting to overlook the challenges that successful implementations will have to overcome to truly support standardization. Extensions, profiles and implementation guides are some of the FHIR tools that are readily available and quite tempting - what the community has to decide however is how to use them, or rather reuse them, wisely.

Most recently, a number of jurisdictional implementation teams have expressed a desire to look at new ways of taking advantage of existing systems and services, such as provider registries, client registries, immunization repositories and consent management. With these efforts underway, and more to come, now is the time to develop a sustainable platform of information building and sharing.

With this in mind, InfoCentral has launched this new Working Group dedicated solely to FHIR. It is the hope that by working together, implementers across the country will have the opportunity to build and share FHIR assets and in turn support the organic growth of solutions and of the community itself. Become part of this movement and help shape a sustainable future in interoperability.

Activity

Gavin Tong replied to a discussion in FHIR® Implementations
Hi, Notes from this week's FHIR Community Call are below. Attendees: Yaron Derman, Natalya Pogrebetsky, Smita Kachroo, Ken Sinn, Fariba Behzadi, Janice Spence, Fang, Sahaana Uthayacumar, Gavin Tong, Kris Lewis, Attila Farkas, Tim Berezny, Alex Goel, John Wills, Pierre Beauchemin, Rita Pyle, Anil Patel, ACTION ITEM REVIEW: Mar 22:1 - Tim Berezny to see if there is anyone else interested in SMART on FHIR and working on Canadianizing the US Profiles. CLOSED • Tim is looking at using SMART on FHIR for his implementation, and he’s willing to share what he’s done. • OTN is using pieces of SMART on FHIR. Yaron to see if we can find anyone there who wants to join the WG. Mar 22:2 - Yaron to post the google sheet and share with the forum, others to contribute. CLOSED. Jan 25:4: Rod Thurber to reach out to RelayHealth to get involved in eReferral workstream. CLOSED. Jan 25:5: Susan Anderson: find out if someone from Orion to get involved in eReferral workstream. CLOSED. NEW ACTION ITEMS: May 24:1: Gavin to update event instance on Infocentral with correct URL and Dial-In # May 24:2: Yaron to see if there is anyone at OTN who wants to share what they are doing with SMART on FHIR. May 24:3: Attila to post his notes on the HL7 WGM including the link to the HL7 WIKI on Registries. May 24:4: Gavin to follow up with Rod and Susan to see if they know people who want to join the eReferral workstream. Minutes 1. Updates (Gavin, 10 mins): HL7 WGM in Madrid: 302 attendees (vs 525 for the previous WGM). Productive sessions focused on advancing various topics, with a heavy focus on FHIR in the majority of the working groups. 2 new affiliates joined – HL7 Poland and HL7 United Arab Emirates for a total of 36 affiliates. Netherlands has published FHIR profiles and established governance around them, and Norway reported out on a number of FHIR related initiatives and using Simplifier.net to register profiles. Planning is underway for a FHIR Dev Days event in the US, similar to the one Furore has put on in the Netherlands previously. Slides available here: https://infocentral.infoway-inforoute.ca/en/resources/docs/hl7/2051-hl7-international-wgm-may-2017-update Attila has several pages of notes on tooling, and will share those findings at the next FHIR tooling WG meeting. Attila noted that Simplifier.net has an overview of all the different profiles created by people from different countries. Yaron asked if there is a person from HL7 Netherlands that could share their experiences in setting up rules for the governance and maintenance. Attila believes there will be recommendations on this topic coming out of the business case and tooling tracks. Ken asked if there were any updates on terminology and vocabulary at the HL7 WGM, and some intel about harmonizing vocabulary across different HL7 versions. Attila attended the connectathon and noted that the big focus going forward will be more on the semantic interoperability. He noted that there are several terminology servers available to support the connectathons, but doesn’t know if there are any specific work items related to this harmonization. FHIR North: 238 registrants. The day focused on providing education sessions in parallel to the connectathon. The connectathon featured FHIR based exchanges with systems representing components of Ontario’s EHR, such as the Ontario Lab Information System, Digital Health Drug and Immunization Repositories, HRM, and others. Majority of participants where there for the education. Probably a symptom of two things: marketing not reaching developers and the fact that it’s still early days for many organizations as they are likely in the Awareness and Deciding to act – using the ADKAR model of change. Attila will provide a high-level overview of the same presentation he provided at FHIR north will be presented at Friday’s tooling meeting. 2. Roundtable: Registries Natalya reported that the last few meetings have been on sharing what different implementers have built to date. The next meeting will be focused on providing eHealth Ontario business model overview for PR and CR. Attila noted that during the HL7 WGM connectathon he came across a wealth of knowledge on the HL7 Wiki about registries and work that is happening internationally. May 24:3: Attila to post his notes on the HL7 WGM including the link to the HL7 WIKI on registries. Tooling Attila noted that the weekly meeting stopped about 2 weeks before FHIR North. One of the things they were looking at was API generation and the other on FHIR Profile Registry. The working group hasn’t had a chance to work on these topics for a month but are hoping to reinvigorate the confirmations. Attila noted that he received great feedback from HL7 WGM attendees who supported the idea of going from capability statements through to API generation, as well as a desire to share tooling information and work together on evolving them. Attila reported that the work on FHIR API generation has evolved well but the work on the FHIR Registry needs some strategic thinking and input from professionals in the field. These will continue to be discussed at the Friday meeting. Gavin asked for examples of strategic considerations with the FHIR Registry. Attila noted that there are number of implementations out there like – HAPI FHIR, Graham Grieves implementation, etc. and Furore’s Simplifier, Forge and their new FHIR server/client side resources. All three are reactive to changes and evolution of FHIR. It would be inefficient for Canada to go off and build its own, and instead determine how to invest in the current tooling work. Business Case Attila noted that the best role for us is to ensure we share knowledge and tools from across Canada and around the world. SMART on FHIR is being brought under HL7 international governance and there would theoretically be rules for its use in Canada. An end goal could be a portal that helps developers determine if their Smart on FHIR app conforms to profiles in Canada, and could be used in other parts of the world. The business case has reached a point that it was ready for reviewing. Feedback from one reviewer was that it seemed a bit pessimistic and didn’t provide an optimistic view. Igor contributed some quantifiable benefits for the work. This track will likely merge into the tooling track by focusing on how FHIR can add value rather than articulating a specific business case. Solution Architecture Kris said that there has been good work developing the URI spreadsheet and the next meeting is on Friday. Natalya reported that they are working on how to spell out the URI names (e.g. health card number instead of HCN), and that there is a proposal out for people to review the spreadsheet and provide their feedback. eReferral Tim reported that they have a new co-chair – Caryn Harris (Orion Health) - and they’ve met to lay out plans going forward. The group is working on defining the eReferral pathways and putting boundaries on them. The WG has a good number of representatives from the eReferral vendor community to contribute to conversations, but needs more warm bodies to do actual work. Tim is building an API and bringing back to the group with questions and getting feedback from them. Once all the key questions are resolved, there will be a step where this gets converted into an actual implementation guide. Tim presented a quick demo on an app and the referral request data package that is sent to a server, and then at the server using a bit of SMART on FHIR approach to managing workflow/business processes. Tim noted that they are open to others if they want to try using the ‘EMR lite’ tool that CareDove has built to send messages to their products/apps. 3. Any new projects that would like broader input / review (Yaron, 5 mins) This item was skipped due to lack of time. 4. Recruitment drive (Yaron, 5 mins) Reminder to all to encourage others to attend the FHIR Implementers WG call and/or the topic focused calls. There is a lot of great progress on the tooling fronts, URI, and eReferral API work that people across the country probably want to know about. 5. Additional discussion items (15 mins) None
FHIR Tooling workstream
Friday, June 09, 2017, 11:00am - 12:00pm
FHIR Tooling working stream. Agenda: - update on the business requirements for the FHIR Registry - evaluation of approach to implementation - if necessary conditions met. Topic: FHIR ToolingTime: Jun 9, 2017 11:00 AM Eastern Time (US and Canada) Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/443926318 Or iPhone one-tap (Canada Toll): +16475580588,443926318# Or Telephone: Dial: +1 647 558 0588 (Canada Toll) +1 855 880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free) Meeting ID: 443 926 318
Attila Farkas replied to a discussion in FHIR® Implementations
Hi everyone, As promised during the monthly FHIR WG call, I have uploaded my notes from attending the HL7 International WG meetings in Madrid, June 5-12, 2017. The document (since it's long) is uploaded to the document section. You can download it here: .... Feel free to send me any questions you may have. Thanks, Attila
Attila Farkas replied to a discussion in FHIR® Implementations
Tooling meeting in progress. Please join here: https://zoom.us/j/726859879
FHIR Community - monthly tcon
Wednesday, June 28, 2017, 12:00pm - 01:00pm
Video Conference: https://zoom.us/j/563726340 Teleconference #: 1 877 369 0926 Meeting ID: 563 726 340
Jaimes Blunt joined a group
Logo
Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.
Sisira De Sliva joined a group
Logo
Dedicated to the discovery, definition and publishing of HL7® FHIR® Implementation Guides, Conformance, Profiles, Extensions and ValueSets serving the Canadian context.

Events



Upcoming events:
Wed May 31 @ 1:00PM - 02:00PM
CR/PR FHIR Spec Development Workstream
Fri Jun 02 @ 2:00PM - 03:00PM
FHIR Solution Architecture
Fri Jun 09 @11:00AM - 12:00PM
FHIR Tooling workstream

Forum

Upcoming FHIR Community Call - May 24, 12 - 1 EST 05/26/17
Hi, Notes from this week's FHIR Community Call are below. Attendees: Yaron Derman, Natalya Pogrebetsky, Smita Kachroo, Ken Sinn, Fariba Behzadi, Janice Spence, Fang, Sahaana Uthayacumar, Gavin Tong, Kris Lewis, Attila Farkas, Tim Berezny, Alex...
Upcoming FHIR Community Call - May 24, 12 - 1 EST 05/26/17
Hi everyone, As promised during the monthly FHIR WG call, I have uploaded my notes from attending the HL7 International WG meetings in Madrid, June 5-12, 2017. The document (since it's long) is uploaded to the document section. You can download it...
Tooling work stream 05/26/17
Tooling meeting in progress. Please join here: https://zoom.us/j/726859879
PR/CR Spec Development work stream 05/25/17
FYI - Added a meeting to the calendar for Wednesday May 31, at 1:00 eastern (Also June 14 and June 28) https://zoom.us/j/587634756
PR/CR Spec Development work stream 05/24/17
This is a link to a matrix whose purpose is to try to determine which use cases to document (in InfoScribe) for a pan-Canadian FHIR profile for the Provider Registry domain. Please note the last column of the matrix, "Proposed Canadian FHIR PR use c...
PR/CR Spec Development work stream 05/24/17
Here is the link for PCR/PPR business overview: ...
How to represent Health Card Number and other identifiers in the Patient Identifier 05/24/17
Hi. We have published a FHIR specification for Ontario provincial client registry (PCR) that may give you an idea how to implement patient identifiers. You can access it at http://ehealthontario.on.ca/en/standards/view/provincial-client-registry-fhir...
Tooling work stream 05/24/17
Hi Gavin, It is Friday, May 26 at 11:00am. I booked an hour and a half as we have quite the agenda. The event coordinates are available here: .... See you there, Attila
Tooling work stream 05/24/17
Hi Attila, Is the next tooling meeting this Friday, May 25? If so, can you point me to the event and connection details? Thanks, Gavin
FHIR WG Call - Zoom Info 05/24/17
Hi, The correct connection details for today's call are: video conferencing: https://zoom.us/j/563726340 Teleconference #: 1 877 369 0926 Meeting ID: 563 726 340 Thanks, Gavin
Solution Architecture work stream 05/24/17
My apologies for not posting about the decision to cancel the meeting last Friday, May 19, which we made at a meeting on May 12. Please note that the meeting this week is on. See you all on Friday, May 26 at 2 pm. Igor
How to represent Health Card Number and other identifiers in the Patient Identifier 05/23/17
I'm new to the FHIR. We are checking into how to expose our assessment data stored in repository to other systems using FHIR Rest API. First i'm trying to define the major FHIR resources to be used in exchange. One of them is the Patient. Having trou...
PR/CR Spec Development work stream 05/23/17
Our next meeting will be Wednesday May 24 at 1:00 Eastern. Topic of interest this week: Use Cases A Zoom meeting and calendar item will be added shortly. -Kris
Upcoming FHIR Community Call - May 24, 12 - 1 EST 05/18/17
Hi Everyone, Below is the proposed agenda for the upcoming May 24 monthly FHIR community call and tcon/videoconference info. Please let me know if there are additional discussion items you would like included. 1. Updates (Gavin, 10 mins):...
eReferral Spec Development work stream 05/16/17
Hi everyone - thanks for the engaging discussion. below are my draft notes of today's call. my apologies for any typos. BTW: a reminder that the tcon # and video conference info are the same for every meeting. you can pull down a meeting invit...

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.

Architecture ( 1 Document )

BusinessCase ( 5 Documents )

Client Registry ( 2 Documents )

Consent Management ( 0 Document )

eReferral ( 0 Document )

Meeting Materials ( 6 Documents )

Provider Registry ( 1 Document )

Tooling ( 5 Documents )

Video

FHIR source control and build

The recording of the October 26, 2016 FHIR tooling meeting

10/26/16

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

Attila Farkas
Canada Health Infoway
ONLINE
Contact
Andrew Liu
Canada Health Infoway
OFFLINE
Admin
Linda Monico
Canada Health Infoway
OFFLINE
Admin
Tasha Shaw-Verbic
Canada Health Infoway
ONLINE
Admin
Jaimes Blunt
Allscripts Canada
OFFLINE
Member
Sisira De Sliva
Newfoundland Labrador Centre for Health Information
ONLINE
Member
Fang Cao
eHealth Ontario
OFFLINE
Member
Yaroslav Hradowy
CCIM
OFFLINE
Member
Stan Shaw
Corban Technology Solutions Inc
OFFLINE
Member
Sanya Palli
CIHI
ONLINE
Member
Arsalan Karim
InfoClin
OFFLINE
Member
Shelley Weslosky
Alberta Health (ministry)
OFFLINE
Member
Joel Francis
Canada Health Infoway
ONLINE
Member
Avneet Bhatia
CGI
OFFLINE
Member
Reed MacMillan
Novari Health Corporation
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