HL7 Terminology (THO)
7.0.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 7.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: ActRelationshipSequel

Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSequel Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: ActRelationshipSequel
Other Identifiers: OID:2.16.840.1.113883.1.11.10337

Copyright/Legal: 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.html

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.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Language: en

 

Expansion

Expansion performed internally based on codesystem ActRelationshipType v4.0.0 (CodeSystem)

This value set contains 23 concepts

LevelSystemCodeDisplay (en) - English (English, en)JSONXML
1http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType  SEQLis sequel
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    APNDis appendage
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    BSLNhas baseline
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    COMPLYcomplies with
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    DOCdocuments
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    FLFSfulfills
3http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType      OCCRoccurrence
3http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType      OREFreferences order
3http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType      SCHschedules request
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    GENhas generalization
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    GEVLevaluates (goal)
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    INSTinstantiates (master)
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    MODmodifies
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    MTCHmatches (trigger)
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    OPTNhas option
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    RCHALre-challenge
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    REVreverses
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    RPLCreplaces
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    SUCCsucceeds
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    UPDTupdates (condition)
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    XCRPTExcerpts
3http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType      VRXCRPTExcerpt verbatim
2http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType    XFRMtransformation

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
System 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

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26