MR 02.06 Release Notes - Mar. 11, 2016

 Go to downloadable artifacts

Purpose of the Release notes

The Release Notes provide a high level summary of the changes made to the Terminology artifacts in support of the MR02.06 release of the pan-Canadian standards. A detailed description of all of the changes can be found in the corresponding Terminology Change File (SC-3004-EN-Terminology Change MR02.06 -20160311). 

The Release Notes are intended to be used in conjunctions with the other business (e.g. HL7 Explorer) and technical artifacts (e.g. Vocabulary MIFs) published as part of this release.

Stakeholders are strongly encouraged to review the Release Notes prior to exploring the rest of the published artifacts.

Synopsis of the Release Changes

To support existing and new implementations, there were a considerable number of changes applied to MR 02.06, which include: 

• Updates to Value set content reflecting implementation status (deprecation of temporary concepts) 

• Updates to Value Set content based on implementation requests in the following domains: 

  • Drug domain o Laboratory domain 
  • Provider Registry domain 
  • Shared Health Record domain 
  • Infrastructure domain 

• Value sets were updated to the: Deprecation of Non-human subset as a result of SNOMED CT version update

  • January 2015 release of SNOMED CT International and May 2015 release of SNOMED CT Canadian Extension; 

Details of all of these changes can be found in the Terminology Change File (SC-3004EN-Terminology Change MR02.06 -20160311) which is an Excel file that allows implementers to filter by any of the column headings on the respective tabs of the Excel file to identify relevant changes. The Change File contains a “How to Read” tab to assist implementers with determining the changes that may impact them.

List of Known Issues

The following are general known issues that will be addressed and reflected in a subsequent release (full or delta):

• Value Sets with noted Value Set Comments (e.g. ActProfessionalServiceCode, DiagnosisValue, NonDrugAgentEntity) 

• Empty Value Sets – these require implementation and business requirement input: 

  • ProviderQueryResponseObject • RoutedDocumentType 
  • Binding strength (CNE or CWE) discrepancy between models and terminology documentations. 
  • The source of truth of each concept domain’s binding strength resides in the Terminology Worksheet. 
  • Where the model reference a value set, the source of truth of the binding strength resides in the specific model attribute. 
  • Risk of Changes indicated in Master Terminology Worksheet, Vocabulary Summary tab, column E (Risk of Change) 
    • For example OtherIdentifierRoleType concept domain name will be renamed as PersonIdentifierRoleType 

For guidance on how to implement and use the Master Terminology Worksheet, please refer to the SC-0006-EN - Implementation Guide Volume 2 - Terminology- MR02.05_Release - 20130923.doc.

Guidance for Existing and New Implementers

New Implementers

A new implementer is one that has not implemented any of the pan-Canadian HL7 messaging standards into their environment. New implementers are encouraged to begin with the latest release of the Master Terminology Worksheet, associated HL7 messaging standards and supporting documents.

Existing Implementers

Existing implementers are those that have implemented one or more versions of the pan-Canadian HL7 messaging standards into their environment. Careful consideration of the impact of the changes associated with this release must be reviewed when planning to upgrade from a previous release. All changes associated with the artifacts in use must be reviewed and considered. 

Implementations that have implemented a single HL7 domain specific messaging standard and are now adding new domains will want to consider ensuring that the content for both domains is compatible (e.g. upgrade the existing domain to the latest version, implement a compatible previous version or ensure the most recent version is compatible with the existing domain version).

Summary of HL7 Terminology and SC Code System related changes 

Summary of SNOMED CT related changes

The changes made to SNOMED CT Value Sets were to the January 2015 release of SNOMED CT International and May 2015 release of SNOMED CT Canadian Extension.