001package org.hl7.fhir.dstu3.model.codesystems; 002 003 004 005 006/* 007 Copyright (c) 2011+, HL7, Inc. 008 All rights reserved. 009 010 Redistribution and use in source and binary forms, with or without modification, 011 are permitted provided that the following conditions are met: 012 013 * Redistributions of source code must retain the above copyright notice, this 014 list of conditions and the following disclaimer. 015 * Redistributions in binary form must reproduce the above copyright notice, 016 this list of conditions and the following disclaimer in the documentation 017 and/or other materials provided with the distribution. 018 * Neither the name of HL7 nor the names of its contributors may be used to 019 endorse or promote products derived from this software without specific 020 prior written permission. 021 022 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 023 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 024 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 025 IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 026 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 027 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 028 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, 029 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 030 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 031 POSSIBILITY OF SUCH DAMAGE. 032 033*/ 034 035// Generated on Sat, Mar 25, 2017 21:03-0400 for FHIR v3.0.0 036 037 038import org.hl7.fhir.exceptions.FHIRException; 039 040public enum V3ActRelationshipType { 041 042 /** 043 * Description: A directed association between a source Act and a target Act. 044 045 046 Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute) 047 */ 048 ART, 049 /** 050 * ActClassTemporallyPertains 051 */ 052 _ACTCLASSTEMPORALLYPERTAINS, 053 /** 054 * Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element. 055 */ 056 _ACTRELATIONSHIPACCOUNTING, 057 /** 058 * Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act. 059 */ 060 _ACTRELATIONSHIPCOSTTRACKING, 061 /** 062 * 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. 063 064 The financial transaction will define the charge (bill) for delivery or performance of the service. 065 066 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. 067 */ 068 CHRG, 069 /** 070 * 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. 071 072 The financial transaction will define the cost of delivery or performance of the service. 073 074 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. 075 */ 076 COST, 077 /** 078 * Expresses values for describing the relationship between a FinancialTransaction and an Account. 079 */ 080 _ACTRELATIONSHIPPOSTING, 081 /** 082 * 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. 083 */ 084 CREDIT, 085 /** 086 * 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. 087 */ 088 DEBIT, 089 /** 090 * Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred 091 */ 092 _ACTRELATIONSHIPCONDITIONAL, 093 /** 094 * 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. 095 */ 096 CIND, 097 /** 098 * 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. 099 */ 100 PRCN, 101 /** 102 * 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. 103 104 105 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. 106 */ 107 RSON, 108 /** 109 * 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. 110 */ 111 BLOCK, 112 /** 113 * 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. 114 */ 115 DIAG, 116 /** 117 * Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease) 118 */ 119 IMM, 120 /** 121 * Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease) 122 */ 123 ACTIMM, 124 /** 125 * Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease). 126 */ 127 PASSIMM, 128 /** 129 * The source act removes or lessens the occurrence or effect of the target act. 130 */ 131 MITGT, 132 /** 133 * Definition: The source act is performed to recover from the effects of the target act. 134 */ 135 RCVY, 136 /** 137 * 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. 138 */ 139 PRYLX, 140 /** 141 * 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. 142 */ 143 TREAT, 144 /** 145 * 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. 146 */ 147 ADJUNCT, 148 /** 149 * 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. 150 */ 151 MTREAT, 152 /** 153 * Description: The source act is intended to provide palliation for the effects of the target act. 154 */ 155 PALLTREAT, 156 /** 157 * Description: The source act is intented to provide symptomatic relief for the effects of the target act. 158 */ 159 SYMP, 160 /** 161 * 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. 162 163 164 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. 165 */ 166 TRIG, 167 /** 168 * Abstract collector for ActRelationhsip types that relate two acts by their timing. 169 */ 170 _ACTRELATIONSHIPTEMPORALLYPERTAINS, 171 /** 172 * Abstract collector for ActRelationship types that relate two acts by their approximate timing. 173 */ 174 _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES, 175 /** 176 * 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. 177 178 179 Usage Note: Inverse code is ENS 180 */ 181 ENE, 182 /** 183 * A relationship in which the source act's effective time ends with the end of the target act's effective time. 184 185 186 UsageNote: This code is reflexive. Therefore its inverse code is itself. 187 */ 188 ECW, 189 /** 190 * A relationship in which the source act's effective time is the same as the target act's effective time. 191 192 193 UsageNote: This code is reflexive. Therefore its inverse code is itself. 194 */ 195 CONCURRENT, 196 /** 197 * The source Act starts before the start of the target Act, and ends with the target Act. 198 199 200 UsageNote: Inverse code is SASECWE 201 */ 202 SBSECWE, 203 /** 204 * 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. 205 206 207 Usage Note: Inverse code is ENE 208 */ 209 ENS, 210 /** 211 * 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). 212 213 214 UsageNote: Inverse code is SCWE 215 */ 216 ECWS, 217 /** 218 * 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. 219 220 221 Usage Note: Inverse code is SNS 222 */ 223 SNE, 224 /** 225 * 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). 226 227 228 UsageNote: Inverse code is SBSECWS 229 */ 230 SCWE, 231 /** 232 * 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. 233 234 235 Usage Note: Inverse code is SNE 236 */ 237 SNS, 238 /** 239 * A relationship in which the source act's effective time starts with the start of the target act's effective time. 240 241 242 UsageNote: This code is reflexive. Therefore its inverse code is itself. 243 */ 244 SCW, 245 /** 246 * The source Act starts with.the target Act and ends before the end of the target Act. 247 248 249 UsageNote: Inverse code is SCWSEAE 250 */ 251 SCWSEBE, 252 /** 253 * The source Act starts with the target Act, and ends after the end of the target Act. 254 */ 255 SCWSEAE, 256 /** 257 * A relationship in which the source act ends after the target act starts. 258 259 260 UsageNote: Inverse code is SBE 261 */ 262 EAS, 263 /** 264 * A relationship in which the source act ends after the target act ends. 265 266 267 UsageNote: Inverse code is EBE 268 */ 269 EAE, 270 /** 271 * The source Act starts after start of the target Act and ends after end of the target Act. 272 273 274 UsageNote: Inverse code is SBSEBE 275 */ 276 SASEAE, 277 /** 278 * The source Act contains the end of the target Act. 279 280 281 UsageNote: Inverse code is EDU 282 */ 283 SBEEAE, 284 /** 285 * The source Act start after the start of the target Act, and contains the end of the target Act. 286 287 288 UsageNote: Inverse code is SBSEASEBE 289 */ 290 SASSBEEAS, 291 /** 292 * The source Act contains the time of the target Act. 293 294 295 UsageNote: Inverse code is DURING 296 */ 297 SBSEAE, 298 /** 299 * 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). 300 301 302 UsageNote: Inverse code is SBS 303 */ 304 SAS, 305 /** 306 * A relationship in which the source act starts after the target act ends. 307 308 309 UsageNote: Inverse code is EBS 310 */ 311 SAE, 312 /** 313 * 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) 314 315 316 UsageNote: Inverse code is SBSEAE 317 */ 318 DURING, 319 /** 320 * The source Act starts after start of the target Act, and ends with the target Act. 321 322 323 UsageNote: Inverse code is SBSECWE 324 */ 325 SASECWE, 326 /** 327 * A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time. 328 329 330 Usage Note: Inverse code is EBSORECWS 331 */ 332 EASORECWS, 333 /** 334 * A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time. 335 336 337 Usage Note: Inverse code is EBEORECW 338 */ 339 EAEORECW, 340 /** 341 * The source Act is independent of the time of the target Act. 342 343 344 UsageNote: This code is reflexive. Therefore its inverse code is itself. 345 */ 346 INDEPENDENT, 347 /** 348 * A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time. 349 350 351 Usage Note: Inverse code is SBEORSCWE 352 */ 353 SAEORSCWE, 354 /** 355 * A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time. 356 357 358 Usage Note: Inverse code is SBSORSCW 359 */ 360 SASORSCW, 361 /** 362 * A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time. 363 364 365 Usage Note: Inverse code is SAEORSCWE 366 */ 367 SBEORSCWE, 368 /** 369 * A relationship in which the source act's effective time overlaps the target act's effective time in any way. 370 371 372 UsageNote: This code is reflexive. Therefore its inverse code is itself. 373 */ 374 OVERLAP, 375 /** 376 * 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) 377 378 379 UsageNote: Inverse code is SBEEAE 380 */ 381 EDU, 382 /** 383 * The source Act contains the start of the target Act, and ends before the end of the target Act. 384 385 386 UsageNote: Inverse code is SASSBEEAS 387 */ 388 SBSEASEBE, 389 /** 390 * The source Act contains the start of the target Act. 391 392 393 UsageNote: Inverse code is SDU 394 */ 395 SBSEAS, 396 /** 397 * 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) 398 399 400 UsageNote: Inverse code is SBSEAS 401 */ 402 SDU, 403 /** 404 * 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). 405 406 407 UsageNote: Inverse code is EAS 408 */ 409 SBE, 410 /** 411 * 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). 412 413 414 UsageNote: Inverse code is EAE 415 */ 416 EBE, 417 /** 418 * The source Act starts before the start of the target Act, and ends before the end of the target Act. 419 420 421 UsageNote: Inverse code is SASEAE 422 */ 423 SBSEBE, 424 /** 425 * A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time. 426 427 428 Usage Note: Inverse code is EASORECWS 429 */ 430 EBSORECWS, 431 /** 432 * A relationship in which the source act ends before the target act starts. 433 434 435 UsageNote: Inverse code is SAE 436 */ 437 EBS, 438 /** 439 * A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time. 440 441 442 Usage Note: Inverse code is EAEORECW 443 */ 444 EBEORECW, 445 /** 446 * A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time. 447 448 449 Usage Note: Inverse code is SASORSCW 450 */ 451 SBSORSCW, 452 /** 453 * A relationship in which the source act begins before the target act begins. 454 455 456 UsageNote: Inverse code is SAS 457 */ 458 SBS, 459 /** 460 * A relationship in which the target act authorizes or certifies the source act. 461 */ 462 AUTH, 463 /** 464 * 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. 465 466 467 Examples: 468 469 470 471 a growth of Staphylococcus aureus may be considered the cause of an abscess 472 contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced 473 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 474 */ 475 CAUS, 476 /** 477 * The target act is a component of the source act, with no semantics regarding composition or aggregation implied. 478 */ 479 COMP, 480 /** 481 * 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. 482 */ 483 CTRLV, 484 /** 485 * 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. 486 487 488 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). 489 490 It is expected that this will be primarily used with _ActClassRecordOrganizer, BATTERY, and LIST 491 */ 492 MBR, 493 /** 494 * A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently. 495 496 497 UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode. 498 499 500 OpenIssue: Need Additional guidelines on when each approach should be used. 501 */ 502 STEP, 503 /** 504 * 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. 505 */ 506 ARR, 507 /** 508 * 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. 509 */ 510 DEP, 511 /** 512 * The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act. 513 514 515 UsageNote: In UML 1.1, this is a "composition" defined as: 516 "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." 517 */ 518 PART, 519 /** 520 * 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. 521 */ 522 COVBY, 523 /** 524 * 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. 525 */ 526 DRIV, 527 /** 528 * 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. 529 */ 530 ELNK, 531 /** 532 * 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. 533 534 535 Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies. 536 */ 537 EVID, 538 /** 539 * Description:The source act is aggravated by the target act. (Example "chest pain" EXACBY "exercise") 540 */ 541 EXACBY, 542 /** 543 * This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition. 544 */ 545 EXPL, 546 /** 547 * the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act. 548 549 550 UsageNote: This provides the semantics to document barriers to care 551 */ 552 INTF, 553 /** 554 * Items located 555 */ 556 ITEMSLOC, 557 /** 558 * 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. 559 */ 560 LIMIT, 561 /** 562 * Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act. 563 564 565 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". 566 */ 567 META, 568 /** 569 * 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. 570 */ 571 MFST, 572 /** 573 * Used to assign a "name" to a condition thread. Source is a condition node, target can be any service. 574 */ 575 NAME, 576 /** 577 * 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. 578 */ 579 OUTC, 580 /** 581 * 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. 582 */ 583 _ACTRELATIONSIPOBJECTIVE, 584 /** 585 * 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. 586 */ 587 OBJC, 588 /** 589 * 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. 590 */ 591 OBJF, 592 /** 593 * 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. 594 */ 595 GOAL, 596 /** 597 * 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. 598 */ 599 RISK, 600 /** 601 * 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. 602 */ 603 PERT, 604 /** 605 * 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. 606 */ 607 PREV, 608 /** 609 * 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. 610 */ 611 REFR, 612 /** 613 * Indicates that the source act makes use of (or will make use of) the information content of the target act. 614 615 616 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. 617 618 619 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. 620 */ 621 USE, 622 /** 623 * 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. 624 */ 625 REFV, 626 /** 627 * Description:The source act is wholly or partially alleviated by the target act. (Example "chest pain" RELVBY "sublingual nitroglycerin administration") 628 */ 629 RELVBY, 630 /** 631 * 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. 632 */ 633 SEQL, 634 /** 635 * 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. 636 */ 637 APND, 638 /** 639 * Indicates that the target observation(s) provide an initial reference for the source observation or observation group. 640 641 642 UsageConstraints: Both source and target must be Observations or specializations thereof. 643 */ 644 BSLN, 645 /** 646 * 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. 647 648 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. 649 */ 650 COMPLY, 651 /** 652 * The source act documents the target act. 653 */ 654 DOC, 655 /** 656 * 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. 657 */ 658 FLFS, 659 /** 660 * 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). 661 */ 662 OCCR, 663 /** 664 * Relates either an appointment request or an appointment to the order for the service being scheduled. 665 */ 666 OREF, 667 /** 668 * Associates a specific time (and associated resources) with a scheduling request or other intent. 669 */ 670 SCH, 671 /** 672 * 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). 673 */ 674 GEN, 675 /** 676 * 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. 677 */ 678 GEVL, 679 /** 680 * 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. 681 */ 682 INST, 683 /** 684 * 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). 685 686 687 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. 688 689 Name from source to target = "modifiesPrior" 690 691 Name from target to source = "modifiesByNew" 692 */ 693 MOD, 694 /** 695 * 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. 696 */ 697 MTCH, 698 /** 699 * A relationship between a source Act that provides more detailed properties to the target Act. 700 701 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. 702 703 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. 704 705 Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options. 706 */ 707 OPTN, 708 /** 709 * Description:A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated. 710 */ 711 RCHAL, 712 /** 713 * A relationship between a source Act that seeks to reverse or undo the action of the prior target Act. 714 715 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. 716 717 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. 718 */ 719 REV, 720 /** 721 * 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. 722 */ 723 RPLC, 724 /** 725 * 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. 726 */ 727 SUCC, 728 /** 729 * 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. 730 */ 731 UPDT, 732 /** 733 * The source is an excerpt from the target. 734 */ 735 XCRPT, 736 /** 737 * The source is a direct quote from the target. 738 */ 739 VRXCRPT, 740 /** 741 * 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.) 742 */ 743 XFRM, 744 /** 745 * 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). 746 */ 747 SPRT, 748 /** 749 * 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. 750 */ 751 SPRTBND, 752 /** 753 * Relates an Act to its subject Act that the first Act is primarily concerned with. 754 755 Examples 756 757 758 759 The first Act may be a ControlAct manipulating the subject Act 760 761 762 763 The first act is a region of interest (ROI) that defines a region within the subject Act. 764 765 766 767 The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose. 768 769 770 771 Constraints 772 773 An Act may have multiple subject acts. 774 775 Rationale 776 777 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. 778 */ 779 SUBJ, 780 /** 781 * The target observation qualifies (refines) the semantics of the source observation. 782 783 784 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. 785 */ 786 QUALF, 787 /** 788 * 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. 789 */ 790 SUMM, 791 /** 792 * Description:Indicates that the target Act represents the result of the source observation Act. 793 794 795 FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified 796 797 798 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. 799 800 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. 801 802 803 OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation. 804 */ 805 VALUE, 806 /** 807 * curative indication 808 */ 809 CURE, 810 /** 811 * adjunct curative indication 812 */ 813 CURE_ADJ, 814 /** 815 * adjunct mitigation 816 */ 817 MTGT_ADJ, 818 /** 819 * null 820 */ 821 RACT, 822 /** 823 * null 824 */ 825 SUGG, 826 /** 827 * added to help the parsers 828 */ 829 NULL; 830 public static V3ActRelationshipType fromCode(String codeString) throws FHIRException { 831 if (codeString == null || "".equals(codeString)) 832 return null; 833 if ("ART".equals(codeString)) 834 return ART; 835 if ("_ActClassTemporallyPertains".equals(codeString)) 836 return _ACTCLASSTEMPORALLYPERTAINS; 837 if ("_ActRelationshipAccounting".equals(codeString)) 838 return _ACTRELATIONSHIPACCOUNTING; 839 if ("_ActRelationshipCostTracking".equals(codeString)) 840 return _ACTRELATIONSHIPCOSTTRACKING; 841 if ("CHRG".equals(codeString)) 842 return CHRG; 843 if ("COST".equals(codeString)) 844 return COST; 845 if ("_ActRelationshipPosting".equals(codeString)) 846 return _ACTRELATIONSHIPPOSTING; 847 if ("CREDIT".equals(codeString)) 848 return CREDIT; 849 if ("DEBIT".equals(codeString)) 850 return DEBIT; 851 if ("_ActRelationshipConditional".equals(codeString)) 852 return _ACTRELATIONSHIPCONDITIONAL; 853 if ("CIND".equals(codeString)) 854 return CIND; 855 if ("PRCN".equals(codeString)) 856 return PRCN; 857 if ("RSON".equals(codeString)) 858 return RSON; 859 if ("BLOCK".equals(codeString)) 860 return BLOCK; 861 if ("DIAG".equals(codeString)) 862 return DIAG; 863 if ("IMM".equals(codeString)) 864 return IMM; 865 if ("ACTIMM".equals(codeString)) 866 return ACTIMM; 867 if ("PASSIMM".equals(codeString)) 868 return PASSIMM; 869 if ("MITGT".equals(codeString)) 870 return MITGT; 871 if ("RCVY".equals(codeString)) 872 return RCVY; 873 if ("PRYLX".equals(codeString)) 874 return PRYLX; 875 if ("TREAT".equals(codeString)) 876 return TREAT; 877 if ("ADJUNCT".equals(codeString)) 878 return ADJUNCT; 879 if ("MTREAT".equals(codeString)) 880 return MTREAT; 881 if ("PALLTREAT".equals(codeString)) 882 return PALLTREAT; 883 if ("SYMP".equals(codeString)) 884 return SYMP; 885 if ("TRIG".equals(codeString)) 886 return TRIG; 887 if ("_ActRelationshipTemporallyPertains".equals(codeString)) 888 return _ACTRELATIONSHIPTEMPORALLYPERTAINS; 889 if ("_ActRelationshipTemporallyPertainsApproximates".equals(codeString)) 890 return _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES; 891 if ("ENE".equals(codeString)) 892 return ENE; 893 if ("ECW".equals(codeString)) 894 return ECW; 895 if ("CONCURRENT".equals(codeString)) 896 return CONCURRENT; 897 if ("SBSECWE".equals(codeString)) 898 return SBSECWE; 899 if ("ENS".equals(codeString)) 900 return ENS; 901 if ("ECWS".equals(codeString)) 902 return ECWS; 903 if ("SNE".equals(codeString)) 904 return SNE; 905 if ("SCWE".equals(codeString)) 906 return SCWE; 907 if ("SNS".equals(codeString)) 908 return SNS; 909 if ("SCW".equals(codeString)) 910 return SCW; 911 if ("SCWSEBE".equals(codeString)) 912 return SCWSEBE; 913 if ("SCWSEAE".equals(codeString)) 914 return SCWSEAE; 915 if ("EAS".equals(codeString)) 916 return EAS; 917 if ("EAE".equals(codeString)) 918 return EAE; 919 if ("SASEAE".equals(codeString)) 920 return SASEAE; 921 if ("SBEEAE".equals(codeString)) 922 return SBEEAE; 923 if ("SASSBEEAS".equals(codeString)) 924 return SASSBEEAS; 925 if ("SBSEAE".equals(codeString)) 926 return SBSEAE; 927 if ("SAS".equals(codeString)) 928 return SAS; 929 if ("SAE".equals(codeString)) 930 return SAE; 931 if ("DURING".equals(codeString)) 932 return DURING; 933 if ("SASECWE".equals(codeString)) 934 return SASECWE; 935 if ("EASORECWS".equals(codeString)) 936 return EASORECWS; 937 if ("EAEORECW".equals(codeString)) 938 return EAEORECW; 939 if ("INDEPENDENT".equals(codeString)) 940 return INDEPENDENT; 941 if ("SAEORSCWE".equals(codeString)) 942 return SAEORSCWE; 943 if ("SASORSCW".equals(codeString)) 944 return SASORSCW; 945 if ("SBEORSCWE".equals(codeString)) 946 return SBEORSCWE; 947 if ("OVERLAP".equals(codeString)) 948 return OVERLAP; 949 if ("EDU".equals(codeString)) 950 return EDU; 951 if ("SBSEASEBE".equals(codeString)) 952 return SBSEASEBE; 953 if ("SBSEAS".equals(codeString)) 954 return SBSEAS; 955 if ("SDU".equals(codeString)) 956 return SDU; 957 if ("SBE".equals(codeString)) 958 return SBE; 959 if ("EBE".equals(codeString)) 960 return EBE; 961 if ("SBSEBE".equals(codeString)) 962 return SBSEBE; 963 if ("EBSORECWS".equals(codeString)) 964 return EBSORECWS; 965 if ("EBS".equals(codeString)) 966 return EBS; 967 if ("EBEORECW".equals(codeString)) 968 return EBEORECW; 969 if ("SBSORSCW".equals(codeString)) 970 return SBSORSCW; 971 if ("SBS".equals(codeString)) 972 return SBS; 973 if ("AUTH".equals(codeString)) 974 return AUTH; 975 if ("CAUS".equals(codeString)) 976 return CAUS; 977 if ("COMP".equals(codeString)) 978 return COMP; 979 if ("CTRLV".equals(codeString)) 980 return CTRLV; 981 if ("MBR".equals(codeString)) 982 return MBR; 983 if ("STEP".equals(codeString)) 984 return STEP; 985 if ("ARR".equals(codeString)) 986 return ARR; 987 if ("DEP".equals(codeString)) 988 return DEP; 989 if ("PART".equals(codeString)) 990 return PART; 991 if ("COVBY".equals(codeString)) 992 return COVBY; 993 if ("DRIV".equals(codeString)) 994 return DRIV; 995 if ("ELNK".equals(codeString)) 996 return ELNK; 997 if ("EVID".equals(codeString)) 998 return EVID; 999 if ("EXACBY".equals(codeString)) 1000 return EXACBY; 1001 if ("EXPL".equals(codeString)) 1002 return EXPL; 1003 if ("INTF".equals(codeString)) 1004 return INTF; 1005 if ("ITEMSLOC".equals(codeString)) 1006 return ITEMSLOC; 1007 if ("LIMIT".equals(codeString)) 1008 return LIMIT; 1009 if ("META".equals(codeString)) 1010 return META; 1011 if ("MFST".equals(codeString)) 1012 return MFST; 1013 if ("NAME".equals(codeString)) 1014 return NAME; 1015 if ("OUTC".equals(codeString)) 1016 return OUTC; 1017 if ("_ActRelationsipObjective".equals(codeString)) 1018 return _ACTRELATIONSIPOBJECTIVE; 1019 if ("OBJC".equals(codeString)) 1020 return OBJC; 1021 if ("OBJF".equals(codeString)) 1022 return OBJF; 1023 if ("GOAL".equals(codeString)) 1024 return GOAL; 1025 if ("RISK".equals(codeString)) 1026 return RISK; 1027 if ("PERT".equals(codeString)) 1028 return PERT; 1029 if ("PREV".equals(codeString)) 1030 return PREV; 1031 if ("REFR".equals(codeString)) 1032 return REFR; 1033 if ("USE".equals(codeString)) 1034 return USE; 1035 if ("REFV".equals(codeString)) 1036 return REFV; 1037 if ("RELVBY".equals(codeString)) 1038 return RELVBY; 1039 if ("SEQL".equals(codeString)) 1040 return SEQL; 1041 if ("APND".equals(codeString)) 1042 return APND; 1043 if ("BSLN".equals(codeString)) 1044 return BSLN; 1045 if ("COMPLY".equals(codeString)) 1046 return COMPLY; 1047 if ("DOC".equals(codeString)) 1048 return DOC; 1049 if ("FLFS".equals(codeString)) 1050 return FLFS; 1051 if ("OCCR".equals(codeString)) 1052 return OCCR; 1053 if ("OREF".equals(codeString)) 1054 return OREF; 1055 if ("SCH".equals(codeString)) 1056 return SCH; 1057 if ("GEN".equals(codeString)) 1058 return GEN; 1059 if ("GEVL".equals(codeString)) 1060 return GEVL; 1061 if ("INST".equals(codeString)) 1062 return INST; 1063 if ("MOD".equals(codeString)) 1064 return MOD; 1065 if ("MTCH".equals(codeString)) 1066 return MTCH; 1067 if ("OPTN".equals(codeString)) 1068 return OPTN; 1069 if ("RCHAL".equals(codeString)) 1070 return RCHAL; 1071 if ("REV".equals(codeString)) 1072 return REV; 1073 if ("RPLC".equals(codeString)) 1074 return RPLC; 1075 if ("SUCC".equals(codeString)) 1076 return SUCC; 1077 if ("UPDT".equals(codeString)) 1078 return UPDT; 1079 if ("XCRPT".equals(codeString)) 1080 return XCRPT; 1081 if ("VRXCRPT".equals(codeString)) 1082 return VRXCRPT; 1083 if ("XFRM".equals(codeString)) 1084 return XFRM; 1085 if ("SPRT".equals(codeString)) 1086 return SPRT; 1087 if ("SPRTBND".equals(codeString)) 1088 return SPRTBND; 1089 if ("SUBJ".equals(codeString)) 1090 return SUBJ; 1091 if ("QUALF".equals(codeString)) 1092 return QUALF; 1093 if ("SUMM".equals(codeString)) 1094 return SUMM; 1095 if ("VALUE".equals(codeString)) 1096 return VALUE; 1097 if ("CURE".equals(codeString)) 1098 return CURE; 1099 if ("CURE.ADJ".equals(codeString)) 1100 return CURE_ADJ; 1101 if ("MTGT.ADJ".equals(codeString)) 1102 return MTGT_ADJ; 1103 if ("RACT".equals(codeString)) 1104 return RACT; 1105 if ("SUGG".equals(codeString)) 1106 return SUGG; 1107 throw new FHIRException("Unknown V3ActRelationshipType code '"+codeString+"'"); 1108 } 1109 public String toCode() { 1110 switch (this) { 1111 case ART: return "ART"; 1112 case _ACTCLASSTEMPORALLYPERTAINS: return "_ActClassTemporallyPertains"; 1113 case _ACTRELATIONSHIPACCOUNTING: return "_ActRelationshipAccounting"; 1114 case _ACTRELATIONSHIPCOSTTRACKING: return "_ActRelationshipCostTracking"; 1115 case CHRG: return "CHRG"; 1116 case COST: return "COST"; 1117 case _ACTRELATIONSHIPPOSTING: return "_ActRelationshipPosting"; 1118 case CREDIT: return "CREDIT"; 1119 case DEBIT: return "DEBIT"; 1120 case _ACTRELATIONSHIPCONDITIONAL: return "_ActRelationshipConditional"; 1121 case CIND: return "CIND"; 1122 case PRCN: return "PRCN"; 1123 case RSON: return "RSON"; 1124 case BLOCK: return "BLOCK"; 1125 case DIAG: return "DIAG"; 1126 case IMM: return "IMM"; 1127 case ACTIMM: return "ACTIMM"; 1128 case PASSIMM: return "PASSIMM"; 1129 case MITGT: return "MITGT"; 1130 case RCVY: return "RCVY"; 1131 case PRYLX: return "PRYLX"; 1132 case TREAT: return "TREAT"; 1133 case ADJUNCT: return "ADJUNCT"; 1134 case MTREAT: return "MTREAT"; 1135 case PALLTREAT: return "PALLTREAT"; 1136 case SYMP: return "SYMP"; 1137 case TRIG: return "TRIG"; 1138 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: return "_ActRelationshipTemporallyPertains"; 1139 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: return "_ActRelationshipTemporallyPertainsApproximates"; 1140 case ENE: return "ENE"; 1141 case ECW: return "ECW"; 1142 case CONCURRENT: return "CONCURRENT"; 1143 case SBSECWE: return "SBSECWE"; 1144 case ENS: return "ENS"; 1145 case ECWS: return "ECWS"; 1146 case SNE: return "SNE"; 1147 case SCWE: return "SCWE"; 1148 case SNS: return "SNS"; 1149 case SCW: return "SCW"; 1150 case SCWSEBE: return "SCWSEBE"; 1151 case SCWSEAE: return "SCWSEAE"; 1152 case EAS: return "EAS"; 1153 case EAE: return "EAE"; 1154 case SASEAE: return "SASEAE"; 1155 case SBEEAE: return "SBEEAE"; 1156 case SASSBEEAS: return "SASSBEEAS"; 1157 case SBSEAE: return "SBSEAE"; 1158 case SAS: return "SAS"; 1159 case SAE: return "SAE"; 1160 case DURING: return "DURING"; 1161 case SASECWE: return "SASECWE"; 1162 case EASORECWS: return "EASORECWS"; 1163 case EAEORECW: return "EAEORECW"; 1164 case INDEPENDENT: return "INDEPENDENT"; 1165 case SAEORSCWE: return "SAEORSCWE"; 1166 case SASORSCW: return "SASORSCW"; 1167 case SBEORSCWE: return "SBEORSCWE"; 1168 case OVERLAP: return "OVERLAP"; 1169 case EDU: return "EDU"; 1170 case SBSEASEBE: return "SBSEASEBE"; 1171 case SBSEAS: return "SBSEAS"; 1172 case SDU: return "SDU"; 1173 case SBE: return "SBE"; 1174 case EBE: return "EBE"; 1175 case SBSEBE: return "SBSEBE"; 1176 case EBSORECWS: return "EBSORECWS"; 1177 case EBS: return "EBS"; 1178 case EBEORECW: return "EBEORECW"; 1179 case SBSORSCW: return "SBSORSCW"; 1180 case SBS: return "SBS"; 1181 case AUTH: return "AUTH"; 1182 case CAUS: return "CAUS"; 1183 case COMP: return "COMP"; 1184 case CTRLV: return "CTRLV"; 1185 case MBR: return "MBR"; 1186 case STEP: return "STEP"; 1187 case ARR: return "ARR"; 1188 case DEP: return "DEP"; 1189 case PART: return "PART"; 1190 case COVBY: return "COVBY"; 1191 case DRIV: return "DRIV"; 1192 case ELNK: return "ELNK"; 1193 case EVID: return "EVID"; 1194 case EXACBY: return "EXACBY"; 1195 case EXPL: return "EXPL"; 1196 case INTF: return "INTF"; 1197 case ITEMSLOC: return "ITEMSLOC"; 1198 case LIMIT: return "LIMIT"; 1199 case META: return "META"; 1200 case MFST: return "MFST"; 1201 case NAME: return "NAME"; 1202 case OUTC: return "OUTC"; 1203 case _ACTRELATIONSIPOBJECTIVE: return "_ActRelationsipObjective"; 1204 case OBJC: return "OBJC"; 1205 case OBJF: return "OBJF"; 1206 case GOAL: return "GOAL"; 1207 case RISK: return "RISK"; 1208 case PERT: return "PERT"; 1209 case PREV: return "PREV"; 1210 case REFR: return "REFR"; 1211 case USE: return "USE"; 1212 case REFV: return "REFV"; 1213 case RELVBY: return "RELVBY"; 1214 case SEQL: return "SEQL"; 1215 case APND: return "APND"; 1216 case BSLN: return "BSLN"; 1217 case COMPLY: return "COMPLY"; 1218 case DOC: return "DOC"; 1219 case FLFS: return "FLFS"; 1220 case OCCR: return "OCCR"; 1221 case OREF: return "OREF"; 1222 case SCH: return "SCH"; 1223 case GEN: return "GEN"; 1224 case GEVL: return "GEVL"; 1225 case INST: return "INST"; 1226 case MOD: return "MOD"; 1227 case MTCH: return "MTCH"; 1228 case OPTN: return "OPTN"; 1229 case RCHAL: return "RCHAL"; 1230 case REV: return "REV"; 1231 case RPLC: return "RPLC"; 1232 case SUCC: return "SUCC"; 1233 case UPDT: return "UPDT"; 1234 case XCRPT: return "XCRPT"; 1235 case VRXCRPT: return "VRXCRPT"; 1236 case XFRM: return "XFRM"; 1237 case SPRT: return "SPRT"; 1238 case SPRTBND: return "SPRTBND"; 1239 case SUBJ: return "SUBJ"; 1240 case QUALF: return "QUALF"; 1241 case SUMM: return "SUMM"; 1242 case VALUE: return "VALUE"; 1243 case CURE: return "CURE"; 1244 case CURE_ADJ: return "CURE.ADJ"; 1245 case MTGT_ADJ: return "MTGT.ADJ"; 1246 case RACT: return "RACT"; 1247 case SUGG: return "SUGG"; 1248 case NULL: return null; 1249 default: return "?"; 1250 } 1251 } 1252 public String getSystem() { 1253 return "http://hl7.org/fhir/v3/ActRelationshipType"; 1254 } 1255 public String getDefinition() { 1256 switch (this) { 1257 case ART: return "Description: A directed association between a source Act and a target Act.\r\n\n \n Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute)"; 1258 case _ACTCLASSTEMPORALLYPERTAINS: return "ActClassTemporallyPertains"; 1259 case _ACTRELATIONSHIPACCOUNTING: return "Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element."; 1260 case _ACTRELATIONSHIPCOSTTRACKING: return "Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act."; 1261 case CHRG: return "A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service.\r\n\n The financial transaction will define the charge (bill) for delivery or performance of the service.\r\n\n Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product."; 1262 case COST: return "A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service.\r\n\n The financial transaction will define the cost of delivery or performance of the service.\r\n\n Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product."; 1263 case _ACTRELATIONSHIPPOSTING: return "Expresses values for describing the relationship between a FinancialTransaction and an Account."; 1264 case CREDIT: return "A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance."; 1265 case DEBIT: return "A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance."; 1266 case _ACTRELATIONSHIPCONDITIONAL: return "Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred"; 1267 case CIND: return "A contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used."; 1268 case PRCN: return "A requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable."; 1269 case RSON: return "Description: The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication. Child concepts may be used to describe types of indication. \r\n\n \n Discussion: In prior releases, the code \"SUGG\" (suggests) was expressed as \"an inversion of the reason link.\" That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship."; 1270 case BLOCK: return "Definition: The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring."; 1271 case DIAG: return "Description: The source act is intended to help establish the presence of a (an adverse) situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature."; 1272 case IMM: return "Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease)"; 1273 case ACTIMM: return "Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease)"; 1274 case PASSIMM: return "Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease)."; 1275 case MITGT: return "The source act removes or lessens the occurrence or effect of the target act."; 1276 case RCVY: return "Definition: The source act is performed to recover from the effects of the target act."; 1277 case PRYLX: return "Description: The source act is intended to reduce the risk of of an adverse situation to emerge as described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature."; 1278 case TREAT: return "Description: The source act is intended to improve a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature."; 1279 case ADJUNCT: return "Description: The source act is intended to offer an additional treatment for the management or cure of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. It is not a requirement that the non-adjunctive treatment is explicitly specified."; 1280 case MTREAT: return "Description: The source act is intended to provide long term maintenance improvement or management of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature."; 1281 case PALLTREAT: return "Description: The source act is intended to provide palliation for the effects of the target act."; 1282 case SYMP: return "Description: The source act is intented to provide symptomatic relief for the effects of the target act."; 1283 case TRIG: return "A pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified.\r\n\n \n Discussion: This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded."; 1284 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: return "Abstract collector for ActRelationhsip types that relate two acts by their timing."; 1285 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: return "Abstract collector for ActRelationship types that relate two acts by their approximate timing."; 1286 case ENE: return "A relationship in which the source act's effective time ends near the end of the target act's effective time. Near is defined separately as a time interval.\r\n\n \n Usage Note: Inverse code is ENS"; 1287 case ECW: return "A relationship in which the source act's effective time ends with the end of the target act's effective time.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1288 case CONCURRENT: return "A relationship in which the source act's effective time is the same as the target act's effective time.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1289 case SBSECWE: return "The source Act starts before the start of the target Act, and ends with the target Act.\r\n\n \n UsageNote: Inverse code is SASECWE"; 1290 case ENS: return "A relationship in which the source act's effective time ends near the start of the target act's effective time. Near is defined separately as a time interval.\r\n\n \n Usage Note: Inverse code is ENE"; 1291 case ECWS: return "The source Act ends when the target act starts (i.e. if we say \"ActOne ECWS ActTwo\", it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target).\r\n\n \n UsageNote: Inverse code is SCWE"; 1292 case SNE: return "A relationship in which the source act's effective time starts near the end of the target act's effective time. Near is defined separately as a time interval.\r\n\n \n Usage Note: Inverse code is SNS"; 1293 case SCWE: return "The source Act starts when the target act ends (i.e. if we say \"ActOne SCWE ActTwo\", it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target).\r\n\n \n UsageNote: Inverse code is SBSECWS"; 1294 case SNS: return "A relationship in which the source act's effective time starts near the start of the target act's effective time. Near is defined separately as a time interval.\r\n\n \n Usage Note: Inverse code is SNE"; 1295 case SCW: return "A relationship in which the source act's effective time starts with the start of the target act's effective time.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1296 case SCWSEBE: return "The source Act starts with.the target Act and ends before the end of the target Act.\r\n\n \n UsageNote: Inverse code is SCWSEAE"; 1297 case SCWSEAE: return "The source Act starts with the target Act, and ends after the end of the target Act."; 1298 case EAS: return "A relationship in which the source act ends after the target act starts.\r\n\n \n UsageNote: Inverse code is SBE"; 1299 case EAE: return "A relationship in which the source act ends after the target act ends.\r\n\n \n UsageNote: Inverse code is EBE"; 1300 case SASEAE: return "The source Act starts after start of the target Act and ends after end of the target Act.\r\n\n \n UsageNote: Inverse code is SBSEBE"; 1301 case SBEEAE: return "The source Act contains the end of the target Act.\r\n\n \n UsageNote: Inverse code is EDU"; 1302 case SASSBEEAS: return "The source Act start after the start of the target Act, and contains the end of the target Act.\r\n\n \n UsageNote: Inverse code is SBSEASEBE"; 1303 case SBSEAE: return "The source Act contains the time of the target Act.\r\n\n \n UsageNote: Inverse code is DURING"; 1304 case SAS: return "The source Act starts after the start of the target Act (i.e. if we say \"ActOne SAS ActTwo\", it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).\r\n\n \n UsageNote: Inverse code is SBS"; 1305 case SAE: return "A relationship in which the source act starts after the target act ends.\r\n\n \n UsageNote: Inverse code is EBS"; 1306 case DURING: return "A relationship in which the source act's effective time is wholly within the target act's effective time (including end points, as defined in the act's effective times)\r\n\n \n UsageNote: Inverse code is SBSEAE"; 1307 case SASECWE: return "The source Act starts after start of the target Act, and ends with the target Act.\r\n\n \n UsageNote: Inverse code is SBSECWE"; 1308 case EASORECWS: return "A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time.\r\n\n \n Usage Note: Inverse code is EBSORECWS"; 1309 case EAEORECW: return "A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time.\r\n\n \n Usage Note: Inverse code is EBEORECW"; 1310 case INDEPENDENT: return "The source Act is independent of the time of the target Act.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1311 case SAEORSCWE: return "A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time.\r\n\n \n Usage Note: Inverse code is SBEORSCWE"; 1312 case SASORSCW: return "A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time.\r\n\n \n Usage Note: Inverse code is SBSORSCW"; 1313 case SBEORSCWE: return "A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time.\r\n\n \n Usage Note: Inverse code is SAEORSCWE"; 1314 case OVERLAP: return "A relationship in which the source act's effective time overlaps the target act's effective time in any way.\r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself."; 1315 case EDU: return "A relationship in which the source act ends within the target act's effective time (including end points, as defined in the act's effective times)\r\n\n \n UsageNote: Inverse code is SBEEAE"; 1316 case SBSEASEBE: return "The source Act contains the start of the target Act, and ends before the end of the target Act.\r\n\n \n UsageNote: Inverse code is SASSBEEAS"; 1317 case SBSEAS: return "The source Act contains the start of the target Act.\r\n\n \n UsageNote: Inverse code is SDU"; 1318 case SDU: return "A relationship in which the source act starts within the target act's effective time (including end points, as defined in the act's effective times)\r\n\n \n UsageNote: Inverse code is SBSEAS"; 1319 case SBE: return "The source Act starts before the end of the target Act (i.e. if we say \"ActOne SBE ActTwo\", it means that ActOne starts before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).\r\n\n \n UsageNote: Inverse code is EAS"; 1320 case EBE: return "The source Act ends before the end of the target Act (i.e. if we say \"ActOne EBE ActTwo\", it means that ActOne ends before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).\r\n\n \n UsageNote: Inverse code is EAE"; 1321 case SBSEBE: return "The source Act starts before the start of the target Act, and ends before the end of the target Act.\r\n\n \n UsageNote: Inverse code is SASEAE"; 1322 case EBSORECWS: return "A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time.\r\n\n \n Usage Note: Inverse code is EASORECWS"; 1323 case EBS: return "A relationship in which the source act ends before the target act starts.\r\n\n \n UsageNote: Inverse code is SAE"; 1324 case EBEORECW: return "A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time.\r\n\n \n Usage Note: Inverse code is EAEORECW"; 1325 case SBSORSCW: return "A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time.\r\n\n \n Usage Note: Inverse code is SASORSCW"; 1326 case SBS: return "A relationship in which the source act begins before the target act begins.\r\n\n \n UsageNote: Inverse code is SAS"; 1327 case AUTH: return "A relationship in which the target act authorizes or certifies the source act."; 1328 case CAUS: return "Description: An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act.\r\n\n \n Examples:\n \r\n\n \n a growth of Staphylococcus aureus may be considered the cause of an abscess\n contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced\n lack of staff on the shift was deemed to be a supporting factor (proximal factor) causing the patient safety incident where the patient fell out of bed because the bed-sides had not been put up which caused the night patient to fall out of bed"; 1329 case COMP: return "The target act is a component of the source act, with no semantics regarding composition or aggregation implied."; 1330 case CTRLV: return "A relationship from an Act to a Control Variable. For example, if a Device makes an Observation, this relates the Observation to its Control Variables documenting the device's settings that influenced the observation."; 1331 case MBR: return "The target Acts are aggregated by the source Act. Target Acts may have independent existence, participate in multiple ActRelationships, and do not contribute to the meaning of the source.\r\n\n \n UsageNotes: This explicitly represents the conventional notion of aggregation. The target Act is part of a collection of Acts (no implication is made of cardinality, a source of Acts may contain zero, one, or more member target Acts).\r\n\n It is expected that this will be primarily used with _ActClassRecordOrganizer, BATTERY, and LIST"; 1332 case STEP: return "A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.\r\n\n \n UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode.\r\n\n \n OpenIssue: Need Additional guidelines on when each approach should be used."; 1333 case ARR: return "The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act entered into the source Act by means of the target Transportation act."; 1334 case DEP: return "The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act departed from the source Act by means of the target Transportation act."; 1335 case PART: return "The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act.\r\n\n \n UsageNote: In UML 1.1, this is a \"composition\" defined as: \n \"A form of aggregation with strong ownership and coincident lifetime as part of the whole. Parts with non-fixed multiplicity may be created after the composite itself, but once created they live and die with it (i.e., they share lifetimes). Such parts can also be explicitly removed before the death of the composite. Composition may be recursive.\""; 1336 case COVBY: return "A relationship in which the source act is covered by or is under the authority of a target act. A financial instrument such as an Invoice Element is covered by one or more specific instances of an Insurance Policy."; 1337 case DRIV: return "Associates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts."; 1338 case ELNK: return "Expresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter."; 1339 case EVID: return "Indicates that the target Act provides evidence in support of the action represented by the source Act. The target is not a 'reason' for the source act, but rather gives supporting information on why the source act is an appropriate course of action. Possible targets might be clinical trial results, journal articles, similar successful therapies, etc.\r\n\n \n Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies."; 1340 case EXACBY: return "Description:The source act is aggravated by the target act. (Example \"chest pain\" EXACBY \"exercise\")"; 1341 case EXPL: return "This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition."; 1342 case INTF: return "the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act.\r\n\n \n UsageNote: This provides the semantics to document barriers to care"; 1343 case ITEMSLOC: return "Items located"; 1344 case LIMIT: return "A relationship that limits or restricts the source act by the elements of the target act. For example, an authorization may be limited by a financial amount (up to $500). Target Act must be in EVN.CRIT mood."; 1345 case META: return "Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act.\r\n\n \n Constraint: Source act must have either a mood code that is not \"EVN\" (event) or its \"isCriterion\" attribute must set to \"true\". Target act must be an Act with a mood code of EVN and with isCriterionInd attribute set to \"true\"."; 1346 case MFST: return "An assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation."; 1347 case NAME: return "Used to assign a \"name\" to a condition thread. Source is a condition node, target can be any service."; 1348 case OUTC: return "An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called \"post-conditional\".) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute (AND, OR, XOR) can be used. An outcome link is often inverted to describe an outcome assessment."; 1349 case _ACTRELATIONSIPOBJECTIVE: return "The target act is a desired outcome of the source act. Source is any act (typically an intervention). Target must be an observation in criterion mood."; 1350 case OBJC: return "A desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood."; 1351 case OBJF: return "A desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood."; 1352 case GOAL: return "A goal that one defines given a patient's health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood."; 1353 case RISK: return "A noteworthy undesired outcome of a patient's condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed."; 1354 case PERT: return "This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays."; 1355 case PREV: return "A relationship in which the target act is a predecessor instance to the source act. Generally each of these instances is similar, but no identical. In healthcare coverage it is used to link a claim item to a previous claim item that might have claimed for the same set of services."; 1356 case REFR: return "A relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee."; 1357 case USE: return "Indicates that the source act makes use of (or will make use of) the information content of the target act.\r\n\n \n UsageNotes: A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate.\r\n\n \n Rationale: There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of \"references\". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference."; 1358 case REFV: return "Reference ranges are essentially descriptors of a class of result values assumed to be \"normal\", \"abnormal\", or \"critical.\" Those can vary by sex, age, or any other criterion. Source and target are observations, the target is in criterion mood. This link type can act as a trigger in case of alarms being triggered by critical results."; 1359 case RELVBY: return "Description:The source act is wholly or partially alleviated by the target act. (Example \"chest pain\" RELVBY \"sublingual nitroglycerin administration\")"; 1360 case SEQL: return "An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation."; 1361 case APND: return "An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered."; 1362 case BSLN: return "Indicates that the target observation(s) provide an initial reference for the source observation or observation group.\r\n\n \n UsageConstraints: Both source and target must be Observations or specializations thereof."; 1363 case COMPLY: return "Description:The source act complies with, adheres to, conforms to, or is permissible under (in whole or in part) the policy, contract, agreement, law, conformance criteria, certification guidelines or requirement conveyed by the target act.\r\n\n Examples for compliance relationships are: audits of adherence with a security policy, certificate of conformance to system certification requirements, or consent directive in compliance with or permissible under a privacy policy."; 1364 case DOC: return "The source act documents the target act."; 1365 case FLFS: return "The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act."; 1366 case OCCR: return "The source act is a single occurrence of a repeatable target act. The source and target act can be in any mood on the \"completion track\" but the source act must be as far as or further along the track than the target act (i.e., the occurrence of an intent can be an event but not vice versa)."; 1367 case OREF: return "Relates either an appointment request or an appointment to the order for the service being scheduled."; 1368 case SCH: return "Associates a specific time (and associated resources) with a scheduling request or other intent."; 1369 case GEN: return "The generalization relationship can be used to express categorical knowledge about services (e.g., amilorid, triamterene, and spironolactone have the common generalization potassium sparing diuretic)."; 1370 case GEVL: return "A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a \"goal distance\" (e.g., goal to observation) can be \"calculated\" and need not be sent explicitly."; 1371 case INST: return "Used to capture the link between a potential service (\"master\" or plan) and an actual service, where the actual service instantiates the potential service. The instantiation may override the master's defaults."; 1372 case MOD: return "Definition: Used to link a newer version or 'snapshot' of a business object (source) to an older version or 'snapshot' of the same business object (target).\r\n\n \n Usage:The identifier of the Act should be the same for both source and target. If the identifiers are distinct, RPLC should be used instead.\r\n\n Name from source to target = \"modifiesPrior\"\r\n\n Name from target to source = \"modifiesByNew\""; 1373 case MTCH: return "A trigger-match links an actual service (e.g., an observation or procedure that took place) with a service in criterion mood. For example if the trigger is \"observation of pain\" and pain is actually observed, and if that pain-observation caused the trigger to fire, that pain-observation can be linked with the trigger."; 1374 case OPTN: return "A relationship between a source Act that provides more detailed properties to the target Act.\r\n\n The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements.\r\n\n The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements.\r\n\n Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options."; 1375 case RCHAL: return "Description:A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated."; 1376 case REV: return "A relationship between a source Act that seeks to reverse or undo the action of the prior target Act.\r\n\n Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction.\r\n\n Constraints: the \"completion track\" mood of the target Act must be equally or more \"actual\" than the source act. I.e., when the target act is EVN the source act can be EVN, or any INT. If the target act is INT, the source act can be INT."; 1377 case RPLC: return "A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type."; 1378 case SUCC: return "Definition: A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act."; 1379 case UPDT: return "A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread."; 1380 case XCRPT: return "The source is an excerpt from the target."; 1381 case VRXCRPT: return "The source is a direct quote from the target."; 1382 case XFRM: return "Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.)"; 1383 case SPRT: return "Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post)."; 1384 case SPRTBND: return "A specialization of \"has support\" (SPRT), used to relate a secondary observation to a Region of Interest on a multidimensional observation, if the ROI specifies the true boundaries of the secondary observation as opposed to only marking the approximate area. For example, if the start and end of an ST elevation episode is visible in an EKG, this relation would indicate the ROI bounds the \"ST elevation\" observation -- the ROI defines the true beginning and ending of the episode. Conversely, if a ROI simply contains ST elevation, but it does not define the bounds (start and end) of the episode, the more general \"has support\" relation is used. Likewise, if a ROI on an image defines the true bounds of a \"1st degree burn\", the relation \"has bounded support\" is used; but if the ROI only points to the approximate area of the burn, the general \"has support\" relation is used."; 1385 case SUBJ: return "Relates an Act to its subject Act that the first Act is primarily concerned with.\r\n\n Examples\r\n\n \n \n The first Act may be a ControlAct manipulating the subject Act \r\n\n \n \n The first act is a region of interest (ROI) that defines a region within the subject Act.\r\n\n \n \n The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.\r\n\n \n \n Constraints\r\n\n An Act may have multiple subject acts.\r\n\n Rationale\r\n\n The ActRelationshipType \"has subject\" is similar to the ParticipationType \"subject\", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship."; 1386 case QUALF: return "The target observation qualifies (refines) the semantics of the source observation.\r\n\n \n UsageNote: This is not intended to replace concept refinement and qualification via vocabulary. It is used when there are multiple components which together provide the complete understanding of the source Act."; 1387 case SUMM: return "An act that contains summary values for a list or set of subordinate acts. For example, a summary of transactions for a particular accounting period."; 1388 case VALUE: return "Description:Indicates that the target Act represents the result of the source observation Act.\r\n\n \n FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified\r\n\n \n UsageNote: This relationship allows the result of an observation to be fully expressed as RIM acts as opposed to being embedded in the value attribute. For example, sending a Document act as the result of an imaging observation, sending a list of Procedures and/or other acts as the result of a medical history observation.\r\n\n The valueNegationInd attribute on the source Act has the same semantics of \"negated finding\" when it applies to the target of a VALUE ActRelationship as it does to the value attribute. On the other hand, if the ActRelationship.negationInd is true for a VALUE ActRelationship, that means the specified observation does not have the indicated value but does not imply a negated finding. Because the semantics are extremely close, it is recommended that Observation.valueNegationInd be used, not ActRelationship.negationInd.\r\n\n \n OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation."; 1389 case CURE: return "curative indication"; 1390 case CURE_ADJ: return "adjunct curative indication"; 1391 case MTGT_ADJ: return "adjunct mitigation"; 1392 case RACT: return ""; 1393 case SUGG: return ""; 1394 case NULL: return null; 1395 default: return "?"; 1396 } 1397 } 1398 public String getDisplay() { 1399 switch (this) { 1400 case ART: return "act relationship type"; 1401 case _ACTCLASSTEMPORALLYPERTAINS: return "ActClassTemporallyPertains"; 1402 case _ACTRELATIONSHIPACCOUNTING: return "ActRelationshipAccounting"; 1403 case _ACTRELATIONSHIPCOSTTRACKING: return "ActRelationshipCostTracking"; 1404 case CHRG: return "has charge"; 1405 case COST: return "has cost"; 1406 case _ACTRELATIONSHIPPOSTING: return "ActRelationshipPosting"; 1407 case CREDIT: return "has credit"; 1408 case DEBIT: return "has debit"; 1409 case _ACTRELATIONSHIPCONDITIONAL: return "ActRelationshipConditional"; 1410 case CIND: return "has contra-indication"; 1411 case PRCN: return "has pre-condition"; 1412 case RSON: return "has reason"; 1413 case BLOCK: return "blocks"; 1414 case DIAG: return "diagnoses"; 1415 case IMM: return "immunization against"; 1416 case ACTIMM: return "active immunization against"; 1417 case PASSIMM: return "passive immunization against"; 1418 case MITGT: return "mitigates"; 1419 case RCVY: return "recovers"; 1420 case PRYLX: return "prophylaxis of"; 1421 case TREAT: return "treats"; 1422 case ADJUNCT: return "adjunctive treatment"; 1423 case MTREAT: return "maintenance treatment"; 1424 case PALLTREAT: return "palliates"; 1425 case SYMP: return "symptomatic relief"; 1426 case TRIG: return "has trigger"; 1427 case _ACTRELATIONSHIPTEMPORALLYPERTAINS: return "ActRelationshipTemporallyPertains"; 1428 case _ACTRELATIONSHIPTEMPORALLYPERTAINSAPPROXIMATES: return "ActRelationshipTemporallyPertainsApproximates"; 1429 case ENE: return "ends near end"; 1430 case ECW: return "ends concurrent with"; 1431 case CONCURRENT: return "concurrent with"; 1432 case SBSECWE: return "starts before start of, ends with"; 1433 case ENS: return "ends near start"; 1434 case ECWS: return "ends concurrent with start of"; 1435 case SNE: return "starts near end"; 1436 case SCWE: return "starts concurrent with end of"; 1437 case SNS: return "starts near start"; 1438 case SCW: return "starts concurrent with"; 1439 case SCWSEBE: return "starts with. ends before end of"; 1440 case SCWSEAE: return "starts with, ends after end of"; 1441 case EAS: return "ends after start of"; 1442 case EAE: return "ends after end of"; 1443 case SASEAE: return "starts after start of, ends after end of"; 1444 case SBEEAE: return "contains end of"; 1445 case SASSBEEAS: return "start after start of, contains end of"; 1446 case SBSEAE: return "contains time of"; 1447 case SAS: return "starts after start of"; 1448 case SAE: return "starts after end of"; 1449 case DURING: return "occurs during"; 1450 case SASECWE: return "starts after start of, ends with"; 1451 case EASORECWS: return "ends after or concurrent with start of"; 1452 case EAEORECW: return "ends after or concurrent with end of"; 1453 case INDEPENDENT: return "independent of time of"; 1454 case SAEORSCWE: return "starts after or concurrent with end of"; 1455 case SASORSCW: return "starts after or concurrent with start of"; 1456 case SBEORSCWE: return "starts before or concurrent with end of"; 1457 case OVERLAP: return "overlaps with"; 1458 case EDU: return "ends during"; 1459 case SBSEASEBE: return "contains start of, ends before end of"; 1460 case SBSEAS: return "contains start of"; 1461 case SDU: return "starts during"; 1462 case SBE: return "starts before end of"; 1463 case EBE: return "ends before end of"; 1464 case SBSEBE: return "starts before start of, ends before end of"; 1465 case EBSORECWS: return "ends before or concurrent with start of"; 1466 case EBS: return "ends before start of"; 1467 case EBEORECW: return "ends before or concurrent with end of"; 1468 case SBSORSCW: return "starts before or concurrent with start of"; 1469 case SBS: return "starts before start of"; 1470 case AUTH: return "authorized by"; 1471 case CAUS: return "is etiology for"; 1472 case COMP: return "has component"; 1473 case CTRLV: return "has control variable"; 1474 case MBR: return "has member"; 1475 case STEP: return "has step"; 1476 case ARR: return "arrival"; 1477 case DEP: return "departure"; 1478 case PART: return "has part"; 1479 case COVBY: return "covered by"; 1480 case DRIV: return "is derived from"; 1481 case ELNK: return "episodeLink"; 1482 case EVID: return "provides evidence for"; 1483 case EXACBY: return "exacerbated by"; 1484 case EXPL: return "has explanation"; 1485 case INTF: return "interfered by"; 1486 case ITEMSLOC: return "items located"; 1487 case LIMIT: return "limited by"; 1488 case META: return "has metadata"; 1489 case MFST: return "is manifestation of"; 1490 case NAME: return "assigns name"; 1491 case OUTC: return "has outcome"; 1492 case _ACTRELATIONSIPOBJECTIVE: return "Act Relationsip Objective"; 1493 case OBJC: return "has continuing objective"; 1494 case OBJF: return "has final objective"; 1495 case GOAL: return "has goal"; 1496 case RISK: return "has risk"; 1497 case PERT: return "has pertinent information"; 1498 case PREV: return "has previous instance"; 1499 case REFR: return "refers to"; 1500 case USE: return "uses"; 1501 case REFV: return "has reference values"; 1502 case RELVBY: return "relieved by"; 1503 case SEQL: return "is sequel"; 1504 case APND: return "is appendage"; 1505 case BSLN: return "has baseline"; 1506 case COMPLY: return "complies with"; 1507 case DOC: return "documents"; 1508 case FLFS: return "fulfills"; 1509 case OCCR: return "occurrence"; 1510 case OREF: return "references order"; 1511 case SCH: return "schedules request"; 1512 case GEN: return "has generalization"; 1513 case GEVL: return "evaluates (goal)"; 1514 case INST: return "instantiates (master)"; 1515 case MOD: return "modifies"; 1516 case MTCH: return "matches (trigger)"; 1517 case OPTN: return "has option"; 1518 case RCHAL: return "re-challenge"; 1519 case REV: return "reverses"; 1520 case RPLC: return "replaces"; 1521 case SUCC: return "succeeds"; 1522 case UPDT: return "updates (condition)"; 1523 case XCRPT: return "Excerpts"; 1524 case VRXCRPT: return "Excerpt verbatim"; 1525 case XFRM: return "transformation"; 1526 case SPRT: return "has support"; 1527 case SPRTBND: return "has bounded support"; 1528 case SUBJ: return "has subject"; 1529 case QUALF: return "has qualifier"; 1530 case SUMM: return "summarized by"; 1531 case VALUE: return "has value"; 1532 case CURE: return "curative indication"; 1533 case CURE_ADJ: return "adjunct curative indication"; 1534 case MTGT_ADJ: return "adjunct mitigation"; 1535 case RACT: return "RACT"; 1536 case SUGG: return "SUGG"; 1537 case NULL: return null; 1538 default: return "?"; 1539 } 1540 } 1541 1542 1543}