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

FHIR IG Statistics: Requirements/EHRSFMR2-AS.7.2

Packagehl7.ehrs.uv.ehrsfmr2
TypeRequirements
IdEHRSFMR2-AS.7.2
FHIR VersionR5
Sourcehttp://hl7.org/ehrs/uv/ehrsfmr2/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2-AS.7.2.html
URLhttp://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.7.2
Version2.1.1-ballot
Statusactive
Date2025-05-13T15:11:00+00:00
NameAS_7_2_Support_Encounter_Documentation
TitleAS.7.2 Support Encounter Documentation (Function)
Realmuv
Authorityhl7
DescriptionProvide assistance in assembling data, supporting data collection and processing output from a specific encounter.
PurposeWorkflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry.

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:

Provide assistance in assembling data, supporting data collection and processing output from a specific encounter.

Description I:

Workflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry.

Actors:
ehr
Criteria N:
AS.7.2#01 SHOULD

The system SHOULD determine and render workflow support for data collection in a care setting.

AS.7.2#02 SHOULD

The system SHOULD provide the ability to capture and maintain encounter and care setting specific data entry workflows.

AS.7.2#03 SHOULD

The system SHOULD provide the ability to extract information from the patient record as necessary to support documentation of the patient encounter.

AS.7.2#04 SHOULD

The system SHOULD capture and maintain a reduced set of diagnostic and procedure codes for the care setting.

AS.7.2#05 MAY

The system MAY analyze the information entered into the encounter and, based on business rules, initiate secondary reporting workflows.


Source

{
  "resourceType": "Requirements",
  "id": "EHRSFMR2-AS.7.2",
  "meta": {
    "profile": [
      "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"
    ]
  },
  "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.7.2",
  "version": "2.1.1-ballot",
  "name": "AS_7_2_Support_Encounter_Documentation",
  "title": "AS.7.2 Support Encounter Documentation (Function)",
  "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": "Provide assistance in assembling data, supporting data collection and processing output from a specific encounter.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "purpose": "Workflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry.",
  "statement": [
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-AS.7.2-01",
      "label": "AS.7.2#01",
      "conformance": [
        "SHOULD"
      ],
      "conditionality": false,
      "requirement": "The system SHOULD determine and render workflow support for data collection in a care setting.",
      "derivedFrom": "EHR-S_FM_R1.1 S.3.1.2#1"
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-AS.7.2-02",
      "label": "AS.7.2#02",
      "conformance": [
        "SHOULD"
      ],
      "conditionality": false,
      "requirement": "The system SHOULD provide the ability to capture and maintain encounter and care setting specific data entry workflows.",
      "derivedFrom": "EHR-S_FM_R1.1 S.3.1.2#2"
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-AS.7.2-03",
      "label": "AS.7.2#03",
      "conformance": [
        "SHOULD"
      ],
      "conditionality": false,
      "requirement": "The system SHOULD provide the ability to extract information from the patient record as necessary to support documentation of the patient encounter.",
      "derivedFrom": "EHR-S_FM_R1.1 S.3.1.2#3"
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-AS.7.2-04",
      "label": "AS.7.2#04",
      "conformance": [
        "SHOULD"
      ],
      "conditionality": false,
      "requirement": "The system SHOULD capture and maintain a reduced set of diagnostic and procedure codes for the care setting.",
      "derivedFrom": "EHR-S_FM_R1.1 S.3.1.2#4"
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-AS.7.2-05",
      "label": "AS.7.2#05",
      "conformance": [
        "MAY"
      ],
      "conditionality": false,
      "requirement": "The system MAY analyze the information entered into the encounter and, based on business rules, initiate secondary reporting workflows.",
      "derivedFrom": "EHR-S_FM_R1.1 S.3.1.2#5"
    }
  ]
}