<?xml version="1.0" encoding="UTF-8"?>

<Requirements xmlns="http://hl7.org/fhir">
  <id value="DHFPR2-AS.9"/>
  <meta>
    <profile value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMHeader"/>
  </meta>
  <language value="en"/>
  <text>
    <status value="extensions"/><div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
    
             
    
    
    <div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>Support the creation (including using external data sources, if necessary), electronic interchange, and processing of transactions listed below that may be necessary for administrative management during an episode of care.</p>
<p>The EHR system collects patient health-related information needed for purpose of administrative and financial activities including reimbursement.</p>
<p>Captures the episode and encounter information to pass to administrative or financial processes (e.g., triggers transmissions of charge transactions as by-product of on-line interaction including order entry, order statusing, result entry, documentation entry, medication administration charting).Automatically retrieves information needed to verify coverage and medical necessity. As a byproduct of care delivery and documentation captures and presents all patient information needed to support coding. Ideally performs coding based on documentation.</p>
<p>Clinically automated revenue cycle - examples of reduced denials and error rates in claims.</p>
<p>Clinical information needed for billing is available on the date of service.</p>
<p>Physician and clinical teams do not perform additional data entry / tasks exclusively to support administrative or financial processes.</p>
</div></div>
    
    
    
    <table id="statements" class="grid dict">
        
    </table>
</div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="informative"/>
  </extension>
  <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
    <valueCode value="NC"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="ehr"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical value="http://hl7.org/ehrs/us/dhfpr2/ImplementationGuide/hl7.ehrs.us.dhfpr2"/>
      </extension>
    </valueInteger>
  </extension>
  <url value="http://hl7.org/ehrs/us/dhfpr2/Requirements/DHFPR2-AS.9"/>
  <version value="2.0.0-ballot"/>
  <name value="AS_9_Manage_Administrative_Transaction_Processing"/>
  <title value="AS.9 Manage Administrative Transaction Processing (Header)"/>
  <status value="active"/>
  <date value="2025-12-19T08:44:27+00: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="Support the creation (including using external data sources, if necessary), electronic interchange, and processing of transactions listed below that may be necessary foradministrative management during an episode of care."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="US"/>
    </coding>
  </jurisdiction>
  <purpose value="Support the creation (including using external data sources, if necessary), electronic interchange, and processing of transactions listed below that may be necessary for administrative management during an episode of care.&#xA;&#xA;The EHR system collects patient health-related information needed for purpose of administrative and financial activities including reimbursement.&#xA;&#xA;Captures the episode and encounter information to pass to administrative or financial processes (e.g., triggers transmissions of charge transactions as by-product of on-line interaction including order entry, order statusing, result entry, documentation entry, medication administration charting).Automatically retrieves information needed to verify coverage and medical necessity. As a byproduct of care delivery and documentation captures and presents all patient information needed to support coding. Ideally performs coding based on documentation.&#xA;&#xA;Clinically automated revenue cycle - examples of reduced denials and error rates in claims.&#xA;&#xA;Clinical information needed for billing is available on the date of service.&#xA;&#xA;Physician and clinical teams do not perform additional data entry / tasks exclusively to support administrative or financial processes."/>
  <derivedFrom value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.9"/>
</Requirements>