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