Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-audit-event-severity-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 4 | Responsible: Security | Computable Name: R5AuditEventSeverityForR4 | |
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/audit-event-severity|5.0.0 for use in FHIR R4.
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/audit-event-severity|5.0.0 as defined in FHIR R5
in FHIR R4.
The source value set is bound to the following FHIR R5 elements:
AuditEvent.severityNote that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
FHIR ValueSet http://hl7.org/fhir/ValueSet/audit-event-severity|5.0.0, defined in FHIR R5 does not have any mapping to FHIR R4
References
http://hl7.org/fhir/audit-event-severity version 📍5.0.0| Code | Display | Definition |
| 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. |
| debug | Debug | Debug-level messages. Information useful to developers for debugging the application. |
| emergency | Emergency | System is unusable. e.g., This level should only be reported by infrastructure and should not be used by applications. |
| error | Error | Error conditions. e.g., An application has exceeded its file storage limit and attempts to write are failing. |
| informational | Informational | Normal operational messages that require no action. e.g., An application has started, paused, or ended successfully. |
| notice | Notice | Notice messages. Normal but significant condition. Events that are unusual, but not error conditions. |
| 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. |
This value set expansion contains 8 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/audit-event-severity | 5.0.0 | alert | Alert | Notification should be sent to trigger action be taken. e.g., Loss of the primary network connection needing attention. | ||
http://hl7.org/fhir/audit-event-severity | 5.0.0 | critical | Critical | Critical conditions. e.g., A failure in the system's primary application that will reset automatically. | ||
http://hl7.org/fhir/audit-event-severity | 5.0.0 | debug | Debug | Debug-level messages. Information useful to developers for debugging the application. | ||
http://hl7.org/fhir/audit-event-severity | 5.0.0 | emergency | Emergency | System is unusable. e.g., This level should only be reported by infrastructure and should not be used by applications. | ||
http://hl7.org/fhir/audit-event-severity | 5.0.0 | error | Error | Error conditions. e.g., An application has exceeded its file storage limit and attempts to write are failing. | ||
http://hl7.org/fhir/audit-event-severity | 5.0.0 | informational | Informational | Normal operational messages that require no action. e.g., An application has started, paused, or ended successfully. | ||
http://hl7.org/fhir/audit-event-severity | 5.0.0 | notice | Notice | Notice messages. Normal but significant condition. Events that are unusual, but not error conditions. | ||
http://hl7.org/fhir/audit-event-severity | 5.0.0 | 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. |
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 |