CeRx Urgent Release Notes V01R04.3 - July 10, 2007
Go to downloadable artifacts
Release Purpose
This Urgent Release includes fixes to the CeRx V01R04.2 Specification uncovered through the work of the early adopters as well as some minor attribute additions to support new requirements. It is intended to provide implementers access to a complete, updated specification. This release includes all artifacts reasonably needed to support the clinical drug messaging requirements for Drug Information System (DIS) and Point of Service (PoS) applications that communicate with a DIS. Agreement on the fixes was supported through a consensus process using the CeRx Discussion forum, several conference calls, as well as through direct dialogue with the early adopters. The specifications are an extension to V01R04.2 - 2006 September 11 and continue to be considered Stable for Use, subject to the continuing stability remarks outlined within the Scope and Tracking Framework (STF). Release
Release Change Synopsis
This release incorporates the following changes:
• Updates to content of the following artifacts to reflect resolution of technical errors or artifact misalignments submitted via the CeRx discussion forum, the Standards Help Desk or through direct contact with the Standards Collaborative (SC) Drug Team
• Technical artifacts
• Implementation Guide Volume 1 (English version only an updated French version is expected to be included in the CeRx Regular Maintenance Release in October 2007 )
• CeRx Data types document
• CeRx Queries Spreadsheet
• CeRx Vocabulary Spreadsheet
• CeRx Scope and Tracking Framework (STF)
• Updated Standards Development Tracking Log to specifically reflect the issues raised and resolved. These are noted in the Feedback Tab.
• Scope and Tracking Framework (STF) updates including
• Updated Stability Remarks in the STF to take into account the latest developments and directions of other pan-Canadian standards initiatives as well as the latest assessment of HL7 ballot progress.
• Rename of Change Request tab in the STF to Artifact Changes tab
• Updates in the Artifact Changes tab of the STF to reflect the content of this release
No patches between V01R04.2 and this release have been identified.
One Addendum to V01R04.2 was issued and all contents of the addendum are included in the release. HL7 redesigned its tools this spring to better differentiate vocabulary components. The models now disambiguate whether theyre referencing code systems, domains or value-sets. Because CeRx makes use of international tools, these changes are reflected in our most recently published models. The fundamental impact of the change is that some attributes that used to refer to vocabulary domains will now refer to code systems. These attributes will be those having fixed values. This may impact implementers who are performing code generation using the MIF, however because the change should only impact attributes with fixed values, it is hoped the impact will be small.
| Anchor | ||||
|---|---|---|---|---|
|
Downloadable Artifacts
| Filename | Description |
|---|---|
| Business Model | |
| Tracking Logs | |
| CeRx Queries | |
| Conformance Matrix | |
| Scope and Tracking Matrix | |
| Standards Development Documentation Framework | |
| Glossary | |
| Implementation Guide Volume 0 - Overview | |
| Implementation Guide Volume 1 - Pharmacy | |
| Implementation Guide Volume 2 - Clinical Records | |
| Implementation Guide Volume 3 - Shared Interactions | |
| MIF | |
| Word View | |
| XML Example Instance Scenarios | |
| Excel View | |
| Table View | |
| Visio Model | |
| XML Schema | |
| Data Types Specification | |
| Vocabulary |
| Info |
|---|
During a review of documentation, it has been determined that a couple points of clarification need to be made with regards to the tools used during the development of this release. These are:
|
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.
Standards
...
| title | Delta release |
|---|
...