Webinar: Digital Health Software Safety Adoption, ISO Community, Sep 27. Add the date to your calendar more >

Share this page:

SNOMED CT
Sharing information, lessons learned and discussion between SNOMED International, Infoway's Canadian stakeholders and implementers.
Members: 163
Type: Open
Access: Public
Sharing information, lessons learned and discussion between SNOMED International, Infoway's Canadian stakeholders and implementers.

About

What is the SNOMED CT Community?

The SNOMED CT Community is a place to share lessons learned and learn about new and existing implementations and updates to both the International version and Canadian English and French Extensions of SNOMED CT. Canada Health Infoway is the National Release Centre (NRC) for SNOMED CT in Canada.

Whether you are looking to add new content to SNOMED CT, consult editorial guidelines, browse the content or want to map your local terminology to SNOMED CT, this is the place to be.

Implementations of SNOMED CT are growing by leaps and bounds in Canada and so is the wealth of International and Canadian knowledge to share.

To become a member of this community select Join Group in the Group Menu .

If you have an idea for a community, working group or project that will drive interoperability forward, let us know! Send your suggestions

LEADERS

Sharilyn Kmech, Director, Provincial Terminology Services, Health Information Management, Alberta Health Services

Shelley Lipon, Customer Relations Lead Americas, SNOMED International

KEY RESOURCES

SNOMED CT Artifacts (Standard, Release Notes, Maintenance, Education, etc.)

Activity

Francis Lau created a new discussion in SNOMED CT
A new graduate certificate program in Health Terminology Standards is being launched by UVic’s School of Health Information Science in partnership with eHealth Ontario, Gevity Consulting and RKL Health Informatics. It will start in September 2018 as a one-year, part-time, online program that includes a 2.5 day on-campus workshop. The Program is currently undergoing accreditation by the Canadian College of Health Information Management (CCHIM). Once accredited, graduates will be eligible to apply for CCHIM terminology certification. Applications will be accepted until March 1, 2018. Learn more? See http://www.uvic.ca/hsd/hinf/graduate/certificate/terminology/index.php Questions? Email us – hinfgradadvisor@uvic.ca
Linda Parisien created a new discussion in SNOMED CT
Thanks to those in attendance at today's meeting. Very good suggestions and feedback were provided on the different topics convered. If you were not there and wish to share your thoughts on the future presentations or how to improve the meeting formats, please post them on the Forum. Thank you! Here is the slide deck from today's meeting. .... Take note that the next SNOMED CT Community Monthly meeting will be on October 31.
Linda Parisien created a new discussion in SNOMED CT
SNOMED International E-Learning Advisory Group is reaching out to the SNOMED Community for feedback on how they can enhance the Content Development Theory Course. The course will not be offered in January 2018 to enable for maintenance and enhancement for a beginner audience to improve learning opportunities. Can you provide us with your responses to the following questions: Which groups within Canada should be part of the target audience for this course? For those who took the course, what areas of the course do you think would most benefit from the addition of hands-on exercises? What additional topics should be included in the course? Past students have suggested the inclusion of material on authoring in extensions. What subtopics of this should be covered? The current course: • Focuses on the theory of SNOMED CT content development • Does not include student access to tooling (with the exception of the browser) • Has three modules: o Module A: Explains the structure of SNOMED CT, content development overview and managing content requests o Module B: Explores the concept models for 4 hierarchies and the creation of new content o Module C: Explores the remaining concept models, as well as making changes to existing content Currently SNOMED International is not planning to add intermediate or advanced topics to this course. More in-depth information on the course can be found at: https://confluence.ihtsdotools.org/display/ELAG/Content+Development+Course+Outline Please respond to this forum posting with your comments and information and thanks in advance for your help!
Sari Schapira created a new discussion in SNOMED CT
The ISO community will be hosting a Webinar on "Digital Health Software Safety Adoption - New Standards Coming our Way" - September 27th 12:00-1:00pm ET. Canada has been an early leader in the area of software safety, an increasing concern in major countries around the world with the growing role of digital health in all care delivery and with the reliance of clinicians on digital health solutions for decision support and treatment. More is now understood about both the breadth of risks of health software and the depth of actions health informatics professionals need to take. Actions including mitigating threats from inadequate software design, system failures, data quality and workflow issues, poor integration, maintenance and implementation practices and from a major emerging concern -cybersecurity. For more details and to add the meeting to your calendar, please see our ... . Cheers, Sari B)
Sari Schapira joined a group
Logo
Sharing information, lessons learned and discussion between SNOMED International, Infoway's Canadian stakeholders and implementers.
Linda Parisien created an event in SNOMED CT
SNOMED CT Canadian Edition Release Webinar
Thursday, November 02, 2017, 01:00pm - 02:30pm
Come and learn about the newest SNOMED CT® Canadian Edition. Our agenda will include: Canadian Release Highlights Release scope What the updates mean to Canadian stakeholders? RF2 Format Implementation of the release IHTSDO References Maintenance considerations Where to find the new release files? Browsing the Canadian Edition Demo & Hands On Questions Weblinks: Add to Calendar & Join the meeting Audio connection: 1-8666260833 (US) Call-in toll-free number Conference Code: 510 611 0296 https://infoway-inforoute.webex.com/infoway-inforoute/j.php?MTID=m636adef81a8bba64fe3a5510cd1c0a26
Linda Parisien created an event in SNOMED CT
CA Edition Release of SNOMED CT
Tuesday, October 31, 2017, 08:00am
Today Infoway is releasing the latest version of the Canadian Edition of SNOMED CT. This release aligns the Canadian content to the July 31, 2017 version of SNOMED CT International. Learn more: https://infocentral.infoway-inforoute.ca/en/standards/health-information/snomed-ct

Forum

A New Graduate Certificate Program in Health Terminology Standards 09/21/17
A new graduate certificate program in Health Terminology Standards is being launched by UVic’s School of Health Information Science in partnership with eHealth Ontario, Gevity Consulting and RKL Health Informatics. It will start in September 2018 as...
SNOMED CT Community Meeting 09/19/17
Thanks to those in attendance at today's meeting. Very good suggestions and feedback were provided on the different topics convered. If you were not there and wish to share your thoughts on the future presentations or how to improve the meeting form...
Enhancement of the SNOMED International Content Development Theory Course 09/15/17
SNOMED International E-Learning Advisory Group is reaching out to the SNOMED Community for feedback on how they can enhance the Content Development Theory Course. The course will not be offered in January 2018 to enable for maintenance and enhance...
Webinar "Digital Health Software Safety Adoption - New Standards Coming our Way" - September 27th 12:00-1:00pm ET 09/13/17
The ISO community will be hosting a Webinar on "Digital Health Software Safety Adoption - New Standards Coming our Way" - September 27th 12:00-1:00pm ET. Canada has been an early leader in the area of software safety, an increasing concern in maj...
New Season for SNOMED CT Community starting Sept 19. 09/06/17
We are pleased to invite you to this first meeting of the new 2017-2018 season for the SNOMED CT Community, which will be held on September 19 from 11h00-12h00 ET. Join the call to discuss your interests and needs for future presentations....
Are you using SNOMED CT for both the clinical question and the answer? 08/25/17
Hi Lorie, Thank you so much.This is very helpful. Regards, Harsh Sharma
Are you using SNOMED CT for both the clinical question and the answer? 08/25/17
Hi, Across Canada, 8 of 10 provinces and 1 territory have implemented LOINC as the question for lab observables. Some have done a little work on also implementing SNOMED CT for coded result values such as microorganism. LOINC and SNOMED CT can...
Are you using SNOMED CT for both the clinical question and the answer? 08/25/17
Hi Linda, Thank you so much for such valuable information. Regards, Harsh
Are you using SNOMED CT for both the clinical question and the answer? 08/25/17
Hi Sharma, These are good questions. SNOMED International has developed reference materials on the use of both LOINC and SNOMED CT that can be found .... From that page, I would encourage you to read the following guide called: Guidance on use of S...
Are you using SNOMED CT for both the clinical question and the answer? 08/24/17
Hello, I am looking for some online resources to see any active work going on with regards to LOINC - SNOMED CT mapping? The question is, Can we use LOINC and SNOMED-CT together in HL7 messaging? What is the success rate if we implement SNOMED-CT...
Are you using SNOMED CT for both the clinical question and the answer? 08/18/17
Hi, as SNOMED CT implementers, can you provide input on this topic? The context of use is either a question on a survey or form, a measurement on a patient or a distinct element on a report. Thank you!
Update of the outstanding open RFC policy 08/11/17
Infoway is updating the policy on outstanding open RFC’s to better align with international SDO policies. Infoway has revised the timeframe that an RFC will be closed when an answer is pending. The current timeframe is 90 days and will change to...
The July 2017 SNOMED CT International Release is now available 08/08/17
Hi Shujath, We no longer record presentations... but the powerpoint presentation can be found at: https://infocentral.infoway-inforoute.ca/en/resources/docs/snomedct/presentations/2192-july2017-snomed-ct-international-presentation Linda
The July 2017 SNOMED CT International Release is now available 08/08/17
Hi Linda Hope you are doing well do you by any chance have the recording for the presentation on the snomed release from Aug 3rd? please email me at shujath.khan@ahs.ca Thanks. S.Khan
Webinar: July 2017 release of SNOMED CT International version 08/03/17
Thanks to all participants at today's meeting. Please find the slide deck I presented: ... If you have questions, please post them on the Forum or submit to the Standards Help Desk.

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.

Implementation ( 23 Documents )

TermWorks ( 7 Documents )

Video

This Group has no videos.

Solutions

  • FHIR Terminology Service API
  • HAPI FHIR
  • HAPI v2
  • HL7 Explorer
  • InfoRMS
  • InfoScribe
  • Message Builder
  • Message ReMixer
  • Object Identifier (OID)
  • SNOMED CT Browser
  • Terminology Gateway
  • Terminology Service API
  • TermWorks

FHIR web services used to access terminology data

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

terminology gateway APIFHIR Terminology Service API

Open source integration tools useful for health IT integration projects

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

HAPI FHIR

 

External Solutions for API integration

Open source integration tools useful for health IT integration projects.

HAPI v2
 

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

HAPI FHIR
 

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

-->

Open source integration tool useful for health IT integration projects

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

HAPI v2

Enhanced browsing of HL7 v3

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

Overview
 

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

MR 02.06
 

HL7 Explorer applied to the MR 02.06 HL7 v3 maintenance release

CeRx 4.4.2
 

HL7 Explorer applied to the CeRx 4.4.2 HL7 v3 maintenance release

 

 

Standards versions available for viewing in HL7 Explorer

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

Request Management Solution

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

Submit or follow requests to SNOMED CT

pCLOCD/LOINC
 

Submit or follow requests to pCLOCD/LOINC

pan-Canadian Subsets
 

Submit or follow requests to pan-Canadian Subsets

HL7
 

Follow requests to pan-Canadian HL7 messaging

 

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

Standards Selection Framework

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

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

clinical requirements

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

business requirements

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

standards selection

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

standards

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

specifications

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

Solution for API integration

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

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

 Implementation and Exchange

 

Key features and benefits

Message Builder offers a number of key features and benefits:

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

Out of the box support

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

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

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

Detailed product features

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

Forward looking

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

 

How it works

Message Builder comprises two parts:

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

Message Builder Generator

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

MBG process

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

Message Builder Runtime

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

MB process

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

 

*Developer friendly

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

 

CDA Support

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

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

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

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

Message Builder is available for Java and .NET

Message Builder for Java

System Requirements

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

Download

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

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

Select a Message Builder Version:

 

Select one or more Message Builder API releases:

 

Optional Message Builder components:

Terminology Database Resolver
Message Builder Example

Message Builder pom.xml file:

 

Message Builder for .NET

System Requirements

  • .Net Framework 3.5 or higher

Download

Message Builder v2.1 for .NET

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

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

Message Builder v1.5.8.1 for .NET

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

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

Message Builder v1.4.6 for .NET

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

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

Localization of pan-Canadian Standards

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

msg remixerAccess Message ReMixer Now

 Implementation and Exchange

Jurisdictional ReMixes

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

Canada Health Infoway has an arrangement in place with HL7 International that allows Infoway to submit OIDs to HL7 International on behalf of Canadian Implementers free of charge (normally $100 USD fee per OID request).

Browse International and Canadian Content

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

snomed browser Browse SNOMED CT Now

 General Documentation

Browse, download and leverage the terminology used in Canada

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

terminology gatewayBrowse Terminology Gateway Now

RESTful web services used to browse terminology data

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

terminology gateway APITerminology Service API

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

 Education

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

Web Conference

Please login to acquire access to the InfoCentral web conferencing.

Members

Linda Parisien
Canada Health Infoway
OFFLINE
Contact
Linda Monico
Canada Health Infoway
ONLINE
Admin
Tasha Shaw-Verbic
Canada Health Infoway
ONLINE
Admin
Andrea MacLean
Canada Health Infoway
OFFLINE
Admin
Sari Schapira
Canada Health Infoway
OFFLINE
Member
Guillaume Crétot-Richert
Mckesson Canada
OFFLINE
Member
Dahlia Khajeei
University of Waterloo
OFFLINE
Member
Harsh Sharma
Alberta Health Services
OFFLINE
Member
Prasanth Joseph
Niagara Health
OFFLINE
Member
Julie Boutin
Ministère de la santé et des services sociaux
OFFLINE
Member
Kristin Morrison
n/a
OFFLINE
Member
Abdullah Khan
-
OFFLINE
Member
Shamhad Abdi
eHealth Ontario
OFFLINE
Member
Marise Bonenfant
Polyvalence/Myelin
OFFLINE
Member
Halina Labikova
Evinance
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