This page is part of the FHIR Specification v6.0.0-ballot1: Release 6 Ballot (1st Draft) (see Ballot Notes). The current version is 5.0.0. For a full list of available versions, see the Directory of published versions
FHIR Infrastructure Work Group | Maturity Level: 2 | Trial Use | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/subscriptiontopic-cr-behavior
|
Version: 6.0.0-ballot1 | |||
draft as of 2020-12-28 | Computable Name: CriteriaNotExistsBehavior | |||
Flags: Immutable | OID: 2.16.840.1.113883.4.642.3.3174 |
This value set is used in the following places:
Behavior a server can exhibit when a criteria state does not exist (e.g., state prior to a create or after a delete).
http://hl7.org/fhir/subscriptiontopic-cr-behavior
This expansion generated 18 Dec 2023
Expansion based on codesystem Criteria Not Exists Behavior v6.0.0-ballot1 (CodeSystem)
This value set contains 2 concepts
Code | System | Display | Definition |
test-passes | http://hl7.org/fhir/subscriptiontopic-cr-behavior | Test passes | The requested conditional statement will pass if a matching state does not exist (e.g., previous state during create). |
test-fails | http://hl7.org/fhir/subscriptiontopic-cr-behavior | Test fails | The requested conditional statement will fail if a matching state does not exist (e.g., previous state during create). |
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 |