Package | hl7.ehrs.uv.phrsfmr2 |
Type | Requirements |
Id | PHRSFMR2-TI.2.1 |
FHIR Version | R5 |
Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-TI.2.1.html |
URL | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.2.1 |
Version | 2.0.1-ballot |
Status | active |
Date | 2025-04-03T15:15:30+00:00 |
Name | TI_2_1_Audit_Triggers |
Title | TI.2.1 Audit Triggers (Function) |
Authority | hl7 |
Description | Manage Audit Triggers |
Purpose | PHR Systems have built in audit triggers to capture key events in real-time. Audit triggers signal key: - Record management and lifecycle events; - Security events related to system and data safeguards, both routine and exceptional; - System events related to performance and operations, both routine and exceptional; - Clinical events with special log requirements. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Manage Audit Triggers
PHR Systems have built in audit triggers to capture key events in real-time. Audit triggers signal key:
TI.2.1#01 | dependent SHALL |
The system SHALL audit key events, as specified in function TI.2.1 (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law. |
TI.2.1#02 | dependent SHALL |
The system SHALL capture key Audit Metadata at each Audit Trigger, as specified in TI.2.1 (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law. |
TI.2.1#03 | dependent SHALL |
The system SHALL capture an Audit Log Entry at each Audit Trigger as specified in TI.2.1 (Audit Triggers) according to scope of practice, organizational policy, and/or jurisdictional law. |
TI.2.1#04 | SHALL |
The system SHALL capture the current master clock time to establish valid record date and time metadata. |
TI.2.1#05 | MAY |
The system MAY manage Audit Trigger logging using a common audit engine (e.g., using schema and transports such as specified in the Audit Log specification of IHE Audit Trails and Node Authentication (ATNA) Profile). |
{ "resourceType": "Requirements", "id": "PHRSFMR2-TI.2.1", "meta": { "profile": [ "http://hl7.org/ehrs/uv/phrsfmr2/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/phrsfmr2/Requirements/PHRSFMR2-TI.2.1", "version": "2.0.1-ballot", "name": "TI_2_1_Audit_Triggers", "title": "TI.2.1 Audit Triggers (Function)", "status": "active", "date": "2025-04-03T15:15:30+00:00", "publisher": "EHR WG", "contact": [ { "telecom": [ { "system": "url", "value": "http://www.hl7.org/Special/committees/ehr" } ] } ], "description": "Manage Audit Triggers", "purpose": "PHR Systems have built in audit triggers to capture key events in real-time. Audit triggers signal key:\r\n- Record management and lifecycle events;\r\n- Security events related to system and data safeguards, both routine and exceptional;\r\n- System events related to performance and operations, both routine and exceptional;\r\n- Clinical events with special log requirements.", "statement": [ { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": true } ], "key": "PHRSFMR2-TI.2.1-01", "label": "TI.2.1#01", "conformance": [ "SHALL" ], "conditionality": false, "requirement": "The system SHALL audit key events, as specified in function [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": true } ], "key": "PHRSFMR2-TI.2.1-02", "label": "TI.2.1#02", "conformance": [ "SHALL" ], "conditionality": false, "requirement": "The system SHALL capture key Audit Metadata at each Audit Trigger, as specified in [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": true } ], "key": "PHRSFMR2-TI.2.1-03", "label": "TI.2.1#03", "conformance": [ "SHALL" ], "conditionality": false, "requirement": "The system SHALL capture an Audit Log Entry at each Audit Trigger as specified in [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) according to scope of practice, organizational policy, and/or jurisdictional law." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": false } ], "key": "PHRSFMR2-TI.2.1-04", "label": "TI.2.1#04", "conformance": [ "SHALL" ], "conditionality": false, "requirement": "The system SHALL capture the current master clock time to establish valid record date and time metadata." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": false } ], "key": "PHRSFMR2-TI.2.1-05", "label": "TI.2.1#05", "conformance": [ "MAY" ], "conditionality": false, "requirement": "The system MAY manage Audit Trigger logging using a common audit engine (e.g., using schema and transports such as specified in the Audit Log specification of IHE Audit Trails and Node Authentication (ATNA) Profile)." } ] }