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-ActRelationshipHasSubject |
Version: | 2.0.0 |
Name: | ActRelationshipHasSubject |
Status: | Active |
Title: | ActRelationshipHasSubject |
Definition: | Relates an Act to its subject Act that the first Act is primarily concerned with. Examples
Constraints An Act may have multiple subject acts. Rationale The ActRelationshipType "has subject" is similar to the ParticipationType "subject", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship. |
OID: | 2.16.840.1.113883.1.11.20014 (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 SUBJ
This value set contains 2 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 | SUBJ | has subject | Relates an Act to its subject Act that the first Act is primarily concerned with. Examples 1. The first Act may be a ControlAct manipulating the subject Act 2. The first act is a region of interest (ROI) that defines a region within the subject Act. 3. The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose. Constraints An Act may have multiple subject acts. Rationale The ActRelationshipType "has subject" is similar to the ParticipationType "subject", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship. |
1 | QUALF | has qualifier | The target observation qualifies (refines) the semantics of the source observation. *UsageNote:* This is not intended to replace concept refinement and qualification via vocabulary. It is used when there are multiple components which together provide the complete understanding of the source Act. |
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 |