STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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.1.0 Value Set http://hl7.org/fhir/ValueSet/reference-handling-policy

This is a value set defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/ValueSet/reference-handling-policy
Name: ReferenceHandlingPolicy
Definition: A set of flags that defines how references are supported
Committee: FHIR Infrastructure Work Group
OID: 2.16.840.1.113883.4.642.2.0 (for OID based terminology systems)
Source Resource XML / JSON

This value set is used in the following places:

4.3.1.0.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.1.0.2 Expansion

This expansion generated 06 Dec 2016

This value set contains 5 concepts

Expansion based on http://hl7.org/fhir/reference-handling-policy version 1.8.0

All codes from system http://hl7.org/fhir/reference-handling-policy

Code Display Definition
literal Literal References The server supports and populates Literal references where they are known (this code does not guarantee that all references are literal; see 'enforced')
logical Logical References The server allows logical references
resolves Resolves References The server will attempt to resolve logical references to literal references (if resolution fails, the server may still accept resources; see logical)
enforced Reference Integrity Enforced The server enforces that references have integrity - e.g. it ensures that references can always be resolved. This is typically the case for clinical record systems, but often no the case for middleware/proxy systems
local Local References Only The server does not support references that point to other servers

 

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