This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). 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 R2
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/assert-response-code-types |
Name: | AssertionResponseTypes |
Definition: | The type of response code to use for assertion. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.2.361 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
This expansion generated 11 Aug 2016
This value set contains 12 concepts
All codes from system http://hl7.org/fhir/assert-response-code-types
Code | Display | Definition |
okay | okay | Response code is 200. |
created | created | Response code is 201. |
noContent | noContent | Response code is 204. |
notModified | notModified | Response code is 304. |
bad | bad | Response code is 400. |
forbidden | forbidden | Response code is 403. |
notFound | notFound | Response code is 404. |
methodNotAllowed | methodNotAllowed | Response code is 405. |
conflict | conflict | Response code is 409. |
gone | gone | Response code is 410. |
preconditionFailed | preconditionFailed | Response code is 412. |
unprocessable | unprocessable | Response code is 422. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |