001package org.hl7.fhir.r4.model.codesystems; 002 003/* 004 Copyright (c) 2011+, HL7, Inc. 005 All rights reserved. 006 007 Redistribution and use in source and binary forms, with or without modification, 008 are permitted provided that the following conditions are met: 009 010 * Redistributions of source code must retain the above copyright notice, this 011 list of conditions and the following disclaimer. 012 * Redistributions in binary form must reproduce the above copyright notice, 013 this list of conditions and the following disclaimer in the documentation 014 and/or other materials provided with the distribution. 015 * Neither the name of HL7 nor the names of its contributors may be used to 016 endorse or promote products derived from this software without specific 017 prior written permission. 018 019 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 020 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 021 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 022 IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 023 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 024 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 025 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, 026 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 027 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 028 POSSIBILITY OF SUCH DAMAGE. 029 030*/ 031 032// Generated on Wed, Jan 30, 2019 16:19-0500 for FHIR v4.0.0 033 034import org.hl7.fhir.exceptions.FHIRException; 035 036public enum V3Hl7PublishingDomain { 037 038 /** 039 * Description: Represents the HL7 content "domain" that supports accounting and 040 * billing functions - and "provides support for the creation and management of 041 * patient billing accounts and the post of financial transactions against 042 * patient billing accounts for the purpose of aggregating financial 043 * transactions that will be submitted as claims or invoices for reimbursemen" 044 * 045 * 046 * UsageNote: V3 Specifications are published in a set of "domains", which 047 * contain interactions and related specifications for a single area of health 048 * care within which can be supported by a single, coherent set of 049 * interoperability specifications. 050 */ 051 AB, 052 /** 053 * Description: Represents the HL7 content "domain" that supports trigger event 054 * control act infrastructure - and "covers the alternate structures of the 055 * message Trigger Event Control Acts in the HL7 Composite Message." 056 * 057 * 058 * UsageNote: V3 Specifications are published in a set of "domains", which 059 * contain interactions and related specifications for a single area of health 060 * care within which can be supported by a single, coherent set of 061 * interoperability specifications. 062 */ 063 AI, 064 /** 065 * Description: Represents the HL7 content "domain" that was defined as an 066 * "artificial listing" domain to support publication testing. 067 */ 068 AL, 069 /** 070 * Description: Represents the HL7 content "domain" that supports blood tissue 071 * and organ domain - and "comprises the models, messages, and other artIfacts 072 * that are needed to support messaging related to the process of blood, tissue, 073 * and organ banking operations such as donations, eligibility, storage, 074 * dispense, administration/transfusion, explantation, and implantation. " 075 * 076 * 077 * UsageNote: V3 Specifications are published in a set of "domains", which 078 * contain interactions and related specifications for a single area of health 079 * care within which can be supported by a single, coherent set of 080 * interoperability specifications. 081 */ 082 BB, 083 /** 084 * Description: Represents the HL7 content "domain" that supports the clinical 085 * document architecture. 086 * 087 * 088 * UsageNote: V3 Specifications are published in a set of "domains", which 089 * contain interactions and related specifications for a single area of health 090 * care within which can be supported by a single, coherent set of 091 * interoperability specifications. 092 */ 093 CD, 094 /** 095 * Description: Represents the HL7 content "domain" that supports clinical 096 * genomics - and includes " standards to enable the exchange of interrelated 097 * clinical and personalized genomic data between interested parties." 098 * 099 * 100 * UsageNote: V3 Specifications are published in a set of "domains", which 101 * contain interactions and related specifications for a single area of health 102 * care within which can be supported by a single, coherent set of 103 * interoperability specifications. 104 */ 105 CG, 106 /** 107 * Description: Represents the HL7 content "domain" that supports transmission 108 * infrastructure - and " is primarily concerned with the data content of 109 * exchanges between healthcare applications, the sequence or interrelationships 110 * in the flow of messages and the communication of significant application 111 * level exceptions or error conditions." 112 * 113 * 114 * UsageNote: V3 Specifications are published in a set of "domains", which 115 * contain interactions and related specifications for a single area of health 116 * care within which can be supported by a single, coherent set of 117 * interoperability specifications. 118 */ 119 CI, 120 /** 121 * Description: Represents the HL7 content "domain" that supports Coverage - and 122 * provides support for managing health care coverage in the reimbursement 123 * system(s). 124 * 125 * 126 * UsageNote: V3 Specifications are published in a set of "domains", which 127 * contain interactions and related specifications for a single area of health 128 * care within which can be supported by a single, coherent set of 129 * interoperability specifications. 130 */ 131 CO, 132 /** 133 * Description: Represents the HL7 content "domain" that supports the common 134 * product model - which "is used to improve the alignment between the different 135 * representations of products used within the body of HL7 Version 3 models." 136 * 137 * 138 * UsageNote: V3 Specifications are published in a set of "domains", which 139 * contain interactions and related specifications for a single area of health 140 * care within which can be supported by a single, coherent set of 141 * interoperability specifications. 142 */ 143 CP, 144 /** 145 * Description: Represents the HL7 content "domain" that supports Claims and 146 * Reimbursement - and "provides support for Generic, Pharmacy, Preferred 147 * Accommodation, Physician, Oral Health Vision Care and Hospital claims for 148 * eligibility, authorization, coverage extension, pre-determination, invoice 149 * adjudication, payment advice and Statement of Financial Activity (SOFA) 150 * Release 3 of this document adds claims messaging support for Physician, Oral 151 * Health Vision Care and Hospital claims." 152 * 153 * 154 * UsageNote: V3 Specifications are published in a set of "domains", which 155 * contain interactions and related specifications for a single area of health 156 * care within which can be supported by a single, coherent set of 157 * interoperability specifications. 158 */ 159 CR, 160 /** 161 * Description: Represents the HL7 content "domain" that supports a common 162 * clinical statement pattern - and "is a 'pattern' designed to be used within 163 * multiple HL7 Version 3 domain models. This pattern is intended to facilitate 164 * the consistent design of communications that convey clinical information to 165 * meet specific use cases." 166 * 167 * 168 * UsageNote: V3 Specifications are published in a set of "domains", which 169 * contain interactions and related specifications for a single area of health 170 * care within which can be supported by a single, coherent set of 171 * interoperability specifications. 172 */ 173 CS, 174 /** 175 * Description: Represents the HL7 content "domain" that supports common model 176 * types - and "are a work product produced by a particular committee for 177 * expressing a common, useful and reusable concept." 178 * 179 * 180 * UsageNote: V3 Specifications are published in a set of "domains", which 181 * contain interactions and related specifications for a single area of health 182 * care within which can be supported by a single, coherent set of 183 * interoperability specifications. 184 */ 185 CT, 186 /** 187 * Description: Represents the HL7 content "domain" that was created to support 188 * testing and initial set-up functions. 189 */ 190 DD, 191 /** 192 * Description: This domain has been retired in favor of "imaging integration" 193 * (II). 194 */ 195 DI, 196 /** 197 * Description: Represents the HL7 content "domain" that provides decision 198 * support. 199 * 200 * 201 * UsageNote: V3 Specifications are published in a set of "domains", which 202 * contain interactions and related specifications for a single area of health 203 * care within which can be supported by a single, coherent set of 204 * interoperability specifications. 205 */ 206 DS, 207 /** 208 * Description: Represents the HL7 content "domain" that supports Emergency 209 * Medical Services. 210 * 211 * 212 * UsageNote: V3 Specifications are published in a set of "domains", which 213 * contain interactions and related specifications for a single area of health 214 * care within which can be supported by a single, coherent set of 215 * interoperability specifications. 216 */ 217 EM, 218 /** 219 * Description: Represents the HL7 content "domain" that supports imaging 220 * integration - and is "comprises the models, implementation guides, sample 221 * documents and images that are needed to illustrate the transformation of 222 * DICOM structured reports to CDA Release 2 as well as the creation of CDA 223 * diagnostic imaging reports." 224 * 225 * 226 * UsageNote: V3 Specifications are published in a set of "domains", which 227 * contain interactions and related specifications for a single area of health 228 * care within which can be supported by a single, coherent set of 229 * interoperability specifications. 230 */ 231 II, 232 /** 233 * Description: Represents the HL7 content "domain" that supports immunization - 234 * and "describes communication of information about immunization: the 235 * administration of vaccines (and/or antisera) to individuals to prevent 236 * infectious disease." 237 * 238 * 239 * UsageNote: V3 Specifications are published in a set of "domains", which 240 * contain interactions and related specifications for a single area of health 241 * care within which can be supported by a single, coherent set of 242 * interoperability specifications. 243 */ 244 IZ, 245 /** 246 * Description: Represents the HL7 content "domain" that supports clinical 247 * laboratory functions - and is "comprises the models, messages, and other 248 * artifacts that are needed to support messaging related to laboratory tests or 249 * observations. " 250 * 251 * 252 * UsageNote: V3 Specifications are published in a set of "domains", which 253 * contain interactions and related specifications for a single area of health 254 * care within which can be supported by a single, coherent set of 255 * interoperability specifications. 256 */ 257 LB, 258 /** 259 * Description: Represents the HL7 content "domain" that supports medication - 260 * and "deals with the description of a medicine for the purposes of messaging 261 * information about medicines" and the applications of these descriptions. 262 * 263 * 264 * UsageNote: V3 Specifications are published in a set of "domains", which 265 * contain interactions and related specifications for a single area of health 266 * care within which can be supported by a single, coherent set of 267 * interoperability specifications. 268 */ 269 ME, 270 /** 271 * Description: Represents the HL7 content "domain" that supports master file 272 * infrastructure - and is "comprises the classes and attributes needed to 273 * support Master Files and Registries." 274 * 275 * 276 * UsageNote: V3 Specifications are published in a set of "domains", which 277 * contain interactions and related specifications for a single area of health 278 * care within which can be supported by a single, coherent set of 279 * interoperability specifications. 280 */ 281 MI, 282 /** 283 * Description: Represents the HL7 content "domain" that supports Materials 284 * Management - and is "supports the simple scenario of a Materials Management 285 * application sending requests, notifications and queries to an auxiliary 286 * application. The intent is to establish a standard for the minimum 287 * functionality that is useful and comprehensive enough to explore the 288 * important concepts relative to inventory management." 289 * 290 * 291 * UsageNote: V3 Specifications are published in a set of "domains", which 292 * contain interactions and related specifications for a single area of health 293 * care within which can be supported by a single, coherent set of 294 * interoperability specifications. 295 */ 296 MM, 297 /** 298 * Description: Represents the HL7 content "domain" that supports medical 299 * records - and is "supports clinical document management, and document 300 * querying." 301 * 302 * 303 * UsageNote: V3 Specifications are published in a set of "domains", which 304 * contain interactions and related specifications for a single area of health 305 * care within which can be supported by a single, coherent set of 306 * interoperability specifications. 307 */ 308 MR, 309 /** 310 * Description: Represents the HL7 content "domain" that supports shared 311 * messages - and "are a work product produced for expressing common, useful and 312 * reusable message types." 313 * 314 * 315 * UsageNote: V3 Specifications are published in a set of "domains", which 316 * contain interactions and related specifications for a single area of health 317 * care within which can be supported by a single, coherent set of 318 * interoperability specifications. 319 */ 320 MT, 321 /** 322 * Description: Represents the HL7 content "domain" that supports observations - 323 * and is "comprises the models, messages, and other artifacts that are needed 324 * to support messaging related to resulting basic healthcare diagnostic 325 * services. " 326 * 327 * 328 * UsageNote: V3 Specifications are published in a set of "domains", which 329 * contain interactions and related specifications for a single area of health 330 * care within which can be supported by a single, coherent set of 331 * interoperability specifications. 332 */ 333 OB, 334 /** 335 * Description: Represents the HL7 content "domain" that supports orders and 336 * observations - and will provide over-arching support information for the 337 * "Orders" (OR) and "Observations" (OB) domains. 338 * 339 * 340 * UsageNote: V3 Specifications are published in a set of "domains", which 341 * contain interactions and related specifications for a single area of health 342 * care within which can be supported by a single, coherent set of 343 * interoperability specifications. 344 */ 345 OO, 346 /** 347 * Description: Represents the HL7 content "domain" that supports orders - and 348 * "comprises the models, messages, and other artifacts that are needed to 349 * support messaging related to ordering basic healthcare services." 350 * 351 * 352 * UsageNote: V3 Specifications are published in a set of "domains", which 353 * contain interactions and related specifications for a single area of health 354 * care within which can be supported by a single, coherent set of 355 * interoperability specifications. 356 */ 357 OR, 358 /** 359 * Description: Represents the HL7 content "domain" that supports Patient 360 * Administration - and "defines person and patient demographics and visit 361 * information about patients" 362 * 363 * 364 * UsageNote: V3 Specifications are published in a set of "domains", which 365 * contain interactions and related specifications for a single area of health 366 * care within which can be supported by a single, coherent set of 367 * interoperability specifications. 368 */ 369 PA, 370 /** 371 * Description: Represents the HL7 content "domain" that supports Care Provision 372 * - and "addresses the information that is needed for the ongoing care of 373 * individuals, populations, and other targets of care." 374 * 375 * 376 * UsageNote: V3 Specifications are published in a set of "domains", which 377 * contain interactions and related specifications for a single area of health 378 * care within which can be supported by a single, coherent set of 379 * interoperability specifications. 380 */ 381 PC, 382 /** 383 * Description: Represents the HL7 content "domain" that supports public health 384 * - and is "the source of a number of Common Model Element Types (CMET) 385 * designed to meet the needs of public health data exchange." 386 * 387 * 388 * UsageNote: V3 Specifications are published in a set of "domains", which 389 * contain interactions and related specifications for a single area of health 390 * care within which can be supported by a single, coherent set of 391 * interoperability specifications. 392 */ 393 PH, 394 /** 395 * Description: Represents the HL7 content "domain" that supports Personnel 396 * Management - and "spans a variety of clinical-administrative information 397 * functions associated with the organizations, individuals, animals and devices 398 * involved in the delivery and support of healthcare services." 399 * 400 * 401 * UsageNote: V3 Specifications are published in a set of "domains", which 402 * contain interactions and related specifications for a single area of health 403 * care within which can be supported by a single, coherent set of 404 * interoperability specifications. 405 */ 406 PM, 407 /** 408 * Description: Represents the HL7 content "domain" that supports query 409 * infrastructure - and "specifies the formation of information queries and the 410 * responses to these queries to meet the needs of healthcare applications using 411 * the HL7 version 3 messaging standard." 412 * 413 * 414 * UsageNote: V3 Specifications are published in a set of "domains", which 415 * contain interactions and related specifications for a single area of health 416 * care within which can be supported by a single, coherent set of 417 * interoperability specifications. 418 */ 419 QI, 420 /** 421 * Description: Represents the HL7 content "domain" that supports Quality 422 * Measures - and "is a standard for representing a health quality measure as an 423 * electronic document." 424 * 425 * 426 * UsageNote: V3 Specifications are published in a set of "domains", which 427 * contain interactions and related specifications for a single area of health 428 * care within which can be supported by a single, coherent set of 429 * interoperability specifications. 430 */ 431 QM, 432 /** 433 * Description: Represents the HL7 content "domain" that supports Registries - 434 * and "collects HL7 artifacts for administrative registries." 435 * 436 * 437 * UsageNote: V3 Specifications are published in a set of "domains", which 438 * contain interactions and related specifications for a single area of health 439 * care within which can be supported by a single, coherent set of 440 * interoperability specifications. 441 */ 442 RG, 443 /** 444 * Description: Represents the HL7 content "domain" that supports Informative 445 * Public Health. 446 * 447 * 448 * UsageNote: V3 Specifications are published in a set of "domains", which 449 * contain interactions and related specifications for a single area of health 450 * care within which can be supported by a single, coherent set of 451 * interoperability specifications. 452 */ 453 RI, 454 /** 455 * Description: Represents the HL7 content "domain" that supports Regulated 456 * Products - and "includes standards developed as part of the family of 457 * messages targeted for the exchange of information about regulated products 458 * and the exchange of the data needed to provide approval for such products." 459 * 460 * 461 * UsageNote: V3 Specifications are published in a set of "domains", which 462 * contain interactions and related specifications for a single area of health 463 * care within which can be supported by a single, coherent set of 464 * interoperability specifications. 465 */ 466 RP, 467 /** 468 * Description: Represents the HL7 content "domain" that supports Public Health 469 * Reporting - and "includes messages and documents that are specifically 470 * designed to support managment, reporting and investigation in the public 471 * health context." 472 * 473 * 474 * UsageNote: V3 Specifications are published in a set of "domains", which 475 * contain interactions and related specifications for a single area of health 476 * care within which can be supported by a single, coherent set of 477 * interoperability specifications. 478 */ 479 RR, 480 /** 481 * Description: Represents the HL7 content "domain" that supports Regulated 482 * Studies - and is "includes standards developed as part of the family of 483 * messages targeted for the exchange of information about the conduct of 484 * regulated studies, and the exchange of the data collected during those 485 * studies." 486 * 487 * 488 * UsageNote: V3 Specifications are published in a set of "domains", which 489 * contain interactions and related specifications for a single area of health 490 * care within which can be supported by a single, coherent set of 491 * interoperability specifications. 492 */ 493 RT, 494 /** 495 * Description: Represents the HL7 content "domain" that supports pharmacy - and 496 * is a "model used to derive message patterns to describe and communicate 497 * processes related to medication." 498 * 499 * 500 * UsageNote: V3 Specifications are published in a set of "domains", which 501 * contain interactions and related specifications for a single area of health 502 * care within which can be supported by a single, coherent set of 503 * interoperability specifications. 504 */ 505 RX, 506 /** 507 * Description: Represents the HL7 content "domain" that supports Scheduling - 508 * and "offers a generic set of messages and behavior to implement any number of 509 * Scheduling scenarios." 510 * 511 * 512 * UsageNote: V3 Specifications are published in a set of "domains", which 513 * contain interactions and related specifications for a single area of health 514 * care within which can be supported by a single, coherent set of 515 * interoperability specifications. 516 */ 517 SC, 518 /** 519 * Description: Represents the HL7 content "domain" that supports Specimen - and 520 * "comprises the models and artifacts that are needed to support the creation 521 * of messaging related to specimen." 522 * 523 * 524 * UsageNote: V3 Specifications are published in a set of "domains", which 525 * contain interactions and related specifications for a single area of health 526 * care within which can be supported by a single, coherent set of 527 * interoperability specifications. 528 */ 529 SP, 530 /** 531 * Description: Represents the HL7 content "domain" that supports Therapeutic 532 * Devices - and is "comprises the models, messages, and other artifacts that 533 * are needed to support messaging related to therapy delivery and observations 534 * made by a medical device. " 535 * 536 * 537 * UsageNote: V3 Specifications are published in a set of "domains", which 538 * contain interactions and related specifications for a single area of health 539 * care within which can be supported by a single, coherent set of 540 * interoperability specifications. 541 */ 542 TD, 543 /** 544 * added to help the parsers 545 */ 546 NULL; 547 548 public static V3Hl7PublishingDomain fromCode(String codeString) throws FHIRException { 549 if (codeString == null || "".equals(codeString)) 550 return null; 551 if ("AB".equals(codeString)) 552 return AB; 553 if ("AI".equals(codeString)) 554 return AI; 555 if ("AL".equals(codeString)) 556 return AL; 557 if ("BB".equals(codeString)) 558 return BB; 559 if ("CD".equals(codeString)) 560 return CD; 561 if ("CG".equals(codeString)) 562 return CG; 563 if ("CI".equals(codeString)) 564 return CI; 565 if ("CO".equals(codeString)) 566 return CO; 567 if ("CP".equals(codeString)) 568 return CP; 569 if ("CR".equals(codeString)) 570 return CR; 571 if ("CS".equals(codeString)) 572 return CS; 573 if ("CT".equals(codeString)) 574 return CT; 575 if ("DD".equals(codeString)) 576 return DD; 577 if ("DI".equals(codeString)) 578 return DI; 579 if ("DS".equals(codeString)) 580 return DS; 581 if ("EM".equals(codeString)) 582 return EM; 583 if ("II".equals(codeString)) 584 return II; 585 if ("IZ".equals(codeString)) 586 return IZ; 587 if ("LB".equals(codeString)) 588 return LB; 589 if ("ME".equals(codeString)) 590 return ME; 591 if ("MI".equals(codeString)) 592 return MI; 593 if ("MM".equals(codeString)) 594 return MM; 595 if ("MR".equals(codeString)) 596 return MR; 597 if ("MT".equals(codeString)) 598 return MT; 599 if ("OB".equals(codeString)) 600 return OB; 601 if ("OO".equals(codeString)) 602 return OO; 603 if ("OR".equals(codeString)) 604 return OR; 605 if ("PA".equals(codeString)) 606 return PA; 607 if ("PC".equals(codeString)) 608 return PC; 609 if ("PH".equals(codeString)) 610 return PH; 611 if ("PM".equals(codeString)) 612 return PM; 613 if ("QI".equals(codeString)) 614 return QI; 615 if ("QM".equals(codeString)) 616 return QM; 617 if ("RG".equals(codeString)) 618 return RG; 619 if ("RI".equals(codeString)) 620 return RI; 621 if ("RP".equals(codeString)) 622 return RP; 623 if ("RR".equals(codeString)) 624 return RR; 625 if ("RT".equals(codeString)) 626 return RT; 627 if ("RX".equals(codeString)) 628 return RX; 629 if ("SC".equals(codeString)) 630 return SC; 631 if ("SP".equals(codeString)) 632 return SP; 633 if ("TD".equals(codeString)) 634 return TD; 635 throw new FHIRException("Unknown V3Hl7PublishingDomain code '" + codeString + "'"); 636 } 637 638 public String toCode() { 639 switch (this) { 640 case AB: 641 return "AB"; 642 case AI: 643 return "AI"; 644 case AL: 645 return "AL"; 646 case BB: 647 return "BB"; 648 case CD: 649 return "CD"; 650 case CG: 651 return "CG"; 652 case CI: 653 return "CI"; 654 case CO: 655 return "CO"; 656 case CP: 657 return "CP"; 658 case CR: 659 return "CR"; 660 case CS: 661 return "CS"; 662 case CT: 663 return "CT"; 664 case DD: 665 return "DD"; 666 case DI: 667 return "DI"; 668 case DS: 669 return "DS"; 670 case EM: 671 return "EM"; 672 case II: 673 return "II"; 674 case IZ: 675 return "IZ"; 676 case LB: 677 return "LB"; 678 case ME: 679 return "ME"; 680 case MI: 681 return "MI"; 682 case MM: 683 return "MM"; 684 case MR: 685 return "MR"; 686 case MT: 687 return "MT"; 688 case OB: 689 return "OB"; 690 case OO: 691 return "OO"; 692 case OR: 693 return "OR"; 694 case PA: 695 return "PA"; 696 case PC: 697 return "PC"; 698 case PH: 699 return "PH"; 700 case PM: 701 return "PM"; 702 case QI: 703 return "QI"; 704 case QM: 705 return "QM"; 706 case RG: 707 return "RG"; 708 case RI: 709 return "RI"; 710 case RP: 711 return "RP"; 712 case RR: 713 return "RR"; 714 case RT: 715 return "RT"; 716 case RX: 717 return "RX"; 718 case SC: 719 return "SC"; 720 case SP: 721 return "SP"; 722 case TD: 723 return "TD"; 724 case NULL: 725 return null; 726 default: 727 return "?"; 728 } 729 } 730 731 public String getSystem() { 732 return "http://terminology.hl7.org/CodeSystem/v3-hl7PublishingDomain"; 733 } 734 735 public String getDefinition() { 736 switch (this) { 737 case AB: 738 return "Description: Represents the HL7 content \"domain\" that supports accounting and billing functions - and \"provides support for the creation and management of patient billing accounts and the post of financial transactions against patient billing accounts for the purpose of aggregating financial transactions that will be submitted as claims or invoices for reimbursemen\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 739 case AI: 740 return "Description: Represents the HL7 content \"domain\" that supports trigger event control act infrastructure - and \"covers the alternate structures of the message Trigger Event Control Acts in the HL7 Composite Message.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 741 case AL: 742 return "Description: Represents the HL7 content \"domain\" that was defined as an \"artificial listing\" domain to support publication testing."; 743 case BB: 744 return "Description: Represents the HL7 content \"domain\" that supports blood tissue and organ domain - and \"comprises the models, messages, and other artIfacts that are needed to support messaging related to the process of blood, tissue, and organ banking operations such as donations, eligibility, storage, dispense, administration/transfusion, explantation, and implantation. \"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 745 case CD: 746 return "Description: Represents the HL7 content \"domain\" that supports the clinical document architecture.\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 747 case CG: 748 return "Description: Represents the HL7 content \"domain\" that supports clinical genomics - and includes \" standards to enable the exchange of interrelated clinical and personalized genomic data between interested parties.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 749 case CI: 750 return "Description: Represents the HL7 content \"domain\" that supports transmission infrastructure - and \" is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 751 case CO: 752 return "Description: Represents the HL7 content \"domain\" that supports Coverage - and provides support for managing health care coverage in the reimbursement system(s).\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 753 case CP: 754 return "Description: Represents the HL7 content \"domain\" that supports the common product model - which \"is used to improve the alignment between the different representations of products used within the body of HL7 Version 3 models.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 755 case CR: 756 return "Description: Represents the HL7 content \"domain\" that supports Claims and Reimbursement - and \"provides support for Generic, Pharmacy, Preferred Accommodation, Physician, Oral Health Vision Care and Hospital claims for eligibility, authorization, coverage extension, pre-determination, invoice adjudication, payment advice and Statement of Financial Activity (SOFA) Release 3 of this document adds claims messaging support for Physician, Oral Health Vision Care and Hospital claims.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 757 case CS: 758 return "Description: Represents the HL7 content \"domain\" that supports a common clinical statement pattern - and \"is a 'pattern' designed to be used within multiple HL7 Version 3 domain models. This pattern is intended to facilitate the consistent design of communications that convey clinical information to meet specific use cases.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 759 case CT: 760 return "Description: Represents the HL7 content \"domain\" that supports common model types - and \"are a work product produced by a particular committee for expressing a common, useful and reusable concept.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 761 case DD: 762 return "Description: Represents the HL7 content \"domain\" that was created to support testing and initial set-up functions."; 763 case DI: 764 return "Description: This domain has been retired in favor of \"imaging integration\" (II)."; 765 case DS: 766 return "Description: Represents the HL7 content \"domain\" that provides decision support.\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 767 case EM: 768 return "Description: Represents the HL7 content \"domain\" that supports Emergency Medical Services.\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 769 case II: 770 return "Description: Represents the HL7 content \"domain\" that supports imaging integration - and is \"comprises the models, implementation guides, sample documents and images that are needed to illustrate the transformation of DICOM structured reports to CDA Release 2 as well as the creation of CDA diagnostic imaging reports.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 771 case IZ: 772 return "Description: Represents the HL7 content \"domain\" that supports immunization - and \"describes communication of information about immunization: the administration of vaccines (and/or antisera) to individuals to prevent infectious disease.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 773 case LB: 774 return "Description: Represents the HL7 content \"domain\" that supports clinical laboratory functions - and is \"comprises the models, messages, and other artifacts that are needed to support messaging related to laboratory tests or observations. \"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 775 case ME: 776 return "Description: Represents the HL7 content \"domain\" that supports medication - and \"deals with the description of a medicine for the purposes of messaging information about medicines\" and the applications of these descriptions.\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 777 case MI: 778 return "Description: Represents the HL7 content \"domain\" that supports master file infrastructure - and is \"comprises the classes and attributes needed to support Master Files and Registries.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 779 case MM: 780 return "Description: Represents the HL7 content \"domain\" that supports Materials Management - and is \"supports the simple scenario of a Materials Management application sending requests, notifications and queries to an auxiliary application. The intent is to establish a standard for the minimum functionality that is useful and comprehensive enough to explore the important concepts relative to inventory management.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 781 case MR: 782 return "Description: Represents the HL7 content \"domain\" that supports medical records - and is \"supports clinical document management, and document querying.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 783 case MT: 784 return "Description: Represents the HL7 content \"domain\" that supports shared messages - and \"are a work product produced for expressing common, useful and reusable message types.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 785 case OB: 786 return "Description: Represents the HL7 content \"domain\" that supports observations - and is \"comprises the models, messages, and other artifacts that are needed to support messaging related to resulting basic healthcare diagnostic services. \"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 787 case OO: 788 return "Description: Represents the HL7 content \"domain\" that supports orders and observations - and will provide over-arching support information for the \"Orders\" (OR) and \"Observations\" (OB) domains.\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 789 case OR: 790 return "Description: Represents the HL7 content \"domain\" that supports orders - and \"comprises the models, messages, and other artifacts that are needed to support messaging related to ordering basic healthcare services.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 791 case PA: 792 return "Description: Represents the HL7 content \"domain\" that supports Patient Administration - and \"defines person and patient demographics and visit information about patients\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 793 case PC: 794 return "Description: Represents the HL7 content \"domain\" that supports Care Provision - and \"addresses the information that is needed for the ongoing care of individuals, populations, and other targets of care.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 795 case PH: 796 return "Description: Represents the HL7 content \"domain\" that supports public health - and is \"the source of a number of Common Model Element Types (CMET) designed to meet the needs of public health data exchange.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 797 case PM: 798 return "Description: Represents the HL7 content \"domain\" that supports Personnel Management - and \"spans a variety of clinical-administrative information functions associated with the organizations, individuals, animals and devices involved in the delivery and support of healthcare services.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 799 case QI: 800 return "Description: Represents the HL7 content \"domain\" that supports query infrastructure - and \"specifies the formation of information queries and the responses to these queries to meet the needs of healthcare applications using the HL7 version 3 messaging standard.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 801 case QM: 802 return "Description: Represents the HL7 content \"domain\" that supports Quality Measures - and \"is a standard for representing a health quality measure as an electronic document.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 803 case RG: 804 return "Description: Represents the HL7 content \"domain\" that supports Registries - and \"collects HL7 artifacts for administrative registries.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 805 case RI: 806 return "Description: Represents the HL7 content \"domain\" that supports Informative Public Health.\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 807 case RP: 808 return "Description: Represents the HL7 content \"domain\" that supports Regulated Products - and \"includes standards developed as part of the family of messages targeted for the exchange of information about regulated products and the exchange of the data needed to provide approval for such products.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 809 case RR: 810 return "Description: Represents the HL7 content \"domain\" that supports Public Health Reporting - and \"includes messages and documents that are specifically designed to support managment, reporting and investigation in the public health context.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 811 case RT: 812 return "Description: Represents the HL7 content \"domain\" that supports Regulated Studies - and is \"includes standards developed as part of the family of messages targeted for the exchange of information about the conduct of regulated studies, and the exchange of the data collected during those studies.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 813 case RX: 814 return "Description: Represents the HL7 content \"domain\" that supports pharmacy - and is a \"model used to derive message patterns to describe and communicate processes related to medication.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 815 case SC: 816 return "Description: Represents the HL7 content \"domain\" that supports Scheduling - and \"offers a generic set of messages and behavior to implement any number of Scheduling scenarios.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 817 case SP: 818 return "Description: Represents the HL7 content \"domain\" that supports Specimen - and \"comprises the models and artifacts that are needed to support the creation of messaging related to specimen.\"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 819 case TD: 820 return "Description: Represents the HL7 content \"domain\" that supports Therapeutic Devices - and is \"comprises the models, messages, and other artifacts that are needed to support messaging related to therapy delivery and observations made by a medical device. \"\r\n\n \n UsageNote: V3 Specifications are published in a set of \"domains\", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."; 821 case NULL: 822 return null; 823 default: 824 return "?"; 825 } 826 } 827 828 public String getDisplay() { 829 switch (this) { 830 case AB: 831 return "accounting & billing"; 832 case AI: 833 return "trigger event control act infrastructure"; 834 case AL: 835 return "artificial listing for test purposes - faux Domain for testing"; 836 case BB: 837 return "blood tissue and organ"; 838 case CD: 839 return "clinical document architecture"; 840 case CG: 841 return "clinical genomics"; 842 case CI: 843 return "transmission infrastructure"; 844 case CO: 845 return "coverage"; 846 case CP: 847 return "common product model"; 848 case CR: 849 return "claims and reimbursement"; 850 case CS: 851 return "clinical statement"; 852 case CT: 853 return "common types"; 854 case DD: 855 return "dummy domain"; 856 case DI: 857 return "diagnostic imaging"; 858 case DS: 859 return "decision support"; 860 case EM: 861 return "emergency medical services"; 862 case II: 863 return "imaging integration"; 864 case IZ: 865 return "immunization"; 866 case LB: 867 return "laboratory"; 868 case ME: 869 return "medication"; 870 case MI: 871 return "masterfile infrastructure"; 872 case MM: 873 return "materials management"; 874 case MR: 875 return "medical records"; 876 case MT: 877 return "shared messages"; 878 case OB: 879 return "observations"; 880 case OO: 881 return "orders & observations"; 882 case OR: 883 return "orders"; 884 case PA: 885 return "patient administration"; 886 case PC: 887 return "care provision"; 888 case PH: 889 return "public health"; 890 case PM: 891 return "personnel management"; 892 case QI: 893 return "query infrastructure"; 894 case QM: 895 return "quality measures"; 896 case RG: 897 return "registries"; 898 case RI: 899 return "informative public health"; 900 case RP: 901 return "regulated products"; 902 case RR: 903 return "public health reporting"; 904 case RT: 905 return "regulated studies"; 906 case RX: 907 return "pharmacy"; 908 case SC: 909 return "scheduling"; 910 case SP: 911 return "specimen"; 912 case TD: 913 return "therapeutic devices"; 914 case NULL: 915 return null; 916 default: 917 return "?"; 918 } 919 } 920 921}