Terminology| Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
The source is an excerpt from the target.
<?xml version="1.0" encoding="UTF-8"?> <ValueSet xmlns="http://hl7.org/fhir"> <id value="v3-ActRelationshipType"/> <meta> <lastUpdated value="2018-08-12T00:00:00.000+00:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p> Release Date: 2018-08-12</p> <table class="grid"> <tr> <td> <b> Level</b> </td> <td> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td> 1</td> <td> ART <a name="v3-ActRelationshipType-ART"> </a> </td> <td> act relationship type</td> <td> Description: A directed association between a source Act and a target Act. <br/> Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute) <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActClassTemporallyPertains)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActRelationshipType-_ActClassTemporallyPertains"> </a> </td> <td/> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActRelationshipAccounting)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActRelationshipType-_ActRelationshipAccounting"> </a> </td> <td> Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element. <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_ActRelationshipCostTracking)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActRelationshipType-_ActRelationshipCostTracking"> </a> </td> <td> Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act. <br/> </td> </tr> <tr> <td> 4</td> <td> CHRG <a name="v3-ActRelationshipType-CHRG"> </a> </td> <td> has charge</td> <td> A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service. <br/> The financial transaction will define the charge (bill) for delivery or performance of the service. <br/> Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. <br/> </td> </tr> <tr> <td> 4</td> <td> COST <a name="v3-ActRelationshipType-COST"> </a> </td> <td> has cost</td> <td> A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service. <br/> The financial transaction will define the cost of delivery or performance of the service. <br/> Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_ActRelationshipPosting)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActRelationshipType-_ActRelationshipPosting"> </a> </td> <td> Expresses values for describing the relationship between a FinancialTransact ion and an Account. <br/> </td> </tr> <tr> <td> 4</td> <td> CREDIT <a name="v3-ActRelationshipType-CREDIT"> </a> </td> <td> has credit</td> <td> A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance. <br/> </td> </tr> <tr> <td> 4</td> <td> DEBIT <a name="v3-ActRelationshipType-DEBIT"> </a> </td> <td> has debit</td> <td> A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActRelationshipConditional)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActRelationshipType-_ActRelationshipConditional"> </a> </td> <td> Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred <br/> </td> </tr> <tr> <td> 3</td> <td> CIND <a name="v3-ActRelationshipType-CIND"> </a> </td> <td> has contra-indication</td> <td> A contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used. <br/> </td> </tr> <tr> <td> 3</td> <td> PRCN <a name="v3-ActRelationshipType-PRCN"> </a> </td> <td> has pre-condition</td> <td> A requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable. <br/> </td> </tr> <tr> <td> 3</td> <td> RSON <a name="v3-ActRelationshipType-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/> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> BLOCK <a name="v3-ActRelationshipType-BLOCK"> </a> </td> <td> blocks</td> <td> Definition: The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring. <br/> </td> </tr> <tr> <td> 4</td> <td> DIAG <a name="v3-ActRelationshipType-DIAG"> </a> </td> <td> diagnoses</td> <td> Description: The source act is intended to help establish the presence of a (an adverse) situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. <br/> </td> </tr> <tr> <td> 4</td> <td> IMM <a name="v3-ActRelationshipType-IMM"> </a> </td> <td> immunization against</td> <td> Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease) <br/> </td> </tr> <tr> <td> 5</td> <td> ACTIMM <a name="v3-ActRelationshipType-ACTIMM"> </a> </td> <td> active immunization against</td> <td> Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease) <br/> </td> </tr> <tr> <td> 5</td> <td> PASSIMM <a name="v3-ActRelationshipType-PASSIMM"> </a> </td> <td> passive immunization against</td> <td> Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease). <br/> </td> </tr> <tr> <td> 4</td> <td> MITGT <a name="v3-ActRelationshipType-MITGT"> </a> </td> <td> mitigates</td> <td> The source act removes or lessens the occurrence or effect of the target act. <br/> </td> </tr> <tr> <td> 5</td> <td> RCVY <a name="v3-ActRelationshipType-RCVY"> </a> </td> <td> recovers</td> <td> Definition: The source act is performed to recover from the effects of the target act. <br/> </td> </tr> <tr> <td> 4</td> <td> PRYLX <a name="v3-ActRelationshipType-PRYLX"> </a> </td> <td> prophylaxis of</td> <td> Description: The source act is intended to reduce the risk of of an adverse situation to emerge as described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. <br/> </td> </tr> <tr> <td> 4</td> <td> TREAT <a name="v3-ActRelationshipType-TREAT"> </a> </td> <td> treats</td> <td> Description: The source act is intended to improve a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. <br/> </td> </tr> <tr> <td> 5</td> <td> ADJUNCT <a name="v3-ActRelationshipType-ADJUNCT"> </a> </td> <td> adjunctive treatment</td> <td> Description: The source act is intended to offer an additional treatment for the management or cure of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. It is not a requirement that the non-adjunctive treatment is explicitly specified. <br/> </td> </tr> <tr> <td> 5</td> <td> MTREAT <a name="v3-ActRelationshipType-MTREAT"> </a> </td> <td> maintenance treatment</td> <td> Description: The source act is intended to provide long term maintenance improvement or management of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. <br/> </td> </tr> <tr> <td> 5</td> <td> PALLTREAT <a name="v3-ActRelationshipType-PALLTREAT"> </a> </td> <td> palliates</td> <td> Description: The source act is intended to provide palliation for the effects of the target act. <br/> </td> </tr> <tr> <td> 5</td> <td> SYMP <a name="v3-ActRelationshipType-SYMP"> </a> </td> <td> symptomatic relief</td> <td> Description: The source act is intented to provide symptomatic relief for the effects of the target act. <br/> </td> </tr> <tr> <td> 3</td> <td> TRIG <a name="v3-ActRelationshipType-TRIG"> </a> </td> <td> has trigger</td> <td> A pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified. <br/> Discussion: This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActRelationshipTemporallyPertains)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActRelationshipType-_ActRelationshipTemporallyPertains"> </a> </td> <td> Abstract collector for ActRelationhsip types that relate two acts by their timing. <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_ActRelationshipTemporallyPertainsApproximates)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActRelationshipType-_ActRelationshipTemporallyPertainsApproximates"> </a> </td> <td> Abstract collector for ActRelationship types that relate two acts by their approximate timing. <br/> </td> </tr> <tr> <td> 4</td> <td> ENE <a name="v3-ActRelationshipType-ENE"> </a> </td> <td> ends near end</td> <td> A relationship in which the source act's effective time ends near the end of the target act's effective time. Near is defined separately as a time interval. <br/> Usage Note: Inverse code is ENS <br/> </td> </tr> <tr> <td> 5</td> <td> ECW <a name="v3-ActRelationshipType-ECW"> </a> </td> <td> ends concurrent with</td> <td> A relationship in which the source act's effective time ends with the end of the target act's effective time. <br/> UsageNote: This code is reflexive. Therefore its inverse code is itself. <br/> </td> </tr> <tr> <td> 6</td> <td> CONCURRENT <a name="v3-ActRelationshipType-CONCURRENT"> </a> </td> <td> concurrent with</td> <td> A relationship in which the source act's effective time is the same as the target act's effective time. <br/> UsageNote: This code is reflexive. Therefore its inverse code is itself. <br/> </td> </tr> <tr> <td> 6</td> <td> SBSECWE <a name="v3-ActRelationshipType-SBSECWE"> </a> </td> <td> starts before start of, ends with</td> <td> The source Act starts before the start of the target Act, and ends with the target Act. <br/> UsageNote: Inverse code is SASECWE <br/> </td> </tr> <tr> <td> 4</td> <td> ENS <a name="v3-ActRelationshipType-ENS"> </a> </td> <td> ends near start</td> <td> A relationship in which the source act's effective time ends near the start of the target act's effective time. Near is defined separately as a time interval. <br/> Usage Note: Inverse code is ENE <br/> </td> </tr> <tr> <td> 5</td> <td> ECWS <a name="v3-ActRelationshipType-ECWS"> </a> </td> <td> ends concurrent with start of</td> <td> The source Act ends when the target act starts (i.e. if we say "ActOne ECWS ActTwo", it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target). <br/> UsageNote: Inverse code is SCWE <br/> </td> </tr> <tr> <td> 4</td> <td> SNE <a name="v3-ActRelationshipType-SNE"> </a> </td> <td> starts near end</td> <td> A relationship in which the source act's effective time starts near the end of the target act's effective time. Near is defined separately as a time interval. <br/> Usage Note: Inverse code is SNS <br/> </td> </tr> <tr> <td> 5</td> <td> SCWE <a name="v3-ActRelationshipType-SCWE"> </a> </td> <td> starts concurrent with end of</td> <td> The source Act starts when the target act ends (i.e. if we say "ActOne SCWE ActTwo", it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target). <br/> UsageNote: Inverse code is SBSECWS <br/> </td> </tr> <tr> <td> 4</td> <td> SNS <a name="v3-ActRelationshipType-SNS"> </a> </td> <td> starts near start</td> <td> A relationship in which the source act's effective time starts near the start of the target act's effective time. Near is defined separately as a time interval. <br/> Usage Note: Inverse code is SNE <br/> </td> </tr> <tr> <td> 5</td> <td> SCW <a name="v3-ActRelationshipType-SCW"> </a> </td> <td> starts concurrent with</td> <td> A relationship in which the source act's effective time starts with the start of the target act's effective time. <br/> UsageNote: This code is reflexive. Therefore its inverse code is itself. <br/> </td> </tr> <tr> <td> 6</td> <td> <a href="#CONCURRENT">CONCURRENT</a> </td> <td/> <td/> </tr> <tr> <td> 6</td> <td> SCWSEBE <a name="v3-ActRelationshipType-SCWSEBE"> </a> </td> <td> starts with. ends before end of</td> <td> The source Act starts with.the target Act and ends before the end of the target Act. <br/> UsageNote: Inverse code is SCWSEAE <br/> </td> </tr> <tr> <td> 6</td> <td> SCWSEAE <a name="v3-ActRelationshipType-SCWSEAE"> </a> </td> <td> starts with, ends after end of</td> <td> The source Act starts with the target Act, and ends after the end of the target Act.</td> </tr> <tr> <td> 3</td> <td> EAS <a name="v3-ActRelationshipType-EAS"> </a> </td> <td> ends after start of</td> <td> A relationship in which the source act ends after the target act starts. <br/> UsageNote: Inverse code is SBE <br/> </td> </tr> <tr> <td> 4</td> <td> EAE <a name="v3-ActRelationshipType-EAE"> </a> </td> <td> ends after end of</td> <td> A relationship in which the source act ends after the target act ends. <br/> UsageNote: Inverse code is EBE <br/> </td> </tr> <tr> <td> 5</td> <td> SASEAE <a name="v3-ActRelationshipType-SASEAE"> </a> </td> <td> starts after start of, ends after end of</td> <td> The source Act starts after start of the target Act and ends after end of the target Act. <br/> UsageNote: Inverse code is SBSEBE <br/> </td> </tr> <tr> <td> 6</td> <td> SBEEAE <a name="v3-ActRelationshipType-SBEEAE"> </a> </td> <td> contains end of</td> <td> The source Act contains the end of the target Act. <br/> UsageNote: Inverse code is EDU <br/> </td> </tr> <tr> <td> 7</td> <td> SASSBEEAS <a name="v3-ActRelationshipType-SASSBEEAS"> </a> </td> <td> start after start of, contains end of</td> <td> The source Act start after the start of the target Act, and contains the end of the target Act. <br/> UsageNote: Inverse code is SBSEASEBE <br/> </td> </tr> <tr> <td> 7</td> <td> SBSEAE <a name="v3-ActRelationshipType-SBSEAE"> </a> </td> <td> contains time of</td> <td> The source Act contains the time of the target Act. <br/> UsageNote: Inverse code is DURING <br/> </td> </tr> <tr> <td> 7</td> <td> <a href="#SCWSEAE">SCWSEAE</a> </td> <td/> <td/> </tr> <tr> <td> 6</td> <td> <a href="#SASSBEEAS">SASSBEEAS</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td> SAS <a name="v3-ActRelationshipType-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/> UsageNote: Inverse code is SBS <br/> </td> </tr> <tr> <td> 5</td> <td> <a href="#SASEAE">SASEAE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> SAE <a name="v3-ActRelationshipType-SAE"> </a> </td> <td> starts after end of</td> <td> A relationship in which the source act starts after the target act ends. <br/> UsageNote: Inverse code is EBS <br/> </td> </tr> <tr> <td> 5</td> <td> DURING <a name="v3-ActRelationshipType-DURING"> </a> </td> <td> occurs during</td> <td> A relationship in which the source act's effective time is wholly within the target act's effective time (including end points, as defined in the act's effective times) <br/> UsageNote: Inverse code is SBSEAE <br/> </td> </tr> <tr> <td> 5</td> <td> SASECWE <a name="v3-ActRelationshipType-SASECWE"> </a> </td> <td> starts after start of, ends with</td> <td> The source Act starts after start of the target Act, and ends with the target Act. <br/> UsageNote: Inverse code is SBSECWE <br/> </td> </tr> <tr> <td> 3</td> <td> EASORECWS <a name="v3-ActRelationshipType-EASORECWS"> </a> </td> <td> ends after or concurrent with start of</td> <td> A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time. <br/> Usage Note: Inverse code is EBSORECWS <br/> </td> </tr> <tr> <td> 4</td> <td> <a href="#EAS">EAS</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td> EAEORECW <a name="v3-ActRelationshipType-EAEORECW"> </a> </td> <td> ends after or concurrent with end of</td> <td> A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time. <br/> Usage Note: Inverse code is EBEORECW <br/> </td> </tr> <tr> <td> 5</td> <td> <a href="#EAE">EAE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> <a href="#ECW">ECW</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td> <a href="#ECWS">ECWS</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td> INDEPENDENT <a name="v3-ActRelationshipType-INDEPENDENT"> </a> </td> <td> independent of time of</td> <td> The source Act is independent of the time of the target Act. <br/> UsageNote: This code is reflexive. Therefore its inverse code is itself. <br/> </td> </tr> <tr> <td> 3</td> <td> SAEORSCWE <a name="v3-ActRelationshipType-SAEORSCWE"> </a> </td> <td> starts after or concurrent with end of</td> <td> A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time. <br/> Usage Note: Inverse code is SBEORSCWE <br/> </td> </tr> <tr> <td> 4</td> <td> <a href="#SCWE">SCWE</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td> <a href="#SAE">SAE</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td> SASORSCW <a name="v3-ActRelationshipType-SASORSCW"> </a> </td> <td> starts after or concurrent with start of</td> <td> A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time. <br/> Usage Note: Inverse code is SBSORSCW <br/> </td> </tr> <tr> <td> 4</td> <td> <a href="#SAS">SAS</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td> <a href="#SCW">SCW</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td> SBEORSCWE <a name="v3-ActRelationshipType-SBEORSCWE"> </a> </td> <td> starts before or concurrent with end of</td> <td> A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time. <br/> Usage Note: Inverse code is SAEORSCWE <br/> </td> </tr> <tr> <td> 4</td> <td> OVERLAP <a name="v3-ActRelationshipType-OVERLAP"> </a> </td> <td> overlaps with</td> <td> A relationship in which the source act's effective time overlaps the target act's effective time in any way. <br/> UsageNote: This code is reflexive. Therefore its inverse code is itself. <br/> </td> </tr> <tr> <td> 5</td> <td> <a href="#ECW">ECW</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> EDU <a name="v3-ActRelationshipType-EDU"> </a> </td> <td> ends during</td> <td> A relationship in which the source act ends within the target act's effective time (including end points, as defined in the act's effective times) <br/> UsageNote: Inverse code is SBEEAE <br/> </td> </tr> <tr> <td> 6</td> <td> SBSEASEBE <a name="v3-ActRelationshipType-SBSEASEBE"> </a> </td> <td> contains start of, ends before end of</td> <td> The source Act contains the start of the target Act, and ends before the end of the target Act. <br/> UsageNote: Inverse code is SASSBEEAS <br/> </td> </tr> <tr> <td> 6</td> <td> <a href="#SCWSEBE">SCWSEBE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> <a href="#SBEEAE">SBEEAE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> SBSEAS <a name="v3-ActRelationshipType-SBSEAS"> </a> </td> <td> contains start of</td> <td> The source Act contains the start of the target Act. <br/> UsageNote: Inverse code is SDU <br/> </td> </tr> <tr> <td> 6</td> <td> <a href="#SBSECWE">SBSECWE</a> </td> <td/> <td/> </tr> <tr> <td> 6</td> <td> <a href="#SBSEASEBE">SBSEASEBE</a> </td> <td/> <td/> </tr> <tr> <td> 6</td> <td> <a href="#SBSEAE">SBSEAE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> <a href="#SCW">SCW</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> <a href="#SCWE">SCWE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> SDU <a name="v3-ActRelationshipType-SDU"> </a> </td> <td> starts during</td> <td> A relationship in which the source act starts within the target act's effective time (including end points, as defined in the act's effective times) <br/> UsageNote: Inverse code is SBSEAS <br/> </td> </tr> <tr> <td> 6</td> <td> <a href="#SASSBEEAS">SASSBEEAS</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td> SBE <a name="v3-ActRelationshipType-SBE"> </a> </td> <td> starts before end of</td> <td> The source Act starts before the end of the target Act (i.e. if we say "ActOne SBE ActTwo", it means that ActOne starts before the end of ActTwo, therefore ActOne is the source and ActTwo is the target). <br/> UsageNote: Inverse code is EAS <br/> </td> </tr> <tr> <td> 5</td> <td> EBE <a name="v3-ActRelationshipType-EBE"> </a> </td> <td> ends before end of</td> <td> The source Act ends before the end of the target Act (i.e. if we say "ActOne EBE ActTwo", it means that ActOne ends before the end of ActTwo, therefore ActOne is the source and ActTwo is the target). <br/> UsageNote: Inverse code is EAE <br/> </td> </tr> <tr> <td> 6</td> <td> SBSEBE <a name="v3-ActRelationshipType-SBSEBE"> </a> </td> <td> starts before start of, ends before end of</td> <td> The source Act starts before the start of the target Act, and ends before the end of the target Act. <br/> UsageNote: Inverse code is SASEAE <br/> </td> </tr> <tr> <td> 7</td> <td> <a href="#SBSEASEBE">SBSEASEBE</a> </td> <td/> <td/> </tr> <tr> <td> 7</td> <td> EBSORECWS <a name="v3-ActRelationshipType-EBSORECWS"> </a> </td> <td> ends before or concurrent with start of</td> <td> A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time. <br/> Usage Note: Inverse code is EASORECWS <br/> </td> </tr> <tr> <td> 8</td> <td> <a href="#ECWS">ECWS</a> </td> <td/> <td/> </tr> <tr> <td> 8</td> <td> EBS <a name="v3-ActRelationshipType-EBS"> </a> </td> <td> ends before start of</td> <td> A relationship in which the source act ends before the target act starts. <br/> UsageNote: Inverse code is SAE <br/> </td> </tr> <tr> <td> 5</td> <td> <a href="#SBSEASEBE">SBSEASEBE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> <a href="#SCWSEBE">SCWSEBE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> EBEORECW <a name="v3-ActRelationshipType-EBEORECW"> </a> </td> <td> ends before or concurrent with end of</td> <td> A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time. <br/> Usage Note: Inverse code is EAEORECW <br/> </td> </tr> <tr> <td> 6</td> <td> <a href="#ECW">ECW</a> </td> <td/> <td/> </tr> <tr> <td> 6</td> <td> <a href="#EBE">EBE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td> SBSORSCW <a name="v3-ActRelationshipType-SBSORSCW"> </a> </td> <td> starts before or concurrent with start of</td> <td> A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time. <br/> Usage Note: Inverse code is SASORSCW <br/> </td> </tr> <tr> <td> 6</td> <td> <a href="#SCW">SCW</a> </td> <td/> <td/> </tr> <tr> <td> 6</td> <td> SBS <a name="v3-ActRelationshipType-SBS"> </a> </td> <td> starts before start of</td> <td> A relationship in which the source act begins before the target act begins. <br/> UsageNote: Inverse code is SAS <br/> </td> </tr> <tr> <td> 7</td> <td> <a href="#SBSEBE">SBSEBE</a> </td> <td/> <td/> </tr> <tr> <td> 7</td> <td> <a href="#SBSEAS">SBSEAS</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> AUTH <a name="v3-ActRelationshipType-AUTH"> </a> </td> <td> authorized by</td> <td> A relationship in which the target act authorizes or certifies the source act. <br/> </td> </tr> <tr> <td> 2</td> <td> CAUS <a name="v3-ActRelationshipType-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/> Examples: <br/> a growth of Staphylococcus aureus may be considered the cause of an abscess contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced 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> 2</td> <td> COMP <a name="v3-ActRelationshipType-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. <br/> </td> </tr> <tr> <td> 3</td> <td> CTRLV <a name="v3-ActRelationshipType-CTRLV"> </a> </td> <td> has control variable</td> <td> A relationship from an Act to a Control Variable. For example, if a Device makes an Observation, this relates the Observation to its Control Variables documenting the device's settings that influenced the observation. <br/> </td> </tr> <tr> <td> 3</td> <td> MBR <a name="v3-ActRelationshipType-MBR"> </a> </td> <td> has member</td> <td> The target Acts are aggregated by the source Act. Target Acts may have independent existence, participate in multiple ActRelationships, and do not contribute to the meaning of the source. <br/> UsageNotes: This explicitly represents the conventional notion of aggregation. The target Act is part of a collection of Acts (no implication is made of cardinality, a source of Acts may contain zero, one, or more member target Acts). <br/> It is expected that this will be primarily used with _ActClassRecordOrganize r, BATTERY, and LIST <br/> </td> </tr> <tr> <td> 4</td> <td> STEP <a name="v3-ActRelationshipType-STEP"> </a> </td> <td> has step</td> <td> A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently. <br/> UsageNotes: Sequence of steps may be indicated by use of _ActRelationship TemporallyPertains, as well as via ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode. <br/> OpenIssue: Need Additional guidelines on when each approach should be used. <br/> </td> </tr> <tr> <td> 5</td> <td> ARR <a name="v3-ActRelationshipType-ARR"> </a> </td> <td> arrival</td> <td> The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act entered into the source Act by means of the target Transportation act. <br/> </td> </tr> <tr> <td> 5</td> <td> DEP <a name="v3-ActRelationshipType-DEP"> </a> </td> <td> departure</td> <td> The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act departed from the source Act by means of the target Transportation act. <br/> </td> </tr> <tr> <td> 3</td> <td> PART <a name="v3-ActRelationshipType-PART"> </a> </td> <td> has part</td> <td> The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act. <br/> UsageNote: In UML 1.1, this is a "composition" defined as: "A form of aggregation with strong ownership and coincident lifetime as part of the whole. Parts with non-fixed multiplicity may be created after the composite itself, but once created they live and die with it (i.e., they share lifetimes). Such parts can also be explicitly removed before the death of the composite. Composition may be recursive." <br/> </td> </tr> <tr> <td> 2</td> <td> COVBY <a name="v3-ActRelationshipType-COVBY"> </a> </td> <td> covered by</td> <td> A relationship in which the source act is covered by or is under the authority of a target act. A financial instrument such as an Invoice Element is covered by one or more specific instances of an Insurance Policy. <br/> </td> </tr> <tr> <td> 2</td> <td> DRIV <a name="v3-ActRelationshipType-DRIV"> </a> </td> <td> is derived from</td> <td> Associates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts. <br/> </td> </tr> <tr> <td> 2</td> <td> ELNK <a name="v3-ActRelationshipType-ELNK"> </a> </td> <td> episodeLink</td> <td> Expresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter. <br/> </td> </tr> <tr> <td> 2</td> <td> EVID <a name="v3-ActRelationshipType-EVID"> </a> </td> <td> provides evidence for</td> <td> Indicates that the target Act provides evidence in support of the action represented by the source Act. The target is not a 'reason' for the source act, but rather gives supporting information on why the source act is an appropriate course of action. Possible targets might be clinical trial results, journal articles, similar successful therapies, etc. <br/> Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies. <br/> </td> </tr> <tr> <td> 2</td> <td> EXACBY <a name="v3-ActRelationshipType-EXACBY"> </a> </td> <td> exacerbated by</td> <td> Description:The source act is aggravated by the target act. (Example "chest pain" EXACBY "exercise") <br/> </td> </tr> <tr> <td> 2</td> <td> EXPL <a name="v3-ActRelationshipType-EXPL"> </a> </td> <td> has explanation</td> <td> This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition. <br/> </td> </tr> <tr> <td> 2</td> <td> INTF <a name="v3-ActRelationshipType-INTF"> </a> </td> <td> interfered by</td> <td> the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act. <br/> UsageNote: This provides the semantics to document barriers to care <br/> </td> </tr> <tr> <td> 2</td> <td> ITEMSLOC <a name="v3-ActRelationshipType-ITEMSLOC"> </a> </td> <td> items located</td> <td> Items located <br/> </td> </tr> <tr> <td> 2</td> <td> LIMIT <a name="v3-ActRelationshipType-LIMIT"> </a> </td> <td> limited by</td> <td> A relationship that limits or restricts the source act by the elements of the target act. For example, an authorization may be limited by a financial amount (up to $500). Target Act must be in EVN.CRIT mood. <br/> </td> </tr> <tr> <td> 2</td> <td> META <a name="v3-ActRelationshipType-META"> </a> </td> <td> has metadata</td> <td> Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act. <br/> Constraint: Source act must have either a mood code that is not "EVN" (event) or its "isCriterion" attribute must set to "true". Target act must be an Act with a mood code of EVN and with isCriterionInd attribute set to "true". <br/> </td> </tr> <tr> <td> 2</td> <td> MFST <a name="v3-ActRelationshipType-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. <br/> </td> </tr> <tr> <td> 2</td> <td> NAME <a name="v3-ActRelationshipType-NAME"> </a> </td> <td> assigns name</td> <td> Used to assign a "name" to a condition thread. Source is a condition node, target can be any service. <br/> </td> </tr> <tr> <td> 2</td> <td> OUTC <a name="v3-ActRelationshipType-OUTC"> </a> </td> <td> has outcome</td> <td> An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called "post-conditional".) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute (AND, OR, XOR) can be used. An outcome link is often inverted to describe an outcome assessment. <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_ActRelationsipObjective)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActRelationshipType-_ActRelationsipObjective"> </a> </td> <td> The target act is a desired outcome of the source act. Source is any act (typically an intervention). Target must be an observation in criterion mood. <br/> </td> </tr> <tr> <td> 4</td> <td> OBJC <a name="v3-ActRelationshipType-OBJC"> </a> </td> <td> has continuing objective</td> <td> A desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood. <br/> </td> </tr> <tr> <td> 4</td> <td> OBJF <a name="v3-ActRelationshipType-OBJF"> </a> </td> <td> has final objective</td> <td> A desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood. <br/> </td> </tr> <tr> <td> 3</td> <td> GOAL <a name="v3-ActRelationshipType-GOAL"> </a> </td> <td> has goal</td> <td> A goal that one defines given a patient's health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood. <br/> </td> </tr> <tr> <td> 3</td> <td> RISK <a name="v3-ActRelationshipType-RISK"> </a> </td> <td> has risk</td> <td> A noteworthy undesired outcome of a patient's condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed. <br/> </td> </tr> <tr> <td> 2</td> <td> PERT <a name="v3-ActRelationshipType-PERT"> </a> </td> <td> has pertinent information</td> <td> This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays. <br/> </td> </tr> <tr> <td> 2</td> <td> PREV <a name="v3-ActRelationshipType-PREV"> </a> </td> <td> has previous instance</td> <td> A relationship in which the target act is a predecessor instance to the source act. Generally each of these instances is similar, but no identical. In healthcare coverage it is used to link a claim item to a previous claim item that might have claimed for the same set of services. <br/> </td> </tr> <tr> <td> 2</td> <td> REFR <a name="v3-ActRelationshipType-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. <br/> </td> </tr> <tr> <td> 3</td> <td> USE <a name="v3-ActRelationshipType-USE"> </a> </td> <td> uses</td> <td> Indicates that the source act makes use of (or will make use of) the information content of the target act. <br/> UsageNotes: A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate. <br/> Rationale: There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of "references". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference. <br/> </td> </tr> <tr> <td> 2</td> <td> REFV <a name="v3-ActRelationshipType-REFV"> </a> </td> <td> has reference values</td> <td> Reference ranges are essentially descriptors of a class of result values assumed to be "normal", "abnormal", or "critical." Those can vary by sex, age, or any other criterion. Source and target are observations, the target is in criterion mood. This link type can act as a trigger in case of alarms being triggered by critical results. <br/> </td> </tr> <tr> <td> 2</td> <td> RELVBY <a name="v3-ActRelationshipType-RELVBY"> </a> </td> <td> relieved by</td> <td> Description:The source act is wholly or partially alleviated by the target act. (Example "chest pain" RELVBY "sublingual nitroglycerin administration") <br/> </td> </tr> <tr> <td> 2</td> <td> SEQL <a name="v3-ActRelationshipType-SEQL"> </a> </td> <td> is sequel</td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> APND <a name="v3-ActRelationshipType-APND"> </a> </td> <td> is appendage</td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> BSLN <a name="v3-ActRelationshipType-BSLN"> </a> </td> <td> has baseline</td> <td> Indicates that the target observation(s) provide an initial reference for the source observation or observation group. <br/> UsageConstraints: Both source and target must be Observations or specializations thereof. <br/> </td> </tr> <tr> <td> 3</td> <td> COMPLY <a name="v3-ActRelationshipType-COMPLY"> </a> </td> <td> complies with</td> <td> 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. <br/> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> DOC <a name="v3-ActRelationshipType-DOC"> </a> </td> <td> documents</td> <td> The source act documents the target act. <br/> </td> </tr> <tr> <td> 3</td> <td> FLFS <a name="v3-ActRelationshipType-FLFS"> </a> </td> <td> fulfills</td> <td> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> OCCR <a name="v3-ActRelationshipType-OCCR"> </a> </td> <td> occurrence</td> <td> 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). <br/> </td> </tr> <tr> <td> 4</td> <td> OREF <a name="v3-ActRelationshipType-OREF"> </a> </td> <td> references order</td> <td> Relates either an appointment request or an appointment to the order for the service being scheduled. <br/> </td> </tr> <tr> <td> 4</td> <td> SCH <a name="v3-ActRelationshipType-SCH"> </a> </td> <td> schedules request</td> <td> Associates a specific time (and associated resources) with a scheduling request or other intent. <br/> </td> </tr> <tr> <td> 3</td> <td> GEN <a name="v3-ActRelationshipType-GEN"> </a> </td> <td> has generalization</td> <td> 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). <br/> </td> </tr> <tr> <td> 3</td> <td> GEVL <a name="v3-ActRelationshipType-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. <br/> </td> </tr> <tr> <td> 3</td> <td> INST <a name="v3-ActRelationshipType-INST"> </a> </td> <td> instantiates (master)</td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> MOD <a name="v3-ActRelationshipType-MOD"> </a> </td> <td> modifies</td> <td> 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). <br/> 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. <br/> Name from source to target = "modifiesPrior" <br/> Name from target to source = "modifiesByNew" <br/> </td> </tr> <tr> <td> 3</td> <td> MTCH <a name="v3-ActRelationshipType-MTCH"> </a> </td> <td> matches (trigger)</td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> OPTN <a name="v3-ActRelationshipType-OPTN"> </a> </td> <td> has option</td> <td> A relationship between a source Act that provides more detailed properties to the target Act. <br/> 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. <br/> 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. <br/> Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options. <br/> </td> </tr> <tr> <td> 3</td> <td> RCHAL <a name="v3-ActRelationshipType-RCHAL"> </a> </td> <td> re-challenge</td> <td> Description:A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated. <br/> </td> </tr> <tr> <td> 3</td> <td> REV <a name="v3-ActRelationshipType-REV"> </a> </td> <td> reverses</td> <td> A relationship between a source Act that seeks to reverse or undo the action of the prior target Act. <br/> 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. <br/> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> RPLC <a name="v3-ActRelationshipType-RPLC"> </a> </td> <td> replaces</td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> SUCC <a name="v3-ActRelationshipType-SUCC"> </a> </td> <td> succeeds</td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> UPDT <a name="v3-ActRelationshipType-UPDT"> </a> </td> <td> updates (condition)</td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> XCRPT <a name="v3-ActRelationshipType-XCRPT"> </a> </td> <td> Excerpts</td> <td> The source is an excerpt from the target. <br/> </td> </tr> <tr> <td> 4</td> <td> VRXCRPT <a name="v3-ActRelationshipType-VRXCRPT"> </a> </td> <td> Excerpt verbatim</td> <td> The source is a direct quote from the target. <br/> </td> </tr> <tr> <td> 3</td> <td> XFRM <a name="v3-ActRelationshipType-XFRM"> </a> </td> <td> transformation</td> <td> 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.) <br/> </td> </tr> <tr> <td> 2</td> <td> SPRT <a name="v3-ActRelationshipType-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). <br/> </td> </tr> <tr> <td> 3</td> <td> SPRTBND <a name="v3-ActRelationshipType-SPRTBND"> </a> </td> <td> has bounded support</td> <td> A specialization of "has support" (SPRT), used to relate a secondary observation to a Region of Interest on a multidimensional observation, if the ROI specifies the true boundaries of the secondary observation as opposed to only marking the approximate area. For example, if the start and end of an ST elevation episode is visible in an EKG, this relation would indicate the ROI bounds the "ST elevation" observation -- the ROI defines the true beginning and ending of the episode. Conversely, if a ROI simply contains ST elevation, but it does not define the bounds (start and end) of the episode, the more general "has support" relation is used. Likewise, if a ROI on an image defines the true bounds of a "1st degree burn", the relation "has bounded support" is used; but if the ROI only points to the approximate area of the burn, the general "has support" relation is used. <br/> </td> </tr> <tr> <td> 2</td> <td> SUBJ <a name="v3-ActRelationshipType-SUBJ"> </a> </td> <td> has subject</td> <td> Relates an Act to its subject Act that the first Act is primarily concerned with. <br/> Examples <br/> The first Act may be a ControlAct manipulating the subject Act <br/> The first act is a region of interest (ROI) that defines a region within the subject Act. <br/> The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose. <br/> Constraints <br/> An Act may have multiple subject acts. <br/> Rationale <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. <br/> </td> </tr> <tr> <td> 3</td> <td> QUALF <a name="v3-ActRelationshipType-QUALF"> </a> </td> <td> has qualifier</td> <td> The target observation qualifies (refines) the semantics of the source observation. <br/> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> SUMM <a name="v3-ActRelationshipType-SUMM"> </a> </td> <td> summarized by</td> <td> An act that contains summary values for a list or set of subordinate acts. For example, a summary of transactions for a particular accounting period. <br/> </td> </tr> <tr> <td> 2</td> <td> VALUE <a name="v3-ActRelationshipType-VALUE"> </a> </td> <td> has value</td> <td> Description:Indicates that the target Act represents the result of the source observation Act. <br/> FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified <br/> UsageNote: This relationship allows the result of an observation to be fully expressed as RIM acts as opposed to being embedded in the value attribute. For example, sending a Document act as the result of an imaging observation, sending a list of Procedures and/or other acts as the result of a medical history observation. <br/> The valueNegationInd attribute on the source Act has the same semantics of "negated finding" when it applies to the target of a VALUE ActRelationship as it does to the value attribute. On the other hand, if the ActRelationship.negationInd is true for a VALUE ActRelationship, that means the specified observation does not have the indicated value but does not imply a negated finding. Because the semantics are extremely close, it is recommended that Observation.valueNegationInd be used, not ActRelationship.negationInd. <br/> OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation. <br/> </td> </tr> <tr> <td> 1</td> <td> CURE <a name="v3-ActRelationshipType-CURE"> </a> </td> <td> curative indication</td> <td/> </tr> <tr> <td> 1</td> <td> CURE.ADJ <a name="v3-ActRelationshipType-CURE.46ADJ"> </a> </td> <td> adjunct curative indication</td> <td/> </tr> <tr> <td> 1</td> <td> MTGT.ADJ <a name="v3-ActRelationshipType-MTGT.46ADJ"> </a> </td> <td> adjunct mitigation</td> <td/> </tr> <tr> <td> 1</td> <td> RACT <a name="v3-ActRelationshipType-RACT"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> SUGG <a name="v3-ActRelationshipType-SUGG"> </a> </td> <td/> <td/> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="external"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="0"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="vocab"/> </extension> <url value="http://terminology.hl7.org/ValueSet/v3-ActRelationshipType"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.1.11.10317"/> </identifier> <version value="2018-08-12"/> <name value="v3.ActRelationshipType"/> <title value="v3 Code System ActRelationshipType"/> <status value="active"/> <experimental value="false"/> <date value="2018-08-12"/> <publisher value="HL7, Inc"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org"/> </telecom> </contact> <description value=" The source is an excerpt from the target."/> <immutable value="true"/> <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType"/> </include> </compose> </ValueSet>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
®© HL7.org 2011+. FHIR Release 4 (Technical Correction #1) (v4.0.1) generated on Thu, Jan 21, 2021 15:39+0000. QA Page
Links: Search |
Version History |
Table of Contents |
Credits |
Compare to R3 |
|
Propose a change
