001package org.hl7.fhir.r4.model.codesystems; 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, Jan 30, 2019 16:19-0500 for FHIR v4.0.0 033 034import org.hl7.fhir.exceptions.FHIRException; 035 036public enum V3ActRelationshipType { 037 038 /** 039 * Description: A directed association between a source Act and a target Act. 040 * 041 * 042 * Usage Note: This code should never be transmitted in an instance as the value 043 * of ActRelationship.typeCode (attribute) 044 */ 045 ART, 046 /** 047 * ActClassTemporallyPertains 048 */ 049 _ACTCLASSTEMPORALLYPERTAINS, 050 /** 051 * Codes that describe the relationship between an Act and a financial 052 * instrument such as a financial transaction, account or invoice element. 053 */ 054 _ACTRELATIONSHIPACCOUNTING, 055 /** 056 * Expresses values for describing the relationship relationship between an 057 * InvoiceElement or InvoiceElementGroup and a billable act. 058 */ 059 _ACTRELATIONSHIPCOSTTRACKING, 060 /** 061 * A relationship that provides an ability to associate a financial transaction 062 * (target) as a charge to a clinical act (source). A clinical act may have a 063 * charge associated with the execution or delivery of the service. 064 * 065 * The financial transaction will define the charge (bill) for delivery or 066 * performance of the service. 067 * 068 * Charges and costs are distinct terms. A charge defines what is charged or 069 * billed to another organization or entity within an organization. The cost 070 * defines what it costs an organization to perform or deliver a service or 071 * product. 072 */ 073 CHRG, 074 /** 075 * A relationship that provides an ability to associate a financial transaction 076 * (target) as a cost to a clinical act (source). A clinical act may have an 077 * inherit cost associated with the execution or delivery of the service. 078 * 079 * The financial transaction will define the cost of delivery or performance of 080 * the service. 081 * 082 * Charges and costs are distinct terms. A charge defines what is charged or 083 * billed to another organization or entity within an organization. The cost 084 * defines what it costs an organization to perform or deliver a service or 085 * product. 086 */ 087 COST, 088 /** 089 * Expresses values for describing the relationship between a 090 * FinancialTransaction and an Account. 091 */ 092 _ACTRELATIONSHIPPOSTING, 093 /** 094 * A credit relationship ties a financial transaction (target) to an account 095 * (source). A credit, once applied (posted), may have either a positive or 096 * negative effect on the account balance, depending on the type of account. An 097 * asset account credit will decrease the account balance. A non-asset account 098 * credit will decrease the account balance. 099 */ 100 CREDIT, 101 /** 102 * A debit relationship ties a financial transaction (target) to an account 103 * (source). A debit, once applied (posted), may have either a positive or 104 * negative effect on the account balance, depending on the type of account. An 105 * asset account debit will increase the account balance. A non-asset account 106 * debit will decrease the account balance. 107 */ 108 DEBIT, 109 /** 110 * Specifies under what circumstances (target Act) the source-Act may, must, 111 * must not or has occurred 112 */ 113 _ACTRELATIONSHIPCONDITIONAL, 114 /** 115 * A contraindication is just a negation of a reason, i.e. it gives a condition 116 * under which the action is not to be done. Both, source and target can be any 117 * kind of service; target service is in criterion mood. How the strength of a 118 * contraindication is expressed (e.g., relative, absolute) is left as an open 119 * issue. The priorityNumber attribute could be used. 120 */ 121 CIND, 122 /** 123 * A requirement to be true before a service is performed. The target can be any 124 * service in criterion mood. For multiple pre-conditions a conjunction 125 * attribute (AND, OR, XOR) is applicable. 126 */ 127 PRCN, 128 /** 129 * Description: The reason or rationale for a service. A reason link is weaker 130 * than a trigger, it only suggests that some service may be or might have been 131 * a reason for some action, but not that this reason requires/required the 132 * action to be taken. Also, as opposed to the trigger, there is no strong 133 * timely relation between the reason and the action. As well as providing 134 * various types of information about the rationale for a service, the RSON act 135 * relationship is routinely used between a SBADM act and an OBS act to describe 136 * the indication for use of a medication. Child concepts may be used to 137 * describe types of indication. 138 * 139 * 140 * Discussion: In prior releases, the code "SUGG" (suggests) was expressed as 141 * "an inversion of the reason link." That code has been retired in favor of the 142 * inversion indicator that is an attribute of ActRelationship. 143 */ 144 RSON, 145 /** 146 * Definition: The source act is performed to block the effects of the target 147 * act. This act relationship should be used when describing near miss type 148 * incidents where potential harm could have occurred, but the action described 149 * in the source act blocked the potential harmful effects of the incident 150 * actually occurring. 151 */ 152 BLOCK, 153 /** 154 * Description: The source act is intended to help establish the presence of a 155 * (an adverse) situation described by the target act. This is not limited to 156 * diseases but can apply to any adverse situation or condition of medical or 157 * technical nature. 158 */ 159 DIAG, 160 /** 161 * Description: The source act is intented to provide immunity against the 162 * effects of the target act (the target act describes an infectious disease) 163 */ 164 IMM, 165 /** 166 * Description: The source act is intended to provide active immunity against 167 * the effects of the target act (the target act describes an infectious 168 * disease) 169 */ 170 ACTIMM, 171 /** 172 * Description: The source act is intended to provide passive immunity against 173 * the effects of the target act (the target act describes an infectious 174 * disease). 175 */ 176 PASSIMM, 177 /** 178 * The source act removes or lessens the occurrence or effect of the target act. 179 */ 180 MITGT, 181 /** 182 * Definition: The source act is performed to recover from the effects of the 183 * target act. 184 */ 185 RCVY, 186 /** 187 * Description: The source act is intended to reduce the risk of of an adverse 188 * situation to emerge as described by the target act. This is not limited to 189 * diseases but can apply to any adverse situation or condition of medical or 190 * technical nature. 191 */ 192 PRYLX, 193 /** 194 * Description: The source act is intended to improve a pre-existing adverse 195 * situation described by the target act. This is not limited to diseases but 196 * can apply to any adverse situation or condition of medical or technical 197 * nature. 198 */ 199 TREAT, 200 /** 201 * Description: The source act is intended to offer an additional treatment for 202 * the management or cure of a pre-existing adverse situation described by the 203 * target act. This is not limited to diseases but can apply to any adverse 204 * situation or condition of medical or technical nature. It is not a 205 * requirement that the non-adjunctive treatment is explicitly specified. 206 */ 207 ADJUNCT, 208 /** 209 * Description: The source act is intended to provide long term maintenance 210 * improvement or management of a pre-existing adverse situation described by 211 * the target act. This is not limited to diseases but can apply to any adverse 212 * situation or condition of medical or technical nature. 213 */ 214 MTREAT, 215 /** 216 * Description: The source act is intended to provide palliation for the effects 217 * of the target act. 218 */ 219 PALLTREAT, 220 /** 221 * Description: The source act is intented to provide symptomatic relief for the 222 * effects of the target act. 223 */ 224 SYMP, 225 /** 226 * A pre-condition that if true should result in the source Act being executed. 227 * The target is in typically in criterion mood. When reported after the fact 228 * (i.e. the criterion has been met) it may be in Event mood. A delay between 229 * the trigger and the triggered action can be specified. 230 * 231 * 232 * Discussion: This includes the concept of a required act for a service or 233 * financial instrument such as an insurance plan or policy. In such cases, the 234 * trigger is the occurrence of a specific condition such as coverage limits 235 * being exceeded. 236 */ 237 TRIG, 238 /** 239 * Abstract collector for ActRelationhsip types that relate two acts by their 240 * timing. 241 */ 242 _ACTRELATIONSHIPTEMPORALLYPERTAINS, 243 /** 244 * Abstract collector for ActRelationship types that relate two acts by their 245 * approximate timing. 246 */ 247 _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES, 248 /** 249 * A relationship in which the source act's effective time ends near the end of 250 * the target act's effective time. Near is defined separately as a time 251 * interval. 252 * 253 * 254 * Usage Note: Inverse code is ENS 255 */ 256 ENE, 257 /** 258 * A relationship in which the source act's effective time ends with the end of 259 * the target act's effective time. 260 * 261 * 262 * UsageNote: This code is reflexive. Therefore its inverse code is itself. 263 */ 264 ECW, 265 /** 266 * A relationship in which the source act's effective time is the same as the 267 * target act's effective time. 268 * 269 * 270 * UsageNote: This code is reflexive. Therefore its inverse code is itself. 271 */ 272 CONCURRENT, 273 /** 274 * The source Act starts before the start of the target Act, and ends with the 275 * target Act. 276 * 277 * 278 * UsageNote: Inverse code is SASECWE 279 */ 280 SBSECWE, 281 /** 282 * A relationship in which the source act's effective time ends near the start 283 * of the target act's effective time. Near is defined separately as a time 284 * interval. 285 * 286 * 287 * Usage Note: Inverse code is ENE 288 */ 289 ENS, 290 /** 291 * The source Act ends when the target act starts (i.e. if we say "ActOne ECWS 292 * ActTwo", it means that ActOne ends when ActTwo starts, therefore ActOne is 293 * the source and ActTwo is the target). 294 * 295 * 296 * UsageNote: Inverse code is SCWE 297 */ 298 ECWS, 299 /** 300 * A relationship in which the source act's effective time starts near the end 301 * of the target act's effective time. Near is defined separately as a time 302 * interval. 303 * 304 * 305 * Usage Note: Inverse code is SNS 306 */ 307 SNE, 308 /** 309 * The source Act starts when the target act ends (i.e. if we say "ActOne SCWE 310 * ActTwo", it means that ActOne starts when ActTwo ends, therefore ActOne is 311 * the source and ActTwo is the target). 312 * 313 * 314 * UsageNote: Inverse code is SBSECWS 315 */ 316 SCWE, 317 /** 318 * A relationship in which the source act's effective time starts near the start 319 * of the target act's effective time. Near is defined separately as a time 320 * interval. 321 * 322 * 323 * Usage Note: Inverse code is SNE 324 */ 325 SNS, 326 /** 327 * A relationship in which the source act's effective time starts with the start 328 * of the target act's effective time. 329 * 330 * 331 * UsageNote: This code is reflexive. Therefore its inverse code is itself. 332 */ 333 SCW, 334 /** 335 * The source Act starts with.the target Act and ends before the end of the 336 * target Act. 337 * 338 * 339 * UsageNote: Inverse code is SCWSEAE 340 */ 341 SCWSEBE, 342 /** 343 * The source Act starts with the target Act, and ends after the end of the 344 * target Act. 345 */ 346 SCWSEAE, 347 /** 348 * A relationship in which the source act ends after the target act starts. 349 * 350 * 351 * UsageNote: Inverse code is SBE 352 */ 353 EAS, 354 /** 355 * A relationship in which the source act ends after the target act ends. 356 * 357 * 358 * UsageNote: Inverse code is EBE 359 */ 360 EAE, 361 /** 362 * The source Act starts after start of the target Act and ends after end of the 363 * target Act. 364 * 365 * 366 * UsageNote: Inverse code is SBSEBE 367 */ 368 SASEAE, 369 /** 370 * The source Act contains the end of the target Act. 371 * 372 * 373 * UsageNote: Inverse code is EDU 374 */ 375 SBEEAE, 376 /** 377 * The source Act start after the start of the target Act, and contains the end 378 * of the target Act. 379 * 380 * 381 * UsageNote: Inverse code is SBSEASEBE 382 */ 383 SASSBEEAS, 384 /** 385 * The source Act contains the time of the target Act. 386 * 387 * 388 * UsageNote: Inverse code is DURING 389 */ 390 SBSEAE, 391 /** 392 * The source Act starts after the start of the target Act (i.e. if we say 393 * "ActOne SAS ActTwo", it means that ActOne starts after the start of ActTwo, 394 * therefore ActOne is the source and ActTwo is the target). 395 * 396 * 397 * UsageNote: Inverse code is SBS 398 */ 399 SAS, 400 /** 401 * A relationship in which the source act starts after the target act ends. 402 * 403 * 404 * UsageNote: Inverse code is EBS 405 */ 406 SAE, 407 /** 408 * A relationship in which the source act's effective time is wholly within the 409 * target act's effective time (including end points, as defined in the act's 410 * effective times) 411 * 412 * 413 * UsageNote: Inverse code is SBSEAE 414 */ 415 DURING, 416 /** 417 * The source Act starts after start of the target Act, and ends with the target 418 * Act. 419 * 420 * 421 * UsageNote: Inverse code is SBSECWE 422 */ 423 SASECWE, 424 /** 425 * A relationship in which the source act's effective time ends after or 426 * concurrent with the start of the target act's effective time. 427 * 428 * 429 * Usage Note: Inverse code is EBSORECWS 430 */ 431 EASORECWS, 432 /** 433 * A relationship in which the source act's effective time ends after or 434 * concurrent with the end of the target act's effective time. 435 * 436 * 437 * Usage Note: Inverse code is EBEORECW 438 */ 439 EAEORECW, 440 /** 441 * The source Act is independent of the time of the target Act. 442 * 443 * 444 * UsageNote: This code is reflexive. Therefore its inverse code is itself. 445 */ 446 INDEPENDENT, 447 /** 448 * A relationship in which the source act's effective time starts after or 449 * concurrent with the end of the target act's effective time. 450 * 451 * 452 * Usage Note: Inverse code is SBEORSCWE 453 */ 454 SAEORSCWE, 455 /** 456 * A relationship in which the source act's effective time starts after or 457 * concurrent with the start of the target act's effective time. 458 * 459 * 460 * Usage Note: Inverse code is SBSORSCW 461 */ 462 SASORSCW, 463 /** 464 * A relationship in which the source act's effective time starts before or 465 * concurrent with the end of the target act's effective time. 466 * 467 * 468 * Usage Note: Inverse code is SAEORSCWE 469 */ 470 SBEORSCWE, 471 /** 472 * A relationship in which the source act's effective time overlaps the target 473 * act's effective time in any way. 474 * 475 * 476 * UsageNote: This code is reflexive. Therefore its inverse code is itself. 477 */ 478 OVERLAP, 479 /** 480 * A relationship in which the source act ends within the target act's effective 481 * time (including end points, as defined in the act's effective times) 482 * 483 * 484 * UsageNote: Inverse code is SBEEAE 485 */ 486 EDU, 487 /** 488 * The source Act contains the start of the target Act, and ends before the end 489 * of the target Act. 490 * 491 * 492 * UsageNote: Inverse code is SASSBEEAS 493 */ 494 SBSEASEBE, 495 /** 496 * The source Act contains the start of the target Act. 497 * 498 * 499 * UsageNote: Inverse code is SDU 500 */ 501 SBSEAS, 502 /** 503 * A relationship in which the source act starts within the target act's 504 * effective time (including end points, as defined in the act's effective 505 * times) 506 * 507 * 508 * UsageNote: Inverse code is SBSEAS 509 */ 510 SDU, 511 /** 512 * The source Act starts before the end of the target Act (i.e. if we say 513 * "ActOne SBE ActTwo", it means that ActOne starts before the end of ActTwo, 514 * therefore ActOne is the source and ActTwo is the target). 515 * 516 * 517 * UsageNote: Inverse code is EAS 518 */ 519 SBE, 520 /** 521 * The source Act ends before the end of the target Act (i.e. if we say "ActOne 522 * EBE ActTwo", it means that ActOne ends before the end of ActTwo, therefore 523 * ActOne is the source and ActTwo is the target). 524 * 525 * 526 * UsageNote: Inverse code is EAE 527 */ 528 EBE, 529 /** 530 * The source Act starts before the start of the target Act, and ends before the 531 * end of the target Act. 532 * 533 * 534 * UsageNote: Inverse code is SASEAE 535 */ 536 SBSEBE, 537 /** 538 * A relationship in which the source act's effective time ends before or 539 * concurrent with the start of the target act's effective time. 540 * 541 * 542 * Usage Note: Inverse code is EASORECWS 543 */ 544 EBSORECWS, 545 /** 546 * A relationship in which the source act ends before the target act starts. 547 * 548 * 549 * UsageNote: Inverse code is SAE 550 */ 551 EBS, 552 /** 553 * A relationship in which the source act's effective time ends before or 554 * concurrent with the end of the target act's effective time. 555 * 556 * 557 * Usage Note: Inverse code is EAEORECW 558 */ 559 EBEORECW, 560 /** 561 * A relationship in which the source act's effective time starts before or 562 * concurrent with the start of the target act's effective time. 563 * 564 * 565 * Usage Note: Inverse code is SASORSCW 566 */ 567 SBSORSCW, 568 /** 569 * A relationship in which the source act begins before the target act begins. 570 * 571 * 572 * UsageNote: Inverse code is SAS 573 */ 574 SBS, 575 /** 576 * A relationship in which the target act authorizes or certifies the source 577 * act. 578 */ 579 AUTH, 580 /** 581 * Description: An assertion that an act was the cause of another act.This is 582 * stronger and more specific than the support link. The source (cause) is 583 * typically an observation, but may be any act, while the target may be any 584 * act. 585 * 586 * 587 * Examples: 588 * 589 * 590 * 591 * a growth of Staphylococcus aureus may be considered the cause of an abscess 592 * contamination of the infusion bag was deemed to be the cause of the infection 593 * that the patient experienced lack of staff on the shift was deemed to be a 594 * supporting factor (proximal factor) causing the patient safety incident where 595 * the patient fell out of bed because the bed-sides had not been put up which 596 * caused the night patient to fall out of bed 597 */ 598 CAUS, 599 /** 600 * The target act is a component of the source act, with no semantics regarding 601 * composition or aggregation implied. 602 */ 603 COMP, 604 /** 605 * A relationship from an Act to a Control Variable. For example, if a Device 606 * makes an Observation, this relates the Observation to its Control Variables 607 * documenting the device's settings that influenced the observation. 608 */ 609 CTRLV, 610 /** 611 * The target Acts are aggregated by the source Act. Target Acts may have 612 * independent existence, participate in multiple ActRelationships, and do not 613 * contribute to the meaning of the source. 614 * 615 * 616 * UsageNotes: This explicitly represents the conventional notion of 617 * aggregation. The target Act is part of a collection of Acts (no implication 618 * is made of cardinality, a source of Acts may contain zero, one, or more 619 * member target Acts). 620 * 621 * It is expected that this will be primarily used with 622 * _ActClassRecordOrganizer, BATTERY, and LIST 623 */ 624 MBR, 625 /** 626 * A collection of sub-services as steps or subtasks performed for the source 627 * service. Services may be performed sequentially or concurrently. 628 * 629 * 630 * UsageNotes: Sequence of steps may be indicated by use of 631 * _ActRelationshipTemporallyPertains, as well as via 632 * ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, 633 * Target.priorityCode. 634 * 635 * 636 * OpenIssue: Need Additional guidelines on when each approach should be used. 637 */ 638 STEP, 639 /** 640 * The relationship that links to a Transportation Act (target) from another Act 641 * (source) indicating that the subject of the source Act entered into the 642 * source Act by means of the target Transportation act. 643 */ 644 ARR, 645 /** 646 * The relationship that links to a Transportation Act (target) from another Act 647 * (source) indicating that the subject of the source Act departed from the 648 * source Act by means of the target Transportation act. 649 */ 650 DEP, 651 /** 652 * The source Act is a composite of the target Acts. The target Acts do not have 653 * an existence independent of the source Act. 654 * 655 * 656 * UsageNote: In UML 1.1, this is a "composition" defined as: "A form of 657 * aggregation with strong ownership and coincident lifetime as part of the 658 * whole. Parts with non-fixed multiplicity may be created after the composite 659 * itself, but once created they live and die with it (i.e., they share 660 * lifetimes). Such parts can also be explicitly removed before the death of the 661 * composite. Composition may be recursive." 662 */ 663 PART, 664 /** 665 * A relationship in which the source act is covered by or is under the 666 * authority of a target act. A financial instrument such as an Invoice Element 667 * is covered by one or more specific instances of an Insurance Policy. 668 */ 669 COVBY, 670 /** 671 * Associates a derived Act with its input parameters. E.G., an anion-gap 672 * observation can be associated as being derived from given sodium-, 673 * (potassium-,), chloride-, and bicarbonate-observations. The narrative content 674 * (Act.text) of a source act is wholly machine-derived from the collection of 675 * target acts. 676 */ 677 DRIV, 678 /** 679 * Expresses an association that links two instances of the same act over time, 680 * indicating that the instance are part of the same episode, e.g. linking two 681 * condition nodes for episode of illness; linking two encounters for episode of 682 * encounter. 683 */ 684 ELNK, 685 /** 686 * Indicates that the target Act provides evidence in support of the action 687 * represented by the source Act. The target is not a 'reason' for the source 688 * act, but rather gives supporting information on why the source act is an 689 * appropriate course of action. Possible targets might be clinical trial 690 * results, journal articles, similar successful therapies, etc. 691 * 692 * 693 * Rationale: Provides a mechanism for conveying clinical justification for 694 * non-approved or otherwise non-traditional therapies. 695 */ 696 EVID, 697 /** 698 * Description:The source act is aggravated by the target act. (Example "chest 699 * pain" EXACBY "exercise") 700 */ 701 EXACBY, 702 /** 703 * This is the inversion of support. Used to indicate that a given observation 704 * is explained by another observation or condition. 705 */ 706 EXPL, 707 /** 708 * the target act documents a set of circumstances (events, risks) which prevent 709 * successful completion, or degradation of quality of, the source Act. 710 * 711 * 712 * UsageNote: This provides the semantics to document barriers to care 713 */ 714 INTF, 715 /** 716 * Items located 717 */ 718 ITEMSLOC, 719 /** 720 * A relationship that limits or restricts the source act by the elements of the 721 * target act. For example, an authorization may be limited by a financial 722 * amount (up to $500). Target Act must be in EVN.CRIT mood. 723 */ 724 LIMIT, 725 /** 726 * Definition: Indicates that the attributes and associations of the target act 727 * provide metadata (for example, identifiers, authorship, etc.) for the source 728 * act. 729 * 730 * 731 * Constraint: Source act must have either a mood code that is not "EVN" (event) 732 * or its "isCriterion" attribute must set to "true". Target act must be an Act 733 * with a mood code of EVN and with isCriterionInd attribute set to "true". 734 */ 735 META, 736 /** 737 * An assertion that a new observation may be the manifestation of another 738 * existing observation or action. This assumption is attributed to the same 739 * actor who asserts the manifestation. This is stronger and more specific than 740 * an inverted support link. For example, an agitated appearance can be asserted 741 * to be the manifestation (effect) of a known hyperthyroxia. This expresses 742 * that one might not have realized a symptom if it would not be a common 743 * manifestation of a known condition. The target (cause) may be any service, 744 * while the source (manifestation) must be an observation. 745 */ 746 MFST, 747 /** 748 * Used to assign a "name" to a condition thread. Source is a condition node, 749 * target can be any service. 750 */ 751 NAME, 752 /** 753 * An observation that should follow or does actually follow as a result or 754 * consequence of a condition or action (sometimes called "post-conditional".) 755 * Target must be an observation as a goal, risk or any criterion. For complex 756 * outcomes a conjunction attribute (AND, OR, XOR) can be used. An outcome link 757 * is often inverted to describe an outcome assessment. 758 */ 759 OUTC, 760 /** 761 * The target act is a desired outcome of the source act. Source is any act 762 * (typically an intervention). Target must be an observation in criterion mood. 763 */ 764 _ACTRELATIONSIPOBJECTIVE, 765 /** 766 * A desired state that a service action aims to maintain. E.g., keep systolic 767 * blood pressure between 90 and 110 mm Hg. Source is an intervention service. 768 * Target must be an observation in criterion mood. 769 */ 770 OBJC, 771 /** 772 * A desired outcome that a service action aims to meet finally. Source is any 773 * service (typically an intervention). Target must be an observation in 774 * criterion mood. 775 */ 776 OBJF, 777 /** 778 * A goal that one defines given a patient's health condition. Subsequently 779 * planned actions aim to meet that goal. Source is an observation or condition 780 * node, target must be an observation in goal mood. 781 */ 782 GOAL, 783 /** 784 * A noteworthy undesired outcome of a patient's condition that is either likely 785 * enough to become an issue or is less likely but dangerous enough to be 786 * addressed. 787 */ 788 RISK, 789 /** 790 * This is a very unspecific relationship from one item of clinical information 791 * to another. It does not judge about the role the pertinent information plays. 792 */ 793 PERT, 794 /** 795 * A relationship in which the target act is a predecessor instance to the 796 * source act. Generally each of these instances is similar, but no identical. 797 * In healthcare coverage it is used to link a claim item to a previous claim 798 * item that might have claimed for the same set of services. 799 */ 800 PREV, 801 /** 802 * A relationship in which the target act is referred to by the source act. This 803 * permits a simple reference relationship that distinguishes between the 804 * referent and the referee. 805 */ 806 REFR, 807 /** 808 * Indicates that the source act makes use of (or will make use of) the 809 * information content of the target act. 810 * 811 * 812 * UsageNotes: A usage relationship only makes sense if the target act is 813 * authored and occurs independently of the source act. Otherwise a simpler 814 * relationship such as COMP would be appropriate. 815 * 816 * 817 * Rationale: There is a need when defining a clinical trial protocol to 818 * indicate that the protocol makes use of other protocol or treatment 819 * specifications. This is stronger than the assertion of "references". 820 * References may exist without usage, and in a clinical trial protocol is 821 * common to assert both: what other specifications does this trial use and what 822 * other specifications does it merely reference. 823 */ 824 USE, 825 /** 826 * Reference ranges are essentially descriptors of a class of result values 827 * assumed to be "normal", "abnormal", or "critical." Those can vary by sex, 828 * age, or any other criterion. Source and target are observations, the target 829 * is in criterion mood. This link type can act as a trigger in case of alarms 830 * being triggered by critical results. 831 */ 832 REFV, 833 /** 834 * Description:The source act is wholly or partially alleviated by the target 835 * act. (Example "chest pain" RELVBY "sublingual nitroglycerin administration") 836 */ 837 RELVBY, 838 /** 839 * An act relationship indicating that the source act follows the target act. 840 * The source act should in principle represent the same kind of act as the 841 * target. Source and target need not have the same mood code (mood will often 842 * differ). The target of a sequel is called antecedent. Examples for sequel 843 * relationships are: revision, transformation, derivation from a prototype (as 844 * a specialization is a derivation of a generalization), followup, realization, 845 * instantiation. 846 */ 847 SEQL, 848 /** 849 * An addendum (source) to an existing service object (target), containing 850 * supplemental information. The addendum is itself an original service object 851 * linked to the supplemented service object. The supplemented service object 852 * remains in place and its content and status are unaltered. 853 */ 854 APND, 855 /** 856 * Indicates that the target observation(s) provide an initial reference for the 857 * source observation or observation group. 858 * 859 * 860 * UsageConstraints: Both source and target must be Observations or 861 * specializations thereof. 862 */ 863 BSLN, 864 /** 865 * Description:The source act complies with, adheres to, conforms to, or is 866 * permissible under (in whole or in part) the policy, contract, agreement, law, 867 * conformance criteria, certification guidelines or requirement conveyed by the 868 * target act. 869 * 870 * Examples for compliance relationships are: audits of adherence with a 871 * security policy, certificate of conformance to system certification 872 * requirements, or consent directive in compliance with or permissible under a 873 * privacy policy. 874 */ 875 COMPLY, 876 /** 877 * The source act documents the target act. 878 */ 879 DOC, 880 /** 881 * The source act fulfills (in whole or in part) the target act. Source act must 882 * be in a mood equal or more actual than the target act. 883 */ 884 FLFS, 885 /** 886 * The source act is a single occurrence of a repeatable target act. The source 887 * and target act can be in any mood on the "completion track" but the source 888 * act must be as far as or further along the track than the target act (i.e., 889 * the occurrence of an intent can be an event but not vice versa). 890 */ 891 OCCR, 892 /** 893 * Relates either an appointment request or an appointment to the order for the 894 * service being scheduled. 895 */ 896 OREF, 897 /** 898 * Associates a specific time (and associated resources) with a scheduling 899 * request or other intent. 900 */ 901 SCH, 902 /** 903 * The generalization relationship can be used to express categorical knowledge 904 * about services (e.g., amilorid, triamterene, and spironolactone have the 905 * common generalization potassium sparing diuretic). 906 */ 907 GEN, 908 /** 909 * A goal-evaluation links an observation (intent or actual) to a goal to 910 * indicate that the observation evaluates the goal. Given the goal and the 911 * observation, a "goal distance" (e.g., goal to observation) can be 912 * "calculated" and need not be sent explicitly. 913 */ 914 GEVL, 915 /** 916 * Used to capture the link between a potential service ("master" or plan) and 917 * an actual service, where the actual service instantiates the potential 918 * service. The instantiation may override the master's defaults. 919 */ 920 INST, 921 /** 922 * Definition: Used to link a newer version or 'snapshot' of a business object 923 * (source) to an older version or 'snapshot' of the same business object 924 * (target). 925 * 926 * 927 * Usage:The identifier of the Act should be the same for both source and 928 * target. If the identifiers are distinct, RPLC should be used instead. 929 * 930 * Name from source to target = "modifiesPrior" 931 * 932 * Name from target to source = "modifiesByNew" 933 */ 934 MOD, 935 /** 936 * A trigger-match links an actual service (e.g., an observation or procedure 937 * that took place) with a service in criterion mood. For example if the trigger 938 * is "observation of pain" and pain is actually observed, and if that 939 * pain-observation caused the trigger to fire, that pain-observation can be 940 * linked with the trigger. 941 */ 942 MTCH, 943 /** 944 * A relationship between a source Act that provides more detailed properties to 945 * the target Act. 946 * 947 * The source act thus is a specialization of the target act, but instead of 948 * mentioning all the inherited properties it only mentions new property 949 * bindings or refinements. 950 * 951 * The typical use case is to specify certain alternative variants of one kind 952 * of Act. The priorityNumber attribute is used to weigh refinements as 953 * preferred over other alternative refinements. 954 * 955 * Example: several routing options for a drug are specified as one 956 * SubstanceAdministration for the general treatment with attached refinements 957 * for the various routing options. 958 */ 959 OPTN, 960 /** 961 * Description:A relationship in which the target act is carried out to 962 * determine whether an effect attributed to the source act can be recreated. 963 */ 964 RCHAL, 965 /** 966 * A relationship between a source Act that seeks to reverse or undo the action 967 * of the prior target Act. 968 * 969 * Example: A posted financial transaction (e.g., a debit transaction) was 970 * applied in error and must be reversed (e.g., by a credit transaction) the 971 * credit transaction is identified as an undo (or reversal) of the prior target 972 * transaction. 973 * 974 * Constraints: the "completion track" mood of the target Act must be equally or 975 * more "actual" than the source act. I.e., when the target act is EVN the 976 * source act can be EVN, or any INT. If the target act is INT, the source act 977 * can be INT. 978 */ 979 REV, 980 /** 981 * A replacement source act replaces an existing target act. The state of the 982 * target act being replaced becomes obselete, but the act is typically still 983 * retained in the system for historical reference. The source and target must 984 * be of the same type. 985 */ 986 RPLC, 987 /** 988 * Definition: A new act that carries forward the intention of the original act, 989 * but does not completely replace it. The status of the predecessor act must be 990 * 'completed'. The original act is the target act and the successor is the 991 * source act. 992 */ 993 SUCC, 994 /** 995 * A condition thread relationship specifically links condition nodes together 996 * to form a condition thread. The source is the new condition node and the 997 * target links to the most recent node of the existing condition thread. 998 */ 999 UPDT, 1000 /** 1001 * The source is an excerpt from the target. 1002 */ 1003 XCRPT, 1004 /** 1005 * The source is a direct quote from the target. 1006 */ 1007 VRXCRPT, 1008 /** 1009 * Used when the target Act is a transformation of the source Act. (For 1010 * instance, used to show that a CDA document is a transformation of a DICOM SR 1011 * document.) 1012 */ 1013 XFRM, 1014 /** 1015 * Used to indicate that an existing service is suggesting evidence for a new 1016 * observation. The assumption of support is attributed to the same actor who 1017 * asserts the observation. Source must be an observation, target may be any 1018 * service (e.g., to indicate a status post). 1019 */ 1020 SPRT, 1021 /** 1022 * A specialization of "has support" (SPRT), used to relate a secondary 1023 * observation to a Region of Interest on a multidimensional observation, if the 1024 * ROI specifies the true boundaries of the secondary observation as opposed to 1025 * only marking the approximate area. For example, if the start and end of an ST 1026 * elevation episode is visible in an EKG, this relation would indicate the ROI 1027 * bounds the "ST elevation" observation -- the ROI defines the true beginning 1028 * and ending of the episode. Conversely, if a ROI simply contains ST elevation, 1029 * but it does not define the bounds (start and end) of the episode, the more 1030 * general "has support" relation is used. Likewise, if a ROI on an image 1031 * defines the true bounds of a "1st degree burn", the relation "has bounded 1032 * support" is used; but if the ROI only points to the approximate area of the 1033 * burn, the general "has support" relation is used. 1034 */ 1035 SPRTBND, 1036 /** 1037 * Relates an Act to its subject Act that the first Act is primarily concerned 1038 * with. 1039 * 1040 * Examples 1041 * 1042 * 1043 * 1044 * The first Act may be a ControlAct manipulating the subject Act 1045 * 1046 * 1047 * 1048 * The first act is a region of interest (ROI) that defines a region within the 1049 * subject Act. 1050 * 1051 * 1052 * 1053 * The first act is a reporting or notification Act, that echos the subject Act 1054 * for a specific new purpose. 1055 * 1056 * 1057 * 1058 * Constraints 1059 * 1060 * An Act may have multiple subject acts. 1061 * 1062 * Rationale 1063 * 1064 * The ActRelationshipType "has subject" is similar to the ParticipationType 1065 * "subject", Acts that primarily operate on physical subjects use the 1066 * Participation, those Acts that primarily operate on other Acts (other 1067 * information) use the ActRelationship. 1068 */ 1069 SUBJ, 1070 /** 1071 * The target observation qualifies (refines) the semantics of the source 1072 * observation. 1073 * 1074 * 1075 * UsageNote: This is not intended to replace concept refinement and 1076 * qualification via vocabulary. It is used when there are multiple components 1077 * which together provide the complete understanding of the source Act. 1078 */ 1079 QUALF, 1080 /** 1081 * An act that contains summary values for a list or set of subordinate acts. 1082 * For example, a summary of transactions for a particular accounting period. 1083 */ 1084 SUMM, 1085 /** 1086 * Description:Indicates that the target Act represents the result of the source 1087 * observation Act. 1088 * 1089 * 1090 * FormalConstraint: Source Act must be an Observation or specialization 1091 * there-of. Source Act must not have the value attribute specified 1092 * 1093 * 1094 * UsageNote: This relationship allows the result of an observation to be fully 1095 * expressed as RIM acts as opposed to being embedded in the value attribute. 1096 * For example, sending a Document act as the result of an imaging observation, 1097 * sending a list of Procedures and/or other acts as the result of a medical 1098 * history observation. 1099 * 1100 * The valueNegationInd attribute on the source Act has the same semantics of 1101 * "negated finding" when it applies to the target of a VALUE ActRelationship as 1102 * it does to the value attribute. On the other hand, if the 1103 * ActRelationship.negationInd is true for a VALUE ActRelationship, that means 1104 * the specified observation does not have the indicated value but does not 1105 * imply a negated finding. Because the semantics are extremely close, it is 1106 * recommended that Observation.valueNegationInd be used, not 1107 * ActRelationship.negationInd. 1108 * 1109 * 1110 * OpenIssue: The implications of negationInd on ActRelationship and the 1111 * valueNegationind on Observation. 1112 */ 1113 VALUE, 1114 /** 1115 * curative indication 1116 */ 1117 CURE, 1118 /** 1119 * adjunct curative indication 1120 */ 1121 CURE_ADJ, 1122 /** 1123 * adjunct mitigation 1124 */ 1125 MTGT_ADJ, 1126 /** 1127 * null 1128 */ 1129 RACT, 1130 /** 1131 * null 1132 */ 1133 SUGG, 1134 /** 1135 * added to help the parsers 1136 */ 1137 NULL; 1138 1139 public static V3ActRelationshipType fromCode(String codeString) throws FHIRException { 1140 if (codeString == null || "".equals(codeString)) 1141 return null; 1142 if ("ART".equals(codeString)) 1143 return ART; 1144 if ("_ActClassTemporallyPertains".equals(codeString)) 1145 return _ACTCLASSTEMPORALLYPERTAINS; 1146 if ("_ActRelationshipAccounting".equals(codeString)) 1147 return _ACTRELATIONSHIPACCOUNTING; 1148 if ("_ActRelationshipCostTracking".equals(codeString)) 1149 return _ACTRELATIONSHIPCOSTTRACKING; 1150 if ("CHRG".equals(codeString)) 1151 return CHRG; 1152 if ("COST".equals(codeString)) 1153 return COST; 1154 if ("_ActRelationshipPosting".equals(codeString)) 1155 return _ACTRELATIONSHIPPOSTING; 1156 if ("CREDIT".equals(codeString)) 1157 return CREDIT; 1158 if ("DEBIT".equals(codeString)) 1159 return DEBIT; 1160 if ("_ActRelationshipConditional".equals(codeString)) 1161 return _ACTRELATIONSHIPCONDITIONAL; 1162 if ("CIND".equals(codeString)) 1163 return CIND; 1164 if ("PRCN".equals(codeString)) 1165 return PRCN; 1166 if ("RSON".equals(codeString)) 1167 return RSON; 1168 if ("BLOCK".equals(codeString)) 1169 return BLOCK; 1170 if ("DIAG".equals(codeString)) 1171 return DIAG; 1172 if ("IMM".equals(codeString)) 1173 return IMM; 1174 if ("ACTIMM".equals(codeString)) 1175 return ACTIMM; 1176 if ("PASSIMM".equals(codeString)) 1177 return PASSIMM; 1178 if ("MITGT".equals(codeString)) 1179 return MITGT; 1180 if ("RCVY".equals(codeString)) 1181 return RCVY; 1182 if ("PRYLX".equals(codeString)) 1183 return PRYLX; 1184 if ("TREAT".equals(codeString)) 1185 return TREAT; 1186 if ("ADJUNCT".equals(codeString)) 1187 return ADJUNCT; 1188 if ("MTREAT".equals(codeString)) 1189 return MTREAT; 1190 if ("PALLTREAT".equals(codeString)) 1191 return PALLTREAT; 1192 if ("SYMP".equals(codeString)) 1193 return SYMP; 1194 if ("TRIG".equals(codeString)) 1195 return TRIG; 1196 if ("_ActRelationshipTemporallyPertains".equals(codeString)) 1197 return _ACTRELATIONSHIPTEMPORALLYPERTAINS; 1198 if ("_ActRelationshipTemporallyPertainsApproximates".equals(codeString)) 1199 return _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES; 1200 if ("ENE".equals(codeString)) 1201 return ENE; 1202 if ("ECW".equals(codeString)) 1203 return ECW; 1204 if ("CONCURRENT".equals(codeString)) 1205 return CONCURRENT; 1206 if ("SBSECWE".equals(codeString)) 1207 return SBSECWE; 1208 if ("ENS".equals(codeString)) 1209 return ENS; 1210 if ("ECWS".equals(codeString)) 1211 return ECWS; 1212 if ("SNE".equals(codeString)) 1213 return SNE; 1214 if ("SCWE".equals(codeString)) 1215 return SCWE; 1216 if ("SNS".equals(codeString)) 1217 return SNS; 1218 if ("SCW".equals(codeString)) 1219 return SCW; 1220 if ("SCWSEBE".equals(codeString)) 1221 return SCWSEBE; 1222 if ("SCWSEAE".equals(codeString)) 1223 return SCWSEAE; 1224 if ("EAS".equals(codeString)) 1225 return EAS; 1226 if ("EAE".equals(codeString)) 1227 return EAE; 1228 if ("SASEAE".equals(codeString)) 1229 return SASEAE; 1230 if ("SBEEAE".equals(codeString)) 1231 return SBEEAE; 1232 if ("SASSBEEAS".equals(codeString)) 1233 return SASSBEEAS; 1234 if ("SBSEAE".equals(codeString)) 1235 return SBSEAE; 1236 if ("SAS".equals(codeString)) 1237 return SAS; 1238 if ("SAE".equals(codeString)) 1239 return SAE; 1240 if ("DURING".equals(codeString)) 1241 return DURING; 1242 if ("SASECWE".equals(codeString)) 1243 return SASECWE; 1244 if ("EASORECWS".equals(codeString)) 1245 return EASORECWS; 1246 if ("EAEORECW".equals(codeString)) 1247 return EAEORECW; 1248 if ("INDEPENDENT".equals(codeString)) 1249 return INDEPENDENT; 1250 if ("SAEORSCWE".equals(codeString)) 1251 return SAEORSCWE; 1252 if ("SASORSCW".equals(codeString)) 1253 return SASORSCW; 1254 if ("SBEORSCWE".equals(codeString)) 1255 return SBEORSCWE; 1256 if ("OVERLAP".equals(codeString)) 1257 return OVERLAP; 1258 if ("EDU".equals(codeString)) 1259 return EDU; 1260 if ("SBSEASEBE".equals(codeString)) 1261 return SBSEASEBE; 1262 if ("SBSEAS".equals(codeString)) 1263 return SBSEAS; 1264 if ("SDU".equals(codeString)) 1265 return SDU; 1266 if ("SBE".equals(codeString)) 1267 return SBE; 1268 if ("EBE".equals(codeString)) 1269 return EBE; 1270 if ("SBSEBE".equals(codeString)) 1271 return SBSEBE; 1272 if ("EBSORECWS".equals(codeString)) 1273 return EBSORECWS; 1274 if ("EBS".equals(codeString)) 1275 return EBS; 1276 if ("EBEORECW".equals(codeString)) 1277 return EBEORECW; 1278 if ("SBSORSCW".equals(codeString)) 1279 return SBSORSCW; 1280 if ("SBS".equals(codeString)) 1281 return SBS; 1282 if ("AUTH".equals(codeString)) 1283 return AUTH; 1284 if ("CAUS".equals(codeString)) 1285 return CAUS; 1286 if ("COMP".equals(codeString)) 1287 return COMP; 1288 if ("CTRLV".equals(codeString)) 1289 return CTRLV; 1290 if ("MBR".equals(codeString)) 1291 return MBR; 1292 if ("STEP".equals(codeString)) 1293 return STEP; 1294 if ("ARR".equals(codeString)) 1295 return ARR; 1296 if ("DEP".equals(codeString)) 1297 return DEP; 1298 if ("PART".equals(codeString)) 1299 return PART; 1300 if ("COVBY".equals(codeString)) 1301 return COVBY; 1302 if ("DRIV".equals(codeString)) 1303 return DRIV; 1304 if ("ELNK".equals(codeString)) 1305 return ELNK; 1306 if ("EVID".equals(codeString)) 1307 return EVID; 1308 if ("EXACBY".equals(codeString)) 1309 return EXACBY; 1310 if ("EXPL".equals(codeString)) 1311 return EXPL; 1312 if ("INTF".equals(codeString)) 1313 return INTF; 1314 if ("ITEMSLOC".equals(codeString)) 1315 return ITEMSLOC; 1316 if ("LIMIT".equals(codeString)) 1317 return LIMIT; 1318 if ("META".equals(codeString)) 1319 return META; 1320 if ("MFST".equals(codeString)) 1321 return MFST; 1322 if ("NAME".equals(codeString)) 1323 return NAME; 1324 if ("OUTC".equals(codeString)) 1325 return OUTC; 1326 if ("_ActRelationsipObjective".equals(codeString)) 1327 return _ACTRELATIONSIPOBJECTIVE; 1328 if ("OBJC".equals(codeString)) 1329 return OBJC; 1330 if ("OBJF".equals(codeString)) 1331 return OBJF; 1332 if ("GOAL".equals(codeString)) 1333 return GOAL; 1334 if ("RISK".equals(codeString)) 1335 return RISK; 1336 if ("PERT".equals(codeString)) 1337 return PERT; 1338 if ("PREV".equals(codeString)) 1339 return PREV; 1340 if ("REFR".equals(codeString)) 1341 return REFR; 1342 if ("USE".equals(codeString)) 1343 return USE; 1344 if ("REFV".equals(codeString)) 1345 return REFV; 1346 if ("RELVBY".equals(codeString)) 1347 return RELVBY; 1348 if ("SEQL".equals(codeString)) 1349 return SEQL; 1350 if ("APND".equals(codeString)) 1351 return APND; 1352 if ("BSLN".equals(codeString)) 1353 return BSLN; 1354 if ("COMPLY".equals(codeString)) 1355 return COMPLY; 1356 if ("DOC".equals(codeString)) 1357 return DOC; 1358 if ("FLFS".equals(codeString)) 1359 return FLFS; 1360 if ("OCCR".equals(codeString)) 1361 return OCCR; 1362 if ("OREF".equals(codeString)) 1363 return OREF; 1364 if ("SCH".equals(codeString)) 1365 return SCH; 1366 if ("GEN".equals(codeString)) 1367 return GEN; 1368 if ("GEVL".equals(codeString)) 1369 return GEVL; 1370 if ("INST".equals(codeString)) 1371 return INST; 1372 if ("MOD".equals(codeString)) 1373 return MOD; 1374 if ("MTCH".equals(codeString)) 1375 return MTCH; 1376 if ("OPTN".equals(codeString)) 1377 return OPTN; 1378 if ("RCHAL".equals(codeString)) 1379 return RCHAL; 1380 if ("REV".equals(codeString)) 1381 return REV; 1382 if ("RPLC".equals(codeString)) 1383 return RPLC; 1384 if ("SUCC".equals(codeString)) 1385 return SUCC; 1386 if ("UPDT".equals(codeString)) 1387 return UPDT; 1388 if ("XCRPT".equals(codeString)) 1389 return XCRPT; 1390 if ("VRXCRPT".equals(codeString)) 1391 return VRXCRPT; 1392 if ("XFRM".equals(codeString)) 1393 return XFRM; 1394 if ("SPRT".equals(codeString)) 1395 return SPRT; 1396 if ("SPRTBND".equals(codeString)) 1397 return SPRTBND; 1398 if ("SUBJ".equals(codeString)) 1399 return SUBJ; 1400 if ("QUALF".equals(codeString)) 1401 return QUALF; 1402 if ("SUMM".equals(codeString)) 1403 return SUMM; 1404 if ("VALUE".equals(codeString)) 1405 return VALUE; 1406 if ("CURE".equals(codeString)) 1407 return CURE; 1408 if ("CURE.ADJ".equals(codeString)) 1409 return CURE_ADJ; 1410 if ("MTGT.ADJ".equals(codeString)) 1411 return MTGT_ADJ; 1412 if ("RACT".equals(codeString)) 1413 return RACT; 1414 if ("SUGG".equals(codeString)) 1415 return SUGG; 1416 throw new FHIRException("Unknown V3ActRelationshipType code '" + codeString + "'"); 1417 } 1418 1419 public String toCode() { 1420 switch (this) { 1421 case ART: 1422 return "ART"; 1423 case _ACTCLASSTEMPORALLYPERTAINS: 1424 return "_ActClassTemporallyPertains"; 1425 case _ACTRELATIONSHIPACCOUNTING: 1426 return "_ActRelationshipAccounting"; 1427 case _ACTRELATIONSHIPCOSTTRACKING: 1428 return "_ActRelationshipCostTracking"; 1429 case CHRG: 1430 return "CHRG"; 1431 case COST: 1432 return "COST"; 1433 case _ACTRELATIONSHIPPOSTING: 1434 return "_ActRelationshipPosting"; 1435 case CREDIT: 1436 return "CREDIT"; 1437 case DEBIT: 1438 return "DEBIT"; 1439 case _ACTRELATIONSHIPCONDITIONAL: 1440 return "_ActRelationshipConditional"; 1441 case CIND: 1442 return "CIND"; 1443 case PRCN: 1444 return "PRCN"; 1445 case RSON: 1446 return "RSON"; 1447 case BLOCK: 1448 return "BLOCK"; 1449 case DIAG: 1450 return "DIAG"; 1451 case IMM: 1452 return "IMM"; 1453 case ACTIMM: 1454 return "ACTIMM"; 1455 case PASSIMM: 1456 return "PASSIMM"; 1457 case MITGT: 1458 return "MITGT"; 1459 case RCVY: 1460 return "RCVY"; 1461 case PRYLX: 1462 return "PRYLX"; 1463 case TREAT: 1464 return "TREAT"; 1465 case ADJUNCT: 1466 return "ADJUNCT"; 1467 case MTREAT: 1468 return "MTREAT"; 1469 case PALLTREAT: 1470 return "PALLTREAT"; 1471 case SYMP: 1472 return "SYMP"; 1473 case TRIG: 1474 return "TRIG"; 1475 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: 1476 return "_ActRelationshipTemporallyPertains"; 1477 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: 1478 return "_ActRelationshipTemporallyPertainsApproximates"; 1479 case ENE: 1480 return "ENE"; 1481 case ECW: 1482 return "ECW"; 1483 case CONCURRENT: 1484 return "CONCURRENT"; 1485 case SBSECWE: 1486 return "SBSECWE"; 1487 case ENS: 1488 return "ENS"; 1489 case ECWS: 1490 return "ECWS"; 1491 case SNE: 1492 return "SNE"; 1493 case SCWE: 1494 return "SCWE"; 1495 case SNS: 1496 return "SNS"; 1497 case SCW: 1498 return "SCW"; 1499 case SCWSEBE: 1500 return "SCWSEBE"; 1501 case SCWSEAE: 1502 return "SCWSEAE"; 1503 case EAS: 1504 return "EAS"; 1505 case EAE: 1506 return "EAE"; 1507 case SASEAE: 1508 return "SASEAE"; 1509 case SBEEAE: 1510 return "SBEEAE"; 1511 case SASSBEEAS: 1512 return "SASSBEEAS"; 1513 case SBSEAE: 1514 return "SBSEAE"; 1515 case SAS: 1516 return "SAS"; 1517 case SAE: 1518 return "SAE"; 1519 case DURING: 1520 return "DURING"; 1521 case SASECWE: 1522 return "SASECWE"; 1523 case EASORECWS: 1524 return "EASORECWS"; 1525 case EAEORECW: 1526 return "EAEORECW"; 1527 case INDEPENDENT: 1528 return "INDEPENDENT"; 1529 case SAEORSCWE: 1530 return "SAEORSCWE"; 1531 case SASORSCW: 1532 return "SASORSCW"; 1533 case SBEORSCWE: 1534 return "SBEORSCWE"; 1535 case OVERLAP: 1536 return "OVERLAP"; 1537 case EDU: 1538 return "EDU"; 1539 case SBSEASEBE: 1540 return "SBSEASEBE"; 1541 case SBSEAS: 1542 return "SBSEAS"; 1543 case SDU: 1544 return "SDU"; 1545 case SBE: 1546 return "SBE"; 1547 case EBE: 1548 return "EBE"; 1549 case SBSEBE: 1550 return "SBSEBE"; 1551 case EBSORECWS: 1552 return "EBSORECWS"; 1553 case EBS: 1554 return "EBS"; 1555 case EBEORECW: 1556 return "EBEORECW"; 1557 case SBSORSCW: 1558 return "SBSORSCW"; 1559 case SBS: 1560 return "SBS"; 1561 case AUTH: 1562 return "AUTH"; 1563 case CAUS: 1564 return "CAUS"; 1565 case COMP: 1566 return "COMP"; 1567 case CTRLV: 1568 return "CTRLV"; 1569 case MBR: 1570 return "MBR"; 1571 case STEP: 1572 return "STEP"; 1573 case ARR: 1574 return "ARR"; 1575 case DEP: 1576 return "DEP"; 1577 case PART: 1578 return "PART"; 1579 case COVBY: 1580 return "COVBY"; 1581 case DRIV: 1582 return "DRIV"; 1583 case ELNK: 1584 return "ELNK"; 1585 case EVID: 1586 return "EVID"; 1587 case EXACBY: 1588 return "EXACBY"; 1589 case EXPL: 1590 return "EXPL"; 1591 case INTF: 1592 return "INTF"; 1593 case ITEMSLOC: 1594 return "ITEMSLOC"; 1595 case LIMIT: 1596 return "LIMIT"; 1597 case META: 1598 return "META"; 1599 case MFST: 1600 return "MFST"; 1601 case NAME: 1602 return "NAME"; 1603 case OUTC: 1604 return "OUTC"; 1605 case _ACTRELATIONSIPOBJECTIVE: 1606 return "_ActRelationsipObjective"; 1607 case OBJC: 1608 return "OBJC"; 1609 case OBJF: 1610 return "OBJF"; 1611 case GOAL: 1612 return "GOAL"; 1613 case RISK: 1614 return "RISK"; 1615 case PERT: 1616 return "PERT"; 1617 case PREV: 1618 return "PREV"; 1619 case REFR: 1620 return "REFR"; 1621 case USE: 1622 return "USE"; 1623 case REFV: 1624 return "REFV"; 1625 case RELVBY: 1626 return "RELVBY"; 1627 case SEQL: 1628 return "SEQL"; 1629 case APND: 1630 return "APND"; 1631 case BSLN: 1632 return "BSLN"; 1633 case COMPLY: 1634 return "COMPLY"; 1635 case DOC: 1636 return "DOC"; 1637 case FLFS: 1638 return "FLFS"; 1639 case OCCR: 1640 return "OCCR"; 1641 case OREF: 1642 return "OREF"; 1643 case SCH: 1644 return "SCH"; 1645 case GEN: 1646 return "GEN"; 1647 case GEVL: 1648 return "GEVL"; 1649 case INST: 1650 return "INST"; 1651 case MOD: 1652 return "MOD"; 1653 case MTCH: 1654 return "MTCH"; 1655 case OPTN: 1656 return "OPTN"; 1657 case RCHAL: 1658 return "RCHAL"; 1659 case REV: 1660 return "REV"; 1661 case RPLC: 1662 return "RPLC"; 1663 case SUCC: 1664 return "SUCC"; 1665 case UPDT: 1666 return "UPDT"; 1667 case XCRPT: 1668 return "XCRPT"; 1669 case VRXCRPT: 1670 return "VRXCRPT"; 1671 case XFRM: 1672 return "XFRM"; 1673 case SPRT: 1674 return "SPRT"; 1675 case SPRTBND: 1676 return "SPRTBND"; 1677 case SUBJ: 1678 return "SUBJ"; 1679 case QUALF: 1680 return "QUALF"; 1681 case SUMM: 1682 return "SUMM"; 1683 case VALUE: 1684 return "VALUE"; 1685 case CURE: 1686 return "CURE"; 1687 case CURE_ADJ: 1688 return "CURE.ADJ"; 1689 case MTGT_ADJ: 1690 return "MTGT.ADJ"; 1691 case RACT: 1692 return "RACT"; 1693 case SUGG: 1694 return "SUGG"; 1695 case NULL: 1696 return null; 1697 default: 1698 return "?"; 1699 } 1700 } 1701 1702 public String getSystem() { 1703 return "http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType"; 1704 } 1705 1706 public String getDefinition() { 1707 switch (this) { 1708 case ART: 1709 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)"; 1710 case _ACTCLASSTEMPORALLYPERTAINS: 1711 return "ActClassTemporallyPertains"; 1712 case _ACTRELATIONSHIPACCOUNTING: 1713 return "Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element."; 1714 case _ACTRELATIONSHIPCOSTTRACKING: 1715 return "Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act."; 1716 case CHRG: 1717 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."; 1718 case COST: 1719 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."; 1720 case _ACTRELATIONSHIPPOSTING: 1721 return "Expresses values for describing the relationship between a FinancialTransaction and an Account."; 1722 case CREDIT: 1723 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."; 1724 case DEBIT: 1725 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."; 1726 case _ACTRELATIONSHIPCONDITIONAL: 1727 return "Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred"; 1728 case CIND: 1729 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."; 1730 case PRCN: 1731 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."; 1732 case RSON: 1733 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."; 1734 case BLOCK: 1735 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."; 1736 case DIAG: 1737 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."; 1738 case IMM: 1739 return "Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease)"; 1740 case ACTIMM: 1741 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)"; 1742 case PASSIMM: 1743 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)."; 1744 case MITGT: 1745 return "The source act removes or lessens the occurrence or effect of the target act."; 1746 case RCVY: 1747 return "Definition: The source act is performed to recover from the effects of the target act."; 1748 case PRYLX: 1749 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."; 1750 case TREAT: 1751 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."; 1752 case ADJUNCT: 1753 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."; 1754 case MTREAT: 1755 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."; 1756 case PALLTREAT: 1757 return "Description: The source act is intended to provide palliation for the effects of the target act."; 1758 case SYMP: 1759 return "Description: The source act is intented to provide symptomatic relief for the effects of the target act."; 1760 case TRIG: 1761 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."; 1762 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: 1763 return "Abstract collector for ActRelationhsip types that relate two acts by their timing."; 1764 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: 1765 return "Abstract collector for ActRelationship types that relate two acts by their approximate timing."; 1766 case ENE: 1767 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"; 1768 case ECW: 1769 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."; 1770 case CONCURRENT: 1771 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."; 1772 case SBSECWE: 1773 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"; 1774 case ENS: 1775 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"; 1776 case ECWS: 1777 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"; 1778 case SNE: 1779 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"; 1780 case SCWE: 1781 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"; 1782 case SNS: 1783 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"; 1784 case SCW: 1785 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."; 1786 case SCWSEBE: 1787 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"; 1788 case SCWSEAE: 1789 return "The source Act starts with the target Act, and ends after the end of the target Act."; 1790 case EAS: 1791 return "A relationship in which the source act ends after the target act starts.\r\n\n \n UsageNote: Inverse code is SBE"; 1792 case EAE: 1793 return "A relationship in which the source act ends after the target act ends.\r\n\n \n UsageNote: Inverse code is EBE"; 1794 case SASEAE: 1795 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"; 1796 case SBEEAE: 1797 return "The source Act contains the end of the target Act.\r\n\n \n UsageNote: Inverse code is EDU"; 1798 case SASSBEEAS: 1799 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"; 1800 case SBSEAE: 1801 return "The source Act contains the time of the target Act.\r\n\n \n UsageNote: Inverse code is DURING"; 1802 case SAS: 1803 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"; 1804 case SAE: 1805 return "A relationship in which the source act starts after the target act ends.\r\n\n \n UsageNote: Inverse code is EBS"; 1806 case DURING: 1807 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"; 1808 case SASECWE: 1809 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"; 1810 case EASORECWS: 1811 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"; 1812 case EAEORECW: 1813 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"; 1814 case INDEPENDENT: 1815 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."; 1816 case SAEORSCWE: 1817 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"; 1818 case SASORSCW: 1819 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"; 1820 case SBEORSCWE: 1821 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"; 1822 case OVERLAP: 1823 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."; 1824 case EDU: 1825 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"; 1826 case SBSEASEBE: 1827 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"; 1828 case SBSEAS: 1829 return "The source Act contains the start of the target Act.\r\n\n \n UsageNote: Inverse code is SDU"; 1830 case SDU: 1831 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"; 1832 case SBE: 1833 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"; 1834 case EBE: 1835 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"; 1836 case SBSEBE: 1837 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"; 1838 case EBSORECWS: 1839 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"; 1840 case EBS: 1841 return "A relationship in which the source act ends before the target act starts.\r\n\n \n UsageNote: Inverse code is SAE"; 1842 case EBEORECW: 1843 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"; 1844 case SBSORSCW: 1845 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"; 1846 case SBS: 1847 return "A relationship in which the source act begins before the target act begins.\r\n\n \n UsageNote: Inverse code is SAS"; 1848 case AUTH: 1849 return "A relationship in which the target act authorizes or certifies the source act."; 1850 case CAUS: 1851 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"; 1852 case COMP: 1853 return "The target act is a component of the source act, with no semantics regarding composition or aggregation implied."; 1854 case CTRLV: 1855 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."; 1856 case MBR: 1857 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"; 1858 case STEP: 1859 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."; 1860 case ARR: 1861 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."; 1862 case DEP: 1863 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."; 1864 case PART: 1865 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.\""; 1866 case COVBY: 1867 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."; 1868 case DRIV: 1869 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."; 1870 case ELNK: 1871 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."; 1872 case EVID: 1873 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."; 1874 case EXACBY: 1875 return "Description:The source act is aggravated by the target act. (Example \"chest pain\" EXACBY \"exercise\")"; 1876 case EXPL: 1877 return "This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition."; 1878 case INTF: 1879 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"; 1880 case ITEMSLOC: 1881 return "Items located"; 1882 case LIMIT: 1883 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."; 1884 case META: 1885 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\"."; 1886 case MFST: 1887 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."; 1888 case NAME: 1889 return "Used to assign a \"name\" to a condition thread. Source is a condition node, target can be any service."; 1890 case OUTC: 1891 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."; 1892 case _ACTRELATIONSIPOBJECTIVE: 1893 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."; 1894 case OBJC: 1895 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."; 1896 case OBJF: 1897 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."; 1898 case GOAL: 1899 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."; 1900 case RISK: 1901 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."; 1902 case PERT: 1903 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."; 1904 case PREV: 1905 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."; 1906 case REFR: 1907 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."; 1908 case USE: 1909 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."; 1910 case REFV: 1911 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."; 1912 case RELVBY: 1913 return "Description:The source act is wholly or partially alleviated by the target act. (Example \"chest pain\" RELVBY \"sublingual nitroglycerin administration\")"; 1914 case SEQL: 1915 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."; 1916 case APND: 1917 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."; 1918 case BSLN: 1919 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."; 1920 case COMPLY: 1921 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."; 1922 case DOC: 1923 return "The source act documents the target act."; 1924 case FLFS: 1925 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."; 1926 case OCCR: 1927 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)."; 1928 case OREF: 1929 return "Relates either an appointment request or an appointment to the order for the service being scheduled."; 1930 case SCH: 1931 return "Associates a specific time (and associated resources) with a scheduling request or other intent."; 1932 case GEN: 1933 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)."; 1934 case GEVL: 1935 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."; 1936 case INST: 1937 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."; 1938 case MOD: 1939 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\""; 1940 case MTCH: 1941 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."; 1942 case OPTN: 1943 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."; 1944 case RCHAL: 1945 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."; 1946 case REV: 1947 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."; 1948 case RPLC: 1949 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."; 1950 case SUCC: 1951 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."; 1952 case UPDT: 1953 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."; 1954 case XCRPT: 1955 return "The source is an excerpt from the target."; 1956 case VRXCRPT: 1957 return "The source is a direct quote from the target."; 1958 case XFRM: 1959 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.)"; 1960 case SPRT: 1961 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)."; 1962 case SPRTBND: 1963 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."; 1964 case SUBJ: 1965 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."; 1966 case QUALF: 1967 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."; 1968 case SUMM: 1969 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."; 1970 case VALUE: 1971 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."; 1972 case CURE: 1973 return "curative indication"; 1974 case CURE_ADJ: 1975 return "adjunct curative indication"; 1976 case MTGT_ADJ: 1977 return "adjunct mitigation"; 1978 case RACT: 1979 return ""; 1980 case SUGG: 1981 return ""; 1982 case NULL: 1983 return null; 1984 default: 1985 return "?"; 1986 } 1987 } 1988 1989 public String getDisplay() { 1990 switch (this) { 1991 case ART: 1992 return "act relationship type"; 1993 case _ACTCLASSTEMPORALLYPERTAINS: 1994 return "ActClassTemporallyPertains"; 1995 case _ACTRELATIONSHIPACCOUNTING: 1996 return "ActRelationshipAccounting"; 1997 case _ACTRELATIONSHIPCOSTTRACKING: 1998 return "ActRelationshipCostTracking"; 1999 case CHRG: 2000 return "has charge"; 2001 case COST: 2002 return "has cost"; 2003 case _ACTRELATIONSHIPPOSTING: 2004 return "ActRelationshipPosting"; 2005 case CREDIT: 2006 return "has credit"; 2007 case DEBIT: 2008 return "has debit"; 2009 case _ACTRELATIONSHIPCONDITIONAL: 2010 return "ActRelationshipConditional"; 2011 case CIND: 2012 return "has contra-indication"; 2013 case PRCN: 2014 return "has pre-condition"; 2015 case RSON: 2016 return "has reason"; 2017 case BLOCK: 2018 return "blocks"; 2019 case DIAG: 2020 return "diagnoses"; 2021 case IMM: 2022 return "immunization against"; 2023 case ACTIMM: 2024 return "active immunization against"; 2025 case PASSIMM: 2026 return "passive immunization against"; 2027 case MITGT: 2028 return "mitigates"; 2029 case RCVY: 2030 return "recovers"; 2031 case PRYLX: 2032 return "prophylaxis of"; 2033 case TREAT: 2034 return "treats"; 2035 case ADJUNCT: 2036 return "adjunctive treatment"; 2037 case MTREAT: 2038 return "maintenance treatment"; 2039 case PALLTREAT: 2040 return "palliates"; 2041 case SYMP: 2042 return "symptomatic relief"; 2043 case TRIG: 2044 return "has trigger"; 2045 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: 2046 return "ActRelationshipTemporallyPertains"; 2047 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: 2048 return "ActRelationshipTemporallyPertainsApproximates"; 2049 case ENE: 2050 return "ends near end"; 2051 case ECW: 2052 return "ends concurrent with"; 2053 case CONCURRENT: 2054 return "concurrent with"; 2055 case SBSECWE: 2056 return "starts before start of, ends with"; 2057 case ENS: 2058 return "ends near start"; 2059 case ECWS: 2060 return "ends concurrent with start of"; 2061 case SNE: 2062 return "starts near end"; 2063 case SCWE: 2064 return "starts concurrent with end of"; 2065 case SNS: 2066 return "starts near start"; 2067 case SCW: 2068 return "starts concurrent with"; 2069 case SCWSEBE: 2070 return "starts with. ends before end of"; 2071 case SCWSEAE: 2072 return "starts with, ends after end of"; 2073 case EAS: 2074 return "ends after start of"; 2075 case EAE: 2076 return "ends after end of"; 2077 case SASEAE: 2078 return "starts after start of, ends after end of"; 2079 case SBEEAE: 2080 return "contains end of"; 2081 case SASSBEEAS: 2082 return "start after start of, contains end of"; 2083 case SBSEAE: 2084 return "contains time of"; 2085 case SAS: 2086 return "starts after start of"; 2087 case SAE: 2088 return "starts after end of"; 2089 case DURING: 2090 return "occurs during"; 2091 case SASECWE: 2092 return "starts after start of, ends with"; 2093 case EASORECWS: 2094 return "ends after or concurrent with start of"; 2095 case EAEORECW: 2096 return "ends after or concurrent with end of"; 2097 case INDEPENDENT: 2098 return "independent of time of"; 2099 case SAEORSCWE: 2100 return "starts after or concurrent with end of"; 2101 case SASORSCW: 2102 return "starts after or concurrent with start of"; 2103 case SBEORSCWE: 2104 return "starts before or concurrent with end of"; 2105 case OVERLAP: 2106 return "overlaps with"; 2107 case EDU: 2108 return "ends during"; 2109 case SBSEASEBE: 2110 return "contains start of, ends before end of"; 2111 case SBSEAS: 2112 return "contains start of"; 2113 case SDU: 2114 return "starts during"; 2115 case SBE: 2116 return "starts before end of"; 2117 case EBE: 2118 return "ends before end of"; 2119 case SBSEBE: 2120 return "starts before start of, ends before end of"; 2121 case EBSORECWS: 2122 return "ends before or concurrent with start of"; 2123 case EBS: 2124 return "ends before start of"; 2125 case EBEORECW: 2126 return "ends before or concurrent with end of"; 2127 case SBSORSCW: 2128 return "starts before or concurrent with start of"; 2129 case SBS: 2130 return "starts before start of"; 2131 case AUTH: 2132 return "authorized by"; 2133 case CAUS: 2134 return "is etiology for"; 2135 case COMP: 2136 return "has component"; 2137 case CTRLV: 2138 return "has control variable"; 2139 case MBR: 2140 return "has member"; 2141 case STEP: 2142 return "has step"; 2143 case ARR: 2144 return "arrival"; 2145 case DEP: 2146 return "departure"; 2147 case PART: 2148 return "has part"; 2149 case COVBY: 2150 return "covered by"; 2151 case DRIV: 2152 return "is derived from"; 2153 case ELNK: 2154 return "episodeLink"; 2155 case EVID: 2156 return "provides evidence for"; 2157 case EXACBY: 2158 return "exacerbated by"; 2159 case EXPL: 2160 return "has explanation"; 2161 case INTF: 2162 return "interfered by"; 2163 case ITEMSLOC: 2164 return "items located"; 2165 case LIMIT: 2166 return "limited by"; 2167 case META: 2168 return "has metadata"; 2169 case MFST: 2170 return "is manifestation of"; 2171 case NAME: 2172 return "assigns name"; 2173 case OUTC: 2174 return "has outcome"; 2175 case _ACTRELATIONSIPOBJECTIVE: 2176 return "Act Relationsip Objective"; 2177 case OBJC: 2178 return "has continuing objective"; 2179 case OBJF: 2180 return "has final objective"; 2181 case GOAL: 2182 return "has goal"; 2183 case RISK: 2184 return "has risk"; 2185 case PERT: 2186 return "has pertinent information"; 2187 case PREV: 2188 return "has previous instance"; 2189 case REFR: 2190 return "refers to"; 2191 case USE: 2192 return "uses"; 2193 case REFV: 2194 return "has reference values"; 2195 case RELVBY: 2196 return "relieved by"; 2197 case SEQL: 2198 return "is sequel"; 2199 case APND: 2200 return "is appendage"; 2201 case BSLN: 2202 return "has baseline"; 2203 case COMPLY: 2204 return "complies with"; 2205 case DOC: 2206 return "documents"; 2207 case FLFS: 2208 return "fulfills"; 2209 case OCCR: 2210 return "occurrence"; 2211 case OREF: 2212 return "references order"; 2213 case SCH: 2214 return "schedules request"; 2215 case GEN: 2216 return "has generalization"; 2217 case GEVL: 2218 return "evaluates (goal)"; 2219 case INST: 2220 return "instantiates (master)"; 2221 case MOD: 2222 return "modifies"; 2223 case MTCH: 2224 return "matches (trigger)"; 2225 case OPTN: 2226 return "has option"; 2227 case RCHAL: 2228 return "re-challenge"; 2229 case REV: 2230 return "reverses"; 2231 case RPLC: 2232 return "replaces"; 2233 case SUCC: 2234 return "succeeds"; 2235 case UPDT: 2236 return "updates (condition)"; 2237 case XCRPT: 2238 return "Excerpts"; 2239 case VRXCRPT: 2240 return "Excerpt verbatim"; 2241 case XFRM: 2242 return "transformation"; 2243 case SPRT: 2244 return "has support"; 2245 case SPRTBND: 2246 return "has bounded support"; 2247 case SUBJ: 2248 return "has subject"; 2249 case QUALF: 2250 return "has qualifier"; 2251 case SUMM: 2252 return "summarized by"; 2253 case VALUE: 2254 return "has value"; 2255 case CURE: 2256 return "curative indication"; 2257 case CURE_ADJ: 2258 return "adjunct curative indication"; 2259 case MTGT_ADJ: 2260 return "adjunct mitigation"; 2261 case RACT: 2262 return "RACT"; 2263 case SUGG: 2264 return "SUGG"; 2265 case NULL: 2266 return null; 2267 default: 2268 return "?"; 2269 } 2270 } 2271 2272}