FHIR © HL7.org  |  Server Home  |  XIG Home  |  Server Source  |  FHIR  

FHIR IG Statistics: Requirements/EHRSFMR2-AS.9

Packagehl7.ehrs.uv.ehrsfmr2
TypeRequirements
IdEHRSFMR2-AS.9
FHIR VersionR5
Sourcehttp://hl7.org/ehrs/uv/ehrsfmr2/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2-AS.9.html
URLhttp://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.9
Version2.1.1-ballot
Statusactive
Date2025-05-13T15:11:00+00:00
NameAS_9_Manage_Administrative_Transaction_Processing
TitleAS.9 Manage Administrative Transaction Processing (Header)
Realmuv
Authorityhl7
DescriptionSupport 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.
PurposeSupport 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. The EHR system collects patient health-related information needed for purpose of administrative and financial activities including reimbursement. 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. Clinically automated revenue cycle - examples of reduced denials and error rates in claims. Clinical information needed for billing is available on the date of service. Physician and clinical teams do not perform additional data entry / tasks exclusively to support administrative or financial processes.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Statement N:

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.

Description I:

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.

The EHR system collects patient health-related information needed for purpose of administrative and financial activities including reimbursement.

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.

Clinically automated revenue cycle - examples of reduced denials and error rates in claims.

Clinical information needed for billing is available on the date of service.

Physician and clinical teams do not perform additional data entry / tasks exclusively to support administrative or financial processes.

Actors:
ehr

Source

{
  "resourceType": "Requirements",
  "id": "EHRSFMR2-AS.9",
  "meta": {
    "profile": [
      "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMHeader"
    ]
  },
  "text": {
    "status": "extensions",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "ehr"
    }
  ],
  "url": "http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.9",
  "version": "2.1.1-ballot",
  "name": "AS_9_Manage_Administrative_Transaction_Processing",
  "title": "AS.9 Manage Administrative Transaction Processing (Header)",
  "status": "active",
  "date": "2025-05-13T15:11:00+00:00",
  "publisher": "HL7 International / Electronic Health Records",
  "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.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "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."
}