Share this page:

Medication Management
A national medication management stakeholder community sharing knowledge, information and resources to promote medication safety practices.
Members: 246
Contact: Seema Nayani
Type: Open
Access: Public
A national medication management stakeholder community sharing knowledge, information and resources to promote medication safety practices.

Activity

Melanie Hewlett joined a group
Logo
A national medication management stakeholder community sharing knowledge, information and resources to promote medication safety practices.
Bev Knight created a new discussion in Medication Management
Hi We would like to welcome vendors and clinicians to join us in a webinar to learn how you can contribute to the pubic review. At this webinar we will provide a detailed overview of the structure and content within the files that make up the Canadian Clinical Drug Data Set at a business level and the type of feedback that would be most helpful at this stage. Health Canada and Canada Health Infoway are preparing to publish the first release of the new national drug terminology, the Canadian Clinical Drug Data Set at the end of this summer. The Canadian Clinical Drug Data Set is a national drug terminology based on Health Canada’s Drug Product Database that is freely available. It will provide a consistent approach to the identification and naming of medications, resulting in a drug terminology solution that allows the PrescribeIT e-Prescribing service and other digital health solutions to share information about drug products and groups of drug products with otherwise incompatible proprietary systems used in practice management, pharmacy management, and provincial drug information systems. The Canadian Clinical Drug Data set will also contribute to managing the opiod crisis in Canada. The Canadian Clinical Drug Data Set will include manufactured products and therapeutically equivalent (i.e. generic) medications and a few frequently prescribed devices. The Canadian Clinical Drug Data Set will not replace the Health Canada Drug Product Database (DPD) it will be owned and published by Health Canada in addition to the DPD (with monthly updates). In most cases, the Canadian Clinical Drug Data set will be used as an interchange technology, clinical systems will continue to use their existing drug terminology and interfaces while mapping to the Canadian Clinical Drug Data Set. When these systems share drug information, e.g. an electronic prescription, they swill share the Canadian Clinical Drug Data Set codes. Prior to publication, vendors, clinicians and other stakeholders interested in medication safety are invited to participate in the public review period from June 7 to July 7th, 2017. Feedback is requested on the file structure of the Canadian Clinical Drug Data Set and application of editorial guidelines to a small volume of representative content. Please watch for updates on this forum. You can find the "updated" event with webex logistics here https://infocentral.infoway-inforoute.ca/en/?option=com_jevents&task=icalrepeat.detail&evid=2131&Itemid=2109&year=2017&month=06&day=08&title=introduction-to-the-public-review-of-the-canadian-clinical-drug-data-set&uid=9c1e6b11bc39c00983792f6ce9d35856 Thankyou Beverly
Monica Hazra created a new discussion in Medication Management
Here are 2 videos (Video 1:1 minute, Video 2: 2 minutes) that present patients with ways of presenting current medications to their health professionals. Credits go to: Hamilton Health Sciences & ISMP Canada, Video 1 Mount Sinai Academic Family Health Team Video 2 To stimulate further discussion, please comment on the videos or share resources from your organizations. https://vimeo.com/208288045 https://www.youtube.com/watch?v=1qBHnbYD4Bc
Samim Hasham replied to a discussion in Medication Management
Choosing Wisely Canada has created patient pamphlets, using plain language. “The materials are meant to help patients learn about the tests and treatments in question, when they are necessary and when they are not, and what patients can do to improve their health.” Many of their pamphlets are aimed at informed decision making for using medication. Such as: 1. Treating heartburn and gastro-esophageal reflux (GERD): Using proton-pump inhibitors (PPI) carefully 2. Pain medicines: What to do if you have heart problems or kidney disease 3. Insomnia and anxiety in older people: Sleeping pills are usually not the best solution These patient pamphlets and more can be found at Choosing Wisely Canada – Patient Pamphlets. (http://www.choosingwiselycanada.org/materials/) Samim Hasham B.Sc. Pharm (Hons), MMngt, CDE, PharmD.
Alice Watt replied to a discussion in Medication Management
ISMP Canada in collaboration with CPSI, Patients for Patient Safety Canada, CSHP and CPhA created the: ... This consumer resource is a communication tool developed in partnership with patients, that provides the patient with key questions to ask about their medication with the goal that they will be better informed and use medications safely. Healthcare providers are encouraged to share these questions with patients – and be available to answer them, especially at transitions in care. It is now available in over ...! Organizations can also endorse the poster by requesting to have their logo added. Check if your logo is already .... If you are interested in adding your organization to the list of over 100 endorsing organizations, please send me your logo in vector format (.eps) and specify if you would like it in English and/or French. We encourage organizations to share your experiences with using the 5 Questions to ask about your medications. And let us know what you think. Watch this ... to learn more! Kindest Regards, Alice Medication Safety Specialist, ISMP Canada awatt@ismp-canada.org
Lisa Sever replied to a discussion in Medication Management
I would like to start off this Resources folder (Consumer resources) for medication safety, with a captivating presentation about why we need to focus efforts on improving medication safety. This is a recorded ..., from Patients for Patients Safety Canada, hosted by CPSI from October 2016. Real stories, about real families and the preventable harm they suffered from medications. It provides ideas on how to advance patient engagement in medication safety. Worth a listen/read. Here is the video for one presenter's story. ... Feedback, sharing of resources, stories - all is encouraged. Do you know of an initiative to help patients/families become more informed in making decisions about the safe use of medications? Please post! Lisa
Lisa Sever replied to a discussion in Medication Management
Interesting study that examined how CDS (correct vs incorrect) or no CDS impacts eprescribing. Find it here: ... Article is open access. Another reminder about the importance of using accurate and quality information when creating CDS. Can lead to both errors of omission or commission (the paper defines these outcomes). Both can lead to patient harm. Lisa

Forum

Introduction to the Public Review of the Canadian Clinical Drug Data Set June 8th 11:30am-12:30pm ET 05/25/17
Hi We would like to welcome vendors and clinicians to join us in a webinar to learn how you can contribute to the pubic review. At this webinar we will provide a detailed overview of the structure and content within the files that make up the Canadi...
Patient Safety: Create ‘Up to Date’ Medication Lists or Use the Brown Bag Method 05/24/17
Here are 2 videos (Video 1:1 minute, Video 2: 2 minutes) that present patients with ways of presenting current medications to their health professionals. Credits go to: Hamilton Health Sciences & ISMP Canada, Video 1 Mount Sinai Academic Fa...
Choosing Wisely – Patient Pamphlets 05/24/17
Choosing Wisely Canada has created patient pamphlets, using plain language. “The materials are meant to help patients learn about the tests and treatments in question, when they are necessary and when they are not, and what patients can do to improv...
5 Questions to Ask About Your Medications 05/23/17
ISMP Canada in collaboration with CPSI, Patients for Patient Safety Canada, CSHP and CPhA created the: ... This consumer resource is a communication tool developed in partnership with patients, that provides the patient with key questio...
Patient Engagement in medication safety at the point of care 05/23/17
I would like to start off this Resources folder (Consumer resources) for medication safety, with a captivating presentation about why we need to focus efforts on improving medication safety. This is a recorded ..., from Patients for Patients Saf...
Automation bias in electronic prescribing 05/23/17
Interesting study that examined how CDS (correct vs incorrect) or no CDS impacts eprescribing. Find it here: ... Article is open access. Another reminder about the importance of using accurate and quality information when creating CDS. Can le...
Naxolone managment in Ontario 05/17/17
In Ontario, the ministry is tracking the dispensing and reimbursement through the healthcard number of the person requesting the naloxone kit. It may be for the person using opioids or a person with a past history of opioid abuse. Or it may be a par...
Prescription Opioids in Ontario 05/17/17
Health Quality Ontario has just released a report on Opioid Prescribing in Ontario. http://www.hqontario.ca/System-Performance/Specialized-Reports/Opioid-Prescribing Great infograph indicates the number of opioid prescriptions filled is rising....
Opioid resources: Opioid and Pain Evidence Bundles from CADTH 05/17/17
Hello all, CADTH's best evidence on opioids and pain management is centralized in two online resources — ... and ... — which are updated frequently. We wrote about these evidence bundles in the latest issue of Hospital News: • ... Thank you...
Naxolone managment in medication system 05/17/17
Hi, Following the decision of the federal government to make Naloxone easier to access in mather to help solving the crisis caused by the consumption of Fentanyl, it will be allowed for a person to take the prescription in the name of another pers...
Medication Management Working Group meetings 05/10/17
Hi Everyone, The Medication Management Working Group met on May 9th, 2017. Items discussed were: 1) The community description has been updated to better reflect the community's goal and purpose. 2) The group felt an additional "resources" t...
Consumer resources (medication safety) 05/10/17
This thread is where you can share consumer resources. Please use the name or title of the resource, as the subject line. Also, avoid using the words "Link to" or "Document". Please include a short (4 line) description with key words, so that mem...
Opioid resources+PMP 05/09/17
Thank you Lisa and Seema, It would be awesome to learn about these initiatives and move practice forward in Ontario.
Opioid resources 05/09/17
Thought I would share this resource to bring awareness. From the Canadian Centre on Substance Abuse. Authored by Beth Sproule. ... This includes opioids, psychotropics and any other medications that are associated with misuse or addiction....
Additional resources: 2017 Canadian Guideline for Opioids for Chronic Pain 05/08/17
... has some additional resources on their site including: an opioid tapering tool an opioid switching tool the appendices to the guidelines, including the Values & Preferences Statement of their patient panel (interesting read!)

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.

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 ReMixer
  • Object Identifiers (OIDs)
  • SNOMED CT Browser
  • Terminology Gateway
  • Terminology Service API
  • TermWorks

FHIR web services used to access terminology data

FHIR Terminology Service APIs enable automated exchange of clinical terminology content and resources. It allows developers to easily implement healthcare applications that programmatically consume codes and subsets without requiring in-depth expertize in the fine details of terminology.

terminology gateway APIFHIR Terminology Service API

Open source integration tools useful for health IT integration projects

HAPI FHIR® is a simple-but-powerful library for adding FHIR messaging to applications. It is pure Java compatible and licensed under the business-friendly Apache Software License, version 2.0.

HAPI FHIR

 

External Solutions for API integration

Open source integration tools useful for health IT integration projects.

HAPI v2
 

HAPI for HL7 v2 messages is an open-source, object oriented HL7 v2.x parser developed for the Java platform

HAPI FHIR
 

HAPI FHIR is a simple-but-powerful library for adding FHIR messaging to your application. It is pure Java compatible and licensed under the business-friendly Apache Software License, version 2.0.

-->

Open source integration tool useful for health IT integration projects

HAPI for HL7 v2 messages is an open-source, object oriented HL7 v2.x parser developed for the Java platform.

HAPI v2

Enhanced browsing of HL7 v3

Infoway HL7 Explorer is a powerful browser for HL7 v3 structures, vocabulary and references. Used in conjunction with the pan-Canadian releases, HL7 Explorer makes locating details and information more efficient.

Overview
 

Learn about what HL7 Explorer can do for you with this brief online presentation.

MR 02.06
 

HL7 Explorer applied to the MR 02.06 HL7 v3 maintenance release

CeRx 4.4.2
 

HL7 Explorer applied to the CeRx 4.4.2 HL7 v3 maintenance release

 

 

Standards versions available for viewing in HL7 Explorer

Standard URL 
CA MR 02.06 https://infocentral.infoway-inforoute.ca/extra/ca/mr0206-html/html/search.html
CA MR 02.05.01 https://infocentral.infoway-inforoute.ca/extra/ca/mr020501-html/html/start.html
CA MR 02.05 https://infocentral.infoway-inforoute.ca/extra/ca/mr0205-html/html/start.html
CA MR 02.04.03 https://infocentral.infoway-inforoute.ca/extra/ca/mr020403-html/html/start.html
CA CeRx 4.4.2 https://infocentral.infoway-inforoute.ca/extra/ca/cerx442-html/html/search.html
CA CeRx 4.4.1 https://infocentral.infoway-inforoute.ca/extra/ca/cerx441-html/html/start.html 
CA CeRx 4.4 https://infocentral.infoway-inforoute.ca/extra/ca/cerx44-html/html/start.html
BC V02R04 https://infocentral.infoway-inforoute.ca/extra/bc/v02r04-html/html/start.html
NS CeRx 4.3 https://infocentral.infoway-inforoute.ca/extra/ns/cerx43-html/html/start.html
NS R02.04.03 https://infocentral.infoway-inforoute.ca/extra/ns/r020403-html/html/start.html
AB MR2007 https://infocentral.infoway-inforoute.ca/extra/ab/mr2007-html/html/start.html
AB R02.04.03 https://infocentral.infoway-inforoute.ca/extra/ab/r020403-html/html/start.html
AB R02.04.00 SHR https://infocentral.infoway-inforoute.ca/extra/ab/r020400-shr-html/html/start.html
AB R02.04.03 Imm https://infocentral.infoway-inforoute.ca/extra/ab/r020403-imm-html/html/start.html

Request Management Solution

InfoRMS (Infoway Request Management System) is Infoway's Request for Change Tool for SNOMED CT, pCLOCD/LOINC, pan-Canadian Subsets and pan-Canadian HL7 artifacts. Not sure if you have access to InfoRMS? Manage your InfoRMS Access in your user profile.
SNOMED CT
 

Submit or follow requests to SNOMED CT

pCLOCD/LOINC
 

Submit or follow requests to pCLOCD/LOINC

pan-Canadian Subsets
 

Submit or follow requests to pan-Canadian Subsets

HL7
 

Follow requests to pan-Canadian HL7 messaging

 

infoscribeSupporting the Standards Selection Framework, InfoScribe enables teams to collaboratively create, discuss, and publish digital health solutions from clinical requirements to specifications. Featuring templates, versioning, PDF export, inline commenting and HL7 Explorer integration, InfoScribe improves productivity and accelerates the development of healthcare solutions.

Standards Selection Framework

The Standards Selection Framework provides users with the means to plan, choose and document interoperability solutions from concept through to implementation. Starting from the Clinical Requirements identified by clinicians through to business requirements, standards and technical specifications, the framework provides a comprehensive guide through the development of interoperability solutions.

The framework also provides an opportunity for the InfoCentral community to share successful implementation projects, the standards selections made at a point in time of the project and the specifications that result from the selections made. Publishing solutions in this space will help to establish a Canadian repository of references.

clinical requirements

Clinical Requirements describe the information and workflow needs of the clinician for a specific clinical context and clinical data exchange. Using the Clinical Interoperability Principles as a guide, a set of requirements expressed in the clinician’s voice will provide the foundation for a well-designed interoperability solution.

business requirements

Business Requirements are derived from clinical requirements and provide a full picture of the solution that needs to be developed. Use cases, business rules and guidance are used to fully outline the solution design.

standards selection

Standards Selection refers to the process that has been developed to help guide teams through the selection of terminology and messaging standards. Using the line of inquiry and considerations in the forms provided implementation teams may assess the standards available and determine the best option for the point in time. The process also provides an opportunity for the InfoCentral community to share successful implementation projects, promoting standardization through reuse.

standards

Standards are an integral piece of the interoperability solution, covering both the terminology that defines the data sent, and the messaging structures that define how the data is transferred. The framework provides the access and consideration criteria to the international and Canadian standards to facilitate implementation.

specifications

Specifications provide the details for the solution to be implemented. These details include: a review of the data elements used, samples of transferred messages, the system architecture as well as the security specifications including authorization and authentication.

Solution for API integration

Infoway Message Builder allows developers to focus on the business challenges of integrating their solutions with each electronic health record implementation by abstracting the differences between different versions of pan-Canadian HL7 messaging and supporting current implementation constraints. Developers can build interfaces in a familiar development environment, using the programming language of their choice*, while the Message Builder API fosters quick and easy creation, population and access to HL7v3 requests and responses.

Infoway Message Builder v2.0 and later is enhanced to generate JAVA APIs to create, validate, marshal/unmarshal CDA documents.

 Implementation and Exchange

 

Key features and benefits

Message Builder offers a number of key features and benefits:

  1. Abstracts the complexity of HL7v3 messages and greatly simplifies the work of the developer when implementing them;
  2. Reduces the impact on developers from implementation variations;
  3. Enables companies to achieve Infoway product certification with greater confidence and reduced time;
  4. Enables developers to incorporate future message versions without re-writing their products;
  5. Can be embedded in software applications due to its open source distribution under a commercial-friendly Apache 2.0 license.

Out of the box support

Infoway Message Builder comes with built-in runtime APIs that support a number of pan-Canadian specifications:

  • MR2009 (R02.04.02)
  • MR2007 (V02R02)
  • MR 2007 (V02R01)
  • CeRx (V01R04.3)

In addition, while developers can easily build custom transport mechanisms without affecting the core, Message Builder includes native support for SOAP and RESTful message transports. Developers can configure and extend the transport as desired.

Detailed product features

  • Provides the capability to configure and populate message values that are common to all messages—this allows developers to reuse common message data, shortening the time to configure and create an interoperable system.
  • Uses simplified data types that are natural and familiar to the programming language (e.g. String for ST) rather than directly exposing the sometimes complicated HL7v3 data types—yet still allowing access to HL7v3 data types when necessary.
  • Allows developers to focus on the business-aspect of a request/response, avoiding many of the complexities of HL7v3.
  • Code-generation algorithms merge identical and similar classes together to simplify the generated API—meaning less confusion in the resulting code and an increased ability to write generic handlers for certain types.
  • Converts populated objects into HL7v3 XML requests, and converts HL7v3 responses into populated objects.
  • Provides flexibility in configuring and performing terminology-code lookups, including code set and database-backed lookups (can mix and match).
  • Associations and attributes are strongly typed, given business names when provided, and contain code docs directly from the MIFs (see wiki.hl7.org/index.php?title=MIF).
  • The algorithms inline most classes that only have a small number of properties, further simplifying the API.
  • Offers both permissive and strict modes—permissive allows many common errors and generates appropriate error comments in the XML or result object.
  • A separate validation tool is provided to test ad-hoc messages—this tool reuses the same validation components that are executed during message marshaling and unmarshalling, ensuring consistent processing of the message whether during processing or during conformance validation.

Forward looking

The power of the Message Builder architecture is in its MIF-based generation of the specification API. With Message Builder, any MIF is supported—whether a future release of the pan-Canadian specifications or a modified (constrained) jurisdiction-specific release of an existing specification. 

 

How it works

Message Builder comprises two parts:

  1. Message Builder Generator—a tool used by Infoway to take input MIFs and create Message Sets for use by Message Builder Runtime;
  2. Message Builder Runtime—an API used by developers to allow their products to support multiple Message Sets without recoding.

Message Builder Generator

Used by Infoway, Message Builder Generator takes MIFs (as the source of truth for standards specifications) and converts them into a series of Java Classes. This is done by first converting the MIFs to an XML Message Set (a simplified representation of the information present in the original MIFs), then generating Java Classes that reference standard Java data types and use business-friendly names. In the process, groups of related elements are flattened and similar message parts are placed into a single class: these steps increase ease of use and reduce the complexity of the resulting Java Classes.

MBG process

Using Message Builder Generator, Infoway is able to create multiple Message Sets, each representing the MIFs used in a single jurisdiction, but all for the same HL7v3 version.

Message Builder Runtime

Message Builder Runtime allows developers to quickly adapt to implementations in multiple Jurisdictions: incoming messages are first examined to determine the corresponding source Message Set, once identified, a series of Java Objects that represent the message are instantiated. Next, the Java Objects are turned into an HL7 message for the HL7 version corresponding to the desired destination Message Set. 

MB process

Using Message Builder Runtime developers can accept messages over the wire and on-the-fly turn them into a different HL7 message version. Given the capability of Message Builder to support future versions of HL7 messages, developers can easily future proof their products with minimal effort.

*Developer friendly

The Message Builder libraries are available for Java and Microsoft .NET. In addition, a simplified XML message format is available with REST-based services for managing mapping to/from the simplified form to the target specification XML format.

 

CDA Support

Message Builder CDA API supports the following CDA and data type specifications:

Message Builder provides  JAVA and .NET APIs for CDA document creation, validation, marshalling/unmarshalling of the following CDA document types:

  • Continuity of Care Document (CCD) (Release 1.1)
  • Consultation Notes (Release 1.1)
  • Discharge Summary (Release 1.1)
  • Imaging Integration, and DICOM Diagnostic Imaging Reports (DIR) (Release 1)
  • History and Physical (H&P) (Release 1.1)
  • Operative Note (Release 1.1)
  • Progress Note (Release 1.1)
  • Procedure Note (Release 1)
  • Unstructured Documents (Release 1.1)
  • CDA documents using pan Canadian CDA header template

Clinical applications in JAVA or .NET can use the Message Builder CDA APIs to create, validate or parse above listed types of CDA documents. Potential use cases are document source or document consumer actors in IHE XDS profile, content creator/content consumer in any content module/profile, or report creator/viewer in RIS/PACS/EMR systems.

Message Builder is available for Java and .NET

Message Builder for Java

System Requirements

  • Java 1.5 or higher
  • Maven 3.0.3 or higher (can be removed after installing Message Builder if working with a non-Maven project)

Download

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder, you will need

  1. Message Builder Core and
  2. one or more Message Builder API release(s)—depending on your implementation requirements.

Select a Message Builder Version:

 

Select one or more Message Builder API releases:

 

Optional Message Builder components:

Terminology Database Resolver
Message Builder Example

Message Builder pom.xml file:

 

Message Builder for .NET

System Requirements

  • .Net Framework 3.5 or higher

Download

Message Builder v2.1 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder:

  1. Download Message Builder .NET Core 2.1.0 setup
  2. Unzip and pull out the dll files that you need:
     \ → root location of required Message Builder core assemblies (Mandatory - required all)
     \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
  3. Copy them to your .NET project 
  4. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

Message Builder v1.5.8.1 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder:

  1. Download Message Builder .NET Core 1.5.8.1 setup
  2. Unzip and pull out the dll files that you need:
     \ → root location of required Message Builder core assemblies (Mandatory - required all)
     \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
  3. Copy them to your .NET project 
  4. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

Message Builder v1.4.6 for .NET

Message Builder is licensed under Apache License, Version 2.0. To use Message Builder, you will need

  1. Download Message Builder .NET Core 1.4.6 setup
  2. Unzip and run SetupCore.msi file
  3. Choose a installation location <install dir>.  The setup execution should place the following directories in <install dir>:
     \lib\ → location of required Message Builder core assemblies (Mandatory - required all)
      \releases\ → location of Message Builder release assemblies (Mandatory - choose one or more)
     \src\ → location of all source code and project files required to load them into visual studios
     \debug\ → location of debug symbol files
  4. Pull out files the dll files from the \lib\ and \releases\ folders, and copy them to your .NET project 
  5. Download Message Builder .NET 3rd-Party libraries, unzip it, and copy the files to your .NET project

Localization of pan-Canadian Standards

Infoway Message ReMixer is a web-based application that allows for the localization of pan-Canadian Standards (pCS) messages to meet jurisdictional requirements, all while maintaining the integrity of the original, standard message.

msg remixerAccess Message ReMixer Now

 Implementation and Exchange

Jurisdictional ReMixes

Pan-Canadian Standards use Object Identifiers (OIDs) to distinguish between objects by assigning a numeric string that enables other systems to understand the unique information that is being shared between various systems.

  • OIDs are intended to be globally unique and never re-used
  • OIDs in the pan-Canadian standards identify terminology code systems and are transmitted in HL7 messages
  • OIDS used to identify terminology subsets are not transmitted in HL7 messages, rather these OIDs are used for vocabulary maintenance and Terminology Services
  • OIDs are used to qualify local identifiers (e.g. patient identifiers) such that the combination of an OID (assigning authority) and a local identifier remains globally unique

Browse International and Canadian Content

SNOMED International's SNOMED CT browser allows users to browse and search the SNOMED CT International Edition to explore concepts and relationships. It also provides access to browse national extensions from SNOMED International member countries including the Canadian Edition of SNOMED CT in English and French.

snomed browser Browse SNOMED CT Now

 General Documentation

Browse, download and leverage the terminology used in Canada

Terminology Gateway is a web based solution framework that enables the distribution and sharing of terminology concepts, subsets and concept maps, making them available for web browsing, download or real time query.

terminology gatewayBrowse Terminology Gateway Now

RESTful web services used to browse terminology data

Terminology Service RESTful APIs enable automated exchange of clinical terminology content and resources. It allows developers to easily implement healthcare applications that programmatically consume codes and subsets without requiring in-depth expertise in the details of terminology.

terminology gateway APITerminology Service API

Apelon’s TermWorks is an easy-to-use data mapping solution which is provided by request for free to individuals who have Standards Access. It brings powerful terminology capabilities directly to the desktop. TermWorks combines Microsoft® Excel® spreadsheet software with web services-based terminology processing to give organizations comprehensive mapping capability to SNOMED CT and the Canadian Edition of SNOMED CT.

 Education

  • Introduction to SNOMED CT (English)
  • Introduction to SNOMED CT (French)
  • This email address is being protected from spambots. You need JavaScript enabled to view it.

Web Conference

Please login to acquire access to the InfoCentral web conferencing.

Members

Seema Nayani
Canada Health Infoway
OFFLINE
Contact
Tasha Shaw-Verbic
Canada Health Infoway
ONLINE
Admin
Linda Monico
Canada Health Infoway
OFFLINE
Admin
Melanie Hewlett
Central Health
OFFLINE
Member
Andrew Eagleson
Metro Ontario Pharmacies Limited
OFFLINE
Member
Julie James
Blue Wave Informatics LLP
OFFLINE
Member
Nirav Naik
William Osler Health System
OFFLINE
Member
Alain Ferschke
Cofomo
OFFLINE
Member
Marita Tonkin
Hamilton Health Sciences
OFFLINE
Member
Marie Rocchi
University of Toronto
OFFLINE
Member
Tom Janzen
LHSC
OFFLINE
Member
Olga Bondar
Scarborough Centre for Healthy Communities
OFFLINE
Member
Michal Racki
Royal Victoria Regional Health Centre
OFFLINE
Member
Liz Moran-Murray
Saskatoon Health Region
OFFLINE
Member
Kaireen Patton
Health Canada
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