HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative

HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions

Requirements: TI.4.2 Maintenance and Versioning of Standard Terminologies (Function)

Official URL: http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.4.2 Version: 2.0.1
Standards status: Normative Computable Name: TI_4_2_Maintenance_and_Versioning_of_Standard_Terminologies

Enable version control according to scope of practice, organizational policy, and/or jurisdictional law to ensure maintenance of utilized standard terminologies.

This includes the ability to accommodate changes to terminology sets as the source terminology undergoes its natural update process (new codes, retired codes, redirected codes). Such changes need to be cascaded to clinical content embedded in templates, custom formularies, etc., as determined by existing policy.

Description I: Version control allows for multiple sets or versions of the same terminology to exist and be distinctly recognized over time. Standard terminologies are usually periodically updated, and concurrent use of different versions may be required. Ideally, the meaning of a concept never changes over time, but a concept can be deprecated, and replaced with a new concept in a new version. However, in some terminologies, the meaning of a concept can change over time. In any case, it is important that retrospective analysis and research maintains the ability to relate to the appropriate conceptual meaning. If the terminology encoding for a concept changes over time, it is also important that for legal health records, as well as for retrospective analysis and research, the different encodings can be correlated to ensure the permanence of the concept as originally captured. This does not necessarily imply that complete older versions of the terminology be kept in the PHR-S, only access to the changes needs to be maintained.
Criteria N:
TI.4.2#01 SHALL The system SHALL provide the ability to manage data using different versions of standard terminologies.
TI.4.2#02 SHALL The system SHALL provide the ability to update standard terminologies.
TI.4.2#03 SHOULD The system SHOULD maintain relationships among versions of a standard terminology to allow preservation of interpretation over time.
TI.4.2#04 SHOULD The system SHOULD provide the ability to receive and harmonize data from and transmit data to other systems that use known different versions of a terminology standard while preserving the meaning of that data.
TI.4.2#05 SHALL The system SHALL provide the ability to update terminologies to a deprecated status.
TI.4.2#06 SHALL The system SHALL provide the ability to update individual codes within a terminology to a deprecated status.
TI.4.2#07 SHALL The system SHALL provide the ability to update terms with their equivalent when terminology is changed, where coded terminology content is embedded in clinical models (e.g., templates and custom formularies), when the terminology changes can be accomplished unambiguously, and if consistent with scope of practice, organizational policy, and/or jurisdictional law.
TI.4.2#08 SHALL The system SHALL provide the ability to update standard terminologies used to enter clinical content (via templates, custom formularies, etc.)
TI.4.2#09 SHALL The system SHALL maintain an audit log or a change history of code system to the individual code level, for versions used, dates implemented and updated to enable correct interpretation of historical data over time.