{"resourceType":"CodeSystem","id":"response-code","text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: CodeSystem response-code</b></p><a name=\"response-code\"> </a><a name=\"hcresponse-code\"> </a><p>This case-sensitive code system <code>http://hl7.org/fhir/response-code</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>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":4},{"extension":[{"url":"packageId","valueId":"hl7.fhir.uv.xver-r4.r5"},{"url":"version","valueString":"0.1.0"},{"url":"uri","valueUri":"http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5"}],"url":"http://hl7.org/fhir/StructureDefinition/package-source"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-wg","valueCode":"inm"}],"url":"http://hl7.org/fhir/response-code","version":"4.0.1","name":"ResponseType","title":"ResponseType","status":"draft","experimental":false,"date":"2019-10-31T17:29:23-05:00","publisher":"Infrastructure And Messaging","contact":[{"name":"Infrastructure And Messaging","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/inm"}]}],"description":"The kind of response to a message.","jurisdiction":[{"coding":[{"system":"http://unstats.un.org/unsd/methods/m49/m49.htm","code":"001","display":"World"}]}],"caseSensitive":true,"valueSet":"http://hl7.org/fhir/ValueSet/response-code|5.0.0","content":"complete","concept":[{"code":"ok","display":"OK","definition":"The message was accepted and processed without error."},{"code":"transient-error","display":"Transient Error","definition":"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."},{"code":"fatal-error","display":"Fatal Error","definition":"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."}]}