This page is part of the FHIR Specification (v3.2.0: R4 Ballot 1). 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: R5 R4B R4 R3
Vocabulary Work Group | Maturity Level: N/A | Ballot Status: Informative |
Definition for Code System ResponseType
<CodeSystem xmlns="http://hl7.org/fhir"> <id value="response-code"/> <meta> <lastUpdated value="2017-12-20T15:52:34.818+11:00"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> ResponseType</h2> <div> <p> The kind of response to a message</p> </div> <p> This code system http://hl7.org/fhir/response-code defines the following codes:</p> <table class="codes"> <tr> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td style="white-space:nowrap">ok <a name="response-code-ok"> </a> </td> <td> OK</td> <td> The message was accepted and processed without error.</td> </tr> <tr> <td style="white-space:nowrap">transient-error <a name="response-code-transient-error"> </a> </td> <td> Transient Error</td> <td> Some internal unexpected error occurred - wait and try again. Note - this is usually used for things like database unavailable, which may be expected to resolve, though human intervention may be required.</td> </tr> <tr> <td style="white-space:nowrap">fatal-error <a name="response-code-fatal-error"> </a> </td> <td> Fatal Error</td> <td> The message was rejected because of a problem with the content. There is no point in re-sending without change. The response narrative SHALL describe the issue.</td> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="inm"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status"> <valueString value="Trial Use"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="3"/> </extension> <url value="http://hl7.org/fhir/response-code"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.1.381"/> </identifier> <version value="3.2.0"/> <name value="ResponseType"/> <status value="draft"/> <experimental value="false"/> <date value="2017-12-20T15:52:34+11:00"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <description value="The kind of response to a message"/> <caseSensitive value="true"/> <valueSet value="http://hl7.org/fhir/ValueSet/response-code"/> <content value="complete"/> <concept> <code value="ok"/> <display value="OK"/> <definition value="The message was accepted and processed without error."/> </concept> <concept> <code value="transient-error"/> <display value="Transient Error"/> <definition value="Some internal unexpected error occurred - wait and try again. Note - this is usually used for things like database unavailable, which may be expected to resolve, though human intervention may be required."/> </concept> <concept> <code value="fatal-error"/> <display value="Fatal Error"/> <definition value="The message was rejected because of a problem with the content. There is no point in re-sending without change. The response narrative SHALL describe the issue."/> </concept> </CodeSystem>
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.