Release 5 Preview #3

This page is part of the FHIR Specification (v4.5.0: R5 Preview #3). 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

4.3.16.228 Code System http://hl7.org/fhir/assert-response-code-types

FHIR Infrastructure Work Group Maturity Level: 2Trial Use Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/assert-response-code-types
Version:4.5.0
Name:AssertionResponseTypes
Title:AssertionResponseTypes
Definition:

The type of response code to use for assertion.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.1.711 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

4.3.16.228.1 Content

This code system http://hl7.org/fhir/assert-response-code-types 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 code systems 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. See Code System for further information.
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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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