The system SHALL provide the ability to manage data using different versions of standard or preferred clinical models.

The system SHALL provide the ability to update standard or preferred clinical models.

The system SHOULD maintain relationships among versions of a standard or preferred clinical models to allow preservation of interpretation over time.

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 standard or preferred clinical model while preserving the meaning of that model.

The system SHALL provide the ability to update clinical models to a deprecated status.

The system SHALL provide the ability to update individual data elements within a clinical model to a deprecated status.

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.

NEEDS REVIEW

The system SHALL provide the ability to update standard or preferred clinical models used to enter clinical content (via templates, custom formularies, etc.)

The system SHALL maintain an audit log or a change history of clinical models to the individual clinical model, for versions used, dates implemented and updated to enable correct interpretation of historical data over time.