DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 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 . Page versions: R5 R4B R4 R3 R2

1.25.2.1.361 Value Set http://hl7.org/fhir/ValueSet/assert-response-code-types

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. The response code to expect in the response.
OID:2.16.840.1.113883.4.642.2.361 (for OID based terminology systems)
System URL:http://hl7.org/fhir/assert-response-code-types
System OID:2.16.840.1.113883.4.642.1.361
Source ResourceXML / JSON

This value set is used in the following places:

1.25.2.1.361.1 Content Logical Definition

This value set has an inline code system http://hl7.org/fhir/assert-response-code-types, which defines the following codes:

CodeDisplayDefinition
okay okayResponse code is 200.
created createdResponse code is 201.
noContent noContentResponse code is 204.
notModified notModifiedResponse code is 304.
bad badResponse code is 400.
forbidden forbiddenResponse code is 403.
notFound notFoundResponse code is 404.
methodNotAllowed methodNotAllowedResponse code is 405.
conflict conflictResponse code is 409.
gone goneResponse code is 410.
preconditionFailed preconditionFailedResponse code is 412.
unprocessable unprocessableResponse 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:

LevelA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance)
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code