caseSensitivecompositionalcontentcopyrightdatedescriptionexperimentalhierarchyMeaningjurisdictionnamepublisherpurposestatustitleurlversionversionNeeded| Warning | CodeSystem.property.where(code='status').uri | Changed value for uri: 'http://terminology.hl7.org/CodeSystem/utg-concept-properties#status' vs 'http://hl7.org/fhir/concept-properties#status' |
| Warning | CodeSystem.property.where(code='status').description | Changed value for description: 'Status of the concept' vs 'A code that indicates the status of the concept' |
| Name | Value | Comments | |
|---|---|---|---|
| caseSensitive | true | ||
| compositional | false | ||
| content | complete | ||
| copyright | This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html | ||
| date | 2019-12-01 | ||
| description | HL7-defined code system of concepts specifying the severity of an application error as reported during acknowledgment of messages. Knowing if something is Error, Warning or Information is intrinsic to how an application handles the content and the information flow. Used in HL7 Version 2.x messaging acknowledgment in the ERR segment. | ||
| experimental | false | ||
| hierarchyMeaning | is-a | ||
| jurisdiction | |||
| name | ErrorSeverity | ||
| publisher | Health Level Seven International | ||
| purpose | Underlying Master Code System for V2 table 0516 (Error Severity) | ||
| status | active | ||
| title | errorSeverity | ||
| url | http://terminology.hl7.org/CodeSystem/v2-0516 | ||
| version | 2.0.0 | ||
| versionNeeded | false | ||
| Code | Display | status | deprecated | v2-concComment | v2-concCommentAsPub | status | deprecated | v2-concComment | v2-concCommentAsPub | v2-table-deprecated | Comments | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| W | Warning | A | active | Use this severity when parts of the message may not have been stored. | Use this severity when parts of the message may not have been stored. | Transaction successful, but there may issues | Transaction successful, but there may issues | A | active | Use this severity when parts of the message may not have been stored. | Use this severity when parts of the message may not have been stored. | Transaction successful, but there may issues | Transaction successful, but there may issues | ||||||||
| I | Information | A | active | e.g., inform patient | e.g., inform patient | Transaction was successful but includes information e.g., inform patient | Transaction was successful but includes information e.g., inform patient | A | active | e.g., inform patient | e.g., inform patient | Transaction was successful but includes information e.g., inform patient | Transaction was successful but includes information e.g., inform patient | ||||||||
| E | Error | A | active | Transaction was unsuccessful | Transaction was unsuccessful | A | active | Transaction was unsuccessful | Transaction was unsuccessful | ||||||||||||
| F | Fatal Error | A | active | Message not processed due to application or network failure condition | Message not processed due to application or network failure condition | A | active | Message not processed due to application or network failure condition | Message not processed due to application or network failure condition | ||||||||||||