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.9 Manage Administrative Transaction Processing (Header) - JSON Representation

Active as of 2024-06-01

Raw json | Download

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-AS.9",
  "meta" : {
    "profile" : [
      🔗 "http://hl7.org/ehrs/StructureDefinition/FMHeader"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n    <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>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.</p>\n</div></span>\n\n    \n    <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>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>\n<p>The EHR system collects patient health-related information needed for purpose of administrative and financial activities including reimbursement.</p>\n<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>\n<p>Clinically automated revenue cycle - examples of reduced denials and error rates in claims.</p>\n<p>Clinical information needed for billing is available on the date of service.</p>\n<p>Physician and clinical teams do not perform additional data entry / tasks exclusively to support administrative or financial processes.</p>\n</div></span>\n    \n\n    \n\n    \n    <table id=\"statements\" class=\"grid dict\">\n        \n    </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.9",
  "version" : "0.14.0",
  "name" : "AS_9_Manage_Administrative_Transaction_Processing",
  "title" : "AS.9 Manage Administrative Transaction Processing (Header)",
  "status" : "active",
  "date" : "2024-06-01T08:34:10+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "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.",
  "purpose" : "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.\n\nThe EHR system collects patient health-related information needed for purpose of administrative and financial activities including reimbursement.\n\nCaptures 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.\n\nClinically automated revenue cycle - examples of reduced denials and error rates in claims.\n\nClinical information needed for billing is available on the date of service.\n\nPhysician and clinical teams do not perform additional data entry / tasks exclusively to support administrative or financial processes."
}