This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3
A code identifying the specific message to be provided. Discussion: A textual value may be specified as the print name, or for non-coded messages, as the original text. Examples: 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'
{ "resourceType": "CodeSystem", "id": "v3-AcknowledgementDetailType", "meta": { "lastUpdated": "2016-11-11T00:00:00.000+11:00" }, "text": { "status": "generated", "div": "<div>!-- Snipped for Brevity --></div>" }, "url": "http://hl7.org/fhir/v3/AcknowledgementDetailType", "identifier": { "system": "urn:ietf:rfc:3986", "value": "urn:oid:2.16.840.1.113883.5.1082" }, "version": "2016-11-11", "name": "v3 Code System AcknowledgementDetailType", "status": "active", "experimental": false, "publisher": "HL7, Inc", "contact": [ { "telecom": [ { "system": "url", "value": "http://hl7.org" } ] } ], "date": "2016-11-11T00:00:00+11:00", "description": " A code identifying the specific message to be provided. Discussion:\r\nA textual value may be specified as the print name, or for non-coded messages, as the original text. Examples:\r\n'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'", "caseSensitive": true, "valueSet": "http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailType", "hierarchyMeaning": "is-a", "content": "complete", "property": [ { "code": "inactive", "uri": "http://hl7.org/fhir/concept-properties#inactive", "description": "True if the concept is not considered active - e.g. not a valid concept any more", "type": "boolean" } ], "concept": [ { "code": "E", "display": "Error", "definition": "Definition:An issue which has prevented, or will prevent (unless a management is provided for the issue by the sender), the successful processing of an interaction. Response interactions which include an issue which is an Error are a 'rejection', indicating that the request was not successfully processed. \r\n\n \n Example:Unable to find specified patient." }, { "code": "I", "display": "Information", "definition": "Definition: The message relates to an issue which has no bearing on the successful processing of the request. Information issues cannot be overridden by specifying a management.\r\n\n \n Example: A Patient's coverage will expire in 5 days." }, { "code": "W", "display": "Warning", "definition": "Definition: The message relates to an issue which cannot prevent the successful processing of a request, but which could result in the processing not having the ideal or intended effect. Managing a warning issue is not required for successful processing, but will suppress the warning from being raised. \r\n\n \n Example:\n \r\n\n Unexpected additional repetitions of phone number have been ignored." }, { "code": "ERR", "property": [ { "code": "inactive", "valueBoolean": true } ] }, { "code": "INFO", "property": [ { "code": "inactive", "valueBoolean": true } ] }, { "code": "WARN", "property": [ { "code": "inactive", "valueBoolean": true } ] } ] }
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.