Properties This code system defines the following properties for its concepts Name Code URI Type Description Specializes Specializes Coding The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric. Generalizes Generalizes Coding Inverse of Specializes. Only included as a derived relationship. internalId internalId http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id code The internal identifier for the concept in the HL7 Access database repository. status status http://hl7.org/fhir/concept-properties#status code Designation of a concept's state. Normally is not populated unless the state is retired.. Not Selectable notSelectable http://hl7.org/fhir/concept-properties#notSelectable boolean Indicates that the code is abstract - only intended to be used as a selector for other concepts Concepts This case-sensitive code system http://terminology.hl7.org/CodeSystem/v3-HL7UpdateMode defines the following codes in a Is-A hierarchy: Lvl Code Display Definition internalId status Not Selectable 1 A Add **Description:**The item was (or is to be) added, having not been present immediately before. (If it is already present, this may be treated as an error condition.) 22624 active 1 AR Add or Replace **Description:**The item was (or is to be) either added or replaced. 22654 active 1 D Remove **Description:**The item was (or is to be) removed (sometimes referred to as deleted). If the item is part of a collection, delete any matching items. 10020 active 1 K Key **Description:**This item is part of the identifying information for this object. 10022 active 1 N No Change **Description:**There was (or is to be) no change to the item. This is primarily used when this element has not changed, but other attributes in the instance have changed. 22655 active 1 R Replace **Description:**The item existed previously and has (or is to be) revised. (If an item does not already exist, this may be treated as an error condition.) 10019 active 1 REF Reference **Description:**This item provides enough information to allow a processing system to locate the full applicable record by identifying the object. 22623 active 1 U Unknown **Description:**Description:It is not specified whether or what kind of change has occurred to the item, or whether the item is present as a reference or identifying property. 22622 active 1 _SetUpdateMode SetUpdateMode These concepts apply when the element and/or message is updating a set of items. 21082 retired true 2 ESA Set Add Add the message element to the collection of items on the receiving system that correspond to the message element. 10025 retired 2 ESAC Set Add or Change Change the item on the receiving system that corresponds to this message element; if a matching element does not exist, add a new one created with the values in the message. 10028 retired 2 ESC Set Change Change the item on the receiving system that corresponds to this message element; do not process if a matching element does not exist. 10027 retired 2 ESD Set Delete Delete the item on the receiving system that corresponds to this message element. 10026 retired 1 AU Add or Update **Description:** AU: If this item exists, update it with these values. If it does not exist, create it with these values. If the item is part of the collection, update each item that matches this item, and if no items match, add a new item to the collection. 22621 retired 1 I Ignore Ignore this role, it is not relevant to the update. 10021 retired 1 V Verify Verify - this message element must match a value already in the receiving systems database in order to process the message. 10023 retired
The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.
This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license
The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.
Inverse of Specializes. Only included as a derived relationship.
The internal identifier for the concept in the HL7 Access database repository.
Designation of a concept's state. Normally is not populated unless the state is retired..
Indicates that the code is abstract - only intended to be used as a selector for other concepts
**Description:**The item was (or is to be) added, having not been present immediately before. (If it is already present, this may be treated as an error condition.)
**Description:**The item was (or is to be) either added or replaced.
**Description:**The item was (or is to be) removed (sometimes referred to as deleted). If the item is part of a collection, delete any matching items.
**Description:**This item is part of the identifying information for this object.
**Description:**There was (or is to be) no change to the item. This is primarily used when this element has not changed, but other attributes in the instance have changed.
**Description:**The item existed previously and has (or is to be) revised. (If an item does not already exist, this may be treated as an error condition.)
**Description:**This item provides enough information to allow a processing system to locate the full applicable record by identifying the object.
**Description:**Description:It is not specified whether or what kind of change has occurred to the item, or whether the item is present as a reference or identifying property.
These concepts apply when the element and/or message is updating a set of items.
Add the message element to the collection of items on the receiving system that correspond to the message element.
Change the item on the receiving system that corresponds to this message element; if a matching element does not exist, add a new one created with the values in the message.
Change the item on the receiving system that corresponds to this message element; do not process if a matching element does not exist.
Delete the item on the receiving system that corresponds to this message element.
**Description:** AU: If this item exists, update it with these values. If it does not exist, create it with these values. If the item is part of the collection, update each item that matches this item, and if no items match, add a new item to the collection.
Ignore this role, it is not relevant to the update.
Verify - this message element must match a value already in the receiving systems database in order to process the message.