Snapshot 3: Connectathon 32 Base

This page is part of the FHIR Specification (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.4.1.278 ValueSet http://hl7.org/fhir/ValueSet/audit-event-severity

Security icon Work Group Maturity Level: 3Trial Use Use Context: Country: World, Country: World
Official URL: http://hl7.org/fhir/ValueSet/audit-event-severity Version: 5.0.0-snapshot3
draft as of 2020-12-28 Computable Name: AuditEventSeverity
Flags: Immutable OID: 2.16.840.1.113883.4.642.3.2980

This value set is used in the following places:

The severity of the audit entry.


 

This expansion generated 14 Dec 2022


This value set contains 8 concepts

Expansion based on AuditEventSeverity v5.0.0-snapshot3 (CodeSystem)

CodeSystemDisplayDefinition
  emergencyhttp://hl7.org/fhir/audit-event-severityEmergency

System is unusable. e.g., This level should only be reported by infrastructure and should not be used by applications.

  alerthttp://hl7.org/fhir/audit-event-severityAlert

Notification should be sent to trigger action be taken. e.g., Loss of the primary network connection needing attention.

  criticalhttp://hl7.org/fhir/audit-event-severityCritical

Critical conditions. e.g., A failure in the system's primary application that will reset automatically.

  errorhttp://hl7.org/fhir/audit-event-severityError

Error conditions. e.g., An application has exceeded its file storage limit and attempts to write are failing.

  warninghttp://hl7.org/fhir/audit-event-severityWarning

Warning conditions. May indicate that an error will occur if action is not taken. e.g., A non-root file system has only 2GB remaining.

  noticehttp://hl7.org/fhir/audit-event-severityNotice

Notice messages. Normal but significant condition. Events that are unusual, but not error conditions.

  informationalhttp://hl7.org/fhir/audit-event-severityInformational

Normal operational messages that require no action. e.g., An application has started, paused, or ended successfully.

  debughttp://hl7.org/fhir/audit-event-severityDebug

Debug-level messages. Information useful to developers for debugging the application.

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

LvlA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code