Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build

Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## Example Requirements: TI.10.1 Standard or Preferred Clinical Models (Function)

Active as of 2024-01-31

TI.10.1#01 | SHALL | The system SHALL provide the ability to exchange data with other systems (internal or external to the PHR-S) using approved standard or preferred clinical models or compositions of clinical models (e.g patient summary, follow-up message).
TI.10.1#02 | SHALL | The system SHALL determine that clinical terms and coded clinical data exist in an approved Clinical Model.
TI.10.1#03 | SHOULD | The system SHOULD provide the ability to receive and transmit healthcare data using formal standard information models and approved standard or preferred clinical models according to scope of practice, organizational policy, and/or jurisdictional law.
TI.10.1#04 | SHOULD | The system SHOULD provide the ability to manage data using a standard or preferred clinical model according to scope of practice, organizational policy, and/or jurisdictional law.
TI.10.1#05 | SHALL | The system SHALL provide the ability to manage clical model assets and supporting tools (internal or external to the PHR-S).
TI.10.1#06 | MAY | IF there is no recognized-standard or preferred clinical model available, THEN the system MAY provide the ability to manage data using a locally-defined clinical model.
TI.10.1#07 | SHOULD | The system SHOULD provide the ability to capture information into structured data formats using approved standard or preferred clinical models without the user requiring knowledge of the clinical models used.
TI.10.1#08 | SHOULD | The system SHOULD provide the ability to enter data using content that is common to the user, and allow for collection and presentation of text form data to meet the pre-determined purposes of others. Text forms should exclude cryptic or uncommon abbreviations.
TI.10.1#09 | SHOULD | The system SHOULD provide the ability to present the terms used in standard or preferred clinical models in a language which is appropriate for the user.