This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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
FHIR Infrastructure Work Group | Maturity Level: N | Normative (from v4.0.0) | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/discriminator-type |
Version: | 4.2.0 |
Name: | DiscriminatorType |
Title: | DiscriminatorType |
Definition: | How an element value is interpreted when discrimination is evaluated. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.3.91 (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:
http://hl7.org/fhir/discriminator-type
This expansion generated 31 Dec 2019
This value set contains 5 concepts
Expansion based on http://hl7.org/fhir/discriminator-type version 4.2.0
All codes from system http://hl7.org/fhir/discriminator-type
Code | Display | Definition |
value | Value | The slices have different values in the nominated element. |
exists | Exists | The slices are differentiated by the presence or absence of the nominated element. |
pattern | Pattern | The slices have different values in the nominated element, as determined by testing them against the applicable ElementDefinition.pattern[x]. |
type | Type | The slices are differentiated by type of the nominated element. |
profile | Profile | The slices are differentiated by conformance of the nominated element to a specified profile. Note that if the path specifies .resolve() then the profile is the target profile on the reference. In this case, validation by the possible profiles is required to differentiate the slices. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |