This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Definition for Value SetResponseType
<ValueSet xmlns="http://hl7.org/fhir"> <id value="response-code"/> <meta> <lastUpdated value="2015-04-03T14:24:32.000+11:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid"> <valueUri value="urn:oid:2.16.840.1.113883.4.642.2.322"/> </extension> <url value="http://hl7.org/fhir/vs/response-code"/> <version value="0.5.0"/> <name value="ResponseType"/> <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"/> <status value="draft"/> <experimental value="false"/> <date value="2015-04-03T14:24:32+11:00"/> <define> <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid"> <valueUri value="urn:oid:2.16.840.1.113883.4.642.1.322"/> </extension> <system value="http://hl7.org/fhir/response-code"/> <caseSensitive value="true"/> <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 some content in it. There is no point in re-sending without change. The response narrative SHALL describe what the issue is."/> </concept> </define> </ValueSet>
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.