FHIR IG analytics| Package | hl7.fhir.uv.xver-r4.r4b |
| Resource Type | CodeSystem |
| Id | CodeSystem-response-code.json |
| FHIR Version | R4B |
| Source | http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/CodeSystem-response-code.html |
| URL | http://hl7.org/fhir/response-code |
| Version | 4.0.1 |
| Status | draft |
| Date | 2019-11-01T08:29:23+10:00 |
| Name | ResponseType |
| Title | ResponseType |
| Realm | uv |
| Authority | hl7 |
| Description | The kind of response to a message. |
| Content | complete |
| ConceptMap | |
| twcdc-responsetype | 系統回應訊息種類對應 |
| ValueSet | |
| R4-response-code-for-R4B | Cross-version VS for R4.ResponseType for use in FHIR R4B |
| R2-response-code-for-R4B | Cross-version VS for R2.ResponseType for use in FHIR R4B |
| R3-response-code-for-R4B | Cross-version VS for R3.ResponseType for use in FHIR R4B |
| R4-response-code-for-R5 | Cross-version VS for R4.ResponseType for use in FHIR R5 |
| R2-response-code-for-R5 | Cross-version VS for R2.ResponseType for use in FHIR R5 |
| R3-response-code-for-R5 | Cross-version VS for R3.ResponseType for use in FHIR R5 |
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: CodeSystem response-code
This case-sensitive code system http://hl7.org/fhir/response-code defines the following codes:
FHIR
FHIRsmith{
"resourceType": "CodeSystem",
"id": "response-code",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"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.r4b"
},
{
"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": "4.0.1",
"name": "ResponseType",
"title": "ResponseType",
"status": "draft",
"experimental": false,
"date": "2019-11-01T08:29:23+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.3.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."
}
]
}