Webinar: Bundling Standards for Interoperability, ISO Community, Oct 26. Add the date to your calendar more >

Webinar: Advancing patient safety with PrescribeIT™, October 31, 2017, 1-2 P.M., Register Now more >

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

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 and get involved in the work. Here are some of the highlights:

Workstream Co-Chairs Objective Progress to date
Solution Architecture

Igor Sirkovich (OMHLTC)

Kris Lewis (Sierra Systems)

  1. Serve as a forum for all architectural questions about implemention of FHIR based solutions
  2. Discuss Canadian URI (incl. mapping to OIDs), profiles and extensions
  1. Review FHIR URI strategy
  2. Full list of provincial Patient ID URIs
  3. Partial list of provincial Org URIs
  4. Started work on provincial provider URIs
  5. Started discussion paper on IG publisher
Tooling

Attila Farkas (Infoway)

Frederic Laroche (Gevity Inc.)

Main focus of the working group is the discovery, identification, implementation and education surrounding tooling and best practices for FHIR development in Canada
  1. Identified a logical capability model that enables collaborative FHIR development, support digital integration and sharing
  2. Concluded discovery phase for the core component of the model - the FHIR Registry
  3. Launched the Canadian FHIR Registry at the September 2017 FHIR Community meeting
Client & Provider Registries

Kris Lewis (Sierra Systems)

Natalya Pogrebetsky (eHealth Ontario)

Define FHIR PR and CR use cases
  1. Ontario shared PR and CR specs with the working stream and provided business and technical overview
  2. PR/CR working group working on Canadian FHIR use cases
eReferrals

Tim Berezny (CareDove)

Caryn Harris (Orion Health)

  1. Build eReferral use cases
  2. Prototype eReferral use cases
  3. Select Resources to include in Specifications
  4. Write preliminary Specifications for broader use
  1. Overall use case flows combined into a single modular flow diagram: diagram and video.
  2. A demo video of some of eReferral workflows in action in a pilot environment: simple, SMART, advanced business logic
  3. Primary Resources have been identified. Identifying the role of the Task Resource.
  4. FHIR Resources applied in pilot environment, Specification writing still pending, outsanding: authentication mechanisms.
Business Case for FHIR

Attila Farkas (Infoway)

Shamil Nizamov (BC MoH)

Creation of reference material for those new to FHIR on the benefits of its adoption
  1. Concluded a storming phase identifying aspects relevant to a business case
  2. Collected community feedback and published a baseline of best practices.
Community Monthly Calls

Gavin Tong (Gevity Inc.)

Yaron Derman (eHealth Ontario)

  1. Share progress within the workstreams within the broader FHIR community
  2. Identify and promote FHIR education and implementation activities
  1. Informative updates and discussions about FHIR globally and progress across the workstreams
  2. Average 17 participants per call.

Activity

Melva Peters created a new discussion in FHIR® Implementations
The election period of the HL7 Canada Council is now closed and I am that the following individuals have been elected for a two-year term: Jean Duteau Cindy Jiang Iryna Roy Harsh Sharma Thank you to all of the candidates who submitted their names! A special thank you to the retiring Council: Danna Dobson, Lloyd McKenzie, and Rashad Badrawi for their contributions! I hope that you will continue to contribute to the HL7 Community on InfoCentral. Melva Peters HL7 Canada Chair
Gavin Tong replied to a discussion in FHIR® Implementations
Hi, The "click here" link to the DHIR spec seems to have been removed in the post. You can access it here: http://www.ehealthontario.on.ca/en/standards/view/digital-health-immunization-repository-specification-fhir Thanks, Gavin
Attila Farkas created a new discussion in FHIR® Implementations
Background: Starting today, October 18, 2017, health care organizations will have the opportunity to review the Digital Health Immunization Repository (DHIR) Release 3 Specification. The provincial Digital Health Immunization Repository (DHIR) is a centralized repository of standardized electronic immunization data that was originally developed to support the implementation of the Panorama public health platform. The DHIR contains ~95 million immunization records for ~6.5 million clients. Currently, the DHIR primarily supports data sharing for public health purposes. Ontario’s 36 public health units (PHUs) access the DHIR through the Panorama solution. The Public is able to update and access immunization records in the DHIR through Immunization Connect Ontario (ICON). In the upcoming Release 3, Health Care Providers (HCP) will be able to access and update the DHIR through ICON. How to Participate: Click here to download the Digital Health Immunization Repository (DHIR) Release 3 Specification review package. Comments on the DHIR R3 Specification will be accepted from October 18, 2017 – November 16, 2017. Please send your feedback using the comments spreadsheet in the review package to: .... The DHIR R3 specification review package includes: • DHIR FHIR Implementation Guide • Comment Spreadsheet for Submitters Webinar: A webinar will be held on October 24th, 2017 at 12:00 - 1:00 pm (EDT) to walk participants through the DHIR R3 content and provide information on how to provide comments. To register for the webinar, contact us at ... If you have any questions regarding the Digital Health Immunization Repository (DHIR) Release 3 Specification and/or review process, contact us at ...
Attila Farkas replied to a discussion in FHIR® Implementations
Cross post from HL7 Community: Last change to vote for your HL7 Canada Council members. Please visit the post and cast your vote until the end of the day today!
Tue Hoang 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.
Michael Savage created a new discussion in FHIR® Implementations
The draft agenda for the FHIR Implementations Community Call is below. As a reminder, the calendar invite with connection details can be found on the event calendar here: https://infocentral.infoway-inforoute.ca/en/monthly-calendar/month.calendar/2017/10/16/1268 Draft Agenda: 1. Agenda & Action Items Review a. Action Item Progress 2. Updates: a. Registries Work Stream Status b. HL7 Canada Council Election c. World Standards Day d. FHIR Implementation WG Landing Page 3. Updates From Stream Leads a. eReferral b. Tooling c. Solution Architecture If there are any additional items, please comment in this thread in advance of the meeting (Wednesday October 25, 12-1)
Michael Savage created a new discussion in FHIR® Implementations
Hi all! To assist with Working Group planning and logistics going forward, a survey has been created to gather your feedback on your experiences thus far as members of the FHIR Implementations Working Group and its Work Streams. Your participation in the survey is both strongly encouraged and entirely anonymous, so (when time permits) please do not hesitate to take the few minutes needed to fill it out! The link to the survey (below) will remain open until 5pm EST on Wednesday November 1st. https://www.surveymonkey.com/r/B69SHKB On behalf of the Working Group organizers, thank you very much and looking forward to your constructive feedback!

Events



Upcoming events:
Wed Oct 25 @12:00PM - 01:00PM
FHIR Community - monthly tcon
Fri Oct 27 @ 2:00PM - 03:00PM
FHIR Solution Architecture
Tue Oct 31 @11:00AM - 12:00PM
FHIR eReferral Spec Working Group

Forum

Cross Post from HL7 Community - HL7 Canada Council Election Results 10/23/17
The election period of the HL7 Canada Council is now closed and I am that the following individuals have been elected for a two-year term: Jean Duteau Cindy Jiang Iryna Roy Harsh Sharma Thank you to all of the candidates who submitte...
Cross post from Medication Management - Digital Health Immunization Repository (DHIR) Release 3 Specification - FHIR | Call for Participation October 18, 2017 – November 16, 2017 10/20/17
Hi, The "click here" link to the DHIR spec seems to have been removed in the post. You can access it here: http://www.ehealthontario.on.ca/en/standards/view/digital-health-immunization-repository-specification-fhir Thanks, Gavin
Cross post from Medication Management - Digital Health Immunization Repository (DHIR) Release 3 Specification - FHIR | Call for Participation October 18, 2017 – November 16, 2017 10/20/17
Background: Starting today, October 18, 2017, health care organizations will have the opportunity to review the Digital Health Immunization Repository (DHIR) Release 3 Specification. The provincial Digital Health Immunization Repository (DHIR) is a...
HL7 Canada Council Election period now open - Please take the time to vote 10/20/17
Cross post from HL7 Community: Last change to vote for your HL7 Canada Council members. Please visit the post and cast your vote until the end of the day today!
FHIR Implementers' Community Call - October 25, 12-1 EST 10/18/17
The draft agenda for the FHIR Implementations Community Call is below. As a reminder, the calendar invite with connection details can be found on the event calendar here: https://infocentral.infoway-inforoute.ca/en/monthly-calendar/month.calendar/...
FHIR Implementations - Working Group Experience Survey 10/18/17
Hi all! To assist with Working Group planning and logistics going forward, a survey has been created to gather your feedback on your experiences thus far as members of the FHIR Implementations Working Group and its Work Streams. Your participat...
October 20: SmileCDR Presentation by James Agnew 10/17/17
Hello Everyone, This is a cross posting from the FHIR Solution Architecture stream as I believe the topic might be of interest to a broader FHIR community. Please join us on Friday, October 20 at 2 pm, for a presentation of SmileCDR (a FHIR-Bas...
Solution Architecture work stream 10/17/17
Hello Everyone, please join us on Friday, October 20 at 2 pm, for a technical presentation of SmileCDR (a FHIR-Based Clinical Data Repository As A Service) by James Agnew, the creator of HAPI.
eReferral Spec Development work stream 10/17/17
This is where the eReferral spec is currently being drafted: https://simplifier.net/ui/ig/eRefferaldraftiGuide/Overview2
eReferral Spec Development work stream 10/17/17
A reminder about today's biweekly meeting at 11:00 regarding the development of an eReferral FHIR specification. This one will just be 30 min. https://zoom.us/j/265383594 teleconference #: 1 877 369 0926 Meeting ID: 265 383 594 Chair: Tim Ber...
Solution Architecture work stream 10/16/17
Hi Joel, Let's make it permanent why not. As the administrator you may reassign this role to someone else (by granting the admin rights to that person). I'm about to test some simple FHIR client to understand how things work there to begin with....
Solution Architecture work stream 10/16/17
Hi Shamil, I received your request to join the group. Unfortunately, this was just a test account setup during the presentation of the Tocuhstone project at the WGM. Is there anything in particular you were looking for? -Joel
Solution Architecture work stream 10/16/17
I wonder who is the admin of the Canada Health Infoway group in Touchstone, unless this is a top secret. : )
FHIR Testing Presentation on Oct 13 10/10/17
Hello All, This is a cross posting from the FHIR Solution Architecture stream as I believe the topic might be of interest to a broader FHIR community. On October 13, our special guests from Aegis will give us a presentation on the proper ways t...
Solution Architecture work stream 10/10/17
All, please join our next meeting on October 13: our special guests from Aegis will give us a presentation on the proper ways to test FHIR implementations and on the use of their FHIR testing tool Touchstone (which has both free and commercial offeri...

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

Attila Farkas
Canada Health Infoway
OFFLINE
Contact
Andrew Liu
Canada Health Infoway
OFFLINE
Admin
Linda Monico
Canada Health Infoway
OFFLINE
Admin
Tasha Shaw-Verbic
Canada Health Infoway
OFFLINE
Admin
Tue Hoang
Caredove
OFFLINE
Member
Cindy Jiang
eHealth Ontario
OFFLINE
Member
Kjetil Nilsen
Sectra Canada Inc.
OFFLINE
Member
Dat Nguyen
OntarioMD
OFFLINE
Member
Danna Dobson
Ontario Ministry of Health
OFFLINE
Member
Fernando Portilla
AGESIC Salud.uy
OFFLINE
Member
Chris Jowsey
n/a
OFFLINE
Member
Aidan Lee
OntarioMD
OFFLINE
Member
Jean Duteau
Duteau Design Inc
OFFLINE
Member
Michael Savage
OntarioMD
OFFLINE
Member
Dahlia Khajeei
University of Waterloo
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