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

FHIR IG Statistics: Requirements/EHRSFMR2-TI.2.1.4

Packagehl7.ehrs.uv.ehrsfmr2
TypeRequirements
IdEHRSFMR2-TI.2.1.4
FHIR VersionR5
Sourcehttp://hl7.org/ehrs/uv/ehrsfmr2/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2-TI.2.1.4.html
URLhttp://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-TI.2.1.4
Version2.1.1-ballot
Statusactive
Date2025-05-13T15:11:00+00:00
NameTI_2_1_4_Clinical_Audit_Triggers
TitleTI.2.1.4 Clinical Audit Triggers (Function)
Realmuv
Authorityhl7
DescriptionManage Clinical Audit Triggers
PurposeClinical Audit Triggers are designed to capture certain clinical events, both routine and exceptional, including key metadata (who, what, when, where, why).

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:

Manage Clinical Audit Triggers

Description I:

Clinical Audit Triggers are designed to capture certain clinical events, both routine and exceptional, including key metadata (who, what, when, where, why).

Actors:
ehr
Criteria N:
TI.2.1.4#01 SHALL

The system SHALL provide the ability to track all clinical alerts.

TI.2.1.4#02 SHALL

The system SHALL provide the ability to track all acknowledgements of clinically-significant report changes.

TI.2.1.4#03 SHOULD

The system SHOULD provide the ability to track when decision support alerts have been disabled.


Source

{
  "resourceType": "Requirements",
  "id": "EHRSFMR2-TI.2.1.4",
  "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-TI.2.1.4",
  "version": "2.1.1-ballot",
  "name": "TI_2_1_4_Clinical_Audit_Triggers",
  "title": "TI.2.1.4 Clinical Audit Triggers (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": "Manage Clinical Audit Triggers",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "purpose": "Clinical Audit Triggers are designed to capture certain clinical events, both routine and exceptional, including key metadata (who, what, when, where, why).",
  "statement": [
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-TI.2.1.4-01",
      "label": "TI.2.1.4#01",
      "conformance": [
        "SHALL"
      ],
      "conditionality": false,
      "requirement": "The system SHALL provide the ability to track all clinical alerts."
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-TI.2.1.4-02",
      "label": "TI.2.1.4#02",
      "conformance": [
        "SHALL"
      ],
      "conditionality": false,
      "requirement": "The system SHALL provide the ability to track all acknowledgements of clinically-significant report changes."
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-TI.2.1.4-03",
      "label": "TI.2.1.4#03",
      "conformance": [
        "SHOULD"
      ],
      "conditionality": false,
      "requirement": "The system SHOULD provide the ability to track when decision support alerts have been disabled."
    }
  ]
}