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

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

## : AS.1.5 Team/Group of Providers Registry or Directory (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-AS.1.5"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <span id="description"><b>Statement <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b> <div><p>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.</p>
    </div></span>

        <span id="purpose"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>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).</p>
    </div></span>

        <span id="actors"><b>Actors:</b><br/> ehr</span>

        <span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>

        <table id="statements" class="grid dict">

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.1.5#01</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>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.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.1.5#02</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>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.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.1.5#03</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>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.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.1.5#04</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHALL</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>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)</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.1.5#05</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to manage care team membership.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.1.5#06</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>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.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.1.5"/>
      <version value="2.1.1-ballot"/>
      <name value="AS_1_5_Team_Group_of_Providers_Registry_or_Directory"/>
      <title
             value="AS.1.5 Team/Group of Providers Registry or Directory (Function)"/>
      <status value="active"/>
      <date value="2025-04-04T11:04:36+11:00"/>
      <publisher value="HL7 International / Electronic Health Records"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description
                   value="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."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="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)."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-AS.1.5-01"/>
        <label value="AS.1.5#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="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."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.1.3.5#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-AS.1.5-02"/>
        <label value="AS.1.5#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="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."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-AS.1.5-03"/>
        <label value="AS.1.5#03"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="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."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.1.3.5#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-AS.1.5-04"/>
        <label value="AS.1.5#04"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="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)"/>
        <derivedFrom value="EHR-S_FM_R1.1 S.1.3.5#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-AS.1.5-05"/>
        <label value="AS.1.5#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage care team membership."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-AS.1.5-06"/>
        <label value="AS.1.5#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="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."/>
      </statement>
    </Requirements>