HL7 Terminology (THO)
5.1.0 - Publication
HL7 Terminology (THO)
5.1.0 - Publication
This page is part of the HL7 Terminology (v5.1.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 
| Active as of 2014-03-26 |
{
"resourceType" : "ValueSet",
"id" : "v3-xActRelationshipEntryRelationship",
"language" : "en",
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><ul><li>Include these codes as defined in <a href=\"CodeSystem-v3-ActRelationshipType.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType</code></a><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-CAUS\">CAUS</a></td><td>is etiology for</td><td>**Description:** An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act.<br/><br/>**Examples:**<br/><br/> * a growth of Staphylococcus aureus may be considered the cause of an abscess<br/> * contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced<br/> * lack of staff on the shift was deemed to be a supporting factor (proximal factor) causing the patient safety incident where the patient fell out of bed because the bed-sides had not been put up which caused the night patient to fall out of bed</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-COMP\">COMP</a></td><td>has component</td><td>The target act is a component of the source act, with no semantics regarding composition or aggregation implied.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-GEVL\">GEVL</a></td><td>evaluates (goal)</td><td>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.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-MFST\">MFST</a></td><td>is manifestation of</td><td>An assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-REFR\">REFR</a></td><td>refers to</td><td>A relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-RSON\">RSON</a></td><td>has reason</td><td>**Description:** The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication. Child concepts may be used to describe types of indication.<br/><br/>*Discussion:* In prior releases, the code "SUGG" (suggests) was expressed as "an inversion of the reason link." That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SAS\">SAS</a></td><td>starts after start of</td><td>The source Act starts after the start of the target Act (i.e. if we say "ActOne SAS ActTwo", it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).<br/><br/>*UsageNote:* Inverse code is **SBS**</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SPRT\">SPRT</a></td><td>has support</td><td>Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post).</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SUBJ\">SUBJ</a></td><td>has subject</td><td>Relates an Act to its subject Act that the first Act is primarily concerned with.<br/><br/>Examples<br/><br/>1. The first Act may be a ControlAct manipulating the subject Act<br/>2. The first act is a region of interest (ROI) that defines a region within the subject Act.<br/>3. The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.<br/><br/>Constraints<br/><br/>An Act may have multiple subject acts.<br/><br/>Rationale<br/><br/>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.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-XCRPT\">XCRPT</a></td><td>Excerpts</td><td>The source is an excerpt from the target.</td></tr></table></li></ul></div>"
},
"extension" : [
{
"extension" : [
{
"url" : "name",
"valueString" : "Name:Act:inboundRelationship:ActRelationship"
},
{
"url" : "value",
"valueString" : "entryRelationshipOf"
}
],
"url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp"
},
{
"extension" : [
{
"url" : "name",
"valueString" : "Name:Act:outboundRelationship:ActRelationship"
},
{
"url" : "value",
"valueString" : "entryRelationship"
}
],
"url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp"
},
{
"extension" : [
{
"url" : "name",
"valueString" : "Sort:Act:inboundRelationship:ActRelationship"
},
{
"url" : "value",
"valueString" : "BD_______"
}
],
"url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp"
},
{
"extension" : [
{
"url" : "name",
"valueString" : "Sort:Act:outboundRelationship:ActRelationship"
},
{
"url" : "value",
"valueString" : "BD_______"
}
],
"url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp"
}
],
"url" : "http://terminology.hl7.org/ValueSet/v3-xActRelationshipEntryRelationship",
"identifier" : [
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.1.11.19447"
}
],
"version" : "2.0.0",
"name" : "XActRelationshipEntryRelationship",
"title" : "x_ActRelationshipEntryRelationship",
"status" : "active",
"experimental" : false,
"date" : "2014-03-26",
"description" : "Used to enumerate the relationships between two CDA entries.",
"compose" : {
"include" : [
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType",
"concept" : [
{
"code" : "CAUS"
},
{
"code" : "COMP"
},
{
"code" : "GEVL"
},
{
"code" : "MFST"
},
{
"code" : "REFR"
},
{
"code" : "RSON"
},
{
"code" : "SAS"
},
{
"code" : "SPRT"
},
{
"code" : "SUBJ"
},
{
"code" : "XCRPT"
}
]
}
]
}
}
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#5.1.0 based on FHIR 4.0.1. Generated 2023-02-25
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change