HL7 Terminology
1.0.0 - Publication
HL7 Terminology
1.0.0 - Publication
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-ActRelationshipSequel |
| Version: | 2.0.0 |
| Name: | ActRelationshipSequel |
| Status: | Active |
| Title: | ActRelationshipSequel |
| Definition: | An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation. |
| OID: | 2.16.840.1.113883.1.11.10337 (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 SEQL
This value set contains 23 concepts
Expansion based on ActRelationshipType v2.0.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
| Lvl | Code | Display | Definition |
| 0 | SEQL | is sequel | An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation. |
| 1 | APND | is appendage | An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered. |
| 1 | BSLN | has baseline | Indicates that the target observation(s) provide an initial reference for the source observation or observation group. *UsageConstraints:* Both source and target must be Observations or specializations thereof. |
| 1 | COMPLY | complies with | **Description:**The source act complies with, adheres to, conforms to, or is permissible under (in whole or in part) the policy, contract, agreement, law, conformance criteria, certification guidelines or requirement conveyed by the target act. Examples for compliance relationships are: audits of adherence with a security policy, certificate of conformance to system certification requirements, or consent directive in compliance with or permissible under a privacy policy. |
| 1 | DOC | documents | The source act documents the target act. |
| 1 | FLFS | fulfills | The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act. |
| 2 | OCCR | occurrence | The source act is a single occurrence of a repeatable target act. The source and target act can be in any mood on the "completion track" but the source act must be as far as or further along the track than the target act (i.e., the occurrence of an intent can be an event but not vice versa). |
| 2 | OREF | references order | Relates either an appointment request or an appointment to the order for the service being scheduled. |
| 2 | SCH | schedules request | Associates a specific time (and associated resources) with a scheduling request or other intent. |
| 1 | GEN | has generalization | The generalization relationship can be used to express categorical knowledge about services (e.g., amilorid, triamterene, and spironolactone have the common generalization potassium sparing diuretic). |
| 1 | GEVL | evaluates (goal) | A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a "goal distance" (e.g., goal to observation) can be "calculated" and need not be sent explicitly. |
| 1 | INST | instantiates (master) | Used to capture the link between a potential service ("master" or plan) and an actual service, where the actual service instantiates the potential service. The instantiation may override the master's defaults. |
| 1 | MOD | modifies | Definition: Used to link a newer version or 'snapshot' of a business object (source) to an older version or 'snapshot' of the same business object (target). *Usage:*The identifier of the Act should be the same for both source and target. If the identifiers are distinct, RPLC should be used instead. Name from source to target = "modifiesPrior" Name from target to source = "modifiesByNew" |
| 1 | MTCH | matches (trigger) | A trigger-match links an actual service (e.g., an observation or procedure that took place) with a service in criterion mood. For example if the trigger is "observation of pain" and pain is actually observed, and if that pain-observation caused the trigger to fire, that pain-observation can be linked with the trigger. |
| 1 | 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. |
| 1 | RCHAL | re-challenge | **Description:**A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated. |
| 1 | REV | reverses | A relationship between a source Act that seeks to reverse or undo the action of the prior target Act. Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction. Constraints: the "completion track" mood of the target Act must be equally or more "actual" than the source act. I.e., when the target act is EVN the source act can be EVN, or any INT. If the target act is INT, the source act can be INT. |
| 1 | RPLC | replaces | A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type. |
| 1 | SUCC | succeeds | **Definition:** A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act. |
| 1 | UPDT | updates (condition) | A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread. |
| 1 | XCRPT | Excerpts | The source is an excerpt from the target. |
| 2 | VRXCRPT | Excerpt verbatim | The source is a direct quote from the target. |
| 1 | XFRM | transformation | Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.) |
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 |
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#1.0.0 based on FHIR 4.0.1. Generated 2020-05-09
Links: Table of Contents |
QA Report | Search
| Version History |
Propose a change