FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions
Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-audit-event-severity-for-R4 | Version: 0.0.1-snapshot-2 | |||
Standards status: Informative | Maturity Level: 4 | Responsible: Security | Computable Name: R5_audit_event_severity_for_R4 |
This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/audit-event-severity | 5.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4. |
References
http://hl7.org/fhir/audit-event-severity
version 5.0.0
Code | Display | Definition |
emergency | Emergency | System is unusable. e.g., This level should only be reported by infrastructure and should not be used by applications. |
alert | Alert | Notification should be sent to trigger action be taken. e.g., Loss of the primary network connection needing attention. |
critical | Critical | Critical conditions. e.g., A failure in the system's primary application that will reset automatically. |
error | Error | Error conditions. e.g., An application has exceeded its file storage limit and attempts to write are failing. |
warning | Warning | 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. |
notice | Notice | Notice messages. Normal but significant condition. Events that are unusual, but not error conditions. |
informational | Informational | Normal operational messages that require no action. e.g., An application has started, paused, or ended successfully. |
debug | Debug | Debug-level messages. Information useful to developers for debugging the application. |
This value set expansion contains 8 concepts.
Code | System | Display | Definition |
emergency | http://hl7.org/fhir/audit-event-severity | Emergency | System is unusable. e.g., This level should only be reported by infrastructure and should not be used by applications. |
alert | http://hl7.org/fhir/audit-event-severity | Alert | Notification should be sent to trigger action be taken. e.g., Loss of the primary network connection needing attention. |
critical | http://hl7.org/fhir/audit-event-severity | Critical | Critical conditions. e.g., A failure in the system's primary application that will reset automatically. |
error | http://hl7.org/fhir/audit-event-severity | Error | Error conditions. e.g., An application has exceeded its file storage limit and attempts to write are failing. |
warning | http://hl7.org/fhir/audit-event-severity | Warning | 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. |
notice | http://hl7.org/fhir/audit-event-severity | Notice | Notice messages. Normal but significant condition. Events that are unusual, but not error conditions. |
informational | http://hl7.org/fhir/audit-event-severity | Informational | Normal operational messages that require no action. e.g., An application has started, paused, or ended successfully. |
debug | http://hl7.org/fhir/audit-event-severity | Debug | Debug-level messages. Information useful to developers for debugging the application. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | 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) |
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 |