
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 ResourceTypes { 037 038 /** 039 * A financial tool for tracking value accrued for a particular purpose. In the 040 * healthcare field, used to track charges for a patient, cost centers, etc. 041 */ 042 ACCOUNT, 043 /** 044 * This resource allows for the definition of some activity to be performed, 045 * independent of a particular patient, practitioner, or other performance 046 * context. 047 */ 048 ACTIVITYDEFINITION, 049 /** 050 * Actual or potential/avoided event causing unintended physical injury 051 * resulting from or contributed to by medical care, a research study or other 052 * healthcare setting factors that requires additional monitoring, treatment, or 053 * hospitalization, or that results in death. 054 */ 055 ADVERSEEVENT, 056 /** 057 * Risk of harmful or undesirable, physiological response which is unique to an 058 * individual and associated with exposure to a substance. 059 */ 060 ALLERGYINTOLERANCE, 061 /** 062 * A booking of a healthcare event among patient(s), practitioner(s), related 063 * person(s) and/or device(s) for a specific date/time. This may result in one 064 * or more Encounter(s). 065 */ 066 APPOINTMENT, 067 /** 068 * A reply to an appointment request for a patient and/or practitioner(s), such 069 * as a confirmation or rejection. 070 */ 071 APPOINTMENTRESPONSE, 072 /** 073 * A record of an event made for purposes of maintaining a security log. Typical 074 * uses include detection of intrusion attempts and monitoring for inappropriate 075 * usage. 076 */ 077 AUDITEVENT, 078 /** 079 * Basic is used for handling concepts not yet defined in FHIR, narrative-only 080 * resources that don't map to an existing resource, and custom resources not 081 * appropriate for inclusion in the FHIR specification. 082 */ 083 BASIC, 084 /** 085 * A resource that represents the data of a single raw artifact as digital 086 * content accessible in its native format. A Binary resource can contain any 087 * content, whether text, image, pdf, zip archive, etc. 088 */ 089 BINARY, 090 /** 091 * A material substance originating from a biological entity intended to be 092 * transplanted or infused into another (possibly the same) biological entity. 093 */ 094 BIOLOGICALLYDERIVEDPRODUCT, 095 /** 096 * Record details about an anatomical structure. This resource may be used when 097 * a coded concept does not provide the necessary detail needed for the use 098 * case. 099 */ 100 BODYSTRUCTURE, 101 /** 102 * A container for a collection of resources. 103 */ 104 BUNDLE, 105 /** 106 * A Capability Statement documents a set of capabilities (behaviors) of a FHIR 107 * Server for a particular version of FHIR that may be used as a statement of 108 * actual server functionality or a statement of required or desired server 109 * implementation. 110 */ 111 CAPABILITYSTATEMENT, 112 /** 113 * Describes the intention of how one or more practitioners intend to deliver 114 * care for a particular patient, group or community for a period of time, 115 * possibly limited to care for a specific condition or set of conditions. 116 */ 117 CAREPLAN, 118 /** 119 * The Care Team includes all the people and organizations who plan to 120 * participate in the coordination and delivery of care for a patient. 121 */ 122 CARETEAM, 123 /** 124 * Catalog entries are wrappers that contextualize items included in a catalog. 125 */ 126 CATALOGENTRY, 127 /** 128 * The resource ChargeItem describes the provision of healthcare provider 129 * products for a certain patient, therefore referring not only to the product, 130 * but containing in addition details of the provision, like date, time, amounts 131 * and participating organizations and persons. Main Usage of the ChargeItem is 132 * to enable the billing process and internal cost allocation. 133 */ 134 CHARGEITEM, 135 /** 136 * The ChargeItemDefinition resource provides the properties that apply to the 137 * (billing) codes necessary to calculate costs and prices. The properties may 138 * differ largely depending on type and realm, therefore this resource gives 139 * only a rough structure and requires profiling for each type of billing code 140 * system. 141 */ 142 CHARGEITEMDEFINITION, 143 /** 144 * A provider issued list of professional services and products which have been 145 * provided, or are to be provided, to a patient which is sent to an insurer for 146 * reimbursement. 147 */ 148 CLAIM, 149 /** 150 * This resource provides the adjudication details from the processing of a 151 * Claim resource. 152 */ 153 CLAIMRESPONSE, 154 /** 155 * A record of a clinical assessment performed to determine what problem(s) may 156 * affect the patient and before planning the treatments or management 157 * strategies that are best to manage a patient's condition. Assessments are 158 * often 1:1 with a clinical consultation / encounter, but this varies greatly 159 * depending on the clinical workflow. This resource is called 160 * "ClinicalImpression" rather than "ClinicalAssessment" to avoid confusion with 161 * the recording of assessment tools such as Apgar score. 162 */ 163 CLINICALIMPRESSION, 164 /** 165 * The CodeSystem resource is used to declare the existence of and describe a 166 * code system or code system supplement and its key properties, and optionally 167 * define a part or all of its content. 168 */ 169 CODESYSTEM, 170 /** 171 * An occurrence of information being transmitted; e.g. an alert that was sent 172 * to a responsible provider, a public health agency that was notified about a 173 * reportable condition. 174 */ 175 COMMUNICATION, 176 /** 177 * A request to convey information; e.g. the CDS system proposes that an alert 178 * be sent to a responsible provider, the CDS system proposes that the public 179 * health agency be notified about a reportable condition. 180 */ 181 COMMUNICATIONREQUEST, 182 /** 183 * A compartment definition that defines how resources are accessed on a server. 184 */ 185 COMPARTMENTDEFINITION, 186 /** 187 * A set of healthcare-related information that is assembled together into a 188 * single logical package that provides a single coherent statement of meaning, 189 * establishes its own context and that has clinical attestation with regard to 190 * who is making the statement. A Composition defines the structure and 191 * narrative content necessary for a document. However, a Composition alone does 192 * not constitute a document. Rather, the Composition must be the first entry in 193 * a Bundle where Bundle.type=document, and any other resources referenced from 194 * Composition must be included as subsequent entries in the Bundle (for example 195 * Patient, Practitioner, Encounter, etc.). 196 */ 197 COMPOSITION, 198 /** 199 * A statement of relationships from one set of concepts to one or more other 200 * concepts - either concepts in code systems, or data element/data element 201 * concepts, or classes in class models. 202 */ 203 CONCEPTMAP, 204 /** 205 * A clinical condition, problem, diagnosis, or other event, situation, issue, 206 * or clinical concept that has risen to a level of concern. 207 */ 208 CONDITION, 209 /** 210 * A record of a healthcare consumer?s choices, which permits or denies 211 * identified recipient(s) or recipient role(s) to perform one or more actions 212 * within a given policy context, for specific purposes and periods of time. 213 */ 214 CONSENT, 215 /** 216 * Legally enforceable, formally recorded unilateral or bilateral directive 217 * i.e., a policy or agreement. 218 */ 219 CONTRACT, 220 /** 221 * Financial instrument which may be used to reimburse or pay for health care 222 * products and services. Includes both insurance and self-payment. 223 */ 224 COVERAGE, 225 /** 226 * The CoverageEligibilityRequest provides patient and insurance coverage 227 * information to an insurer for them to respond, in the form of an 228 * CoverageEligibilityResponse, with information regarding whether the stated 229 * coverage is valid and in-force and optionally to provide the insurance 230 * details of the policy. 231 */ 232 COVERAGEELIGIBILITYREQUEST, 233 /** 234 * This resource provides eligibility and plan details from the processing of an 235 * CoverageEligibilityRequest resource. 236 */ 237 COVERAGEELIGIBILITYRESPONSE, 238 /** 239 * Indicates an actual or potential clinical issue with or between one or more 240 * active or proposed clinical actions for a patient; e.g. Drug-drug 241 * interaction, Ineffective treatment frequency, Procedure-condition conflict, 242 * etc. 243 */ 244 DETECTEDISSUE, 245 /** 246 * A type of a manufactured item that is used in the provision of healthcare 247 * without being substantially changed through that activity. The device may be 248 * a medical or non-medical device. 249 */ 250 DEVICE, 251 /** 252 * The characteristics, operational status and capabilities of a medical-related 253 * component of a medical device. 254 */ 255 DEVICEDEFINITION, 256 /** 257 * Describes a measurement, calculation or setting capability of a medical 258 * device. 259 */ 260 DEVICEMETRIC, 261 /** 262 * Represents a request for a patient to employ a medical device. The device may 263 * be an implantable device, or an external assistive device, such as a walker. 264 */ 265 DEVICEREQUEST, 266 /** 267 * A record of a device being used by a patient where the record is the result 268 * of a report from the patient or another clinician. 269 */ 270 DEVICEUSESTATEMENT, 271 /** 272 * The findings and interpretation of diagnostic tests performed on patients, 273 * groups of patients, devices, and locations, and/or specimens derived from 274 * these. The report includes clinical context such as requesting and provider 275 * information, and some mix of atomic results, images, textual and coded 276 * interpretations, and formatted representation of diagnostic reports. 277 */ 278 DIAGNOSTICREPORT, 279 /** 280 * A collection of documents compiled for a purpose together with metadata that 281 * applies to the collection. 282 */ 283 DOCUMENTMANIFEST, 284 /** 285 * A reference to a document of any kind for any purpose. Provides metadata 286 * about the document so that the document can be discovered and managed. The 287 * scope of a document is any seralized object with a mime-type, so includes 288 * formal patient centric documents (CDA), cliical notes, scanned paper, and 289 * non-patient specific documents like policy text. 290 */ 291 DOCUMENTREFERENCE, 292 /** 293 * A resource that includes narrative, extensions, and contained resources. 294 */ 295 DOMAINRESOURCE, 296 /** 297 * The EffectEvidenceSynthesis resource describes the difference in an outcome 298 * between exposures states in a population where the effect estimate is derived 299 * from a combination of research studies. 300 */ 301 EFFECTEVIDENCESYNTHESIS, 302 /** 303 * An interaction between a patient and healthcare provider(s) for the purpose 304 * of providing healthcare service(s) or assessing the health status of a 305 * patient. 306 */ 307 ENCOUNTER, 308 /** 309 * The technical details of an endpoint that can be used for electronic 310 * services, such as for web services providing XDS.b or a REST endpoint for 311 * another FHIR server. This may include any security context information. 312 */ 313 ENDPOINT, 314 /** 315 * This resource provides the insurance enrollment details to the insurer 316 * regarding a specified coverage. 317 */ 318 ENROLLMENTREQUEST, 319 /** 320 * This resource provides enrollment and plan details from the processing of an 321 * EnrollmentRequest resource. 322 */ 323 ENROLLMENTRESPONSE, 324 /** 325 * An association between a patient and an organization / healthcare provider(s) 326 * during which time encounters may occur. The managing organization assumes a 327 * level of responsibility for the patient during this time. 328 */ 329 EPISODEOFCARE, 330 /** 331 * The EventDefinition resource provides a reusable description of when a 332 * particular event can occur. 333 */ 334 EVENTDEFINITION, 335 /** 336 * The Evidence resource describes the conditional state (population and any 337 * exposures being compared within the population) and outcome (if specified) 338 * that the knowledge (evidence, assertion, recommendation) is about. 339 */ 340 EVIDENCE, 341 /** 342 * The EvidenceVariable resource describes a "PICO" element that knowledge 343 * (evidence, assertion, recommendation) is about. 344 */ 345 EVIDENCEVARIABLE, 346 /** 347 * Example of workflow instance. 348 */ 349 EXAMPLESCENARIO, 350 /** 351 * This resource provides: the claim details; adjudication details from the 352 * processing of a Claim; and optionally account balance information, for 353 * informing the subscriber of the benefits provided. 354 */ 355 EXPLANATIONOFBENEFIT, 356 /** 357 * Significant health conditions for a person related to the patient relevant in 358 * the context of care for the patient. 359 */ 360 FAMILYMEMBERHISTORY, 361 /** 362 * Prospective warnings of potential issues when providing care to the patient. 363 */ 364 FLAG, 365 /** 366 * Describes the intended objective(s) for a patient, group or organization 367 * care, for example, weight loss, restoring an activity of daily living, 368 * obtaining herd immunity via immunization, meeting a process improvement 369 * objective, etc. 370 */ 371 GOAL, 372 /** 373 * A formal computable definition of a graph of resources - that is, a coherent 374 * set of resources that form a graph by following references. The Graph 375 * Definition resource defines a set and makes rules about the set. 376 */ 377 GRAPHDEFINITION, 378 /** 379 * Represents a defined collection of entities that may be discussed or acted 380 * upon collectively but which are not expected to act collectively, and are not 381 * formally or legally recognized; i.e. a collection of entities that isn't an 382 * Organization. 383 */ 384 GROUP, 385 /** 386 * A guidance response is the formal response to a guidance request, including 387 * any output parameters returned by the evaluation, as well as the description 388 * of any proposed actions to be taken. 389 */ 390 GUIDANCERESPONSE, 391 /** 392 * The details of a healthcare service available at a location. 393 */ 394 HEALTHCARESERVICE, 395 /** 396 * Representation of the content produced in a DICOM imaging study. A study 397 * comprises a set of series, each of which includes a set of Service-Object 398 * Pair Instances (SOP Instances - images or other data) acquired or produced in 399 * a common context. A series is of only one modality (e.g. X-ray, CT, MR, 400 * ultrasound), but a study may have multiple series of different modalities. 401 */ 402 IMAGINGSTUDY, 403 /** 404 * Describes the event of a patient being administered a vaccine or a record of 405 * an immunization as reported by a patient, a clinician or another party. 406 */ 407 IMMUNIZATION, 408 /** 409 * Describes a comparison of an immunization event against published 410 * recommendations to determine if the administration is "valid" in relation to 411 * those recommendations. 412 */ 413 IMMUNIZATIONEVALUATION, 414 /** 415 * A patient's point-in-time set of recommendations (i.e. forecasting) according 416 * to a published schedule with optional supporting justification. 417 */ 418 IMMUNIZATIONRECOMMENDATION, 419 /** 420 * A set of rules of how a particular interoperability or standards problem is 421 * solved - typically through the use of FHIR resources. This resource is used 422 * to gather all the parts of an implementation guide into a logical whole and 423 * to publish a computable definition of all the parts. 424 */ 425 IMPLEMENTATIONGUIDE, 426 /** 427 * Details of a Health Insurance product/plan provided by an organization. 428 */ 429 INSURANCEPLAN, 430 /** 431 * Invoice containing collected ChargeItems from an Account with calculated 432 * individual and total price for Billing purpose. 433 */ 434 INVOICE, 435 /** 436 * The Library resource is a general-purpose container for knowledge asset 437 * definitions. It can be used to describe and expose existing knowledge assets 438 * such as logic libraries and information model descriptions, as well as to 439 * describe a collection of knowledge assets. 440 */ 441 LIBRARY, 442 /** 443 * Identifies two or more records (resource instances) that refer to the same 444 * real-world "occurrence". 445 */ 446 LINKAGE, 447 /** 448 * A list is a curated collection of resources. 449 */ 450 LIST, 451 /** 452 * Details and position information for a physical place where services are 453 * provided and resources and participants may be stored, found, contained, or 454 * accommodated. 455 */ 456 LOCATION, 457 /** 458 * The Measure resource provides the definition of a quality measure. 459 */ 460 MEASURE, 461 /** 462 * The MeasureReport resource contains the results of the calculation of a 463 * measure; and optionally a reference to the resources involved in that 464 * calculation. 465 */ 466 MEASUREREPORT, 467 /** 468 * A photo, video, or audio recording acquired or used in healthcare. The actual 469 * content may be inline or provided by direct reference. 470 */ 471 MEDIA, 472 /** 473 * This resource is primarily used for the identification and definition of a 474 * medication for the purposes of prescribing, dispensing, and administering a 475 * medication as well as for making statements about medication use. 476 */ 477 MEDICATION, 478 /** 479 * Describes the event of a patient consuming or otherwise being administered a 480 * medication. This may be as simple as swallowing a tablet or it may be a long 481 * running infusion. Related resources tie this event to the authorizing 482 * prescription, and the specific encounter between patient and health care 483 * practitioner. 484 */ 485 MEDICATIONADMINISTRATION, 486 /** 487 * Indicates that a medication product is to be or has been dispensed for a 488 * named person/patient. This includes a description of the medication product 489 * (supply) provided and the instructions for administering the medication. The 490 * medication dispense is the result of a pharmacy system responding to a 491 * medication order. 492 */ 493 MEDICATIONDISPENSE, 494 /** 495 * Information about a medication that is used to support knowledge. 496 */ 497 MEDICATIONKNOWLEDGE, 498 /** 499 * An order or request for both supply of the medication and the instructions 500 * for administration of the medication to a patient. The resource is called 501 * "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" 502 * to generalize the use across inpatient and outpatient settings, including 503 * care plans, etc., and to harmonize with workflow patterns. 504 */ 505 MEDICATIONREQUEST, 506 /** 507 * A record of a medication that is being consumed by a patient. A 508 * MedicationStatement may indicate that the patient may be taking the 509 * medication now or has taken the medication in the past or will be taking the 510 * medication in the future. The source of this information can be the patient, 511 * significant other (such as a family member or spouse), or a clinician. A 512 * common scenario where this information is captured is during the history 513 * taking process during a patient visit or stay. The medication information may 514 * come from sources such as the patient's memory, from a prescription bottle, 515 * or from a list of medications the patient, clinician or other party 516 * maintains. 517 * 518 * The primary difference between a medication statement and a medication 519 * administration is that the medication administration has complete 520 * administration information and is based on actual administration information 521 * from the person who administered the medication. A medication statement is 522 * often, if not always, less specific. There is no required date/time when the 523 * medication was administered, in fact we only know that a source has reported 524 * the patient is taking this medication, where details such as time, quantity, 525 * or rate or even medication product may be incomplete or missing or less 526 * precise. As stated earlier, the medication statement information may come 527 * from the patient's memory, from a prescription bottle or from a list of 528 * medications the patient, clinician or other party maintains. Medication 529 * administration is more formal and is not missing detailed information. 530 */ 531 MEDICATIONSTATEMENT, 532 /** 533 * Detailed definition of a medicinal product, typically for uses other than 534 * direct patient care (e.g. regulatory use). 535 */ 536 MEDICINALPRODUCT, 537 /** 538 * The regulatory authorization of a medicinal product. 539 */ 540 MEDICINALPRODUCTAUTHORIZATION, 541 /** 542 * The clinical particulars - indications, contraindications etc. of a medicinal 543 * product, including for regulatory purposes. 544 */ 545 MEDICINALPRODUCTCONTRAINDICATION, 546 /** 547 * Indication for the Medicinal Product. 548 */ 549 MEDICINALPRODUCTINDICATION, 550 /** 551 * An ingredient of a manufactured item or pharmaceutical product. 552 */ 553 MEDICINALPRODUCTINGREDIENT, 554 /** 555 * The interactions of the medicinal product with other medicinal products, or 556 * other forms of interactions. 557 */ 558 MEDICINALPRODUCTINTERACTION, 559 /** 560 * The manufactured item as contained in the packaged medicinal product. 561 */ 562 MEDICINALPRODUCTMANUFACTURED, 563 /** 564 * A medicinal product in a container or package. 565 */ 566 MEDICINALPRODUCTPACKAGED, 567 /** 568 * A pharmaceutical product described in terms of its composition and dose form. 569 */ 570 MEDICINALPRODUCTPHARMACEUTICAL, 571 /** 572 * Describe the undesirable effects of the medicinal product. 573 */ 574 MEDICINALPRODUCTUNDESIRABLEEFFECT, 575 /** 576 * Defines the characteristics of a message that can be shared between systems, 577 * including the type of event that initiates the message, the content to be 578 * transmitted and what response(s), if any, are permitted. 579 */ 580 MESSAGEDEFINITION, 581 /** 582 * The header for a message exchange that is either requesting or responding to 583 * an action. The reference(s) that are the subject of the action as well as 584 * other information related to the action are typically transmitted in a bundle 585 * in which the MessageHeader resource instance is the first resource in the 586 * bundle. 587 */ 588 MESSAGEHEADER, 589 /** 590 * Raw data describing a biological sequence. 591 */ 592 MOLECULARSEQUENCE, 593 /** 594 * A curated namespace that issues unique symbols within that namespace for the 595 * identification of concepts, people, devices, etc. Represents a "System" used 596 * within the Identifier and Coding data types. 597 */ 598 NAMINGSYSTEM, 599 /** 600 * A request to supply a diet, formula feeding (enteral) or oral nutritional 601 * supplement to a patient/resident. 602 */ 603 NUTRITIONORDER, 604 /** 605 * Measurements and simple assertions made about a patient, device or other 606 * subject. 607 */ 608 OBSERVATION, 609 /** 610 * Set of definitional characteristics for a kind of observation or measurement 611 * produced or consumed by an orderable health care service. 612 */ 613 OBSERVATIONDEFINITION, 614 /** 615 * A formal computable definition of an operation (on the RESTful interface) or 616 * a named query (using the search interaction). 617 */ 618 OPERATIONDEFINITION, 619 /** 620 * A collection of error, warning, or information messages that result from a 621 * system action. 622 */ 623 OPERATIONOUTCOME, 624 /** 625 * A formally or informally recognized grouping of people or organizations 626 * formed for the purpose of achieving some form of collective action. Includes 627 * companies, institutions, corporations, departments, community groups, 628 * healthcare practice groups, payer/insurer, etc. 629 */ 630 ORGANIZATION, 631 /** 632 * Defines an affiliation/assotiation/relationship between 2 distinct 633 * oganizations, that is not a part-of relationship/sub-division relationship. 634 */ 635 ORGANIZATIONAFFILIATION, 636 /** 637 * This resource is a non-persisted resource used to pass information into and 638 * back from an [operation](operations.html). It has no other use, and there is 639 * no RESTful endpoint associated with it. 640 */ 641 PARAMETERS, 642 /** 643 * Demographics and other administrative information about an individual or 644 * animal receiving care or other health-related services. 645 */ 646 PATIENT, 647 /** 648 * This resource provides the status of the payment for goods and services 649 * rendered, and the request and response resource references. 650 */ 651 PAYMENTNOTICE, 652 /** 653 * This resource provides the details including amount of a payment and 654 * allocates the payment items being paid. 655 */ 656 PAYMENTRECONCILIATION, 657 /** 658 * Demographics and administrative information about a person independent of a 659 * specific health-related context. 660 */ 661 PERSON, 662 /** 663 * This resource allows for the definition of various types of plans as a 664 * sharable, consumable, and executable artifact. The resource is general enough 665 * to support the description of a broad range of clinical artifacts such as 666 * clinical decision support rules, order sets and protocols. 667 */ 668 PLANDEFINITION, 669 /** 670 * A person who is directly or indirectly involved in the provisioning of 671 * healthcare. 672 */ 673 PRACTITIONER, 674 /** 675 * A specific set of Roles/Locations/specialties/services that a practitioner 676 * may perform at an organization for a period of time. 677 */ 678 PRACTITIONERROLE, 679 /** 680 * An action that is or was performed on or for a patient. This can be a 681 * physical intervention like an operation, or less invasive like long term 682 * services, counseling, or hypnotherapy. 683 */ 684 PROCEDURE, 685 /** 686 * Provenance of a resource is a record that describes entities and processes 687 * involved in producing and delivering or otherwise influencing that resource. 688 * Provenance provides a critical foundation for assessing authenticity, 689 * enabling trust, and allowing reproducibility. Provenance assertions are a 690 * form of contextual metadata and can themselves become important records with 691 * their own provenance. Provenance statement indicates clinical significance in 692 * terms of confidence in authenticity, reliability, and trustworthiness, 693 * integrity, and stage in lifecycle (e.g. Document Completion - has the 694 * artifact been legally authenticated), all of which may impact security, 695 * privacy, and trust policies. 696 */ 697 PROVENANCE, 698 /** 699 * A structured set of questions intended to guide the collection of answers 700 * from end-users. Questionnaires provide detailed control over order, 701 * presentation, phraseology and grouping to allow coherent, consistent data 702 * collection. 703 */ 704 QUESTIONNAIRE, 705 /** 706 * A structured set of questions and their answers. The questions are ordered 707 * and grouped into coherent subsets, corresponding to the structure of the 708 * grouping of the questionnaire being responded to. 709 */ 710 QUESTIONNAIRERESPONSE, 711 /** 712 * Information about a person that is involved in the care for a patient, but 713 * who is not the target of healthcare, nor has a formal responsibility in the 714 * care process. 715 */ 716 RELATEDPERSON, 717 /** 718 * A group of related requests that can be used to capture intended activities 719 * that have inter-dependencies such as "give this medication after that one". 720 */ 721 REQUESTGROUP, 722 /** 723 * The ResearchDefinition resource describes the conditional state (population 724 * and any exposures being compared within the population) and outcome (if 725 * specified) that the knowledge (evidence, assertion, recommendation) is about. 726 */ 727 RESEARCHDEFINITION, 728 /** 729 * The ResearchElementDefinition resource describes a "PICO" element that 730 * knowledge (evidence, assertion, recommendation) is about. 731 */ 732 RESEARCHELEMENTDEFINITION, 733 /** 734 * A process where a researcher or organization plans and then executes a series 735 * of steps intended to increase the field of healthcare-related knowledge. This 736 * includes studies of safety, efficacy, comparative effectiveness and other 737 * information about medications, devices, therapies and other interventional 738 * and investigative techniques. A ResearchStudy involves the gathering of 739 * information about human or animal subjects. 740 */ 741 RESEARCHSTUDY, 742 /** 743 * A physical entity which is the primary unit of operational and/or 744 * administrative interest in a study. 745 */ 746 RESEARCHSUBJECT, 747 /** 748 * This is the base resource type for everything. 749 */ 750 RESOURCE, 751 /** 752 * An assessment of the likely outcome(s) for a patient or other subject as well 753 * as the likelihood of each outcome. 754 */ 755 RISKASSESSMENT, 756 /** 757 * The RiskEvidenceSynthesis resource describes the likelihood of an outcome in 758 * a population plus exposure state where the risk estimate is derived from a 759 * combination of research studies. 760 */ 761 RISKEVIDENCESYNTHESIS, 762 /** 763 * A container for slots of time that may be available for booking appointments. 764 */ 765 SCHEDULE, 766 /** 767 * A search parameter that defines a named search item that can be used to 768 * search/filter on a resource. 769 */ 770 SEARCHPARAMETER, 771 /** 772 * A record of a request for service such as diagnostic investigations, 773 * treatments, or operations to be performed. 774 */ 775 SERVICEREQUEST, 776 /** 777 * A slot of time on a schedule that may be available for booking appointments. 778 */ 779 SLOT, 780 /** 781 * A sample to be used for analysis. 782 */ 783 SPECIMEN, 784 /** 785 * A kind of specimen with associated set of requirements. 786 */ 787 SPECIMENDEFINITION, 788 /** 789 * A definition of a FHIR structure. This resource is used to describe the 790 * underlying resources, data types defined in FHIR, and also for describing 791 * extensions and constraints on resources and data types. 792 */ 793 STRUCTUREDEFINITION, 794 /** 795 * A Map of relationships between 2 structures that can be used to transform 796 * data. 797 */ 798 STRUCTUREMAP, 799 /** 800 * The subscription resource is used to define a push-based subscription from a 801 * server to another system. Once a subscription is registered with the server, 802 * the server checks every resource that is created or updated, and if the 803 * resource matches the given criteria, it sends a message on the defined 804 * "channel" so that another system can take an appropriate action. 805 */ 806 SUBSCRIPTION, 807 /** 808 * A homogeneous material with a definite composition. 809 */ 810 SUBSTANCE, 811 /** 812 * The detailed description of a substance, typically at a level beyond what is 813 * used for prescribing. 814 */ 815 SUBSTANCEDEFINITION, 816 /** 817 * Nucleic acids are defined by three distinct elements: the base, sugar and 818 * linkage. Individual substance/moiety IDs will be created for each of these 819 * elements. The nucleotide sequence will be always entered in the 5?-3? 820 * direction. 821 */ 822 SUBSTANCENUCLEICACID, 823 /** 824 * Todo. 825 */ 826 SUBSTANCEPOLYMER, 827 /** 828 * A SubstanceProtein is defined as a single unit of a linear amino acid 829 * sequence, or a combination of subunits that are either covalently linked or 830 * have a defined invariant stoichiometric relationship. This includes all 831 * synthetic, recombinant and purified SubstanceProteins of defined sequence, 832 * whether the use is therapeutic or prophylactic. This set of elements will be 833 * used to describe albumins, coagulation factors, cytokines, growth factors, 834 * peptide/SubstanceProtein hormones, enzymes, toxins, toxoids, recombinant 835 * vaccines, and immunomodulators. 836 */ 837 SUBSTANCEPROTEIN, 838 /** 839 * Todo. 840 */ 841 SUBSTANCEREFERENCEINFORMATION, 842 /** 843 * Source material shall capture information on the taxonomic and anatomical 844 * origins as well as the fraction of a material that can result in or can be 845 * modified to form a substance. This set of data elements shall be used to 846 * define polymer substances isolated from biological matrices. Taxonomic and 847 * anatomical origins shall be described using a controlled vocabulary as 848 * required. This information is captured for naturally derived polymers ( . 849 * starch) and structurally diverse substances. For Organisms belonging to the 850 * Kingdom Plantae the Substance level defines the fresh material of a single 851 * species or infraspecies, the Herbal Drug and the Herbal preparation. For 852 * Herbal preparations, the fraction information will be captured at the 853 * Substance information level and additional information for herbal extracts 854 * will be captured at the Specified Substance Group 1 information level. See 855 * for further explanation the Substance Class: Structurally Diverse and the 856 * herbal annex. 857 */ 858 SUBSTANCESOURCEMATERIAL, 859 /** 860 * Record of delivery of what is supplied. 861 */ 862 SUPPLYDELIVERY, 863 /** 864 * A record of a request for a medication, substance or device used in the 865 * healthcare setting. 866 */ 867 SUPPLYREQUEST, 868 /** 869 * A task to be performed. 870 */ 871 TASK, 872 /** 873 * A TerminologyCapabilities resource documents a set of capabilities 874 * (behaviors) of a FHIR Terminology Server that may be used as a statement of 875 * actual server functionality or a statement of required or desired server 876 * implementation. 877 */ 878 TERMINOLOGYCAPABILITIES, 879 /** 880 * A summary of information based on the results of executing a TestScript. 881 */ 882 TESTREPORT, 883 /** 884 * A structured set of tests against a FHIR server or client implementation to 885 * determine compliance against the FHIR specification. 886 */ 887 TESTSCRIPT, 888 /** 889 * A ValueSet resource instance specifies a set of codes drawn from one or more 890 * code systems, intended for use in a particular context. Value sets link 891 * between [[[CodeSystem]]] definitions and their use in [coded 892 * elements](terminologies.html). 893 */ 894 VALUESET, 895 /** 896 * Describes validation requirements, source(s), status and dates for one or 897 * more elements. 898 */ 899 VERIFICATIONRESULT, 900 /** 901 * An authorization for the provision of glasses and/or contact lenses to a 902 * patient. 903 */ 904 VISIONPRESCRIPTION, 905 /** 906 * added to help the parsers 907 */ 908 NULL; 909 910 public static ResourceTypes fromCode(String codeString) throws FHIRException { 911 if (codeString == null || "".equals(codeString)) 912 return null; 913 if ("Account".equals(codeString)) 914 return ACCOUNT; 915 if ("ActivityDefinition".equals(codeString)) 916 return ACTIVITYDEFINITION; 917 if ("AdverseEvent".equals(codeString)) 918 return ADVERSEEVENT; 919 if ("AllergyIntolerance".equals(codeString)) 920 return ALLERGYINTOLERANCE; 921 if ("Appointment".equals(codeString)) 922 return APPOINTMENT; 923 if ("AppointmentResponse".equals(codeString)) 924 return APPOINTMENTRESPONSE; 925 if ("AuditEvent".equals(codeString)) 926 return AUDITEVENT; 927 if ("Basic".equals(codeString)) 928 return BASIC; 929 if ("Binary".equals(codeString)) 930 return BINARY; 931 if ("BiologicallyDerivedProduct".equals(codeString)) 932 return BIOLOGICALLYDERIVEDPRODUCT; 933 if ("BodyStructure".equals(codeString)) 934 return BODYSTRUCTURE; 935 if ("Bundle".equals(codeString)) 936 return BUNDLE; 937 if ("CapabilityStatement".equals(codeString)) 938 return CAPABILITYSTATEMENT; 939 if ("CarePlan".equals(codeString)) 940 return CAREPLAN; 941 if ("CareTeam".equals(codeString)) 942 return CARETEAM; 943 if ("CatalogEntry".equals(codeString)) 944 return CATALOGENTRY; 945 if ("ChargeItem".equals(codeString)) 946 return CHARGEITEM; 947 if ("ChargeItemDefinition".equals(codeString)) 948 return CHARGEITEMDEFINITION; 949 if ("Claim".equals(codeString)) 950 return CLAIM; 951 if ("ClaimResponse".equals(codeString)) 952 return CLAIMRESPONSE; 953 if ("ClinicalImpression".equals(codeString)) 954 return CLINICALIMPRESSION; 955 if ("CodeSystem".equals(codeString)) 956 return CODESYSTEM; 957 if ("Communication".equals(codeString)) 958 return COMMUNICATION; 959 if ("CommunicationRequest".equals(codeString)) 960 return COMMUNICATIONREQUEST; 961 if ("CompartmentDefinition".equals(codeString)) 962 return COMPARTMENTDEFINITION; 963 if ("Composition".equals(codeString)) 964 return COMPOSITION; 965 if ("ConceptMap".equals(codeString)) 966 return CONCEPTMAP; 967 if ("Condition".equals(codeString)) 968 return CONDITION; 969 if ("Consent".equals(codeString)) 970 return CONSENT; 971 if ("Contract".equals(codeString)) 972 return CONTRACT; 973 if ("Coverage".equals(codeString)) 974 return COVERAGE; 975 if ("CoverageEligibilityRequest".equals(codeString)) 976 return COVERAGEELIGIBILITYREQUEST; 977 if ("CoverageEligibilityResponse".equals(codeString)) 978 return COVERAGEELIGIBILITYRESPONSE; 979 if ("DetectedIssue".equals(codeString)) 980 return DETECTEDISSUE; 981 if ("Device".equals(codeString)) 982 return DEVICE; 983 if ("DeviceDefinition".equals(codeString)) 984 return DEVICEDEFINITION; 985 if ("DeviceMetric".equals(codeString)) 986 return DEVICEMETRIC; 987 if ("DeviceRequest".equals(codeString)) 988 return DEVICEREQUEST; 989 if ("DeviceUseStatement".equals(codeString)) 990 return DEVICEUSESTATEMENT; 991 if ("DiagnosticReport".equals(codeString)) 992 return DIAGNOSTICREPORT; 993 if ("DocumentManifest".equals(codeString)) 994 return DOCUMENTMANIFEST; 995 if ("DocumentReference".equals(codeString)) 996 return DOCUMENTREFERENCE; 997 if ("DomainResource".equals(codeString)) 998 return DOMAINRESOURCE; 999 if ("EffectEvidenceSynthesis".equals(codeString)) 1000 return EFFECTEVIDENCESYNTHESIS; 1001 if ("Encounter".equals(codeString)) 1002 return ENCOUNTER; 1003 if ("Endpoint".equals(codeString)) 1004 return ENDPOINT; 1005 if ("EnrollmentRequest".equals(codeString)) 1006 return ENROLLMENTREQUEST; 1007 if ("EnrollmentResponse".equals(codeString)) 1008 return ENROLLMENTRESPONSE; 1009 if ("EpisodeOfCare".equals(codeString)) 1010 return EPISODEOFCARE; 1011 if ("EventDefinition".equals(codeString)) 1012 return EVENTDEFINITION; 1013 if ("Evidence".equals(codeString)) 1014 return EVIDENCE; 1015 if ("EvidenceVariable".equals(codeString)) 1016 return EVIDENCEVARIABLE; 1017 if ("ExampleScenario".equals(codeString)) 1018 return EXAMPLESCENARIO; 1019 if ("ExplanationOfBenefit".equals(codeString)) 1020 return EXPLANATIONOFBENEFIT; 1021 if ("FamilyMemberHistory".equals(codeString)) 1022 return FAMILYMEMBERHISTORY; 1023 if ("Flag".equals(codeString)) 1024 return FLAG; 1025 if ("Goal".equals(codeString)) 1026 return GOAL; 1027 if ("GraphDefinition".equals(codeString)) 1028 return GRAPHDEFINITION; 1029 if ("Group".equals(codeString)) 1030 return GROUP; 1031 if ("GuidanceResponse".equals(codeString)) 1032 return GUIDANCERESPONSE; 1033 if ("HealthcareService".equals(codeString)) 1034 return HEALTHCARESERVICE; 1035 if ("ImagingStudy".equals(codeString)) 1036 return IMAGINGSTUDY; 1037 if ("Immunization".equals(codeString)) 1038 return IMMUNIZATION; 1039 if ("ImmunizationEvaluation".equals(codeString)) 1040 return IMMUNIZATIONEVALUATION; 1041 if ("ImmunizationRecommendation".equals(codeString)) 1042 return IMMUNIZATIONRECOMMENDATION; 1043 if ("ImplementationGuide".equals(codeString)) 1044 return IMPLEMENTATIONGUIDE; 1045 if ("InsurancePlan".equals(codeString)) 1046 return INSURANCEPLAN; 1047 if ("Invoice".equals(codeString)) 1048 return INVOICE; 1049 if ("Library".equals(codeString)) 1050 return LIBRARY; 1051 if ("Linkage".equals(codeString)) 1052 return LINKAGE; 1053 if ("List".equals(codeString)) 1054 return LIST; 1055 if ("Location".equals(codeString)) 1056 return LOCATION; 1057 if ("Measure".equals(codeString)) 1058 return MEASURE; 1059 if ("MeasureReport".equals(codeString)) 1060 return MEASUREREPORT; 1061 if ("Media".equals(codeString)) 1062 return MEDIA; 1063 if ("Medication".equals(codeString)) 1064 return MEDICATION; 1065 if ("MedicationAdministration".equals(codeString)) 1066 return MEDICATIONADMINISTRATION; 1067 if ("MedicationDispense".equals(codeString)) 1068 return MEDICATIONDISPENSE; 1069 if ("MedicationKnowledge".equals(codeString)) 1070 return MEDICATIONKNOWLEDGE; 1071 if ("MedicationRequest".equals(codeString)) 1072 return MEDICATIONREQUEST; 1073 if ("MedicationStatement".equals(codeString)) 1074 return MEDICATIONSTATEMENT; 1075 if ("MedicinalProduct".equals(codeString)) 1076 return MEDICINALPRODUCT; 1077 if ("MedicinalProductAuthorization".equals(codeString)) 1078 return MEDICINALPRODUCTAUTHORIZATION; 1079 if ("MedicinalProductContraindication".equals(codeString)) 1080 return MEDICINALPRODUCTCONTRAINDICATION; 1081 if ("MedicinalProductIndication".equals(codeString)) 1082 return MEDICINALPRODUCTINDICATION; 1083 if ("MedicinalProductIngredient".equals(codeString)) 1084 return MEDICINALPRODUCTINGREDIENT; 1085 if ("MedicinalProductInteraction".equals(codeString)) 1086 return MEDICINALPRODUCTINTERACTION; 1087 if ("MedicinalProductManufactured".equals(codeString)) 1088 return MEDICINALPRODUCTMANUFACTURED; 1089 if ("MedicinalProductPackaged".equals(codeString)) 1090 return MEDICINALPRODUCTPACKAGED; 1091 if ("MedicinalProductPharmaceutical".equals(codeString)) 1092 return MEDICINALPRODUCTPHARMACEUTICAL; 1093 if ("MedicinalProductUndesirableEffect".equals(codeString)) 1094 return MEDICINALPRODUCTUNDESIRABLEEFFECT; 1095 if ("MessageDefinition".equals(codeString)) 1096 return MESSAGEDEFINITION; 1097 if ("MessageHeader".equals(codeString)) 1098 return MESSAGEHEADER; 1099 if ("MolecularSequence".equals(codeString)) 1100 return MOLECULARSEQUENCE; 1101 if ("NamingSystem".equals(codeString)) 1102 return NAMINGSYSTEM; 1103 if ("NutritionOrder".equals(codeString)) 1104 return NUTRITIONORDER; 1105 if ("Observation".equals(codeString)) 1106 return OBSERVATION; 1107 if ("ObservationDefinition".equals(codeString)) 1108 return OBSERVATIONDEFINITION; 1109 if ("OperationDefinition".equals(codeString)) 1110 return OPERATIONDEFINITION; 1111 if ("OperationOutcome".equals(codeString)) 1112 return OPERATIONOUTCOME; 1113 if ("Organization".equals(codeString)) 1114 return ORGANIZATION; 1115 if ("OrganizationAffiliation".equals(codeString)) 1116 return ORGANIZATIONAFFILIATION; 1117 if ("Parameters".equals(codeString)) 1118 return PARAMETERS; 1119 if ("Patient".equals(codeString)) 1120 return PATIENT; 1121 if ("PaymentNotice".equals(codeString)) 1122 return PAYMENTNOTICE; 1123 if ("PaymentReconciliation".equals(codeString)) 1124 return PAYMENTRECONCILIATION; 1125 if ("Person".equals(codeString)) 1126 return PERSON; 1127 if ("PlanDefinition".equals(codeString)) 1128 return PLANDEFINITION; 1129 if ("Practitioner".equals(codeString)) 1130 return PRACTITIONER; 1131 if ("PractitionerRole".equals(codeString)) 1132 return PRACTITIONERROLE; 1133 if ("Procedure".equals(codeString)) 1134 return PROCEDURE; 1135 if ("Provenance".equals(codeString)) 1136 return PROVENANCE; 1137 if ("Questionnaire".equals(codeString)) 1138 return QUESTIONNAIRE; 1139 if ("QuestionnaireResponse".equals(codeString)) 1140 return QUESTIONNAIRERESPONSE; 1141 if ("RelatedPerson".equals(codeString)) 1142 return RELATEDPERSON; 1143 if ("RequestGroup".equals(codeString)) 1144 return REQUESTGROUP; 1145 if ("ResearchDefinition".equals(codeString)) 1146 return RESEARCHDEFINITION; 1147 if ("ResearchElementDefinition".equals(codeString)) 1148 return RESEARCHELEMENTDEFINITION; 1149 if ("ResearchStudy".equals(codeString)) 1150 return RESEARCHSTUDY; 1151 if ("ResearchSubject".equals(codeString)) 1152 return RESEARCHSUBJECT; 1153 if ("Resource".equals(codeString)) 1154 return RESOURCE; 1155 if ("RiskAssessment".equals(codeString)) 1156 return RISKASSESSMENT; 1157 if ("RiskEvidenceSynthesis".equals(codeString)) 1158 return RISKEVIDENCESYNTHESIS; 1159 if ("Schedule".equals(codeString)) 1160 return SCHEDULE; 1161 if ("SearchParameter".equals(codeString)) 1162 return SEARCHPARAMETER; 1163 if ("ServiceRequest".equals(codeString)) 1164 return SERVICEREQUEST; 1165 if ("Slot".equals(codeString)) 1166 return SLOT; 1167 if ("Specimen".equals(codeString)) 1168 return SPECIMEN; 1169 if ("SpecimenDefinition".equals(codeString)) 1170 return SPECIMENDEFINITION; 1171 if ("StructureDefinition".equals(codeString)) 1172 return STRUCTUREDEFINITION; 1173 if ("StructureMap".equals(codeString)) 1174 return STRUCTUREMAP; 1175 if ("Subscription".equals(codeString)) 1176 return SUBSCRIPTION; 1177 if ("Substance".equals(codeString)) 1178 return SUBSTANCE; 1179 if ("SubstanceDefinition".equals(codeString)) 1180 return SUBSTANCEDEFINITION; 1181 if ("SubstanceNucleicAcid".equals(codeString)) 1182 return SUBSTANCENUCLEICACID; 1183 if ("SubstancePolymer".equals(codeString)) 1184 return SUBSTANCEPOLYMER; 1185 if ("SubstanceProtein".equals(codeString)) 1186 return SUBSTANCEPROTEIN; 1187 if ("SubstanceReferenceInformation".equals(codeString)) 1188 return SUBSTANCEREFERENCEINFORMATION; 1189 if ("SubstanceSourceMaterial".equals(codeString)) 1190 return SUBSTANCESOURCEMATERIAL; 1191 if ("SupplyDelivery".equals(codeString)) 1192 return SUPPLYDELIVERY; 1193 if ("SupplyRequest".equals(codeString)) 1194 return SUPPLYREQUEST; 1195 if ("Task".equals(codeString)) 1196 return TASK; 1197 if ("TerminologyCapabilities".equals(codeString)) 1198 return TERMINOLOGYCAPABILITIES; 1199 if ("TestReport".equals(codeString)) 1200 return TESTREPORT; 1201 if ("TestScript".equals(codeString)) 1202 return TESTSCRIPT; 1203 if ("ValueSet".equals(codeString)) 1204 return VALUESET; 1205 if ("VerificationResult".equals(codeString)) 1206 return VERIFICATIONRESULT; 1207 if ("VisionPrescription".equals(codeString)) 1208 return VISIONPRESCRIPTION; 1209 throw new FHIRException("Unknown ResourceTypes code '" + codeString + "'"); 1210 } 1211 1212 public String toCode() { 1213 switch (this) { 1214 case ACCOUNT: 1215 return "Account"; 1216 case ACTIVITYDEFINITION: 1217 return "ActivityDefinition"; 1218 case ADVERSEEVENT: 1219 return "AdverseEvent"; 1220 case ALLERGYINTOLERANCE: 1221 return "AllergyIntolerance"; 1222 case APPOINTMENT: 1223 return "Appointment"; 1224 case APPOINTMENTRESPONSE: 1225 return "AppointmentResponse"; 1226 case AUDITEVENT: 1227 return "AuditEvent"; 1228 case BASIC: 1229 return "Basic"; 1230 case BINARY: 1231 return "Binary"; 1232 case BIOLOGICALLYDERIVEDPRODUCT: 1233 return "BiologicallyDerivedProduct"; 1234 case BODYSTRUCTURE: 1235 return "BodyStructure"; 1236 case BUNDLE: 1237 return "Bundle"; 1238 case CAPABILITYSTATEMENT: 1239 return "CapabilityStatement"; 1240 case CAREPLAN: 1241 return "CarePlan"; 1242 case CARETEAM: 1243 return "CareTeam"; 1244 case CATALOGENTRY: 1245 return "CatalogEntry"; 1246 case CHARGEITEM: 1247 return "ChargeItem"; 1248 case CHARGEITEMDEFINITION: 1249 return "ChargeItemDefinition"; 1250 case CLAIM: 1251 return "Claim"; 1252 case CLAIMRESPONSE: 1253 return "ClaimResponse"; 1254 case CLINICALIMPRESSION: 1255 return "ClinicalImpression"; 1256 case CODESYSTEM: 1257 return "CodeSystem"; 1258 case COMMUNICATION: 1259 return "Communication"; 1260 case COMMUNICATIONREQUEST: 1261 return "CommunicationRequest"; 1262 case COMPARTMENTDEFINITION: 1263 return "CompartmentDefinition"; 1264 case COMPOSITION: 1265 return "Composition"; 1266 case CONCEPTMAP: 1267 return "ConceptMap"; 1268 case CONDITION: 1269 return "Condition"; 1270 case CONSENT: 1271 return "Consent"; 1272 case CONTRACT: 1273 return "Contract"; 1274 case COVERAGE: 1275 return "Coverage"; 1276 case COVERAGEELIGIBILITYREQUEST: 1277 return "CoverageEligibilityRequest"; 1278 case COVERAGEELIGIBILITYRESPONSE: 1279 return "CoverageEligibilityResponse"; 1280 case DETECTEDISSUE: 1281 return "DetectedIssue"; 1282 case DEVICE: 1283 return "Device"; 1284 case DEVICEDEFINITION: 1285 return "DeviceDefinition"; 1286 case DEVICEMETRIC: 1287 return "DeviceMetric"; 1288 case DEVICEREQUEST: 1289 return "DeviceRequest"; 1290 case DEVICEUSESTATEMENT: 1291 return "DeviceUseStatement"; 1292 case DIAGNOSTICREPORT: 1293 return "DiagnosticReport"; 1294 case DOCUMENTMANIFEST: 1295 return "DocumentManifest"; 1296 case DOCUMENTREFERENCE: 1297 return "DocumentReference"; 1298 case DOMAINRESOURCE: 1299 return "DomainResource"; 1300 case EFFECTEVIDENCESYNTHESIS: 1301 return "EffectEvidenceSynthesis"; 1302 case ENCOUNTER: 1303 return "Encounter"; 1304 case ENDPOINT: 1305 return "Endpoint"; 1306 case ENROLLMENTREQUEST: 1307 return "EnrollmentRequest"; 1308 case ENROLLMENTRESPONSE: 1309 return "EnrollmentResponse"; 1310 case EPISODEOFCARE: 1311 return "EpisodeOfCare"; 1312 case EVENTDEFINITION: 1313 return "EventDefinition"; 1314 case EVIDENCE: 1315 return "Evidence"; 1316 case EVIDENCEVARIABLE: 1317 return "EvidenceVariable"; 1318 case EXAMPLESCENARIO: 1319 return "ExampleScenario"; 1320 case EXPLANATIONOFBENEFIT: 1321 return "ExplanationOfBenefit"; 1322 case FAMILYMEMBERHISTORY: 1323 return "FamilyMemberHistory"; 1324 case FLAG: 1325 return "Flag"; 1326 case GOAL: 1327 return "Goal"; 1328 case GRAPHDEFINITION: 1329 return "GraphDefinition"; 1330 case GROUP: 1331 return "Group"; 1332 case GUIDANCERESPONSE: 1333 return "GuidanceResponse"; 1334 case HEALTHCARESERVICE: 1335 return "HealthcareService"; 1336 case IMAGINGSTUDY: 1337 return "ImagingStudy"; 1338 case IMMUNIZATION: 1339 return "Immunization"; 1340 case IMMUNIZATIONEVALUATION: 1341 return "ImmunizationEvaluation"; 1342 case IMMUNIZATIONRECOMMENDATION: 1343 return "ImmunizationRecommendation"; 1344 case IMPLEMENTATIONGUIDE: 1345 return "ImplementationGuide"; 1346 case INSURANCEPLAN: 1347 return "InsurancePlan"; 1348 case INVOICE: 1349 return "Invoice"; 1350 case LIBRARY: 1351 return "Library"; 1352 case LINKAGE: 1353 return "Linkage"; 1354 case LIST: 1355 return "List"; 1356 case LOCATION: 1357 return "Location"; 1358 case MEASURE: 1359 return "Measure"; 1360 case MEASUREREPORT: 1361 return "MeasureReport"; 1362 case MEDIA: 1363 return "Media"; 1364 case MEDICATION: 1365 return "Medication"; 1366 case MEDICATIONADMINISTRATION: 1367 return "MedicationAdministration"; 1368 case MEDICATIONDISPENSE: 1369 return "MedicationDispense"; 1370 case MEDICATIONKNOWLEDGE: 1371 return "MedicationKnowledge"; 1372 case MEDICATIONREQUEST: 1373 return "MedicationRequest"; 1374 case MEDICATIONSTATEMENT: 1375 return "MedicationStatement"; 1376 case MEDICINALPRODUCT: 1377 return "MedicinalProduct"; 1378 case MEDICINALPRODUCTAUTHORIZATION: 1379 return "MedicinalProductAuthorization"; 1380 case MEDICINALPRODUCTCONTRAINDICATION: 1381 return "MedicinalProductContraindication"; 1382 case MEDICINALPRODUCTINDICATION: 1383 return "MedicinalProductIndication"; 1384 case MEDICINALPRODUCTINGREDIENT: 1385 return "MedicinalProductIngredient"; 1386 case MEDICINALPRODUCTINTERACTION: 1387 return "MedicinalProductInteraction"; 1388 case MEDICINALPRODUCTMANUFACTURED: 1389 return "MedicinalProductManufactured"; 1390 case MEDICINALPRODUCTPACKAGED: 1391 return "MedicinalProductPackaged"; 1392 case MEDICINALPRODUCTPHARMACEUTICAL: 1393 return "MedicinalProductPharmaceutical"; 1394 case MEDICINALPRODUCTUNDESIRABLEEFFECT: 1395 return "MedicinalProductUndesirableEffect"; 1396 case MESSAGEDEFINITION: 1397 return "MessageDefinition"; 1398 case MESSAGEHEADER: 1399 return "MessageHeader"; 1400 case MOLECULARSEQUENCE: 1401 return "MolecularSequence"; 1402 case NAMINGSYSTEM: 1403 return "NamingSystem"; 1404 case NUTRITIONORDER: 1405 return "NutritionOrder"; 1406 case OBSERVATION: 1407 return "Observation"; 1408 case OBSERVATIONDEFINITION: 1409 return "ObservationDefinition"; 1410 case OPERATIONDEFINITION: 1411 return "OperationDefinition"; 1412 case OPERATIONOUTCOME: 1413 return "OperationOutcome"; 1414 case ORGANIZATION: 1415 return "Organization"; 1416 case ORGANIZATIONAFFILIATION: 1417 return "OrganizationAffiliation"; 1418 case PARAMETERS: 1419 return "Parameters"; 1420 case PATIENT: 1421 return "Patient"; 1422 case PAYMENTNOTICE: 1423 return "PaymentNotice"; 1424 case PAYMENTRECONCILIATION: 1425 return "PaymentReconciliation"; 1426 case PERSON: 1427 return "Person"; 1428 case PLANDEFINITION: 1429 return "PlanDefinition"; 1430 case PRACTITIONER: 1431 return "Practitioner"; 1432 case PRACTITIONERROLE: 1433 return "PractitionerRole"; 1434 case PROCEDURE: 1435 return "Procedure"; 1436 case PROVENANCE: 1437 return "Provenance"; 1438 case QUESTIONNAIRE: 1439 return "Questionnaire"; 1440 case QUESTIONNAIRERESPONSE: 1441 return "QuestionnaireResponse"; 1442 case RELATEDPERSON: 1443 return "RelatedPerson"; 1444 case REQUESTGROUP: 1445 return "RequestGroup"; 1446 case RESEARCHDEFINITION: 1447 return "ResearchDefinition"; 1448 case RESEARCHELEMENTDEFINITION: 1449 return "ResearchElementDefinition"; 1450 case RESEARCHSTUDY: 1451 return "ResearchStudy"; 1452 case RESEARCHSUBJECT: 1453 return "ResearchSubject"; 1454 case RESOURCE: 1455 return "Resource"; 1456 case RISKASSESSMENT: 1457 return "RiskAssessment"; 1458 case RISKEVIDENCESYNTHESIS: 1459 return "RiskEvidenceSynthesis"; 1460 case SCHEDULE: 1461 return "Schedule"; 1462 case SEARCHPARAMETER: 1463 return "SearchParameter"; 1464 case SERVICEREQUEST: 1465 return "ServiceRequest"; 1466 case SLOT: 1467 return "Slot"; 1468 case SPECIMEN: 1469 return "Specimen"; 1470 case SPECIMENDEFINITION: 1471 return "SpecimenDefinition"; 1472 case STRUCTUREDEFINITION: 1473 return "StructureDefinition"; 1474 case STRUCTUREMAP: 1475 return "StructureMap"; 1476 case SUBSCRIPTION: 1477 return "Subscription"; 1478 case SUBSTANCE: 1479 return "Substance"; 1480 case SUBSTANCEDEFINITION: 1481 return "SubstanceDefinition"; 1482 case SUBSTANCENUCLEICACID: 1483 return "SubstanceNucleicAcid"; 1484 case SUBSTANCEPOLYMER: 1485 return "SubstancePolymer"; 1486 case SUBSTANCEPROTEIN: 1487 return "SubstanceProtein"; 1488 case SUBSTANCEREFERENCEINFORMATION: 1489 return "SubstanceReferenceInformation"; 1490 case SUBSTANCESOURCEMATERIAL: 1491 return "SubstanceSourceMaterial"; 1492 case SUPPLYDELIVERY: 1493 return "SupplyDelivery"; 1494 case SUPPLYREQUEST: 1495 return "SupplyRequest"; 1496 case TASK: 1497 return "Task"; 1498 case TERMINOLOGYCAPABILITIES: 1499 return "TerminologyCapabilities"; 1500 case TESTREPORT: 1501 return "TestReport"; 1502 case TESTSCRIPT: 1503 return "TestScript"; 1504 case VALUESET: 1505 return "ValueSet"; 1506 case VERIFICATIONRESULT: 1507 return "VerificationResult"; 1508 case VISIONPRESCRIPTION: 1509 return "VisionPrescription"; 1510 case NULL: 1511 return null; 1512 default: 1513 return "?"; 1514 } 1515 } 1516 1517 public String getSystem() { 1518 return "http://hl7.org/fhir/resource-types"; 1519 } 1520 1521 public String getDefinition() { 1522 switch (this) { 1523 case ACCOUNT: 1524 return "A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc."; 1525 case ACTIVITYDEFINITION: 1526 return "This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context."; 1527 case ADVERSEEVENT: 1528 return "Actual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death."; 1529 case ALLERGYINTOLERANCE: 1530 return "Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance."; 1531 case APPOINTMENT: 1532 return "A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s)."; 1533 case APPOINTMENTRESPONSE: 1534 return "A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection."; 1535 case AUDITEVENT: 1536 return "A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage."; 1537 case BASIC: 1538 return "Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification."; 1539 case BINARY: 1540 return "A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc."; 1541 case BIOLOGICALLYDERIVEDPRODUCT: 1542 return "A material substance originating from a biological entity intended to be transplanted or infused\ninto another (possibly the same) biological entity."; 1543 case BODYSTRUCTURE: 1544 return "Record details about an anatomical structure. This resource may be used when a coded concept does not provide the necessary detail needed for the use case."; 1545 case BUNDLE: 1546 return "A container for a collection of resources."; 1547 case CAPABILITYSTATEMENT: 1548 return "A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation."; 1549 case CAREPLAN: 1550 return "Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions."; 1551 case CARETEAM: 1552 return "The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient."; 1553 case CATALOGENTRY: 1554 return "Catalog entries are wrappers that contextualize items included in a catalog."; 1555 case CHARGEITEM: 1556 return "The resource ChargeItem describes the provision of healthcare provider products for a certain patient, therefore referring not only to the product, but containing in addition details of the provision, like date, time, amounts and participating organizations and persons. Main Usage of the ChargeItem is to enable the billing process and internal cost allocation."; 1557 case CHARGEITEMDEFINITION: 1558 return "The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system."; 1559 case CLAIM: 1560 return "A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement."; 1561 case CLAIMRESPONSE: 1562 return "This resource provides the adjudication details from the processing of a Claim resource."; 1563 case CLINICALIMPRESSION: 1564 return "A record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition. Assessments are often 1:1 with a clinical consultation / encounter, but this varies greatly depending on the clinical workflow. This resource is called \"ClinicalImpression\" rather than \"ClinicalAssessment\" to avoid confusion with the recording of assessment tools such as Apgar score."; 1565 case CODESYSTEM: 1566 return "The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content."; 1567 case COMMUNICATION: 1568 return "An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency that was notified about a reportable condition."; 1569 case COMMUNICATIONREQUEST: 1570 return "A request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition."; 1571 case COMPARTMENTDEFINITION: 1572 return "A compartment definition that defines how resources are accessed on a server."; 1573 case COMPOSITION: 1574 return "A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.)."; 1575 case CONCEPTMAP: 1576 return "A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models."; 1577 case CONDITION: 1578 return "A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern."; 1579 case CONSENT: 1580 return "A record of a healthcare consumer?s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time."; 1581 case CONTRACT: 1582 return "Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement."; 1583 case COVERAGE: 1584 return "Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment."; 1585 case COVERAGEELIGIBILITYREQUEST: 1586 return "The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy."; 1587 case COVERAGEELIGIBILITYRESPONSE: 1588 return "This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource."; 1589 case DETECTEDISSUE: 1590 return "Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, etc."; 1591 case DEVICE: 1592 return "A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device."; 1593 case DEVICEDEFINITION: 1594 return "The characteristics, operational status and capabilities of a medical-related component of a medical device."; 1595 case DEVICEMETRIC: 1596 return "Describes a measurement, calculation or setting capability of a medical device."; 1597 case DEVICEREQUEST: 1598 return "Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker."; 1599 case DEVICEUSESTATEMENT: 1600 return "A record of a device being used by a patient where the record is the result of a report from the patient or another clinician."; 1601 case DIAGNOSTICREPORT: 1602 return "The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports."; 1603 case DOCUMENTMANIFEST: 1604 return "A collection of documents compiled for a purpose together with metadata that applies to the collection."; 1605 case DOCUMENTREFERENCE: 1606 return "A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text."; 1607 case DOMAINRESOURCE: 1608 return "A resource that includes narrative, extensions, and contained resources."; 1609 case EFFECTEVIDENCESYNTHESIS: 1610 return "The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies."; 1611 case ENCOUNTER: 1612 return "An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient."; 1613 case ENDPOINT: 1614 return "The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b or a REST endpoint for another FHIR server. This may include any security context information."; 1615 case ENROLLMENTREQUEST: 1616 return "This resource provides the insurance enrollment details to the insurer regarding a specified coverage."; 1617 case ENROLLMENTRESPONSE: 1618 return "This resource provides enrollment and plan details from the processing of an EnrollmentRequest resource."; 1619 case EPISODEOFCARE: 1620 return "An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time."; 1621 case EVENTDEFINITION: 1622 return "The EventDefinition resource provides a reusable description of when a particular event can occur."; 1623 case EVIDENCE: 1624 return "The Evidence resource describes the conditional state (population and any exposures being compared within the population) and outcome (if specified) that the knowledge (evidence, assertion, recommendation) is about."; 1625 case EVIDENCEVARIABLE: 1626 return "The EvidenceVariable resource describes a \"PICO\" element that knowledge (evidence, assertion, recommendation) is about."; 1627 case EXAMPLESCENARIO: 1628 return "Example of workflow instance."; 1629 case EXPLANATIONOFBENEFIT: 1630 return "This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided."; 1631 case FAMILYMEMBERHISTORY: 1632 return "Significant health conditions for a person related to the patient relevant in the context of care for the patient."; 1633 case FLAG: 1634 return "Prospective warnings of potential issues when providing care to the patient."; 1635 case GOAL: 1636 return "Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc."; 1637 case GRAPHDEFINITION: 1638 return "A formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references. The Graph Definition resource defines a set and makes rules about the set."; 1639 case GROUP: 1640 return "Represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively, and are not formally or legally recognized; i.e. a collection of entities that isn't an Organization."; 1641 case GUIDANCERESPONSE: 1642 return "A guidance response is the formal response to a guidance request, including any output parameters returned by the evaluation, as well as the description of any proposed actions to be taken."; 1643 case HEALTHCARESERVICE: 1644 return "The details of a healthcare service available at a location."; 1645 case IMAGINGSTUDY: 1646 return "Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities."; 1647 case IMMUNIZATION: 1648 return "Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party."; 1649 case IMMUNIZATIONEVALUATION: 1650 return "Describes a comparison of an immunization event against published recommendations to determine if the administration is \"valid\" in relation to those recommendations."; 1651 case IMMUNIZATIONRECOMMENDATION: 1652 return "A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification."; 1653 case IMPLEMENTATIONGUIDE: 1654 return "A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts."; 1655 case INSURANCEPLAN: 1656 return "Details of a Health Insurance product/plan provided by an organization."; 1657 case INVOICE: 1658 return "Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose."; 1659 case LIBRARY: 1660 return "The Library resource is a general-purpose container for knowledge asset definitions. It can be used to describe and expose existing knowledge assets such as logic libraries and information model descriptions, as well as to describe a collection of knowledge assets."; 1661 case LINKAGE: 1662 return "Identifies two or more records (resource instances) that refer to the same real-world \"occurrence\"."; 1663 case LIST: 1664 return "A list is a curated collection of resources."; 1665 case LOCATION: 1666 return "Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated."; 1667 case MEASURE: 1668 return "The Measure resource provides the definition of a quality measure."; 1669 case MEASUREREPORT: 1670 return "The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation."; 1671 case MEDIA: 1672 return "A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference."; 1673 case MEDICATION: 1674 return "This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use."; 1675 case MEDICATIONADMINISTRATION: 1676 return "Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner."; 1677 case MEDICATIONDISPENSE: 1678 return "Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order."; 1679 case MEDICATIONKNOWLEDGE: 1680 return "Information about a medication that is used to support knowledge."; 1681 case MEDICATIONREQUEST: 1682 return "An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called \"MedicationRequest\" rather than \"MedicationPrescription\" or \"MedicationOrder\" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns."; 1683 case MEDICATIONSTATEMENT: 1684 return "A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains. \n\nThe primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information."; 1685 case MEDICINALPRODUCT: 1686 return "Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use)."; 1687 case MEDICINALPRODUCTAUTHORIZATION: 1688 return "The regulatory authorization of a medicinal product."; 1689 case MEDICINALPRODUCTCONTRAINDICATION: 1690 return "The clinical particulars - indications, contraindications etc. of a medicinal product, including for regulatory purposes."; 1691 case MEDICINALPRODUCTINDICATION: 1692 return "Indication for the Medicinal Product."; 1693 case MEDICINALPRODUCTINGREDIENT: 1694 return "An ingredient of a manufactured item or pharmaceutical product."; 1695 case MEDICINALPRODUCTINTERACTION: 1696 return "The interactions of the medicinal product with other medicinal products, or other forms of interactions."; 1697 case MEDICINALPRODUCTMANUFACTURED: 1698 return "The manufactured item as contained in the packaged medicinal product."; 1699 case MEDICINALPRODUCTPACKAGED: 1700 return "A medicinal product in a container or package."; 1701 case MEDICINALPRODUCTPHARMACEUTICAL: 1702 return "A pharmaceutical product described in terms of its composition and dose form."; 1703 case MEDICINALPRODUCTUNDESIRABLEEFFECT: 1704 return "Describe the undesirable effects of the medicinal product."; 1705 case MESSAGEDEFINITION: 1706 return "Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted."; 1707 case MESSAGEHEADER: 1708 return "The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle."; 1709 case MOLECULARSEQUENCE: 1710 return "Raw data describing a biological sequence."; 1711 case NAMINGSYSTEM: 1712 return "A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a \"System\" used within the Identifier and Coding data types."; 1713 case NUTRITIONORDER: 1714 return "A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident."; 1715 case OBSERVATION: 1716 return "Measurements and simple assertions made about a patient, device or other subject."; 1717 case OBSERVATIONDEFINITION: 1718 return "Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service."; 1719 case OPERATIONDEFINITION: 1720 return "A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction)."; 1721 case OPERATIONOUTCOME: 1722 return "A collection of error, warning, or information messages that result from a system action."; 1723 case ORGANIZATION: 1724 return "A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc."; 1725 case ORGANIZATIONAFFILIATION: 1726 return "Defines an affiliation/assotiation/relationship between 2 distinct oganizations, that is not a part-of relationship/sub-division relationship."; 1727 case PARAMETERS: 1728 return "This resource is a non-persisted resource used to pass information into and back from an [operation](operations.html). It has no other use, and there is no RESTful endpoint associated with it."; 1729 case PATIENT: 1730 return "Demographics and other administrative information about an individual or animal receiving care or other health-related services."; 1731 case PAYMENTNOTICE: 1732 return "This resource provides the status of the payment for goods and services rendered, and the request and response resource references."; 1733 case PAYMENTRECONCILIATION: 1734 return "This resource provides the details including amount of a payment and allocates the payment items being paid."; 1735 case PERSON: 1736 return "Demographics and administrative information about a person independent of a specific health-related context."; 1737 case PLANDEFINITION: 1738 return "This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols."; 1739 case PRACTITIONER: 1740 return "A person who is directly or indirectly involved in the provisioning of healthcare."; 1741 case PRACTITIONERROLE: 1742 return "A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time."; 1743 case PROCEDURE: 1744 return "An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy."; 1745 case PROVENANCE: 1746 return "Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies."; 1747 case QUESTIONNAIRE: 1748 return "A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection."; 1749 case QUESTIONNAIRERESPONSE: 1750 return "A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to."; 1751 case RELATEDPERSON: 1752 return "Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process."; 1753 case REQUESTGROUP: 1754 return "A group of related requests that can be used to capture intended activities that have inter-dependencies such as \"give this medication after that one\"."; 1755 case RESEARCHDEFINITION: 1756 return "The ResearchDefinition resource describes the conditional state (population and any exposures being compared within the population) and outcome (if specified) that the knowledge (evidence, assertion, recommendation) is about."; 1757 case RESEARCHELEMENTDEFINITION: 1758 return "The ResearchElementDefinition resource describes a \"PICO\" element that knowledge (evidence, assertion, recommendation) is about."; 1759 case RESEARCHSTUDY: 1760 return "A process where a researcher or organization plans and then executes a series of steps intended to increase the field of healthcare-related knowledge. This includes studies of safety, efficacy, comparative effectiveness and other information about medications, devices, therapies and other interventional and investigative techniques. A ResearchStudy involves the gathering of information about human or animal subjects."; 1761 case RESEARCHSUBJECT: 1762 return "A physical entity which is the primary unit of operational and/or administrative interest in a study."; 1763 case RESOURCE: 1764 return "This is the base resource type for everything."; 1765 case RISKASSESSMENT: 1766 return "An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome."; 1767 case RISKEVIDENCESYNTHESIS: 1768 return "The RiskEvidenceSynthesis resource describes the likelihood of an outcome in a population plus exposure state where the risk estimate is derived from a combination of research studies."; 1769 case SCHEDULE: 1770 return "A container for slots of time that may be available for booking appointments."; 1771 case SEARCHPARAMETER: 1772 return "A search parameter that defines a named search item that can be used to search/filter on a resource."; 1773 case SERVICEREQUEST: 1774 return "A record of a request for service such as diagnostic investigations, treatments, or operations to be performed."; 1775 case SLOT: 1776 return "A slot of time on a schedule that may be available for booking appointments."; 1777 case SPECIMEN: 1778 return "A sample to be used for analysis."; 1779 case SPECIMENDEFINITION: 1780 return "A kind of specimen with associated set of requirements."; 1781 case STRUCTUREDEFINITION: 1782 return "A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types."; 1783 case STRUCTUREMAP: 1784 return "A Map of relationships between 2 structures that can be used to transform data."; 1785 case SUBSCRIPTION: 1786 return "The subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined \"channel\" so that another system can take an appropriate action."; 1787 case SUBSTANCE: 1788 return "A homogeneous material with a definite composition."; 1789 case SUBSTANCEDEFINITION: 1790 return "The detailed description of a substance, typically at a level beyond what is used for prescribing."; 1791 case SUBSTANCENUCLEICACID: 1792 return "Nucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5?-3? direction."; 1793 case SUBSTANCEPOLYMER: 1794 return "Todo."; 1795 case SUBSTANCEPROTEIN: 1796 return "A SubstanceProtein is defined as a single unit of a linear amino acid sequence, or a combination of subunits that are either covalently linked or have a defined invariant stoichiometric relationship. This includes all synthetic, recombinant and purified SubstanceProteins of defined sequence, whether the use is therapeutic or prophylactic. This set of elements will be used to describe albumins, coagulation factors, cytokines, growth factors, peptide/SubstanceProtein hormones, enzymes, toxins, toxoids, recombinant vaccines, and immunomodulators."; 1797 case SUBSTANCEREFERENCEINFORMATION: 1798 return "Todo."; 1799 case SUBSTANCESOURCEMATERIAL: 1800 return "Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex."; 1801 case SUPPLYDELIVERY: 1802 return "Record of delivery of what is supplied."; 1803 case SUPPLYREQUEST: 1804 return "A record of a request for a medication, substance or device used in the healthcare setting."; 1805 case TASK: 1806 return "A task to be performed."; 1807 case TERMINOLOGYCAPABILITIES: 1808 return "A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation."; 1809 case TESTREPORT: 1810 return "A summary of information based on the results of executing a TestScript."; 1811 case TESTSCRIPT: 1812 return "A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification."; 1813 case VALUESET: 1814 return "A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html)."; 1815 case VERIFICATIONRESULT: 1816 return "Describes validation requirements, source(s), status and dates for one or more elements."; 1817 case VISIONPRESCRIPTION: 1818 return "An authorization for the provision of glasses and/or contact lenses to a patient."; 1819 case NULL: 1820 return null; 1821 default: 1822 return "?"; 1823 } 1824 } 1825 1826 public String getDisplay() { 1827 switch (this) { 1828 case ACCOUNT: 1829 return "Account"; 1830 case ACTIVITYDEFINITION: 1831 return "ActivityDefinition"; 1832 case ADVERSEEVENT: 1833 return "AdverseEvent"; 1834 case ALLERGYINTOLERANCE: 1835 return "AllergyIntolerance"; 1836 case APPOINTMENT: 1837 return "Appointment"; 1838 case APPOINTMENTRESPONSE: 1839 return "AppointmentResponse"; 1840 case AUDITEVENT: 1841 return "AuditEvent"; 1842 case BASIC: 1843 return "Basic"; 1844 case BINARY: 1845 return "Binary"; 1846 case BIOLOGICALLYDERIVEDPRODUCT: 1847 return "BiologicallyDerivedProduct"; 1848 case BODYSTRUCTURE: 1849 return "BodyStructure"; 1850 case BUNDLE: 1851 return "Bundle"; 1852 case CAPABILITYSTATEMENT: 1853 return "CapabilityStatement"; 1854 case CAREPLAN: 1855 return "CarePlan"; 1856 case CARETEAM: 1857 return "CareTeam"; 1858 case CATALOGENTRY: 1859 return "CatalogEntry"; 1860 case CHARGEITEM: 1861 return "ChargeItem"; 1862 case CHARGEITEMDEFINITION: 1863 return "ChargeItemDefinition"; 1864 case CLAIM: 1865 return "Claim"; 1866 case CLAIMRESPONSE: 1867 return "ClaimResponse"; 1868 case CLINICALIMPRESSION: 1869 return "ClinicalImpression"; 1870 case CODESYSTEM: 1871 return "CodeSystem"; 1872 case COMMUNICATION: 1873 return "Communication"; 1874 case COMMUNICATIONREQUEST: 1875 return "CommunicationRequest"; 1876 case COMPARTMENTDEFINITION: 1877 return "CompartmentDefinition"; 1878 case COMPOSITION: 1879 return "Composition"; 1880 case CONCEPTMAP: 1881 return "ConceptMap"; 1882 case CONDITION: 1883 return "Condition"; 1884 case CONSENT: 1885 return "Consent"; 1886 case CONTRACT: 1887 return "Contract"; 1888 case COVERAGE: 1889 return "Coverage"; 1890 case COVERAGEELIGIBILITYREQUEST: 1891 return "CoverageEligibilityRequest"; 1892 case COVERAGEELIGIBILITYRESPONSE: 1893 return "CoverageEligibilityResponse"; 1894 case DETECTEDISSUE: 1895 return "DetectedIssue"; 1896 case DEVICE: 1897 return "Device"; 1898 case DEVICEDEFINITION: 1899 return "DeviceDefinition"; 1900 case DEVICEMETRIC: 1901 return "DeviceMetric"; 1902 case DEVICEREQUEST: 1903 return "DeviceRequest"; 1904 case DEVICEUSESTATEMENT: 1905 return "DeviceUseStatement"; 1906 case DIAGNOSTICREPORT: 1907 return "DiagnosticReport"; 1908 case DOCUMENTMANIFEST: 1909 return "DocumentManifest"; 1910 case DOCUMENTREFERENCE: 1911 return "DocumentReference"; 1912 case DOMAINRESOURCE: 1913 return "DomainResource"; 1914 case EFFECTEVIDENCESYNTHESIS: 1915 return "EffectEvidenceSynthesis"; 1916 case ENCOUNTER: 1917 return "Encounter"; 1918 case ENDPOINT: 1919 return "Endpoint"; 1920 case ENROLLMENTREQUEST: 1921 return "EnrollmentRequest"; 1922 case ENROLLMENTRESPONSE: 1923 return "EnrollmentResponse"; 1924 case EPISODEOFCARE: 1925 return "EpisodeOfCare"; 1926 case EVENTDEFINITION: 1927 return "EventDefinition"; 1928 case EVIDENCE: 1929 return "Evidence"; 1930 case EVIDENCEVARIABLE: 1931 return "EvidenceVariable"; 1932 case EXAMPLESCENARIO: 1933 return "ExampleScenario"; 1934 case EXPLANATIONOFBENEFIT: 1935 return "ExplanationOfBenefit"; 1936 case FAMILYMEMBERHISTORY: 1937 return "FamilyMemberHistory"; 1938 case FLAG: 1939 return "Flag"; 1940 case GOAL: 1941 return "Goal"; 1942 case GRAPHDEFINITION: 1943 return "GraphDefinition"; 1944 case GROUP: 1945 return "Group"; 1946 case GUIDANCERESPONSE: 1947 return "GuidanceResponse"; 1948 case HEALTHCARESERVICE: 1949 return "HealthcareService"; 1950 case IMAGINGSTUDY: 1951 return "ImagingStudy"; 1952 case IMMUNIZATION: 1953 return "Immunization"; 1954 case IMMUNIZATIONEVALUATION: 1955 return "ImmunizationEvaluation"; 1956 case IMMUNIZATIONRECOMMENDATION: 1957 return "ImmunizationRecommendation"; 1958 case IMPLEMENTATIONGUIDE: 1959 return "ImplementationGuide"; 1960 case INSURANCEPLAN: 1961 return "InsurancePlan"; 1962 case INVOICE: 1963 return "Invoice"; 1964 case LIBRARY: 1965 return "Library"; 1966 case LINKAGE: 1967 return "Linkage"; 1968 case LIST: 1969 return "List"; 1970 case LOCATION: 1971 return "Location"; 1972 case MEASURE: 1973 return "Measure"; 1974 case MEASUREREPORT: 1975 return "MeasureReport"; 1976 case MEDIA: 1977 return "Media"; 1978 case MEDICATION: 1979 return "Medication"; 1980 case MEDICATIONADMINISTRATION: 1981 return "MedicationAdministration"; 1982 case MEDICATIONDISPENSE: 1983 return "MedicationDispense"; 1984 case MEDICATIONKNOWLEDGE: 1985 return "MedicationKnowledge"; 1986 case MEDICATIONREQUEST: 1987 return "MedicationRequest"; 1988 case MEDICATIONSTATEMENT: 1989 return "MedicationStatement"; 1990 case MEDICINALPRODUCT: 1991 return "MedicinalProduct"; 1992 case MEDICINALPRODUCTAUTHORIZATION: 1993 return "MedicinalProductAuthorization"; 1994 case MEDICINALPRODUCTCONTRAINDICATION: 1995 return "MedicinalProductContraindication"; 1996 case MEDICINALPRODUCTINDICATION: 1997 return "MedicinalProductIndication"; 1998 case MEDICINALPRODUCTINGREDIENT: 1999 return "MedicinalProductIngredient"; 2000 case MEDICINALPRODUCTINTERACTION: 2001 return "MedicinalProductInteraction"; 2002 case MEDICINALPRODUCTMANUFACTURED: 2003 return "MedicinalProductManufactured"; 2004 case MEDICINALPRODUCTPACKAGED: 2005 return "MedicinalProductPackaged"; 2006 case MEDICINALPRODUCTPHARMACEUTICAL: 2007 return "MedicinalProductPharmaceutical"; 2008 case MEDICINALPRODUCTUNDESIRABLEEFFECT: 2009 return "MedicinalProductUndesirableEffect"; 2010 case MESSAGEDEFINITION: 2011 return "MessageDefinition"; 2012 case MESSAGEHEADER: 2013 return "MessageHeader"; 2014 case MOLECULARSEQUENCE: 2015 return "MolecularSequence"; 2016 case NAMINGSYSTEM: 2017 return "NamingSystem"; 2018 case NUTRITIONORDER: 2019 return "NutritionOrder"; 2020 case OBSERVATION: 2021 return "Observation"; 2022 case OBSERVATIONDEFINITION: 2023 return "ObservationDefinition"; 2024 case OPERATIONDEFINITION: 2025 return "OperationDefinition"; 2026 case OPERATIONOUTCOME: 2027 return "OperationOutcome"; 2028 case ORGANIZATION: 2029 return "Organization"; 2030 case ORGANIZATIONAFFILIATION: 2031 return "OrganizationAffiliation"; 2032 case PARAMETERS: 2033 return "Parameters"; 2034 case PATIENT: 2035 return "Patient"; 2036 case PAYMENTNOTICE: 2037 return "PaymentNotice"; 2038 case PAYMENTRECONCILIATION: 2039 return "PaymentReconciliation"; 2040 case PERSON: 2041 return "Person"; 2042 case PLANDEFINITION: 2043 return "PlanDefinition"; 2044 case PRACTITIONER: 2045 return "Practitioner"; 2046 case PRACTITIONERROLE: 2047 return "PractitionerRole"; 2048 case PROCEDURE: 2049 return "Procedure"; 2050 case PROVENANCE: 2051 return "Provenance"; 2052 case QUESTIONNAIRE: 2053 return "Questionnaire"; 2054 case QUESTIONNAIRERESPONSE: 2055 return "QuestionnaireResponse"; 2056 case RELATEDPERSON: 2057 return "RelatedPerson"; 2058 case REQUESTGROUP: 2059 return "RequestGroup"; 2060 case RESEARCHDEFINITION: 2061 return "ResearchDefinition"; 2062 case RESEARCHELEMENTDEFINITION: 2063 return "ResearchElementDefinition"; 2064 case RESEARCHSTUDY: 2065 return "ResearchStudy"; 2066 case RESEARCHSUBJECT: 2067 return "ResearchSubject"; 2068 case RESOURCE: 2069 return "Resource"; 2070 case RISKASSESSMENT: 2071 return "RiskAssessment"; 2072 case RISKEVIDENCESYNTHESIS: 2073 return "RiskEvidenceSynthesis"; 2074 case SCHEDULE: 2075 return "Schedule"; 2076 case SEARCHPARAMETER: 2077 return "SearchParameter"; 2078 case SERVICEREQUEST: 2079 return "ServiceRequest"; 2080 case SLOT: 2081 return "Slot"; 2082 case SPECIMEN: 2083 return "Specimen"; 2084 case SPECIMENDEFINITION: 2085 return "SpecimenDefinition"; 2086 case STRUCTUREDEFINITION: 2087 return "StructureDefinition"; 2088 case STRUCTUREMAP: 2089 return "StructureMap"; 2090 case SUBSCRIPTION: 2091 return "Subscription"; 2092 case SUBSTANCE: 2093 return "Substance"; 2094 case SUBSTANCEDEFINITION: 2095 return "SubstanceDefinition"; 2096 case SUBSTANCENUCLEICACID: 2097 return "SubstanceNucleicAcid"; 2098 case SUBSTANCEPOLYMER: 2099 return "SubstancePolymer"; 2100 case SUBSTANCEPROTEIN: 2101 return "SubstanceProtein"; 2102 case SUBSTANCEREFERENCEINFORMATION: 2103 return "SubstanceReferenceInformation"; 2104 case SUBSTANCESOURCEMATERIAL: 2105 return "SubstanceSourceMaterial"; 2106 case SUPPLYDELIVERY: 2107 return "SupplyDelivery"; 2108 case SUPPLYREQUEST: 2109 return "SupplyRequest"; 2110 case TASK: 2111 return "Task"; 2112 case TERMINOLOGYCAPABILITIES: 2113 return "TerminologyCapabilities"; 2114 case TESTREPORT: 2115 return "TestReport"; 2116 case TESTSCRIPT: 2117 return "TestScript"; 2118 case VALUESET: 2119 return "ValueSet"; 2120 case VERIFICATIONRESULT: 2121 return "VerificationResult"; 2122 case VISIONPRESCRIPTION: 2123 return "VisionPrescription"; 2124 case NULL: 2125 return null; 2126 default: 2127 return "?"; 2128 } 2129 } 2130 2131}