Renewals for the 2017/2018 HL7 International Standards Access are now being accepted. Please renew your access by April 6, 2017. 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: 94
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

Kris Lewis created an event in FHIR® Implementations
PR/CR Spec Workstream Meeting
Tuesday, April 04, 2017, 03:00pm - 04:00pm
Initial series of 4 workstream meetings. Agendas for each day will be posted to the forum a day or two before the meeting. Post topic requests to the forum at any time. Topic: PR/CR FHIR Specification Development Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/295396317 Or iPhone one-tap (US Toll): +14086380968,295396317# or +16465588656,295396317# Or Telephone:Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)+1 855 880 1246 (US Toll Free)+1 877 369 0926 (US Toll Free)Meeting ID: 295 396 317International numbers available: https://zoom.us/zoomconference?m=C6MiwyK4oeB-9kNPMbHWLPAirGwfo1Ty Or an H.323/SIP room system:H.323:162.255.37.11 (US West)162.255.36.11 (US East)221.122.88.195 (China)115.114.131.7 (India)213.19.144.110 (EMEA)Meeting ID: 295 396 317 SIP: 295396317@zoomcrc.com
James Marlon-Lambert 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.
Kris Lewis replied to a discussion in FHIR® Implementations
Meeting notes from March 21 1. Introduction/Attendees Kris Lewis - Sierra Systems Alan Leung - Sierra Systems Natalya Pogrebetski - eHO Attila Farkas - Infoway Blaine Jenkins - Nevari Health Fariba Behzadi - eHO Grant Gillis - Alberta Health Services ID mgmt team Igor Sirkovich - MOHLTC John Willis - eHealth Center of Excellence in waterloo, eReferral WG Ken Sinn - Lloyd Mackenzie - Gevity Mike Kotuba - Born Ontario Rita Pyle - eHO Shamil Nazimov - BC MOH Smita Kachroo - eHO 2. Tooling and Collaboration (Attila) Expecting this workstream will produce some concrete work, and will be a good working example and a test case for collaboration on FHIR specifications using tools and frameworks that Infoway has been developing. 3. PCR/PPR Ontario updates (Natalya and Smita) a. Noted that there will be a webinar on March 23 explaining the planned publishing of draft specifications from Ontario b. Presented slides outlining Ontario's PCR and PPR interfaces including FHIR support in draft. Questions about PCR: Q: Which ID is being used in the Patient READ? Any of the potential IDs, or some unique one on the server? A: Definitional ID,HCN, EMPI EID. Q: What type and how many resources are being used by this interface? A: Patient resource, Operation Outcome. Q: What transfer models? Restful or also messages? A: Not fully FHIR, only through SOAP. Query only for FHIR (Pub/Sub is for current landscape) Questions about PPR: Q: What specialties are supported? e.g all the X specialties from a certain region? A: Terminology spreadsheet lists specialties supported Q: Notification message to provide information about provider information changing? A: No. Q: Any plans to allow active management of provider, or will it be read-only (of course, role-based) A: Next phase (v3) would allow for merge. Not looking at it for now. Follow up Comment: Maybe something worth considering for those looking for a complete PR package Q: In BC, provider can exist as a provider and an organization - list of resources may not be enough to support needs in BC? A: Our list is just starting point Q: Is this open-access, or is there authentication required? what is the security model? A(Lloyd): Security is defined separately (HTTP layer), set of expectations around system authentication and user authentication. Follow up Q: Single role? A(Lloyd): Different types of users get different results; type of role may impact types & numbers of EMPI match Comment: Different model in BC, will be interesting to see how to harmonize between provinces. Q: Are there plans to adopt STU3? A: In future, to move to STU3 once published. going with STU2 for now c. Slides will be shared on the forum 4. PRSC Updates (Kris) Brief update highlighting the fact that the Provider Registry System Collaborative is beginning a project to scope and define a FHIR specification for the Provider Registry System (PRS) in use in multiple jurisdictions. Plan is to collaborate with other jurisdictions through the FHIR working groups and align to pan-Canadian specifications as they develop 5. Questions/Open discussion Clarified a few topics of interest for future meetings i. Paradigm shifts specific to registries, EMPI-type queries vs RESTful ii. Other Paradigm shifts (RESTful FHIR vs SOAP etc) iii. Boundaries between Patient, Practitioner, Organization, Location, Service and what these mean in the Canadian context iv. URI vs OIDs registries (for Solution Architecture workstream) v. Extensions 6. Future Meetings For April and May bi-weekly meetings will occur starting Tuesday April 4th at 3PM Eastern. Will re-evaluate as the group develops a workplan.
Lloyd Mckenzie replied to a discussion in FHIR® Implementations
Hi everyone, The draft Google document can be found here: https://docs.google.com/document/d/1ClF3XpIrE2FiIDG7K7VD3pPjOPx3T950Sfi1Ip8ORcU/edit?usp=sharing Feel free to edit or add comments. I presume we'll talk about it on next Friday's call.
Igor Sirkovich replied to a discussion in FHIR® Implementations
Thank you everyone who attended the meeting today. We've had a very productive discussion. I've uploaded the minutes, which would eventually become a draft of the URIs recommendations paper to the group's documents section: ... Please provide your comments and propose additional content to the URI recommendations document we've been working on. Lloyd, we are looking forward to reviewing your paper and aligning with your recommendations. We are going to start a Google Sheet with the current inventory of URIs assigned by Canadian projects. This Google Sheet will be publicly available as a read-only short-term Canadian URI Registry until we have a long term solution and process in place. See you all next Friday at 2 pm. Igor
Igor Sirkovich replied to a discussion in FHIR® Implementations
Just a quick reminder that we have a meeting today at 2 pm.
Ron Parker 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:
Fri Mar 31 @ 2:00PM - 03:00PM
FHIR Solution Architecture
Tue Apr 04 @11:00AM - 12:00PM
eReferral FHIR workstream
Tue Apr 04 @ 3:00PM - 04:00PM
PR/CR Spec Workstream Meeting

Forum

PR/CR Spec Development work stream 03/28/17
Meeting notes from March 21 1. Introduction/Attendees Kris Lewis - Sierra Systems Alan Leung - Sierra Systems Natalya Pogrebetski - eHO Attila Farkas - Infoway Blaine Jenkins - Nevari Health Fariba Behzadi - eHO Grant Gillis...
Solution Architecture work stream 03/27/17
Hi everyone, The draft Google document can be found here: https://docs.google.com/document/d/1ClF3XpIrE2FiIDG7K7VD3pPjOPx3T950Sfi1Ip8ORcU/edit?usp=sharing Feel free to edit or add comments. I presume we'll talk about it on next Friday's call.
Solution Architecture work stream 03/24/17
Thank you everyone who attended the meeting today. We've had a very productive discussion. I've uploaded the minutes, which would eventually become a draft of the URIs recommendations paper to the group's documents section: ... Please provide yo...
Solution Architecture work stream 03/24/17
Just a quick reminder that we have a meeting today at 2 pm.
PR/CR Spec Development work stream 03/23/17
the Ontario trial for use FHIR specs for provincial client registry and provider registry are now available for download: http://www.ehealthontario.on.ca/en/standards/view/provincial-client-registry-fhir http://www.ehealthontario.on.ca/en/standar...
FHIR WG Meeting - March 22, 12-1 PM Eastern 03/23/17
Hi, The minutes from the March 22 meeting are below. Once again, a big thanks to all the stream leads and volunteers for self organizing and identifying workplan items. Really look forward to the April meeting when we start to see some of the fi...
PR/CR Spec Development work stream 03/23/17
Here is the link for PCR_PPR Ontario presentation ...
FHIR North Connectathon and Eduacation 03/23/17
Hi, The FHIR North schedule will be posted to the FHIR North registration site soon: http://www.fhirnorth.ca/ In the mean time, I've uploaded the draft schedule and connectathon overview here: https://ic.infoway-inforoute.ca/en/resources/docs/...
HL7 International Publishes FHIR(R) Release 3! 03/22/17
HL7 Publishes FHIR® Release 3 Standard continues to expand and adapt to broad industry feedback Ann Arbor, Michigan, USA – March 22, 2017 – Health Level Seven® International (HL7®), the global authority for interoperability in healthcare informa...
HL7 International Working Group Meeting - May 6-12, 2017 - Madrid, Spain 03/22/17
... The HL7 International Working Group Meeting will be held in Madrid, Spain from May 6-12, 2017 Hotel room rate & early bird registration deadline: - Friday, April 14! Hurry – the hotel room rate and early bird registration discount deadlin...
PR/CR Spec Development work stream 03/21/17
Reminder of today's meeting at 3:00 Eastern. Agenda: 1. Introduction - 5 min (Kris/Natalya) 2. Tooling and Collaboration -10 min (Attila) 3. PCR/PPR Ontario updates – 20 min (Natalya/Smita?) 4. PRSC (formerly WHIC) updates - 10...
eReferral Spec Working Group Today 03/21/17
Hello all, A reminder that today we have our biweekly FHIR eReferral spec meeting, details as follows: Tuesdays, 11am, biweekly, March 21. https://zoom.us/j/265383594 teleconference #: 1 877 369 0926 Meeting ID: 265 383 594 Agenda posted...
FHIR WG Meeting - March 22, 12-1 PM Eastern 03/20/17
Hi, The agenda for this Wednesday's FHIR WG meeting is below. Meeting info and connection details are here: https://ic.infoway-inforoute.ca/en/news-events/event-calendar/icalrepeat.detail/2017/03/22/2031/1268/fhir-community-call 1. Welcome,...
ICD-10-CA URI 03/20/17
Hi, As an FYI, I have requested ICD-10-CA code system and value set to be added in FHIR. Here is the link to the request. http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13111 Code system name: icd10-CA Co...
PR/CR Spec Development work stream 03/20/17
Based on the poll, Tuesday, March 21, at 3:00 eastern was the most popular time slot. I have scheduled a zoom meeting for that time... https://zoom.us/j/852129419 The event is also the calendar for those who want the Outlook/Google Calendar...

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 ( 1 Document )

Consent Management ( 0 Document )

eReferral ( 0 Document )

Meeting Materials ( 5 Documents )

Provider Registry ( 1 Document )

Tooling ( 4 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 Builder Installation
  • 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

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.

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.

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
ONLINE
Admin
Tasha Shaw-Verbic
Canada Health Infoway
ONLINE
Admin
James Marlon-Lambert
Collaborative Solutions for Active Living, Inc.
OFFLINE
Member
Ron Parker
Canada Health Infoway
OFFLINE
Member
Natalya Pogrebetsky
eHealth Ontario
OFFLINE
Member
Lynne Zucker
Canada Health Infoway
OFFLINE
Member
Douglas Kingsford
Interior Health Authority
OFFLINE
Member
ISSAAD ASSOUFI
Individual
OFFLINE
Member
Francis Lau
University of Victoria
OFFLINE
Member
Russ Pastorchik
Year
OFFLINE
Member
Dennis Cabel
Providence Healthcare
ONLINE
Member
Anne Belford
TELUS Health Solutions
OFFLINE
Member
Stacey Lloyd
Novari Health
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