001package org.hl7.fhir.instance.model.valuesets; 002 003/* 004 Copyright (c) 2011+, HL7, Inc. 005 All rights reserved. 006 007 Redistribution and use in source and binary forms, with or without modification, 008 are permitted provided that the following conditions are met: 009 010 * Redistributions of source code must retain the above copyright notice, this 011 list of conditions and the following disclaimer. 012 * Redistributions in binary form must reproduce the above copyright notice, 013 this list of conditions and the following disclaimer in the documentation 014 and/or other materials provided with the distribution. 015 * Neither the name of HL7 nor the names of its contributors may be used to 016 endorse or promote products derived from this software without specific 017 prior written permission. 018 019 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 020 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 021 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 022 IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 023 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 024 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 025 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, 026 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 027 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 028 POSSIBILITY OF SUCH DAMAGE. 029 030*/ 031 032// Generated on Wed, Nov 11, 2015 10:54-0500 for FHIR v1.0.2 033 034 035public enum V3ActRelationshipType { 036 037 /** 038 * Description: A directed association between a source Act and a target Act. 039 040 041 Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute) 042 */ 043 ART, 044 /** 045 * ActClassTemporallyPertains 046 */ 047 _ACTCLASSTEMPORALLYPERTAINS, 048 /** 049 * Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element. 050 */ 051 _ACTRELATIONSHIPACCOUNTING, 052 /** 053 * Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act. 054 */ 055 _ACTRELATIONSHIPCOSTTRACKING, 056 /** 057 * 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. 058 059 The financial transaction will define the charge (bill) for delivery or performance of the service. 060 061 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. 062 */ 063 CHRG, 064 /** 065 * 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. 066 067 The financial transaction will define the cost of delivery or performance of the service. 068 069 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. 070 */ 071 COST, 072 /** 073 * Expresses values for describing the relationship between a FinancialTransaction and an Account. 074 */ 075 _ACTRELATIONSHIPPOSTING, 076 /** 077 * 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. 078 */ 079 CREDIT, 080 /** 081 * 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. 082 */ 083 DEBIT, 084 /** 085 * Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred 086 */ 087 _ACTRELATIONSHIPCONDITIONAL, 088 /** 089 * 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. 090 */ 091 CIND, 092 /** 093 * 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. 094 */ 095 PRCN, 096 /** 097 * 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. 098 099 100 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. 101 */ 102 RSON, 103 /** 104 * 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. 105 */ 106 BLOCK, 107 /** 108 * 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. 109 */ 110 DIAG, 111 /** 112 * Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease) 113 */ 114 IMM, 115 /** 116 * Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease) 117 */ 118 ACTIMM, 119 /** 120 * Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease). 121 */ 122 PASSIMM, 123 /** 124 * The source act removes or lessens the occurrence or effect of the target act. 125 */ 126 MITGT, 127 /** 128 * Definition: The source act is performed to recover from the effects of the target act. 129 */ 130 RCVY, 131 /** 132 * 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. 133 */ 134 PRYLX, 135 /** 136 * 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. 137 */ 138 TREAT, 139 /** 140 * 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. 141 */ 142 ADJUNCT, 143 /** 144 * 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. 145 */ 146 MTREAT, 147 /** 148 * Description: The source act is intended to provide palliation for the effects of the target act. 149 */ 150 PALLTREAT, 151 /** 152 * Description: The source act is intented to provide symptomatic relief for the effects of the target act. 153 */ 154 SYMP, 155 /** 156 * 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. 157 158 159 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. 160 */ 161 TRIG, 162 /** 163 * Abstract collector for ActRelationhsip types that relate two acts by their timing. 164 */ 165 _ACTRELATIONSHIPTEMPORALLYPERTAINS, 166 /** 167 * Abstract collector for ActRelationship types that relate two acts by their approximate timing. 168 */ 169 _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES, 170 /** 171 * 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. 172 173 174 Usage Note: Inverse code is ENS 175 */ 176 ENE, 177 /** 178 * A relationship in which the source act's effective time ends with the end of the target act's effective time. 179 180 181 UsageNote: This code is reflexive. Therefore its inverse code is itself. 182 */ 183 ECW, 184 /** 185 * A relationship in which the source act's effective time is the same as the target act's effective time. 186 187 188 UsageNote: This code is reflexive. Therefore its inverse code is itself. 189 */ 190 CONCURRENT, 191 /** 192 * The source Act starts before the start of the target Act, and ends with the target Act. 193 194 195 UsageNote: Inverse code is SASECWE 196 */ 197 SBSECWE, 198 /** 199 * 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. 200 201 202 Usage Note: Inverse code is ENE 203 */ 204 ENS, 205 /** 206 * 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). 207 208 209 UsageNote: Inverse code is SCWE 210 */ 211 ECWS, 212 /** 213 * 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. 214 215 216 Usage Note: Inverse code is SNS 217 */ 218 SNE, 219 /** 220 * 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). 221 222 223 UsageNote: Inverse code is SBSECWS 224 */ 225 SCWE, 226 /** 227 * 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. 228 229 230 Usage Note: Inverse code is SNE 231 */ 232 SNS, 233 /** 234 * A relationship in which the source act's effective time starts with the start of the target act's effective time. 235 236 237 UsageNote: This code is reflexive. Therefore its inverse code is itself. 238 */ 239 SCW, 240 /** 241 * The source Act starts with.the target Act and ends before the end of the target Act. 242 243 244 UsageNote: Inverse code is SCWSEAE 245 */ 246 SCWSEBE, 247 /** 248 * The source Act starts with the target Act, and ends after the end of the target Act. 249 */ 250 SCWSEAE, 251 /** 252 * A relationship in which the source act ends after the target act starts. 253 254 255 UsageNote: Inverse code is SBE 256 */ 257 EAS, 258 /** 259 * A relationship in which the source act ends after the target act ends. 260 261 262 UsageNote: Inverse code is EBE 263 */ 264 EAE, 265 /** 266 * The source Act starts after start of the target Act and ends after end of the target Act. 267 268 269 UsageNote: Inverse code is SBSEBE 270 */ 271 SASEAE, 272 /** 273 * The source Act contains the end of the target Act. 274 275 276 UsageNote: Inverse code is EDU 277 */ 278 SBEEAE, 279 /** 280 * The source Act start after the start of the target Act, and contains the end of the target Act. 281 282 283 UsageNote: Inverse code is SBSEASEBE 284 */ 285 SASSBEEAS, 286 /** 287 * The source Act contains the time of the target Act. 288 289 290 UsageNote: Inverse code is DURING 291 */ 292 SBSEAE, 293 /** 294 * 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). 295 296 297 UsageNote: Inverse code is SBS 298 */ 299 SAS, 300 /** 301 * A relationship in which the source act starts after the target act ends. 302 303 304 UsageNote: Inverse code is EBS 305 */ 306 SAE, 307 /** 308 * 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) 309 310 311 UsageNote: Inverse code is SBSEAE 312 */ 313 DURING, 314 /** 315 * The source Act starts after start of the target Act, and ends with the target Act. 316 317 318 UsageNote: Inverse code is SBSECWE 319 */ 320 SASECWE, 321 /** 322 * A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time. 323 324 325 Usage Note: Inverse code is EBSORECWS 326 */ 327 EASORECWS, 328 /** 329 * A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time. 330 331 332 Usage Note: Inverse code is EBEORECW 333 */ 334 EAEORECW, 335 /** 336 * The source Act is independent of the time of the target Act. 337 338 339 UsageNote: This code is reflexive. Therefore its inverse code is itself. 340 */ 341 INDEPENDENT, 342 /** 343 * A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time. 344 345 346 Usage Note: Inverse code is SBEORSCWE 347 */ 348 SAEORSCWE, 349 /** 350 * A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time. 351 352 353 Usage Note: Inverse code is SBSORSCW 354 */ 355 SASORSCW, 356 /** 357 * A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time. 358 359 360 Usage Note: Inverse code is SAEORSCWE 361 */ 362 SBEORSCWE, 363 /** 364 * A relationship in which the source act's effective time overlaps the target act's effective time in any way. 365 366 367 UsageNote: This code is reflexive. Therefore its inverse code is itself. 368 */ 369 OVERLAP, 370 /** 371 * 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) 372 373 374 UsageNote: Inverse code is SBEEAE 375 */ 376 EDU, 377 /** 378 * The source Act contains the start of the target Act, and ends before the end of the target Act. 379 380 381 UsageNote: Inverse code is SASSBEEAS 382 */ 383 SBSEASEBE, 384 /** 385 * The source Act contains the start of the target Act. 386 387 388 UsageNote: Inverse code is SDU 389 */ 390 SBSEAS, 391 /** 392 * 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) 393 394 395 UsageNote: Inverse code is SBSEAS 396 */ 397 SDU, 398 /** 399 * 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). 400 401 402 UsageNote: Inverse code is EAS 403 */ 404 SBE, 405 /** 406 * 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). 407 408 409 UsageNote: Inverse code is EAE 410 */ 411 EBE, 412 /** 413 * The source Act starts before the start of the target Act, and ends before the end of the target Act. 414 415 416 UsageNote: Inverse code is SASEAE 417 */ 418 SBSEBE, 419 /** 420 * A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time. 421 422 423 Usage Note: Inverse code is EASORECWS 424 */ 425 EBSORECWS, 426 /** 427 * A relationship in which the source act ends before the target act starts. 428 429 430 UsageNote: Inverse code is SAE 431 */ 432 EBS, 433 /** 434 * A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time. 435 436 437 Usage Note: Inverse code is EAEORECW 438 */ 439 EBEORECW, 440 /** 441 * A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time. 442 443 444 Usage Note: Inverse code is SASORSCW 445 */ 446 SBSORSCW, 447 /** 448 * A relationship in which the source act begins before the target act begins. 449 450 451 UsageNote: Inverse code is SAS 452 */ 453 SBS, 454 /** 455 * A relationship in which the target act authorizes or certifies the source act. 456 */ 457 AUTH, 458 /** 459 * 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. 460 461 462 Examples: 463 464 465 466 a growth of Staphylococcus aureus may be considered the cause of an abscess 467 contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced 468 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 469 */ 470 CAUS, 471 /** 472 * The target act is a component of the source act, with no semantics regarding composition or aggregation implied. 473 */ 474 COMP, 475 /** 476 * 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. 477 */ 478 CTRLV, 479 /** 480 * 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. 481 482 483 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). 484 485 It is expected that this will be primarily used with _ActClassRecordOrganizer, BATTERY, and LIST 486 */ 487 MBR, 488 /** 489 * A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently. 490 491 492 UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode. 493 494 495 OpenIssue: Need Additional guidelines on when each approach should be used. 496 */ 497 STEP, 498 /** 499 * 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. 500 */ 501 ARR, 502 /** 503 * 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. 504 */ 505 DEP, 506 /** 507 * The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act. 508 509 510 UsageNote: In UML 1.1, this is a "composition" defined as: 511 "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." 512 */ 513 PART, 514 /** 515 * 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. 516 */ 517 COVBY, 518 /** 519 * 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. 520 */ 521 DRIV, 522 /** 523 * 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. 524 */ 525 ELNK, 526 /** 527 * 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. 528 529 530 Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies. 531 */ 532 EVID, 533 /** 534 * Description:The source act is aggravated by the target act. (Example "chest pain" EXACBY "exercise") 535 */ 536 EXACBY, 537 /** 538 * This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition. 539 */ 540 EXPL, 541 /** 542 * the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act. 543 544 545 UsageNote: This provides the semantics to document barriers to care 546 */ 547 INTF, 548 /** 549 * Items located 550 */ 551 ITEMSLOC, 552 /** 553 * 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. 554 */ 555 LIMIT, 556 /** 557 * Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act. 558 559 560 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". 561 */ 562 META, 563 /** 564 * 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. 565 */ 566 MFST, 567 /** 568 * Used to assign a "name" to a condition thread. Source is a condition node, target can be any service. 569 */ 570 NAME, 571 /** 572 * 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. 573 */ 574 OUTC, 575 /** 576 * 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. 577 */ 578 _ACTRELATIONSIPOBJECTIVE, 579 /** 580 * 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. 581 */ 582 OBJC, 583 /** 584 * 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. 585 */ 586 OBJF, 587 /** 588 * 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. 589 */ 590 GOAL, 591 /** 592 * 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. 593 */ 594 RISK, 595 /** 596 * 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. 597 */ 598 PERT, 599 /** 600 * 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. 601 */ 602 PREV, 603 /** 604 * 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. 605 */ 606 REFR, 607 /** 608 * Indicates that the source act makes use of (or will make use of) the information content of the target act. 609 610 611 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. 612 613 614 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. 615 */ 616 USE, 617 /** 618 * 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. 619 */ 620 REFV, 621 /** 622 * Description:The source act is wholly or partially alleviated by the target act. (Example "chest pain" RELVBY "sublingual nitroglycerin administration") 623 */ 624 RELVBY, 625 /** 626 * 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. 627 */ 628 SEQL, 629 /** 630 * 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. 631 */ 632 APND, 633 /** 634 * Indicates that the target observation(s) provide an initial reference for the source observation or observation group. 635 636 637 UsageConstraints: Both source and target must be Observations or specializations thereof. 638 */ 639 BSLN, 640 /** 641 * 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. 642 643 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. 644 */ 645 COMPLY, 646 /** 647 * The source act documents the target act. 648 */ 649 DOC, 650 /** 651 * 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. 652 */ 653 FLFS, 654 /** 655 * 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). 656 */ 657 OCCR, 658 /** 659 * Relates either an appointment request or an appointment to the order for the service being scheduled. 660 */ 661 OREF, 662 /** 663 * Associates a specific time (and associated resources) with a scheduling request or other intent. 664 */ 665 SCH, 666 /** 667 * 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). 668 */ 669 GEN, 670 /** 671 * 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. 672 */ 673 GEVL, 674 /** 675 * 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. 676 */ 677 INST, 678 /** 679 * 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). 680 681 682 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. 683 684 Name from source to target = "modifiesPrior" 685 686 Name from target to source = "modifiesByNew" 687 */ 688 MOD, 689 /** 690 * 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. 691 */ 692 MTCH, 693 /** 694 * A relationship between a source Act that provides more detailed properties to the target Act. 695 696 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. 697 698 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. 699 700 Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options. 701 */ 702 OPTN, 703 /** 704 * Description:A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated. 705 */ 706 RCHAL, 707 /** 708 * A relationship between a source Act that seeks to reverse or undo the action of the prior target Act. 709 710 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. 711 712 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. 713 */ 714 REV, 715 /** 716 * 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. 717 */ 718 RPLC, 719 /** 720 * 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. 721 */ 722 SUCC, 723 /** 724 * 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. 725 */ 726 UPDT, 727 /** 728 * The source is an excerpt from the target. 729 */ 730 XCRPT, 731 /** 732 * The source is a direct quote from the target. 733 */ 734 VRXCRPT, 735 /** 736 * 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.) 737 */ 738 XFRM, 739 /** 740 * 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). 741 */ 742 SPRT, 743 /** 744 * 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. 745 */ 746 SPRTBND, 747 /** 748 * Relates an Act to its subject Act that the first Act is primarily concerned with. 749 750 Examples 751 752 753 754 The first Act may be a ControlAct manipulating the subject Act 755 756 757 758 The first act is a region of interest (ROI) that defines a region within the subject Act. 759 760 761 762 The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose. 763 764 765 766 Constraints 767 768 An Act may have multiple subject acts. 769 770 Rationale 771 772 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. 773 */ 774 SUBJ, 775 /** 776 * The target observation qualifies (refines) the semantics of the source observation. 777 778 779 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. 780 */ 781 QUALF, 782 /** 783 * 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. 784 */ 785 SUMM, 786 /** 787 * Description:Indicates that the target Act represents the result of the source observation Act. 788 789 790 FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified 791 792 793 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. 794 795 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. 796 797 798 OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation. 799 */ 800 VALUE, 801 /** 802 * curative indication 803 */ 804 CURE, 805 /** 806 * adjunct curative indication 807 */ 808 CURE_ADJ, 809 /** 810 * adjunct mitigation 811 */ 812 MTGT_ADJ, 813 /** 814 * null 815 */ 816 RACT, 817 /** 818 * null 819 */ 820 SUGG, 821 /** 822 * added to help the parsers 823 */ 824 NULL; 825 public static V3ActRelationshipType fromCode(String codeString) throws Exception { 826 if (codeString == null || "".equals(codeString)) 827 return null; 828 if ("ART".equals(codeString)) 829 return ART; 830 if ("_ActClassTemporallyPertains".equals(codeString)) 831 return _ACTCLASSTEMPORALLYPERTAINS; 832 if ("_ActRelationshipAccounting".equals(codeString)) 833 return _ACTRELATIONSHIPACCOUNTING; 834 if ("_ActRelationshipCostTracking".equals(codeString)) 835 return _ACTRELATIONSHIPCOSTTRACKING; 836 if ("CHRG".equals(codeString)) 837 return CHRG; 838 if ("COST".equals(codeString)) 839 return COST; 840 if ("_ActRelationshipPosting".equals(codeString)) 841 return _ACTRELATIONSHIPPOSTING; 842 if ("CREDIT".equals(codeString)) 843 return CREDIT; 844 if ("DEBIT".equals(codeString)) 845 return DEBIT; 846 if ("_ActRelationshipConditional".equals(codeString)) 847 return _ACTRELATIONSHIPCONDITIONAL; 848 if ("CIND".equals(codeString)) 849 return CIND; 850 if ("PRCN".equals(codeString)) 851 return PRCN; 852 if ("RSON".equals(codeString)) 853 return RSON; 854 if ("BLOCK".equals(codeString)) 855 return BLOCK; 856 if ("DIAG".equals(codeString)) 857 return DIAG; 858 if ("IMM".equals(codeString)) 859 return IMM; 860 if ("ACTIMM".equals(codeString)) 861 return ACTIMM; 862 if ("PASSIMM".equals(codeString)) 863 return PASSIMM; 864 if ("MITGT".equals(codeString)) 865 return MITGT; 866 if ("RCVY".equals(codeString)) 867 return RCVY; 868 if ("PRYLX".equals(codeString)) 869 return PRYLX; 870 if ("TREAT".equals(codeString)) 871 return TREAT; 872 if ("ADJUNCT".equals(codeString)) 873 return ADJUNCT; 874 if ("MTREAT".equals(codeString)) 875 return MTREAT; 876 if ("PALLTREAT".equals(codeString)) 877 return PALLTREAT; 878 if ("SYMP".equals(codeString)) 879 return SYMP; 880 if ("TRIG".equals(codeString)) 881 return TRIG; 882 if ("_ActRelationshipTemporallyPertains".equals(codeString)) 883 return _ACTRELATIONSHIPTEMPORALLYPERTAINS; 884 if ("_ActRelationshipTemporallyPertainsApproximates".equals(codeString)) 885 return _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES; 886 if ("ENE".equals(codeString)) 887 return ENE; 888 if ("ECW".equals(codeString)) 889 return ECW; 890 if ("CONCURRENT".equals(codeString)) 891 return CONCURRENT; 892 if ("SBSECWE".equals(codeString)) 893 return SBSECWE; 894 if ("ENS".equals(codeString)) 895 return ENS; 896 if ("ECWS".equals(codeString)) 897 return ECWS; 898 if ("SNE".equals(codeString)) 899 return SNE; 900 if ("SCWE".equals(codeString)) 901 return SCWE; 902 if ("SNS".equals(codeString)) 903 return SNS; 904 if ("SCW".equals(codeString)) 905 return SCW; 906 if ("SCWSEBE".equals(codeString)) 907 return SCWSEBE; 908 if ("SCWSEAE".equals(codeString)) 909 return SCWSEAE; 910 if ("EAS".equals(codeString)) 911 return EAS; 912 if ("EAE".equals(codeString)) 913 return EAE; 914 if ("SASEAE".equals(codeString)) 915 return SASEAE; 916 if ("SBEEAE".equals(codeString)) 917 return SBEEAE; 918 if ("SASSBEEAS".equals(codeString)) 919 return SASSBEEAS; 920 if ("SBSEAE".equals(codeString)) 921 return SBSEAE; 922 if ("SAS".equals(codeString)) 923 return SAS; 924 if ("SAE".equals(codeString)) 925 return SAE; 926 if ("DURING".equals(codeString)) 927 return DURING; 928 if ("SASECWE".equals(codeString)) 929 return SASECWE; 930 if ("EASORECWS".equals(codeString)) 931 return EASORECWS; 932 if ("EAEORECW".equals(codeString)) 933 return EAEORECW; 934 if ("INDEPENDENT".equals(codeString)) 935 return INDEPENDENT; 936 if ("SAEORSCWE".equals(codeString)) 937 return SAEORSCWE; 938 if ("SASORSCW".equals(codeString)) 939 return SASORSCW; 940 if ("SBEORSCWE".equals(codeString)) 941 return SBEORSCWE; 942 if ("OVERLAP".equals(codeString)) 943 return OVERLAP; 944 if ("EDU".equals(codeString)) 945 return EDU; 946 if ("SBSEASEBE".equals(codeString)) 947 return SBSEASEBE; 948 if ("SBSEAS".equals(codeString)) 949 return SBSEAS; 950 if ("SDU".equals(codeString)) 951 return SDU; 952 if ("SBE".equals(codeString)) 953 return SBE; 954 if ("EBE".equals(codeString)) 955 return EBE; 956 if ("SBSEBE".equals(codeString)) 957 return SBSEBE; 958 if ("EBSORECWS".equals(codeString)) 959 return EBSORECWS; 960 if ("EBS".equals(codeString)) 961 return EBS; 962 if ("EBEORECW".equals(codeString)) 963 return EBEORECW; 964 if ("SBSORSCW".equals(codeString)) 965 return SBSORSCW; 966 if ("SBS".equals(codeString)) 967 return SBS; 968 if ("AUTH".equals(codeString)) 969 return AUTH; 970 if ("CAUS".equals(codeString)) 971 return CAUS; 972 if ("COMP".equals(codeString)) 973 return COMP; 974 if ("CTRLV".equals(codeString)) 975 return CTRLV; 976 if ("MBR".equals(codeString)) 977 return MBR; 978 if ("STEP".equals(codeString)) 979 return STEP; 980 if ("ARR".equals(codeString)) 981 return ARR; 982 if ("DEP".equals(codeString)) 983 return DEP; 984 if ("PART".equals(codeString)) 985 return PART; 986 if ("COVBY".equals(codeString)) 987 return COVBY; 988 if ("DRIV".equals(codeString)) 989 return DRIV; 990 if ("ELNK".equals(codeString)) 991 return ELNK; 992 if ("EVID".equals(codeString)) 993 return EVID; 994 if ("EXACBY".equals(codeString)) 995 return EXACBY; 996 if ("EXPL".equals(codeString)) 997 return EXPL; 998 if ("INTF".equals(codeString)) 999 return INTF; 1000 if ("ITEMSLOC".equals(codeString)) 1001 return ITEMSLOC; 1002 if ("LIMIT".equals(codeString)) 1003 return LIMIT; 1004 if ("META".equals(codeString)) 1005 return META; 1006 if ("MFST".equals(codeString)) 1007 return MFST; 1008 if ("NAME".equals(codeString)) 1009 return NAME; 1010 if ("OUTC".equals(codeString)) 1011 return OUTC; 1012 if ("_ActRelationsipObjective".equals(codeString)) 1013 return _ACTRELATIONSIPOBJECTIVE; 1014 if ("OBJC".equals(codeString)) 1015 return OBJC; 1016 if ("OBJF".equals(codeString)) 1017 return OBJF; 1018 if ("GOAL".equals(codeString)) 1019 return GOAL; 1020 if ("RISK".equals(codeString)) 1021 return RISK; 1022 if ("PERT".equals(codeString)) 1023 return PERT; 1024 if ("PREV".equals(codeString)) 1025 return PREV; 1026 if ("REFR".equals(codeString)) 1027 return REFR; 1028 if ("USE".equals(codeString)) 1029 return USE; 1030 if ("REFV".equals(codeString)) 1031 return REFV; 1032 if ("RELVBY".equals(codeString)) 1033 return RELVBY; 1034 if ("SEQL".equals(codeString)) 1035 return SEQL; 1036 if ("APND".equals(codeString)) 1037 return APND; 1038 if ("BSLN".equals(codeString)) 1039 return BSLN; 1040 if ("COMPLY".equals(codeString)) 1041 return COMPLY; 1042 if ("DOC".equals(codeString)) 1043 return DOC; 1044 if ("FLFS".equals(codeString)) 1045 return FLFS; 1046 if ("OCCR".equals(codeString)) 1047 return OCCR; 1048 if ("OREF".equals(codeString)) 1049 return OREF; 1050 if ("SCH".equals(codeString)) 1051 return SCH; 1052 if ("GEN".equals(codeString)) 1053 return GEN; 1054 if ("GEVL".equals(codeString)) 1055 return GEVL; 1056 if ("INST".equals(codeString)) 1057 return INST; 1058 if ("MOD".equals(codeString)) 1059 return MOD; 1060 if ("MTCH".equals(codeString)) 1061 return MTCH; 1062 if ("OPTN".equals(codeString)) 1063 return OPTN; 1064 if ("RCHAL".equals(codeString)) 1065 return RCHAL; 1066 if ("REV".equals(codeString)) 1067 return REV; 1068 if ("RPLC".equals(codeString)) 1069 return RPLC; 1070 if ("SUCC".equals(codeString)) 1071 return SUCC; 1072 if ("UPDT".equals(codeString)) 1073 return UPDT; 1074 if ("XCRPT".equals(codeString)) 1075 return XCRPT; 1076 if ("VRXCRPT".equals(codeString)) 1077 return VRXCRPT; 1078 if ("XFRM".equals(codeString)) 1079 return XFRM; 1080 if ("SPRT".equals(codeString)) 1081 return SPRT; 1082 if ("SPRTBND".equals(codeString)) 1083 return SPRTBND; 1084 if ("SUBJ".equals(codeString)) 1085 return SUBJ; 1086 if ("QUALF".equals(codeString)) 1087 return QUALF; 1088 if ("SUMM".equals(codeString)) 1089 return SUMM; 1090 if ("VALUE".equals(codeString)) 1091 return VALUE; 1092 if ("CURE".equals(codeString)) 1093 return CURE; 1094 if ("CURE.ADJ".equals(codeString)) 1095 return CURE_ADJ; 1096 if ("MTGT.ADJ".equals(codeString)) 1097 return MTGT_ADJ; 1098 if ("RACT".equals(codeString)) 1099 return RACT; 1100 if ("SUGG".equals(codeString)) 1101 return SUGG; 1102 throw new Exception("Unknown V3ActRelationshipType code '"+codeString+"'"); 1103 } 1104 public String toCode() { 1105 switch (this) { 1106 case ART: return "ART"; 1107 case _ACTCLASSTEMPORALLYPERTAINS: return "_ActClassTemporallyPertains"; 1108 case _ACTRELATIONSHIPACCOUNTING: return "_ActRelationshipAccounting"; 1109 case _ACTRELATIONSHIPCOSTTRACKING: return "_ActRelationshipCostTracking"; 1110 case CHRG: return "CHRG"; 1111 case COST: return "COST"; 1112 case _ACTRELATIONSHIPPOSTING: return "_ActRelationshipPosting"; 1113 case CREDIT: return "CREDIT"; 1114 case DEBIT: return "DEBIT"; 1115 case _ACTRELATIONSHIPCONDITIONAL: return "_ActRelationshipConditional"; 1116 case CIND: return "CIND"; 1117 case PRCN: return "PRCN"; 1118 case RSON: return "RSON"; 1119 case BLOCK: return "BLOCK"; 1120 case DIAG: return "DIAG"; 1121 case IMM: return "IMM"; 1122 case ACTIMM: return "ACTIMM"; 1123 case PASSIMM: return "PASSIMM"; 1124 case MITGT: return "MITGT"; 1125 case RCVY: return "RCVY"; 1126 case PRYLX: return "PRYLX"; 1127 case TREAT: return "TREAT"; 1128 case ADJUNCT: return "ADJUNCT"; 1129 case MTREAT: return "MTREAT"; 1130 case PALLTREAT: return "PALLTREAT"; 1131 case SYMP: return "SYMP"; 1132 case TRIG: return "TRIG"; 1133 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: return "_ActRelationshipTemporallyPertains"; 1134 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: return "_ActRelationshipTemporallyPertainsApproximates"; 1135 case ENE: return "ENE"; 1136 case ECW: return "ECW"; 1137 case CONCURRENT: return "CONCURRENT"; 1138 case SBSECWE: return "SBSECWE"; 1139 case ENS: return "ENS"; 1140 case ECWS: return "ECWS"; 1141 case SNE: return "SNE"; 1142 case SCWE: return "SCWE"; 1143 case SNS: return "SNS"; 1144 case SCW: return "SCW"; 1145 case SCWSEBE: return "SCWSEBE"; 1146 case SCWSEAE: return "SCWSEAE"; 1147 case EAS: return "EAS"; 1148 case EAE: return "EAE"; 1149 case SASEAE: return "SASEAE"; 1150 case SBEEAE: return "SBEEAE"; 1151 case SASSBEEAS: return "SASSBEEAS"; 1152 case SBSEAE: return "SBSEAE"; 1153 case SAS: return "SAS"; 1154 case SAE: return "SAE"; 1155 case DURING: return "DURING"; 1156 case SASECWE: return "SASECWE"; 1157 case EASORECWS: return "EASORECWS"; 1158 case EAEORECW: return "EAEORECW"; 1159 case INDEPENDENT: return "INDEPENDENT"; 1160 case SAEORSCWE: return "SAEORSCWE"; 1161 case SASORSCW: return "SASORSCW"; 1162 case SBEORSCWE: return "SBEORSCWE"; 1163 case OVERLAP: return "OVERLAP"; 1164 case EDU: return "EDU"; 1165 case SBSEASEBE: return "SBSEASEBE"; 1166 case SBSEAS: return "SBSEAS"; 1167 case SDU: return "SDU"; 1168 case SBE: return "SBE"; 1169 case EBE: return "EBE"; 1170 case SBSEBE: return "SBSEBE"; 1171 case EBSORECWS: return "EBSORECWS"; 1172 case EBS: return "EBS"; 1173 case EBEORECW: return "EBEORECW"; 1174 case SBSORSCW: return "SBSORSCW"; 1175 case SBS: return "SBS"; 1176 case AUTH: return "AUTH"; 1177 case CAUS: return "CAUS"; 1178 case COMP: return "COMP"; 1179 case CTRLV: return "CTRLV"; 1180 case MBR: return "MBR"; 1181 case STEP: return "STEP"; 1182 case ARR: return "ARR"; 1183 case DEP: return "DEP"; 1184 case PART: return "PART"; 1185 case COVBY: return "COVBY"; 1186 case DRIV: return "DRIV"; 1187 case ELNK: return "ELNK"; 1188 case EVID: return "EVID"; 1189 case EXACBY: return "EXACBY"; 1190 case EXPL: return "EXPL"; 1191 case INTF: return "INTF"; 1192 case ITEMSLOC: return "ITEMSLOC"; 1193 case LIMIT: return "LIMIT"; 1194 case META: return "META"; 1195 case MFST: return "MFST"; 1196 case NAME: return "NAME"; 1197 case OUTC: return "OUTC"; 1198 case _ACTRELATIONSIPOBJECTIVE: return "_ActRelationsipObjective"; 1199 case OBJC: return "OBJC"; 1200 case OBJF: return "OBJF"; 1201 case GOAL: return "GOAL"; 1202 case RISK: return "RISK"; 1203 case PERT: return "PERT"; 1204 case PREV: return "PREV"; 1205 case REFR: return "REFR"; 1206 case USE: return "USE"; 1207 case REFV: return "REFV"; 1208 case RELVBY: return "RELVBY"; 1209 case SEQL: return "SEQL"; 1210 case APND: return "APND"; 1211 case BSLN: return "BSLN"; 1212 case COMPLY: return "COMPLY"; 1213 case DOC: return "DOC"; 1214 case FLFS: return "FLFS"; 1215 case OCCR: return "OCCR"; 1216 case OREF: return "OREF"; 1217 case SCH: return "SCH"; 1218 case GEN: return "GEN"; 1219 case GEVL: return "GEVL"; 1220 case INST: return "INST"; 1221 case MOD: return "MOD"; 1222 case MTCH: return "MTCH"; 1223 case OPTN: return "OPTN"; 1224 case RCHAL: return "RCHAL"; 1225 case REV: return "REV"; 1226 case RPLC: return "RPLC"; 1227 case SUCC: return "SUCC"; 1228 case UPDT: return "UPDT"; 1229 case XCRPT: return "XCRPT"; 1230 case VRXCRPT: return "VRXCRPT"; 1231 case XFRM: return "XFRM"; 1232 case SPRT: return "SPRT"; 1233 case SPRTBND: return "SPRTBND"; 1234 case SUBJ: return "SUBJ"; 1235 case QUALF: return "QUALF"; 1236 case SUMM: return "SUMM"; 1237 case VALUE: return "VALUE"; 1238 case CURE: return "CURE"; 1239 case CURE_ADJ: return "CURE.ADJ"; 1240 case MTGT_ADJ: return "MTGT.ADJ"; 1241 case RACT: return "RACT"; 1242 case SUGG: return "SUGG"; 1243 default: return "?"; 1244 } 1245 } 1246 public String getSystem() { 1247 return "http://hl7.org/fhir/v3/ActRelationshipType"; 1248 } 1249 public String getDefinition() { 1250 switch (this) { 1251 case ART: return "Description: A directed association between a source Act and a target Act.\r\n\n \n Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute)"; 1252 case _ACTCLASSTEMPORALLYPERTAINS: return "ActClassTemporallyPertains"; 1253 case _ACTRELATIONSHIPACCOUNTING: return "Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element."; 1254 case _ACTRELATIONSHIPCOSTTRACKING: return "Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act."; 1255 case CHRG: return "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.\r\n\n The financial transaction will define the charge (bill) for delivery or performance of the service.\r\n\n 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."; 1256 case COST: return "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.\r\n\n The financial transaction will define the cost of delivery or performance of the service.\r\n\n 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."; 1257 case _ACTRELATIONSHIPPOSTING: return "Expresses values for describing the relationship between a FinancialTransaction and an Account."; 1258 case CREDIT: return "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."; 1259 case DEBIT: return "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."; 1260 case _ACTRELATIONSHIPCONDITIONAL: return "Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred"; 1261 case CIND: return "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."; 1262 case PRCN: return "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."; 1263 case RSON: return "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. \r\n\n \n 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."; 1264 case BLOCK: return "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."; 1265 case DIAG: return "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."; 1266 case IMM: return "Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease)"; 1267 case ACTIMM: return "Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease)"; 1268 case PASSIMM: return "Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease)."; 1269 case MITGT: return "The source act removes or lessens the occurrence or effect of the target act."; 1270 case RCVY: return "Definition: The source act is performed to recover from the effects of the target act."; 1271 case PRYLX: return "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."; 1272 case TREAT: return "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."; 1273 case ADJUNCT: return "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."; 1274 case MTREAT: return "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."; 1275 case PALLTREAT: return "Description: The source act is intended to provide palliation for the effects of the target act."; 1276 case SYMP: return "Description: The source act is intented to provide symptomatic relief for the effects of the target act."; 1277 case TRIG: return "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.\r\n\n \n 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."; 1278 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: return "Abstract collector for ActRelationhsip types that relate two acts by their timing."; 1279 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: return "Abstract collector for ActRelationship types that relate two acts by their approximate timing."; 1280 case ENE: return "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.\r\n\n \n Usage Note: Inverse code is ENS"; 1281 case ECW: return "A relationship in which the source act's effective time ends with the end of the target act's effective time.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1282 case CONCURRENT: return "A relationship in which the source act's effective time is the same as the target act's effective time.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1283 case SBSECWE: return "The source Act starts before the start of the target Act, and ends with the target Act.\r\n\n \n UsageNote: Inverse code is SASECWE"; 1284 case ENS: return "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.\r\n\n \n Usage Note: Inverse code is ENE"; 1285 case ECWS: return "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).\r\n\n \n UsageNote: Inverse code is SCWE"; 1286 case SNE: return "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.\r\n\n \n Usage Note: Inverse code is SNS"; 1287 case SCWE: return "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).\r\n\n \n UsageNote: Inverse code is SBSECWS"; 1288 case SNS: return "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.\r\n\n \n Usage Note: Inverse code is SNE"; 1289 case SCW: return "A relationship in which the source act's effective time starts with the start of the target act's effective time.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1290 case SCWSEBE: return "The source Act starts with.the target Act and ends before the end of the target Act.\r\n\n \n UsageNote: Inverse code is SCWSEAE"; 1291 case SCWSEAE: return "The source Act starts with the target Act, and ends after the end of the target Act."; 1292 case EAS: return "A relationship in which the source act ends after the target act starts.\r\n\n \n UsageNote: Inverse code is SBE"; 1293 case EAE: return "A relationship in which the source act ends after the target act ends.\r\n\n \n UsageNote: Inverse code is EBE"; 1294 case SASEAE: return "The source Act starts after start of the target Act and ends after end of the target Act.\r\n\n \n UsageNote: Inverse code is SBSEBE"; 1295 case SBEEAE: return "The source Act contains the end of the target Act.\r\n\n \n UsageNote: Inverse code is EDU"; 1296 case SASSBEEAS: return "The source Act start after the start of the target Act, and contains the end of the target Act.\r\n\n \n UsageNote: Inverse code is SBSEASEBE"; 1297 case SBSEAE: return "The source Act contains the time of the target Act.\r\n\n \n UsageNote: Inverse code is DURING"; 1298 case SAS: return "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).\r\n\n \n UsageNote: Inverse code is SBS"; 1299 case SAE: return "A relationship in which the source act starts after the target act ends.\r\n\n \n UsageNote: Inverse code is EBS"; 1300 case DURING: return "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)\r\n\n \n UsageNote: Inverse code is SBSEAE"; 1301 case SASECWE: return "The source Act starts after start of the target Act, and ends with the target Act.\r\n\n \n UsageNote: Inverse code is SBSECWE"; 1302 case EASORECWS: return "A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time.\r\n\n \n Usage Note: Inverse code is EBSORECWS"; 1303 case EAEORECW: return "A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time.\r\n\n \n Usage Note: Inverse code is EBEORECW"; 1304 case INDEPENDENT: return "The source Act is independent of the time of the target Act.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1305 case SAEORSCWE: return "A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time.\r\n\n \n Usage Note: Inverse code is SBEORSCWE"; 1306 case SASORSCW: return "A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time.\r\n\n \n Usage Note: Inverse code is SBSORSCW"; 1307 case SBEORSCWE: return "A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time.\r\n\n \n Usage Note: Inverse code is SAEORSCWE"; 1308 case OVERLAP: return "A relationship in which the source act's effective time overlaps the target act's effective time in any way.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1309 case EDU: return "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)\r\n\n \n UsageNote: Inverse code is SBEEAE"; 1310 case SBSEASEBE: return "The source Act contains the start of the target Act, and ends before the end of the target Act.\r\n\n \n UsageNote: Inverse code is SASSBEEAS"; 1311 case SBSEAS: return "The source Act contains the start of the target Act.\r\n\n \n UsageNote: Inverse code is SDU"; 1312 case SDU: return "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)\r\n\n \n UsageNote: Inverse code is SBSEAS"; 1313 case SBE: return "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).\r\n\n \n UsageNote: Inverse code is EAS"; 1314 case EBE: return "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).\r\n\n \n UsageNote: Inverse code is EAE"; 1315 case SBSEBE: return "The source Act starts before the start of the target Act, and ends before the end of the target Act.\r\n\n \n UsageNote: Inverse code is SASEAE"; 1316 case EBSORECWS: return "A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time.\r\n\n \n Usage Note: Inverse code is EASORECWS"; 1317 case EBS: return "A relationship in which the source act ends before the target act starts.\r\n\n \n UsageNote: Inverse code is SAE"; 1318 case EBEORECW: return "A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time.\r\n\n \n Usage Note: Inverse code is EAEORECW"; 1319 case SBSORSCW: return "A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time.\r\n\n \n Usage Note: Inverse code is SASORSCW"; 1320 case SBS: return "A relationship in which the source act begins before the target act begins.\r\n\n \n UsageNote: Inverse code is SAS"; 1321 case AUTH: return "A relationship in which the target act authorizes or certifies the source act."; 1322 case CAUS: return "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.\r\n\n \n Examples:\n \r\n\n \n a growth of Staphylococcus aureus may be considered the cause of an abscess\n contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced\n 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"; 1323 case COMP: return "The target act is a component of the source act, with no semantics regarding composition or aggregation implied."; 1324 case CTRLV: return "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."; 1325 case MBR: return "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.\r\n\n \n 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).\r\n\n It is expected that this will be primarily used with _ActClassRecordOrganizer, BATTERY, and LIST"; 1326 case STEP: return "A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.\r\n\n \n UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode.\r\n\n \n OpenIssue: Need Additional guidelines on when each approach should be used."; 1327 case ARR: return "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."; 1328 case DEP: return "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."; 1329 case PART: return "The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act.\r\n\n \n UsageNote: In UML 1.1, this is a \"composition\" defined as: \n \"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.\""; 1330 case COVBY: return "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."; 1331 case DRIV: return "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."; 1332 case ELNK: return "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."; 1333 case EVID: return "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.\r\n\n \n Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies."; 1334 case EXACBY: return "Description:The source act is aggravated by the target act. (Example \"chest pain\" EXACBY \"exercise\")"; 1335 case EXPL: return "This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition."; 1336 case INTF: return "the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act.\r\n\n \n UsageNote: This provides the semantics to document barriers to care"; 1337 case ITEMSLOC: return "Items located"; 1338 case LIMIT: return "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."; 1339 case META: return "Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act.\r\n\n \n 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\"."; 1340 case MFST: return "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."; 1341 case NAME: return "Used to assign a \"name\" to a condition thread. Source is a condition node, target can be any service."; 1342 case OUTC: return "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."; 1343 case _ACTRELATIONSIPOBJECTIVE: return "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."; 1344 case OBJC: return "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."; 1345 case OBJF: return "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."; 1346 case GOAL: return "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."; 1347 case RISK: return "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."; 1348 case PERT: return "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."; 1349 case PREV: return "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."; 1350 case REFR: return "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."; 1351 case USE: return "Indicates that the source act makes use of (or will make use of) the information content of the target act.\r\n\n \n 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.\r\n\n \n 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."; 1352 case REFV: return "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."; 1353 case RELVBY: return "Description:The source act is wholly or partially alleviated by the target act. (Example \"chest pain\" RELVBY \"sublingual nitroglycerin administration\")"; 1354 case SEQL: return "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."; 1355 case APND: return "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."; 1356 case BSLN: return "Indicates that the target observation(s) provide an initial reference for the source observation or observation group.\r\n\n \n UsageConstraints: Both source and target must be Observations or specializations thereof."; 1357 case COMPLY: return "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.\r\n\n 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."; 1358 case DOC: return "The source act documents the target act."; 1359 case FLFS: return "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."; 1360 case OCCR: return "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)."; 1361 case OREF: return "Relates either an appointment request or an appointment to the order for the service being scheduled."; 1362 case SCH: return "Associates a specific time (and associated resources) with a scheduling request or other intent."; 1363 case GEN: return "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)."; 1364 case GEVL: return "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."; 1365 case INST: return "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."; 1366 case MOD: return "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).\r\n\n \n 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.\r\n\n Name from source to target = \"modifiesPrior\"\r\n\n Name from target to source = \"modifiesByNew\""; 1367 case MTCH: return "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."; 1368 case OPTN: return "A relationship between a source Act that provides more detailed properties to the target Act.\r\n\n 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.\r\n\n 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.\r\n\n Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options."; 1369 case RCHAL: return "Description:A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated."; 1370 case REV: return "A relationship between a source Act that seeks to reverse or undo the action of the prior target Act.\r\n\n 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.\r\n\n 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."; 1371 case RPLC: return "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."; 1372 case SUCC: return "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."; 1373 case UPDT: return "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."; 1374 case XCRPT: return "The source is an excerpt from the target."; 1375 case VRXCRPT: return "The source is a direct quote from the target."; 1376 case XFRM: return "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.)"; 1377 case SPRT: return "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)."; 1378 case SPRTBND: return "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."; 1379 case SUBJ: return "Relates an Act to its subject Act that the first Act is primarily concerned with.\r\n\n Examples\r\n\n \n \n The first Act may be a ControlAct manipulating the subject Act \r\n\n \n \n The first act is a region of interest (ROI) that defines a region within the subject Act.\r\n\n \n \n The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.\r\n\n \n \n Constraints\r\n\n An Act may have multiple subject acts.\r\n\n Rationale\r\n\n 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."; 1380 case QUALF: return "The target observation qualifies (refines) the semantics of the source observation.\r\n\n \n 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."; 1381 case SUMM: return "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."; 1382 case VALUE: return "Description:Indicates that the target Act represents the result of the source observation Act.\r\n\n \n FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified\r\n\n \n 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.\r\n\n 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.\r\n\n \n OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation."; 1383 case CURE: return "curative indication"; 1384 case CURE_ADJ: return "adjunct curative indication"; 1385 case MTGT_ADJ: return "adjunct mitigation"; 1386 case RACT: return ""; 1387 case SUGG: return ""; 1388 default: return "?"; 1389 } 1390 } 1391 public String getDisplay() { 1392 switch (this) { 1393 case ART: return "act relationship type"; 1394 case _ACTCLASSTEMPORALLYPERTAINS: return "ActClassTemporallyPertains"; 1395 case _ACTRELATIONSHIPACCOUNTING: return "ActRelationshipAccounting"; 1396 case _ACTRELATIONSHIPCOSTTRACKING: return "ActRelationshipCostTracking"; 1397 case CHRG: return "has charge"; 1398 case COST: return "has cost"; 1399 case _ACTRELATIONSHIPPOSTING: return "ActRelationshipPosting"; 1400 case CREDIT: return "has credit"; 1401 case DEBIT: return "has debit"; 1402 case _ACTRELATIONSHIPCONDITIONAL: return "ActRelationshipConditional"; 1403 case CIND: return "has contra-indication"; 1404 case PRCN: return "has pre-condition"; 1405 case RSON: return "has reason"; 1406 case BLOCK: return "blocks"; 1407 case DIAG: return "diagnoses"; 1408 case IMM: return "immunization against"; 1409 case ACTIMM: return "active immunization against"; 1410 case PASSIMM: return "passive immunization against"; 1411 case MITGT: return "mitigates"; 1412 case RCVY: return "recovers"; 1413 case PRYLX: return "prophylaxis of"; 1414 case TREAT: return "treats"; 1415 case ADJUNCT: return "adjunctive treatment"; 1416 case MTREAT: return "maintenance treatment"; 1417 case PALLTREAT: return "palliates"; 1418 case SYMP: return "symptomatic relief"; 1419 case TRIG: return "has trigger"; 1420 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: return "ActRelationshipTemporallyPertains"; 1421 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: return "ActRelationshipTemporallyPertainsApproximates"; 1422 case ENE: return "ends near end"; 1423 case ECW: return "ends concurrent with"; 1424 case CONCURRENT: return "concurrent with"; 1425 case SBSECWE: return "starts before start of, ends with"; 1426 case ENS: return "ends near start"; 1427 case ECWS: return "ends concurrent with start of"; 1428 case SNE: return "starts near end"; 1429 case SCWE: return "starts concurrent with end of"; 1430 case SNS: return "starts near start"; 1431 case SCW: return "starts concurrent with"; 1432 case SCWSEBE: return "starts with. ends before end of"; 1433 case SCWSEAE: return "starts with, ends after end of"; 1434 case EAS: return "ends after start of"; 1435 case EAE: return "ends after end of"; 1436 case SASEAE: return "starts after start of, ends after end of"; 1437 case SBEEAE: return "contains end of"; 1438 case SASSBEEAS: return "start after start of, contains end of"; 1439 case SBSEAE: return "contains time of"; 1440 case SAS: return "starts after start of"; 1441 case SAE: return "starts after end of"; 1442 case DURING: return "occurs during"; 1443 case SASECWE: return "starts after start of, ends with"; 1444 case EASORECWS: return "ends after or concurrent with start of"; 1445 case EAEORECW: return "ends after or concurrent with end of"; 1446 case INDEPENDENT: return "independent of time of"; 1447 case SAEORSCWE: return "starts after or concurrent with end of"; 1448 case SASORSCW: return "starts after or concurrent with start of"; 1449 case SBEORSCWE: return "starts before or concurrent with end of"; 1450 case OVERLAP: return "overlaps with"; 1451 case EDU: return "ends during"; 1452 case SBSEASEBE: return "contains start of, ends before end of"; 1453 case SBSEAS: return "contains start of"; 1454 case SDU: return "starts during"; 1455 case SBE: return "starts before end of"; 1456 case EBE: return "ends before end of"; 1457 case SBSEBE: return "starts before start of, ends before end of"; 1458 case EBSORECWS: return "ends before or concurrent with start of"; 1459 case EBS: return "ends before start of"; 1460 case EBEORECW: return "ends before or concurrent with end of"; 1461 case SBSORSCW: return "starts before or concurrent with start of"; 1462 case SBS: return "starts before start of"; 1463 case AUTH: return "authorized by"; 1464 case CAUS: return "is etiology for"; 1465 case COMP: return "has component"; 1466 case CTRLV: return "has control variable"; 1467 case MBR: return "has member"; 1468 case STEP: return "has step"; 1469 case ARR: return "arrival"; 1470 case DEP: return "departure"; 1471 case PART: return "has part"; 1472 case COVBY: return "covered by"; 1473 case DRIV: return "is derived from"; 1474 case ELNK: return "episodeLink"; 1475 case EVID: return "provides evidence for"; 1476 case EXACBY: return "exacerbated by"; 1477 case EXPL: return "has explanation"; 1478 case INTF: return "interfered by"; 1479 case ITEMSLOC: return "items located"; 1480 case LIMIT: return "limited by"; 1481 case META: return "has metadata"; 1482 case MFST: return "is manifestation of"; 1483 case NAME: return "assigns name"; 1484 case OUTC: return "has outcome"; 1485 case _ACTRELATIONSIPOBJECTIVE: return "Act Relationsip Objective"; 1486 case OBJC: return "has continuing objective"; 1487 case OBJF: return "has final objective"; 1488 case GOAL: return "has goal"; 1489 case RISK: return "has risk"; 1490 case PERT: return "has pertinent information"; 1491 case PREV: return "has previous instance"; 1492 case REFR: return "refers to"; 1493 case USE: return "uses"; 1494 case REFV: return "has reference values"; 1495 case RELVBY: return "relieved by"; 1496 case SEQL: return "is sequel"; 1497 case APND: return "is appendage"; 1498 case BSLN: return "has baseline"; 1499 case COMPLY: return "complies with"; 1500 case DOC: return "documents"; 1501 case FLFS: return "fulfills"; 1502 case OCCR: return "occurrence"; 1503 case OREF: return "references order"; 1504 case SCH: return "schedules request"; 1505 case GEN: return "has generalization"; 1506 case GEVL: return "evaluates (goal)"; 1507 case INST: return "instantiates (master)"; 1508 case MOD: return "modifies"; 1509 case MTCH: return "matches (trigger)"; 1510 case OPTN: return "has option"; 1511 case RCHAL: return "re-challenge"; 1512 case REV: return "reverses"; 1513 case RPLC: return "replaces"; 1514 case SUCC: return "succeeds"; 1515 case UPDT: return "updates (condition)"; 1516 case XCRPT: return "Excerpts"; 1517 case VRXCRPT: return "Excerpt verbatim"; 1518 case XFRM: return "transformation"; 1519 case SPRT: return "has support"; 1520 case SPRTBND: return "has bounded support"; 1521 case SUBJ: return "has subject"; 1522 case QUALF: return "has qualifier"; 1523 case SUMM: return "summarized by"; 1524 case VALUE: return "has value"; 1525 case CURE: return "curative indication"; 1526 case CURE_ADJ: return "adjunct curative indication"; 1527 case MTGT_ADJ: return "adjunct mitigation"; 1528 case RACT: return "RACT"; 1529 case SUGG: return "SUGG"; 1530 default: return "?"; 1531 } 1532 } 1533 1534 1535} 1536