FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Page standards status: Informative | Maturity Level: 4 |
{
"resourceType" : "CodeSystem",
"id" : "response-code",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <p>This code system \n <code>http://hl7.org/fhir/response-code</code> defines the following codes:\n </p>\n <table class=\"codes\">\n <tr>\n <td style=\"white-space:nowrap\">\n <b>Code</b>\n </td>\n <td>\n <b>Display</b>\n </td>\n <td>\n <b>Definition</b>\n </td>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">ok\n <a name=\"response-code-ok\"> </a>\n </td>\n <td>OK</td>\n <td>The message was accepted and processed without error.</td>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">transient-error\n <a name=\"response-code-transient-error\"> </a>\n </td>\n <td>Transient Error</td>\n <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>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">fatal-error\n <a name=\"response-code-fatal-error\"> </a>\n </td>\n <td>Fatal Error</td>\n <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>\n </tr>\n </table>\n </div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "informative"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 4
},
{
"extension" : [
{
"url" : "packageId",
"valueId" : "hl7.fhir.uv.xver-r5.r4"
},
{
"url" : "version",
"valueString" : "0.0.1-snapshot-2"
}
],
"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" : "5.0.0",
"name" : "ResponseType",
"title" : "Response Type",
"status" : "active",
"experimental" : false,
"date" : "2021-01-05T09:01:24+10: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|4.0.1",
"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."
}
]
}