This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasOption |
Version: | 2.0.0 |
Name: | ActRelationshipHasOption |
Status: | Active |
Title: | ActRelationshipHasOption |
Definition: | A relationship between a source Act that provides more detailed properties to the target Act. The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements. The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements. Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options. |
OID: | 2.16.840.1.113883.1.11.19999 (for OID based terminology systems) |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
where concept is-a OPTN
This value set contains 1 concepts
Expansion based on ActRelationshipType v2.0.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
Code | Display | Definition |
OPTN | has option | A relationship between a source Act that provides more detailed properties to the target Act. The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements. The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements. Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options. |
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 |
History
Date | Action | Author | Custodian | Comment |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |
2014-03-26 | revise | Vocabulary (Woody Beeler) (no record of original request) | 2014T1_2014-03-26_001283 (RIM release ID) | Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26 |