Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: CPS.2.7 Support Patient Data Derived from Eligibility, Formulary and Benefit Documentation for Electronic Prescribing (Function) - XML Representation

Active as of 2024-08-12

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-CPS.2.7"/>
  <meta>
    <profile value="http://hl7.org/ehrs/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>Capture and explicitly label patient data derived from eligibility, formulary and benefit information; and link the data source with that data.</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>Sources of eligibility, formulary and benefit may provide data for entry into the electronic prescribing or be given a mechanism for entering this data directly. The data must be explicitly labeled as derived from eligibility, formulary and benefit information. Patient data that is derived from eligibility, formulary and benefit data may be provided by:</p>
<ul>
<li>a provider</li>
<li>a payer, or</li>
<li>entities that transmit or process eligibility, formulary and benefit data</li>
</ul>
</div></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>CPS.2.7#01</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 manage patient data derived from eligibility, formulary and benefit information.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>CPS.2.7#02</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 capture the source of patient data derived from eligibility, formulary and benefit information.</p>
</div></span>
                
                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.2.7"/>
  <version value="0.16.0"/>
  <name
        value="CPS_2_7_Support_Patient_Data_Derived_from_Eligibility__Formulary_and_Benefit_Documentation_for_Electronic_Prescribing"/>
  <title
         value="CPS.2.7 Support Patient Data Derived from Eligibility, Formulary and Benefit Documentation for Electronic Prescribing (Function)"/>
  <status value="active"/>
  <date value="2024-08-12T10:56:01+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="Capture and explicitly label patient data derived from eligibility, formulary and benefit information; and link the data source with that data."/>
  <purpose
           value="Sources of eligibility, formulary and benefit may provide data for entry into the electronic prescribing or be given a mechanism for entering this data directly. The data must be explicitly labeled as derived from eligibility, formulary and benefit information. Patient data that is derived from eligibility, formulary and benefit data may be provided by: 
- a provider 
- a payer, or 
- entities that transmit or process eligibility, formulary and benefit data"/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-CPS.2.7-01"/>
    <label value="CPS.2.7#01"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the ability to manage patient data derived from eligibility, formulary and benefit information."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-CPS.2.7-02"/>
    <label value="CPS.2.7#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to capture the source of patient data derived from eligibility, formulary and benefit information."/>
  </statement>
</Requirements>