United States Health Information Knowledgebase

 

You are viewing the Abridged Children's EHR Format.
To view the Full Children's EHR Format, you must first agree to the HL7 License Agreement.

Children's EHR Format Requirement Comparison

(No Match) Requirement ID: Req-259: Manage Medication List Req-276: Maintenance and Versioning of Standard Terminologies
(Matches) Release Package: 2013 Format 2013 Format
(No Match) Title: Manage Medication List Maintenance and Versioning of Standard Terminologies
(No Match) Description: STATEMENT: Create and maintain patient-specific medication lists.
DESCRIPTION: Medication lists are managed over time, whether over the course of a visit or stay, or the lifetime of a patient. All pertinent dates, including medication start, modification, and end dates are stored. The entire medication history for any medication, including alternative supplements and herbal medications, is viewable. Medication lists are not limited to medication orders recorded by providers, but may include, for example, pharmacy dispense/supply records, patient-reported medications and additional information such as age specific dosage.
STATEMENT: Enable version control according to customized policies to ensure maintenance of utilized standards.
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 local policy.
DESCRIPTION: Version control allows for multiple sets or versions of the same terminology to exist and be distinctly recognized over time.
Terminology standards are usually periodically updated, and concurrent use of different versions may be required. Since the meaning of a concept can change over time, it is important that retrospective analysis and research maintains the ability to relate changing conceptual meanings. If the terminology encoding for a concept changes over time, it is also important that retrospective analysis and research can correlate the different encodings to ensure the permanence of the concept. This does not necessarily imply that complete older versions of the terminology be kept in the EHR-S, only access to the changes needs to be maintained.
It should be possible to retire deprecated versions when applicable business cycles are completed while maintaining obsolescent code sets. An example use of this is for possible claims adjustment throughout the claim's lifecycle.
(No Match) Topic Area(s): Medication Management Special Terminology and Information
(Matches) Provenance: HL7 EHR FM R1 HL7 EHR FM R1
(Matches) Achievability:
(Matches) Requirement Type: Function Function
(Matches) Shall/Should/May:
(Matches) Critical/Core: no no
(Matches) Status: Released Released
(Matches) Links:
(No Match) See Also: S.2.2.1, IN.2.5.1, IN.2.5.2, IN.4.1, IN. 4.2, IN.4.3, IN.5.1, IN.5.2, IN.5.4, IN.6
(Matches) Comments:
(Matches) Additional Information:
(Matches) Implementation Notes:
Scroll To Top