CeRx 4.4.1 Release Notes - Revise Prescription
Go to downloadable artifacts
- The majority of the changes to the models were made with Visio 2002 in combination RMIM Designer 4.5.11
- In order to overcome a known issue with the above-mentioned applications, Visio 2007 and RMIM Designer 4.7.8 was used for certain model changes.
This delta release defines the functionality around the major use cases for Revise Prescription. Revise Prescription is defined as the act of changing a prescription order without replacing it on the DIS. The major use cases defined for Revise Prescription are:
- Error Correction - This is the act of revising a prescription order in order to mitigate a clerical error or errors made by the user on a given prescription order.
- Clinical Modification - The is the act of revising a prescription order based on a clinical decision and/or an interaction with a patient by the original author of the prescription.
This work was requested by Alberta as they have plans to implement the Clinical Modification use case. Quebec supported development of the work as they have already implemented the error correction use case using the MR 2009 message set. Other interested parties include Pharmacy software vendors and the Canadian Association of Chain Drug Stores (CACDS) who requested that Revise Prescription functionality be developed as part of their presentation to jurisdictional CIOs in February of 2013.
Alberta has received these artifacts as a pre-release to meet their development time lines and now this delta release has been officially published.
Delta release
HL7 Explorer 1.0: Browse Pan-Canadian Standards Online
The HL7 Explorer view provides an easy to navigate web based rendering of the pan-Canadian standards. The HL7 Explorer is now considered stable for release and will continue to evolve over time based on stakeholder feedback.
PURPOSE OF THE RELEASE NOTES
These release notes provide a high level summary of the changes made to the pan-Canadian HL7 v3 artifacts in support of the CeRx 4.4.1 release. A detailed description of all of the changes, including Terminology changes, can be found in the corresponding Change Log (SC-3004-EN - Change File – CeRx 4.4.1 - 20141020).
These Release Notes are intended to be used in conjunction with the other business and technical artifacts published as part of this release.
Stakeholders are strongly encouraged to review the Release Notes prior to exploring the rest of the published artifacts.
HIGHLIGHTS OF THE RELEASE
The main focus of the CeRx 4.4.1 delta release is to provide an updated set of Drug Domain artifacts that support the two use cases identified as part of Revise Prescription functionality. These are:
1. Error Correction – This refers to the mitigation of clerical errors made by the user on a given prescription.
2. Clinical Modification – This refers to any change to a prescription order based on a clinical decision and/or based on an interaction with a patient by the original author of the prescription.
KNOWN ISSUES
The following issues are known to exist with this release:
Some MS Word View of the message models references the terminology object type (concept domain or value set) bound by a message attribute incorrectly. Also due to the long name of some concept domains, some text within the message attribute property table is being cut off. In both issues, please refer to the Visio message model for the source of truth.
TOOLING/RIM VERSION
The following is a list of tools used to generate this pre-release:
| Artifacts | Tools |
|---|---|
| Master Terminology Worksheet | Excel 2010 |
| Terminology Reference to Message Models | FindVocabUsage.xslt v13332 |
| Vocabulary Model Interchange Format (MIF) | MTW Conversion.xls v22434 ExpandCAUVSchema.xslt v18104 |
| Model MIF-2 View Remixer (beta) | Remixer v3.0.1rc10 |
| Model MIF-1 View | HL7 V3 Generator 3.2.2_20100219CA |
| Model MIF-2 View | HL7 V3 Generator 3.2.2_20100219CA |
| XML Schemas | HL7 V3 Generator 3.2.2_20100219CA |
| Message Worksheets Excel (xls) view | HL7 V3 Generator 3.2.2_20100219CA HL7_RMIM_HMD_master-v2.26 Excel 2010 |
| Message Worksheet Table View | HL7 V3 Generator 3.2.2_20100219CA |
| Models – Visio View | Visio 2007, RMIM Designer 4.7.1 + a required fix made by the SC and submitted to HL7 International as bug 1966 RoseTree 5.0.20 |
| Models – Word View | Generatedocs.doc v21852 |
| Sample Messages | Eclipse Instance Editor |
| Additional Tools Used as part of the generation process | PubDB_v205.mdb HL7 Description Editor v-1.3.4 HL7 Publishing Widget v-5.0.25 ExportGraphics.vsd v1159 |
RIM Repository – Vocabulary: 2.41.2
RIM Repository – Structure: 2.19
Downloadable Artifacts
| Filename | Description |
Release Notes, Change Log, Storyboards and Diagrams document, and Business Rules and Informational Requirements document | |
This is a zip of the entire CeRx 4.4.1 Release | |
General guidance and specifications on data type usage. | |
MTW is an artifact that specifies the pan-Canadian terminologies developed to support the electronic communication in pan-Canadian standards. | |
| Vocabulary Model Interchange Format Files (MIFs) CeRx4.4.1 - 20141020 | Vocabulary MIFs represent the MTW in a computable format which allows computer systems to consume the content. |
This file provides information on linkage from concept domains and value sets contained in the Master Terminology Worksheet to where they are referenced in the model attributes within the pan-Canadian static models included in this release. A XML editor/viewing is strongly recommended to be used when viewing this information. | |
This spreadsheet is a pivotal document in that it ties together the scope of the pan-Canadian HL7 v3 Specifications from a transaction perspective, through to interactions and finally to messages. | |
This file contains message models in MIF(Model Interchange Format) version 1 format generated from the V3 generator legacy tools. | |
This file contains message models in MIF(Model Interchange Format) version 2 format generated from the V3 legacy tools. | |
This file contains all XML schemas for message types and interactions as well as the core schema files (narrative block, infrastructure root, vocab schema and datatype schema) | |
This file contains all message models in Excel (XLS) format | |
This file contains all message models in Table View format. | |
This file contains all message models in Visio format | |
This file contains a business rendering of the message models in Word format |