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.5 Team/Group of Providers Registry or Directory (Function)

Page standards status: Informative
Statement N:

Provide access to a current directory, registry or repository of information on teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.

 Description I:

An organization may assign caregivers to teams that need to be registered as such. In another scenario, an organization might contract with a group of providers. The group would be listed by the group name or individually or both. A caregiver might be part of more than one team or group. All of these factors need to be supported. Information includes, but is not limited to: full name, address or physical location, and a 24x7 telecommunications address (e.g., a phone or pager access number).

 Criteria N:
AS.1.5#01 dependent SHOULD

The system SHOULD provide the ability to render a current directory, registry or repository of teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.
AS.1.5#02 dependent SHOULD

The system SHOULD provide the ability for authorized users to manage the assignment of providers to appropriate teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.
AS.1.5#03 MAY

The system MAY provide the ability to determine the identity of a provider's employer(s) for administrative or financial purposes through the use of internal, and/or external registry services or directories.
AS.1.5#04 SHALL

The system SHALL provide the ability to tag the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant)
AS.1.5#05 SHOULD

The system SHOULD provide the ability to manage care team membership.
AS.1.5#06 dependent SHOULD

The system SHOULD provide the ability to manage demographic and scheduling information on care team members, according to scope of practice, organizational policy, and/or jurisdictional law.