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:

Medication Management
Discussion of topics such as ePrescribing, Best Possible Medication History and Medication Reconciliation.
Members: 195
Contact: Seema Nayani
Type: Open
Access: Public
Discussion of topics such as ePrescribing, Best Possible Medication History and Medication Reconciliation.

Activity

Jennifer Runge created a new discussion in Medication Management
We are looking for guidance from the HL7 standards on how morphine equivalence information should be returned within the HL7 messaging? We are wondering if any jurisdictions are currently returning morphine equivalence information back to pharmacists for prescriptions and dispenses entered into the jurisdictional EHR , and what elements they are using to returning the information? If the Hl7 standard does not currently support a method for returning morphine equivalence information does Infoway/HL7 have any plans to adopt any additional messaging standards or extend the current HL7 standard to help the jurisdictions with the Canadian National Opioid Strategy?
Seema Nayani replied to a discussion in Medication Management
Hi Michelle, Happy to hear our community has been a a great resource for you! Also, thank-you for sharing this piece of your eMedRec implementation journey! I hope to check-in with you again, as I am sure others will find your insights applicable to their work. You raise some great points about the drug dictionary, and working with the resources you have. In my home care practice, we have a Rapid Response Nursing Team who complete the majority of in-home MedRec. When the RNs feel the patient's medication regimen is too complex, or out of their scope, the Pharmacy Team is then engaged. We have found developing standardized processes in collecting the information and completing the MedRec very useful. And of course, education, education! The RNs really appreciate the on-going education that the pharmacists provide them, which can be 1:1 (arranging joint home visits) or in a formal training environment. Wondering if you could use this model at your site? What has been your experience? Would love to hear your thoughts. Kind regards, Seema
Jonathan Mitchell joined a group
Logo
Discussion of topics such as ePrescribing, Best Possible Medication History and Medication Reconciliation.
Michelle Hoffe replied to a discussion in Medication Management
Hi Seema, So far, we are experiencing delays on the technical side of things. Our drug dictionary had never been used with the vendor so it is taking some time trying to figure that piece out. I am currently involved in current state process mapping and some change management strategies leading up to implementation. One of our biggest challenges is that of low pharmacy resources.....therefore trying to create capacity within the RN's role (which we know from current research is not the best option for quality Med Rec). My experience has been that most facilities that have rolled out eMedRec had ++pharmacy support, which is not the case for us! So if anyone out there has primarily RN's completing Med Rec, I'd be interested in your experience! I've connected with a few from this community! It is certainly a great resource as well all move forward. Thanks, Michelle
Seema Nayani replied to a discussion in Medication Management
Hi Michelle, Wondering how your eMedRec implementation is coming along. Would you be able to share some details of your journey so far? Also, how has our community been able to connect you with the right people or resources? I think we would all love to hear your insights! Kind regards, Seema
Bev Knight created a new discussion in Medication Management
Dear Medication Management stakeholders The ISO/TC 215/TF1 Task Force on Quantities and Units in e-Health is conducting this survey to identify, in broad terms, the authoritative sources for quantities and units that are actually being used in health today and where there may be potential gaps in the underlying standards for quantities and units, particularly where needed to support the use of information and communication technologies for health (“e-health”). This survey is jointly sponsored by the ISO/TC 215 (Health informatics), ISO/TC 12 (Quantities and units) and IEC/TC 25 (Quantities and units) technical committees of ISO and IEC. The survey has been set up online to enable the collection of input from as many potential contributors as possible. You are encouraged to distribute this invitation as widely as possible and encourage as many relevant experts to contribute their views by logging on at: https://www.surveymonkey.com/r/F77TDNX Please complete the survey responses by 17 April 2017. thankyou Beverly
Tanya Achilles replied to a discussion in Medication Management
Thank you for sharing this Lisa. This IS a great article. I just shared it will all of our team members here at Infoway working on the PrescribeIT project. Tanya Achilles Director e-Prescribing Business Operations Canada Health Infoway

Events

Forum

Returning Morphine Equivalence information for Prescriptions/Dispenses 03/29/17
We are looking for guidance from the HL7 standards on how morphine equivalence information should be returned within the HL7 messaging? We are wondering if any jurisdictions are currently returning morphine equivalence information back to pharmac...
eMedRec Implementation 03/29/17
Hi Michelle, Happy to hear our community has been a a great resource for you! Also, thank-you for sharing this piece of your eMedRec implementation journey! I hope to check-in with you again, as I am sure others will find your insights applica...
eMedRec Implementation 03/28/17
Hi Seema, So far, we are experiencing delays on the technical side of things. Our drug dictionary had never been used with the vendor so it is taking some time trying to figure that piece out. I am currently involved in current state process m...
eMedRec Implementation 03/27/17
Hi Michelle, Wondering how your eMedRec implementation is coming along. Would you be able to share some details of your journey so far? Also, how has our community been able to connect you with the right people or resources? I think we woul...
ISO/TC215 WG3: Survey Invitation Letter Task Force on Quantities and Units in e-Health 03/24/17
Dear Medication Management stakeholders The ISO/TC 215/TF1 Task Force on Quantities and Units in e-Health is conducting this survey to identify, in broad terms, the authoritative sources for quantities and units that are actually being used in hea...
It's time to Adopt Electronic Prescriptions for Opioids 03/23/17
Thank you for sharing this Lisa. This IS a great article. I just shared it will all of our team members here at Infoway working on the PrescribeIT project. Tanya Achilles Director e-Prescribing Business Operations Canada Health Infoway
It's time to Adopt Electronic Prescriptions for Opioids 03/23/17
This is a great read, with some clear action items on how to reduce over prescribing of opioids (especially by surgeons). Using technology! Find the article here: http://journals.lww.com/annalsofsurgery/Fulltext/2017/04000/It_s_Time_to_Adopt_...
Medication Management Working Group meetings 03/22/17
Hi Everyone, The Medication Management Working Group met yesterday - March 21st, 2017. Few of the items that were discussed: 1) Based on Doodle poll feedback, the meeting time will remain the same (alternate Tuesdays at 12 p.m. EST). 2) I h...
Webinar: The Medication Profile: what should it be and how could it work? 03/22/17
Join Julie M. James of Blue Wave Informatics, on April 11th, as she discusses “The Medication Profile: what should it be and how could it work?” Drawing on the research from her doctoral thesis at University College, London, Julie will present the e...
Updated! Medication Reconciliation Getting Started kits 03/17/17
Hello Members, The Getting Started Kits for MedRec in Acute Care and Long Term Care have been recently updated to incorporate newly published evidence. They can be found on the ISMP Canada website, under Medication Reconciliation. English and...
Canadian Frailty Network - Medication Use in Frail Older Adults Survey 03/10/17
The Canadian Frailty Network is doing an online survey for healthcare professionals, administrators, quality and risk managers, and caregivers / families to share thoughts and issues concerning medications and frail older adults. They want to hear a...
Webinar: Current Prescribing and Dispensing Landscape in Canada 03/08/17
Thank you for looking into this Seema, the link now works.
Medication Safety Q3 Update from CPSI 03/07/17
Sharing with our members The Q3 Medication Safety Update has been posted on the CPSI website. An example of a multi-organizational collaborative to improve medication safety across the country. Refer to: http://www.patientsafetyinstitute.ca/en/New...
Webinar: Current Prescribing and Dispensing Landscape in Canada 03/03/17
Hi Everyone, The link should take you to the recording now - there seemed to have been an issue with the permissions. Please let me know if you have any further issues. Kind regards, Seema
Webinar: Current Prescribing and Dispensing Landscape in Canada 03/03/17
Thanks Igor and Deidra for bringing this to my attention. I will follow-up with our InfoCentral team, and hope to have a resolution for you soon. Kind regards, Seema

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.

Medication Management Working Group - proposed content list

Published on Jan 31, 2017 by Seema Nayani

Medication Management Community Working Group - Bios

Published on Jan 31, 2017 by Seema Nayani

"Help Advance eMedrec Solutions" webinar recording

Published on Dec 21, 2016 by Seema Nayani

"Help Advance eMedRec Solutions" webinar polling results

Published on Dec 20, 2016 by Seema Nayani

Paper to Electronic MedRec Implementation Toolkit

Published on Nov 30, 2016 by Seema Nayani

e-prescribing Working Group - call for participation

Published on Jun 13, 2016 by Bev Knight

Ontario Public Health FHIR Implementation

Published on Feb 11, 2016 by Wendy Huang

Video

5 Questions to Ask About Your Medications

Empower your patients to ask questions to keep them safe from medication harm. Presented by ISMP Canada

12/19/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

Seema Nayani
Canada Health Infoway
ONLINE
Contact
Tasha Shaw-Verbic
Canada Health Infoway
ONLINE
Admin
Linda Monico
Canada Health Infoway
ONLINE
Admin
Jonathan Mitchell
CADTH
ONLINE
Member
Tasha Shaw Verbic
Infoway
OFFLINE
Member
Douglas Kingsford
Interior Health Authority
OFFLINE
Member
Rebecca Campbell
Queen Elizabeth Hospital
OFFLINE
Member
Heather Rogers
Health PEI
OFFLINE
Member
Peter Amantea
Mustimuhw Information Solutions
OFFLINE
Member
Shelley Bacheldor
Alberta Health Services
ONLINE
Member
Janet Cooper
Association of Faculties of Pharmacy of Canada
OFFLINE
Member
John Matechuk
Interior Health
OFFLINE
Member
Martin Rowland
Queensway Carleton Hospital
OFFLINE
Member
Doug Pankoski
Alberta Health Services
OFFLINE
Member
Jocelyn Boucher
Canada Health Infoway
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