This page is part of the FHIR Specification (v4.4.0: R5 Preview #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Security Work Group | Maturity Level: 3 | Trial Use | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/audit-event-severity |
Version: | 4.4.0 |
Name: | AuditEventSeverity |
Title: | AuditEventSeverity |
Definition: | The severity of the audit entry. |
Committee: | Security Work Group |
OID: | 2.16.840.1.113883.4.642.3.1466 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
http://hl7.org/fhir/audit-event-severity
This expansion generated 03 May 2020
This value set contains 8 concepts
Expansion based on AuditEventSeverity v4.4.0 (CodeSystem)
All codes from system http://hl7.org/fhir/audit-event-severity
Code | Display | Logical Definition (CLD) |
Emergency | Emergency | System is unusable. |
Alert | Alert | Action must be taken immediately. |
Critical | Critical | Critical conditions. |
Error | Error | Error conditions. |
Warning | Warning | Warning conditions. |
Notice | Notice | Normal but significant condition. |
Informational | Informational | Informational messages. |
Debug | Debug | Debug-level messages. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |