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

Publication Build: This will be filled in by the publication tooling

## Requirements: TI.1.1 Entity Authentication (Function)

Page standards status: Informative

Statement N:

Authenticate PHR-S users, and/or entities before allowing access.

Description I:

All entities accessing the PHR-S are subject to authentication.

Examples of entity authentication, with varying levels of authentication rigor, include:

- username/password;
- digital certificate;
- secure token;
- biometrics.

Actors:
ehr Criteria N:

TI.1.1#01 | dependent SHALL | The system SHALL authenticate entities (e.g., users, organizations, applications, components, objects, and/or devices) accessing PHR-S protected resources (e.g., functions and data) according to scope of practice, organizational policy, and/or jurisdictional law, using an authentication mechanism such as an accredited Standards Development Organization-approved authentication standard (e.g., SAML, WS-Trust, Kerberos), username/password, digital certificate, secure token, biometric, or hardware-specific addressing mechanism. (See also ISO 22600.)
TI.1.1#02 | SHALL | The system SHALL manage authentication data/information securely (e.g., passwords or biometric data).
TI.1.1#03 | dependent SHALL | The system SHALL maintain configurable conditions and rules which protect against invalid, possibly malicious, authentication attempts according to organizational policy, and/or jurisdictional law (e.g., consecutive invalid logon attempts).
TI.1.1#04 | dependent conditional SHALL | IF passwords are used to control access to the PHR-S, THEN the system SHALL provide the ability to maintain configurable timeframes (e.g., 180 days) for the reuse of passwords according to organizational policy, and/or jurisdictional law.
TI.1.1#05 | dependent conditional SHALL | IF passwords are used to control access to the PHR-S, THEN the system SHALL provide the ability to maintain a configurable limit on the reuse of recently used passwords (e.g., the last 5 passwords) according to organizational policy, and/or jurisdictional law.
TI.1.1#06 | conditional SHALL | IF username/passwords are used to control access to the PHR-S, THEN the system SHALL maintain password strength rules (e.g., requiring a minimum number of characters and inclusion of alpha-numeric complexity).
TI.1.1#07 | dependent conditional SHALL | IF passwords are used to control access to the system, THEN the system SHALL capture the password using obfuscation techniques (e.g., during user password entry) according to scope of practice, organizational policy, and/or jurisdictional law.
TI.1.1#08 | conditional SHALL | IF passwords are used to control access to the PHR-S, THEN the system SHALL manage password reset as an administrative function.
TI.1.1#09 | conditional SHALL | IF user passwords are initially set or later reset by an administrator, THEN the system SHALL provide the ability to update password at the next successful logon.
TI.1.1#10 | SHALL | The system SHALL present limited feedback to the user during authentication.
TI.1.1#11 | SHALL | The system SHALL provide the ability to enter case-insensitive 'usernames' that contain typeable alpha-numeric characters in support of ISO-646/ECMA-6 (aka US ASCII).
TI.1.1#12 | conditional SHALL | IF passwords are used, THEN the system SHALL provide the ability to enter case-sensitive passwords that contain typeable alpha-numeric characters in support of ISO-646/ECMA-6 (aka US ASCII).