ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.14.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: AS.1 Manage Provider Information (Header) - XML Representation

Active as of 2024-06-01

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-AS.1"/>
  <meta>
    <profile value="http://hl7.org/ehrs/StructureDefinition/FMHeader"/>
  </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>Maintain, or provide access to, current provider information.</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>Manage the information regarding providers within and external to an organization that is required to support care provision. This information includes a registry of providers (internal to the EHR-S or external), the provider's location, on-call information, and office information. Information regarding teams or groups of providers as well as individual patient relationships with providers is necessary to support care coordination and access to patient information.
Example:
For example, a hospital's directory ought to contain the full name, specialty, credentials, address, and contact information for each provider. A directory might also manage information regarding a given provider's work assignment/allocation, expectations, and/or history (e.g., the percentage of time planned towards (or devoted to) patient care, research, teaching, administration, and/or other duties). Directory Information could also describe the type of care offered by a given care provider (e.g, cardiologist or general practitioner), health care setting (e.g., long term care facility or hospital), and categories of patient (e.g., children or geriatric patients).</p>
</div></span>
    

    

    
    <table id="statements" class="grid dict">
        
    </table>
</div>
  </text>
  <url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.1"/>
  <version value="0.14.0"/>
  <name value="AS_1_Manage_Provider_Information"/>
  <title value="AS.1 Manage Provider Information (Header)"/>
  <status value="active"/>
  <date value="2024-06-01T08:34:10+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="Maintain, or provide access to, current provider information."/>
  <purpose
           value="Manage the information regarding providers within and external to an organization that is required to support care provision. This information includes a registry of providers (internal to the EHR-S or external), the provider's location, on-call information, and office information. Information regarding teams or groups of providers as well as individual patient relationships with providers is necessary to support care coordination and access to patient information.
Example:
For example, a hospital's directory ought to contain the full name, specialty, credentials, address, and contact information for each provider. A directory might also manage information regarding a given provider's work assignment/allocation, expectations, and/or history (e.g., the percentage of time planned towards (or devoted to) patient care, research, teaching, administration, and/or other duties). Directory Information could also describe the type of care offered by a given care provider (e.g, cardiologist or general practitioner), health care setting (e.g., long term care facility or hospital), and categories of patient (e.g., children or geriatric patients)."/>
</Requirements>