HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1-ballot - Normative Ballot International flag

HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/mvdzel/ehrsfm-fhir-r5/ and changes regularly. See the Directory of published versions

Requirements: AS.1.1 Manage Provider Registry or Directory (Function)

Page standards status: Informative
Statement N:

Provide a current registry or directory of practitioners that contains data needed to determine levels of access required by the system.

 Description I:

Provider information may include any credentials, certifications, or any other information that may be used to verify that a practitioner is permitted to use or access authorized data.

 Criteria N:
AS.1.1#01 dependent SHOULD

The system SHOULD provide the ability to manage a registry or directory of all personnel who currently use or access the system according to scope of practice, organizational policy, and/or jurisdictional law.
AS.1.1#02 SHOULD

The system SHOULD provide the ability to capture and maintain realm-specific legal identifiers required for care delivery (e.g., the provider's license number or national provider identifier).
AS.1.1#03 SHALL

The system SHALL provide the ability to capture and maintain the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant).
AS.1.1#04 SHOULD

The system SHOULD link provider information in the registry or directory with the security function to determine or identify authorized levels of access.
AS.1.1#05 MAY

The system MAY provide the ability to manage a directory of clinical/support personnel external to the organization that are not users of the system (to facilitate documentation and information communication).
AS.1.1#06 dependent SHOULD

The system SHOULD provide the ability to update the provider's access to the requested patient's information when a patient-provider relationship is established in the system (e.g., when patient is cared for in Emergency, system enables emergency attending provider to access patient's information); according to scope of practice, organizational policy, and/or jurisdictional law.
AS.1.1#07 conditional SHALL

IF TI.3 (Registry and Directory Services) is implemented, THEN the system SHALL conform to function TI.3 and provide the ability to use registries or directories to uniquely identify providers for the provision of care.
AS.1.1#08 SHOULD

The system SHOULD provide the ability for authorized users to hide selected elements of the registry or directory information for the users of the system based on the user's security level and access needs. For example, the administrator hides from data-entry clerks the name of the data-entry clerk's immediate relatives who are listed on the hospital's cancer registry.
AS.1.1#09 MAY

The system MAY provide the ability to maintain a registry or directory which identifies the provider by multiple unique identifiers.