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 Thu, Sep 13, 2018 09:04-0400 for FHIR v3.5.0 033 034 035import org.hl7.fhir.exceptions.FHIRException; 036 037public enum ResourceTypes { 038 039 /** 040 * 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. 041 */ 042 ACCOUNT, 043 /** 044 * This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context. 045 */ 046 ACTIVITYDEFINITION, 047 /** 048 * 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. 049 */ 050 ADVERSEEVENT, 051 /** 052 * Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. 053 */ 054 ALLERGYINTOLERANCE, 055 /** 056 * 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). 057 */ 058 APPOINTMENT, 059 /** 060 * A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection. 061 */ 062 APPOINTMENTRESPONSE, 063 /** 064 * 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. 065 */ 066 AUDITEVENT, 067 /** 068 * 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. 069 */ 070 BASIC, 071 /** 072 * 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. 073 */ 074 BINARY, 075 /** 076 * A material substance originating from a biological entity intended to be transplanted or infused 077into another (possibly the same) biological entity. 078 */ 079 BIOLOGICALLYDERIVEDPRODUCT, 080 /** 081 * 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. 082 */ 083 BODYSTRUCTURE, 084 /** 085 * A container for a collection of resources. 086 */ 087 BUNDLE, 088 /** 089 * A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. 090 */ 091 CAPABILITYSTATEMENT, 092 /** 093 * 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. 094 */ 095 CAREPLAN, 096 /** 097 * The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. 098 */ 099 CARETEAM, 100 /** 101 * Catalog entries are wrappers that contextualize items included in a catalog. 102 */ 103 CATALOGENTRY, 104 /** 105 * 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. 106 */ 107 CHARGEITEM, 108 /** 109 * 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. 110 */ 111 CHARGEITEMDEFINITION, 112 /** 113 * A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. 114 */ 115 CLAIM, 116 /** 117 * This resource provides the adjudication details from the processing of a Claim resource. 118 */ 119 CLAIMRESPONSE, 120 /** 121 * 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. 122 */ 123 CLINICALIMPRESSION, 124 /** 125 * 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. 126 */ 127 CODESYSTEM, 128 /** 129 * An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency was notified about a reportable condition. 130 */ 131 COMMUNICATION, 132 /** 133 * 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. 134 */ 135 COMMUNICATIONREQUEST, 136 /** 137 * A compartment definition that defines how resources are accessed on a server. 138 */ 139 COMPARTMENTDEFINITION, 140 /** 141 * 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.). 142 */ 143 COMPOSITION, 144 /** 145 * 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. 146 */ 147 CONCEPTMAP, 148 /** 149 * A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. 150 */ 151 CONDITION, 152 /** 153 * 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. 154 */ 155 CONSENT, 156 /** 157 * Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. 158 */ 159 CONTRACT, 160 /** 161 * Financial instrument which may be used to reimburse or pay for health care products and services. 162 */ 163 COVERAGE, 164 /** 165 * 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. 166 */ 167 COVERAGEELIGIBILITYREQUEST, 168 /** 169 * This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource. 170 */ 171 COVERAGEELIGIBILITYRESPONSE, 172 /** 173 * 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. 174 */ 175 DETECTEDISSUE, 176 /** 177 * This resource identifies 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. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc. This is the catalog description of a device (not the specific instance). 178 */ 179 DEVICE, 180 /** 181 * The characteristics, operational status and capabilities of a medical-related component of a medical device. 182 */ 183 DEVICEDEFINITION, 184 /** 185 * Describes a measurement, calculation or setting capability of a medical device. 186 */ 187 DEVICEMETRIC, 188 /** 189 * 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. 190 */ 191 DEVICEREQUEST, 192 /** 193 * 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. 194 */ 195 DEVICEUSESTATEMENT, 196 /** 197 * 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. 198 */ 199 DIAGNOSTICREPORT, 200 /** 201 * A collection of documents compiled for a purpose together with metadata that applies to the collection. 202 */ 203 DOCUMENTMANIFEST, 204 /** 205 * A reference to a document. 206 */ 207 DOCUMENTREFERENCE, 208 /** 209 * A resource that includes narrative, extensions, and contained resources. 210 */ 211 DOMAINRESOURCE, 212 /** 213 * 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. 214 */ 215 ENCOUNTER, 216 /** 217 * 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. 218 */ 219 ENDPOINT, 220 /** 221 * This resource provides the insurance enrollment details to the insurer regarding a specified coverage. 222 */ 223 ENROLLMENTREQUEST, 224 /** 225 * This resource provides enrollment and plan details from the processing of an Enrollment resource. 226 */ 227 ENROLLMENTRESPONSE, 228 /** 229 * 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. 230 */ 231 EPISODEOFCARE, 232 /** 233 * The EventDefinition resource provides a reusable description of when a particular event can occur. 234 */ 235 EVENTDEFINITION, 236 /** 237 * Example of workflow instance. 238 */ 239 EXAMPLESCENARIO, 240 /** 241 * 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. 242 */ 243 EXPLANATIONOFBENEFIT, 244 /** 245 * Significant health conditions for a person related to the patient relevant in the context of care for the patient. 246 */ 247 FAMILYMEMBERHISTORY, 248 /** 249 * Prospective warnings of potential issues when providing care to the patient. 250 */ 251 FLAG, 252 /** 253 * 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. 254 */ 255 GOAL, 256 /** 257 * 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. 258 */ 259 GRAPHDEFINITION, 260 /** 261 * 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. 262 */ 263 GROUP, 264 /** 265 * 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. 266 */ 267 GUIDANCERESPONSE, 268 /** 269 * The details of a healthcare service available at a location. 270 */ 271 HEALTHCARESERVICE, 272 /** 273 * 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. 274 */ 275 IMAGINGSTUDY, 276 /** 277 * 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. 278 */ 279 IMMUNIZATION, 280 /** 281 * Describes a comparison of an immunization event against published recommendations to determine if the administration is "valid" in relation to those recommendations. 282 */ 283 IMMUNIZATIONEVALUATION, 284 /** 285 * A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification. 286 */ 287 IMMUNIZATIONRECOMMENDATION, 288 /** 289 * A set of rules of how FHIR is used to solve a particular problem. 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. 290 */ 291 IMPLEMENTATIONGUIDE, 292 /** 293 * Details of a Health Insurance product/plan provided by an organization. 294 */ 295 INSURANCEPLAN, 296 /** 297 * Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose. 298 */ 299 INVOICE, 300 /** 301 * A physical, countable instance of an item, for example one box or one unit. 302 */ 303 ITEMINSTANCE, 304 /** 305 * 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. 306 */ 307 LIBRARY, 308 /** 309 * Identifies two or more records (resource instances) that are referring to the same real-world "occurrence". 310 */ 311 LINKAGE, 312 /** 313 * A set of information summarized from a list of other resources. 314 */ 315 LIST, 316 /** 317 * Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated. 318 */ 319 LOCATION, 320 /** 321 * The Measure resource provides the definition of a quality measure. 322 */ 323 MEASURE, 324 /** 325 * The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. 326 */ 327 MEASUREREPORT, 328 /** 329 * A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference. 330 */ 331 MEDIA, 332 /** 333 * 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. 334 */ 335 MEDICATION, 336 /** 337 * 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. 338 */ 339 MEDICATIONADMINISTRATION, 340 /** 341 * 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. 342 */ 343 MEDICATIONDISPENSE, 344 /** 345 * Information about a medication that is used to support knowledge. 346 */ 347 MEDICATIONKNOWLEDGE, 348 /** 349 * 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. 350 */ 351 MEDICATIONREQUEST, 352 /** 353 * 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. 354 355The 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. 356 */ 357 MEDICATIONSTATEMENT, 358 /** 359 * Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). 360 */ 361 MEDICINALPRODUCT, 362 /** 363 * The regulatory authorization of a medicinal product. 364 */ 365 MEDICINALPRODUCTAUTHORIZATION, 366 /** 367 * The clinical particulars - indications, contraindications etc. of a medicinal product, including for regulatory purposes. 368 */ 369 MEDICINALPRODUCTCLINICALS, 370 /** 371 * The clinical particulars - indications, contraindications etc. of a medicinal product, including for regulatory purposes. 372 */ 373 MEDICINALPRODUCTCONTRAINDICATION, 374 /** 375 * A detailed description of a device, typically as part of a regulated medicinal product. It is not intended to replace the Device resource, which covers use of device instances. 376 */ 377 MEDICINALPRODUCTDEVICESPEC, 378 /** 379 * Indication for the Medicinal Product. 380 */ 381 MEDICINALPRODUCTINDICATION, 382 /** 383 * An ingredient of a manufactured item or pharmaceutical product. 384 */ 385 MEDICINALPRODUCTINGREDIENT, 386 /** 387 * The interactions of the medicinal product with other medicinal products, or other forms of interactions. 388 */ 389 MEDICINALPRODUCTINTERACTION, 390 /** 391 * The manufactured item as contained in the packaged medicinal product. 392 */ 393 MEDICINALPRODUCTMANUFACTURED, 394 /** 395 * A medicinal product in a container or package. 396 */ 397 MEDICINALPRODUCTPACKAGED, 398 /** 399 * A pharmaceutical product described in terms of its composition and dose form. 400 */ 401 MEDICINALPRODUCTPHARMACEUTICAL, 402 /** 403 * Describe the undesirable effects of the medicinal product. 404 */ 405 MEDICINALPRODUCTUNDESIRABLEEFFECT, 406 /** 407 * 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. 408 */ 409 MESSAGEDEFINITION, 410 /** 411 * 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. 412 */ 413 MESSAGEHEADER, 414 /** 415 * 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. 416 */ 417 NAMINGSYSTEM, 418 /** 419 * A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. 420 */ 421 NUTRITIONORDER, 422 /** 423 * Measurements and simple assertions made about a patient, device or other subject. 424 */ 425 OBSERVATION, 426 /** 427 * Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. 428 */ 429 OBSERVATIONDEFINITION, 430 /** 431 * A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). 432 */ 433 OPERATIONDEFINITION, 434 /** 435 * A collection of error, warning or information messages that result from a system action. 436 */ 437 OPERATIONOUTCOME, 438 /** 439 * 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. 440 */ 441 ORGANIZATION, 442 /** 443 * Defines an affiliation/assotiation/relationship between 2 distinct oganizations, that is not a part-of relationship/sub-division relationship. 444 */ 445 ORGANIZATIONAFFILIATION, 446 /** 447 * This special resource type is used to represent an operation request and response (operations.html). It has no other use, and there is no RESTful endpoint associated with it. 448 */ 449 PARAMETERS, 450 /** 451 * Demographics and other administrative information about an individual or animal receiving care or other health-related services. 452 */ 453 PATIENT, 454 /** 455 * This resource provides the status of the payment for goods and services rendered, and the request and response resource references. 456 */ 457 PAYMENTNOTICE, 458 /** 459 * This resource provides payment details and claim references supporting a bulk payment. 460 */ 461 PAYMENTRECONCILIATION, 462 /** 463 * Demographics and administrative information about a person independent of a specific health-related context. 464 */ 465 PERSON, 466 /** 467 * 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. 468 */ 469 PLANDEFINITION, 470 /** 471 * A person who is directly or indirectly involved in the provisioning of healthcare. 472 */ 473 PRACTITIONER, 474 /** 475 * A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. 476 */ 477 PRACTITIONERROLE, 478 /** 479 * 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. 480 */ 481 PROCEDURE, 482 /** 483 * This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources. 484 */ 485 PROCESSREQUEST, 486 /** 487 * This resource provides processing status, errors and notes from the processing of a resource. 488 */ 489 PROCESSRESPONSE, 490 /** 491 * 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. 492 */ 493 PROVENANCE, 494 /** 495 * 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. 496 */ 497 QUESTIONNAIRE, 498 /** 499 * 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. 500 */ 501 QUESTIONNAIRERESPONSE, 502 /** 503 * 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. 504 */ 505 RELATEDPERSON, 506 /** 507 * 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". 508 */ 509 REQUESTGROUP, 510 /** 511 * 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. 512 */ 513 RESEARCHSTUDY, 514 /** 515 * A physical entity which is the primary unit of operational and/or administrative interest in a study. 516 */ 517 RESEARCHSUBJECT, 518 /** 519 * This is the base resource type for everything. 520 */ 521 RESOURCE, 522 /** 523 * An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. 524 */ 525 RISKASSESSMENT, 526 /** 527 * A container for slots of time that may be available for booking appointments. 528 */ 529 SCHEDULE, 530 /** 531 * A search parameter that defines a named search item that can be used to search/filter on a resource. 532 */ 533 SEARCHPARAMETER, 534 /** 535 * Raw data describing a biological sequence. 536 */ 537 SEQUENCE, 538 /** 539 * A record of a request for service such as diagnostic investigations, treatments, or operations to be performed. 540 */ 541 SERVICEREQUEST, 542 /** 543 * A slot of time on a schedule that may be available for booking appointments. 544 */ 545 SLOT, 546 /** 547 * A sample to be used for analysis. 548 */ 549 SPECIMEN, 550 /** 551 * A kind of specimen with associated set of requirements. 552 */ 553 SPECIMENDEFINITION, 554 /** 555 * 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. 556 */ 557 STRUCTUREDEFINITION, 558 /** 559 * A Map of relationships between 2 structures that can be used to transform data. 560 */ 561 STRUCTUREMAP, 562 /** 563 * 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. 564 */ 565 SUBSCRIPTION, 566 /** 567 * A homogeneous material with a definite composition. 568 */ 569 SUBSTANCE, 570 /** 571 * Todo. 572 */ 573 SUBSTANCEPOLYMER, 574 /** 575 * Todo. 576 */ 577 SUBSTANCEREFERENCEINFORMATION, 578 /** 579 * The detailed description of a substance, typically at a level beyond what is used for prescribing. 580 */ 581 SUBSTANCESPECIFICATION, 582 /** 583 * Record of delivery of what is supplied. 584 */ 585 SUPPLYDELIVERY, 586 /** 587 * A record of a request for a medication, substance or device used in the healthcare setting. 588 */ 589 SUPPLYREQUEST, 590 /** 591 * A task to be performed. 592 */ 593 TASK, 594 /** 595 * A Terminology Capabilities documents a set of capabilities (behaviors) of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. 596 */ 597 TERMINOLOGYCAPABILITIES, 598 /** 599 * A summary of information based on the results of executing a TestScript. 600 */ 601 TESTREPORT, 602 /** 603 * A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. 604 */ 605 TESTSCRIPT, 606 /** 607 * Information about a user's current session. 608 */ 609 USERSESSION, 610 /** 611 * A ValueSet resource instances 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). 612 */ 613 VALUESET, 614 /** 615 * Describes validation requirements, source(s), status and dates for one or more elements. 616 */ 617 VERIFICATIONRESULT, 618 /** 619 * An authorization for the supply of glasses and/or contact lenses to a patient. 620 */ 621 VISIONPRESCRIPTION, 622 /** 623 * added to help the parsers 624 */ 625 NULL; 626 public static ResourceTypes fromCode(String codeString) throws FHIRException { 627 if (codeString == null || "".equals(codeString)) 628 return null; 629 if ("Account".equals(codeString)) 630 return ACCOUNT; 631 if ("ActivityDefinition".equals(codeString)) 632 return ACTIVITYDEFINITION; 633 if ("AdverseEvent".equals(codeString)) 634 return ADVERSEEVENT; 635 if ("AllergyIntolerance".equals(codeString)) 636 return ALLERGYINTOLERANCE; 637 if ("Appointment".equals(codeString)) 638 return APPOINTMENT; 639 if ("AppointmentResponse".equals(codeString)) 640 return APPOINTMENTRESPONSE; 641 if ("AuditEvent".equals(codeString)) 642 return AUDITEVENT; 643 if ("Basic".equals(codeString)) 644 return BASIC; 645 if ("Binary".equals(codeString)) 646 return BINARY; 647 if ("BiologicallyDerivedProduct".equals(codeString)) 648 return BIOLOGICALLYDERIVEDPRODUCT; 649 if ("BodyStructure".equals(codeString)) 650 return BODYSTRUCTURE; 651 if ("Bundle".equals(codeString)) 652 return BUNDLE; 653 if ("CapabilityStatement".equals(codeString)) 654 return CAPABILITYSTATEMENT; 655 if ("CarePlan".equals(codeString)) 656 return CAREPLAN; 657 if ("CareTeam".equals(codeString)) 658 return CARETEAM; 659 if ("CatalogEntry".equals(codeString)) 660 return CATALOGENTRY; 661 if ("ChargeItem".equals(codeString)) 662 return CHARGEITEM; 663 if ("ChargeItemDefinition".equals(codeString)) 664 return CHARGEITEMDEFINITION; 665 if ("Claim".equals(codeString)) 666 return CLAIM; 667 if ("ClaimResponse".equals(codeString)) 668 return CLAIMRESPONSE; 669 if ("ClinicalImpression".equals(codeString)) 670 return CLINICALIMPRESSION; 671 if ("CodeSystem".equals(codeString)) 672 return CODESYSTEM; 673 if ("Communication".equals(codeString)) 674 return COMMUNICATION; 675 if ("CommunicationRequest".equals(codeString)) 676 return COMMUNICATIONREQUEST; 677 if ("CompartmentDefinition".equals(codeString)) 678 return COMPARTMENTDEFINITION; 679 if ("Composition".equals(codeString)) 680 return COMPOSITION; 681 if ("ConceptMap".equals(codeString)) 682 return CONCEPTMAP; 683 if ("Condition".equals(codeString)) 684 return CONDITION; 685 if ("Consent".equals(codeString)) 686 return CONSENT; 687 if ("Contract".equals(codeString)) 688 return CONTRACT; 689 if ("Coverage".equals(codeString)) 690 return COVERAGE; 691 if ("CoverageEligibilityRequest".equals(codeString)) 692 return COVERAGEELIGIBILITYREQUEST; 693 if ("CoverageEligibilityResponse".equals(codeString)) 694 return COVERAGEELIGIBILITYRESPONSE; 695 if ("DetectedIssue".equals(codeString)) 696 return DETECTEDISSUE; 697 if ("Device".equals(codeString)) 698 return DEVICE; 699 if ("DeviceDefinition".equals(codeString)) 700 return DEVICEDEFINITION; 701 if ("DeviceMetric".equals(codeString)) 702 return DEVICEMETRIC; 703 if ("DeviceRequest".equals(codeString)) 704 return DEVICEREQUEST; 705 if ("DeviceUseStatement".equals(codeString)) 706 return DEVICEUSESTATEMENT; 707 if ("DiagnosticReport".equals(codeString)) 708 return DIAGNOSTICREPORT; 709 if ("DocumentManifest".equals(codeString)) 710 return DOCUMENTMANIFEST; 711 if ("DocumentReference".equals(codeString)) 712 return DOCUMENTREFERENCE; 713 if ("DomainResource".equals(codeString)) 714 return DOMAINRESOURCE; 715 if ("Encounter".equals(codeString)) 716 return ENCOUNTER; 717 if ("Endpoint".equals(codeString)) 718 return ENDPOINT; 719 if ("EnrollmentRequest".equals(codeString)) 720 return ENROLLMENTREQUEST; 721 if ("EnrollmentResponse".equals(codeString)) 722 return ENROLLMENTRESPONSE; 723 if ("EpisodeOfCare".equals(codeString)) 724 return EPISODEOFCARE; 725 if ("EventDefinition".equals(codeString)) 726 return EVENTDEFINITION; 727 if ("ExampleScenario".equals(codeString)) 728 return EXAMPLESCENARIO; 729 if ("ExplanationOfBenefit".equals(codeString)) 730 return EXPLANATIONOFBENEFIT; 731 if ("FamilyMemberHistory".equals(codeString)) 732 return FAMILYMEMBERHISTORY; 733 if ("Flag".equals(codeString)) 734 return FLAG; 735 if ("Goal".equals(codeString)) 736 return GOAL; 737 if ("GraphDefinition".equals(codeString)) 738 return GRAPHDEFINITION; 739 if ("Group".equals(codeString)) 740 return GROUP; 741 if ("GuidanceResponse".equals(codeString)) 742 return GUIDANCERESPONSE; 743 if ("HealthcareService".equals(codeString)) 744 return HEALTHCARESERVICE; 745 if ("ImagingStudy".equals(codeString)) 746 return IMAGINGSTUDY; 747 if ("Immunization".equals(codeString)) 748 return IMMUNIZATION; 749 if ("ImmunizationEvaluation".equals(codeString)) 750 return IMMUNIZATIONEVALUATION; 751 if ("ImmunizationRecommendation".equals(codeString)) 752 return IMMUNIZATIONRECOMMENDATION; 753 if ("ImplementationGuide".equals(codeString)) 754 return IMPLEMENTATIONGUIDE; 755 if ("InsurancePlan".equals(codeString)) 756 return INSURANCEPLAN; 757 if ("Invoice".equals(codeString)) 758 return INVOICE; 759 if ("ItemInstance".equals(codeString)) 760 return ITEMINSTANCE; 761 if ("Library".equals(codeString)) 762 return LIBRARY; 763 if ("Linkage".equals(codeString)) 764 return LINKAGE; 765 if ("List".equals(codeString)) 766 return LIST; 767 if ("Location".equals(codeString)) 768 return LOCATION; 769 if ("Measure".equals(codeString)) 770 return MEASURE; 771 if ("MeasureReport".equals(codeString)) 772 return MEASUREREPORT; 773 if ("Media".equals(codeString)) 774 return MEDIA; 775 if ("Medication".equals(codeString)) 776 return MEDICATION; 777 if ("MedicationAdministration".equals(codeString)) 778 return MEDICATIONADMINISTRATION; 779 if ("MedicationDispense".equals(codeString)) 780 return MEDICATIONDISPENSE; 781 if ("MedicationKnowledge".equals(codeString)) 782 return MEDICATIONKNOWLEDGE; 783 if ("MedicationRequest".equals(codeString)) 784 return MEDICATIONREQUEST; 785 if ("MedicationStatement".equals(codeString)) 786 return MEDICATIONSTATEMENT; 787 if ("MedicinalProduct".equals(codeString)) 788 return MEDICINALPRODUCT; 789 if ("MedicinalProductAuthorization".equals(codeString)) 790 return MEDICINALPRODUCTAUTHORIZATION; 791 if ("MedicinalProductClinicals".equals(codeString)) 792 return MEDICINALPRODUCTCLINICALS; 793 if ("MedicinalProductContraindication".equals(codeString)) 794 return MEDICINALPRODUCTCONTRAINDICATION; 795 if ("MedicinalProductDeviceSpec".equals(codeString)) 796 return MEDICINALPRODUCTDEVICESPEC; 797 if ("MedicinalProductIndication".equals(codeString)) 798 return MEDICINALPRODUCTINDICATION; 799 if ("MedicinalProductIngredient".equals(codeString)) 800 return MEDICINALPRODUCTINGREDIENT; 801 if ("MedicinalProductInteraction".equals(codeString)) 802 return MEDICINALPRODUCTINTERACTION; 803 if ("MedicinalProductManufactured".equals(codeString)) 804 return MEDICINALPRODUCTMANUFACTURED; 805 if ("MedicinalProductPackaged".equals(codeString)) 806 return MEDICINALPRODUCTPACKAGED; 807 if ("MedicinalProductPharmaceutical".equals(codeString)) 808 return MEDICINALPRODUCTPHARMACEUTICAL; 809 if ("MedicinalProductUndesirableEffect".equals(codeString)) 810 return MEDICINALPRODUCTUNDESIRABLEEFFECT; 811 if ("MessageDefinition".equals(codeString)) 812 return MESSAGEDEFINITION; 813 if ("MessageHeader".equals(codeString)) 814 return MESSAGEHEADER; 815 if ("NamingSystem".equals(codeString)) 816 return NAMINGSYSTEM; 817 if ("NutritionOrder".equals(codeString)) 818 return NUTRITIONORDER; 819 if ("Observation".equals(codeString)) 820 return OBSERVATION; 821 if ("ObservationDefinition".equals(codeString)) 822 return OBSERVATIONDEFINITION; 823 if ("OperationDefinition".equals(codeString)) 824 return OPERATIONDEFINITION; 825 if ("OperationOutcome".equals(codeString)) 826 return OPERATIONOUTCOME; 827 if ("Organization".equals(codeString)) 828 return ORGANIZATION; 829 if ("OrganizationAffiliation".equals(codeString)) 830 return ORGANIZATIONAFFILIATION; 831 if ("Parameters".equals(codeString)) 832 return PARAMETERS; 833 if ("Patient".equals(codeString)) 834 return PATIENT; 835 if ("PaymentNotice".equals(codeString)) 836 return PAYMENTNOTICE; 837 if ("PaymentReconciliation".equals(codeString)) 838 return PAYMENTRECONCILIATION; 839 if ("Person".equals(codeString)) 840 return PERSON; 841 if ("PlanDefinition".equals(codeString)) 842 return PLANDEFINITION; 843 if ("Practitioner".equals(codeString)) 844 return PRACTITIONER; 845 if ("PractitionerRole".equals(codeString)) 846 return PRACTITIONERROLE; 847 if ("Procedure".equals(codeString)) 848 return PROCEDURE; 849 if ("ProcessRequest".equals(codeString)) 850 return PROCESSREQUEST; 851 if ("ProcessResponse".equals(codeString)) 852 return PROCESSRESPONSE; 853 if ("Provenance".equals(codeString)) 854 return PROVENANCE; 855 if ("Questionnaire".equals(codeString)) 856 return QUESTIONNAIRE; 857 if ("QuestionnaireResponse".equals(codeString)) 858 return QUESTIONNAIRERESPONSE; 859 if ("RelatedPerson".equals(codeString)) 860 return RELATEDPERSON; 861 if ("RequestGroup".equals(codeString)) 862 return REQUESTGROUP; 863 if ("ResearchStudy".equals(codeString)) 864 return RESEARCHSTUDY; 865 if ("ResearchSubject".equals(codeString)) 866 return RESEARCHSUBJECT; 867 if ("Resource".equals(codeString)) 868 return RESOURCE; 869 if ("RiskAssessment".equals(codeString)) 870 return RISKASSESSMENT; 871 if ("Schedule".equals(codeString)) 872 return SCHEDULE; 873 if ("SearchParameter".equals(codeString)) 874 return SEARCHPARAMETER; 875 if ("Sequence".equals(codeString)) 876 return SEQUENCE; 877 if ("ServiceRequest".equals(codeString)) 878 return SERVICEREQUEST; 879 if ("Slot".equals(codeString)) 880 return SLOT; 881 if ("Specimen".equals(codeString)) 882 return SPECIMEN; 883 if ("SpecimenDefinition".equals(codeString)) 884 return SPECIMENDEFINITION; 885 if ("StructureDefinition".equals(codeString)) 886 return STRUCTUREDEFINITION; 887 if ("StructureMap".equals(codeString)) 888 return STRUCTUREMAP; 889 if ("Subscription".equals(codeString)) 890 return SUBSCRIPTION; 891 if ("Substance".equals(codeString)) 892 return SUBSTANCE; 893 if ("SubstancePolymer".equals(codeString)) 894 return SUBSTANCEPOLYMER; 895 if ("SubstanceReferenceInformation".equals(codeString)) 896 return SUBSTANCEREFERENCEINFORMATION; 897 if ("SubstanceSpecification".equals(codeString)) 898 return SUBSTANCESPECIFICATION; 899 if ("SupplyDelivery".equals(codeString)) 900 return SUPPLYDELIVERY; 901 if ("SupplyRequest".equals(codeString)) 902 return SUPPLYREQUEST; 903 if ("Task".equals(codeString)) 904 return TASK; 905 if ("TerminologyCapabilities".equals(codeString)) 906 return TERMINOLOGYCAPABILITIES; 907 if ("TestReport".equals(codeString)) 908 return TESTREPORT; 909 if ("TestScript".equals(codeString)) 910 return TESTSCRIPT; 911 if ("UserSession".equals(codeString)) 912 return USERSESSION; 913 if ("ValueSet".equals(codeString)) 914 return VALUESET; 915 if ("VerificationResult".equals(codeString)) 916 return VERIFICATIONRESULT; 917 if ("VisionPrescription".equals(codeString)) 918 return VISIONPRESCRIPTION; 919 throw new FHIRException("Unknown ResourceTypes code '"+codeString+"'"); 920 } 921 public String toCode() { 922 switch (this) { 923 case ACCOUNT: return "Account"; 924 case ACTIVITYDEFINITION: return "ActivityDefinition"; 925 case ADVERSEEVENT: return "AdverseEvent"; 926 case ALLERGYINTOLERANCE: return "AllergyIntolerance"; 927 case APPOINTMENT: return "Appointment"; 928 case APPOINTMENTRESPONSE: return "AppointmentResponse"; 929 case AUDITEVENT: return "AuditEvent"; 930 case BASIC: return "Basic"; 931 case BINARY: return "Binary"; 932 case BIOLOGICALLYDERIVEDPRODUCT: return "BiologicallyDerivedProduct"; 933 case BODYSTRUCTURE: return "BodyStructure"; 934 case BUNDLE: return "Bundle"; 935 case CAPABILITYSTATEMENT: return "CapabilityStatement"; 936 case CAREPLAN: return "CarePlan"; 937 case CARETEAM: return "CareTeam"; 938 case CATALOGENTRY: return "CatalogEntry"; 939 case CHARGEITEM: return "ChargeItem"; 940 case CHARGEITEMDEFINITION: return "ChargeItemDefinition"; 941 case CLAIM: return "Claim"; 942 case CLAIMRESPONSE: return "ClaimResponse"; 943 case CLINICALIMPRESSION: return "ClinicalImpression"; 944 case CODESYSTEM: return "CodeSystem"; 945 case COMMUNICATION: return "Communication"; 946 case COMMUNICATIONREQUEST: return "CommunicationRequest"; 947 case COMPARTMENTDEFINITION: return "CompartmentDefinition"; 948 case COMPOSITION: return "Composition"; 949 case CONCEPTMAP: return "ConceptMap"; 950 case CONDITION: return "Condition"; 951 case CONSENT: return "Consent"; 952 case CONTRACT: return "Contract"; 953 case COVERAGE: return "Coverage"; 954 case COVERAGEELIGIBILITYREQUEST: return "CoverageEligibilityRequest"; 955 case COVERAGEELIGIBILITYRESPONSE: return "CoverageEligibilityResponse"; 956 case DETECTEDISSUE: return "DetectedIssue"; 957 case DEVICE: return "Device"; 958 case DEVICEDEFINITION: return "DeviceDefinition"; 959 case DEVICEMETRIC: return "DeviceMetric"; 960 case DEVICEREQUEST: return "DeviceRequest"; 961 case DEVICEUSESTATEMENT: return "DeviceUseStatement"; 962 case DIAGNOSTICREPORT: return "DiagnosticReport"; 963 case DOCUMENTMANIFEST: return "DocumentManifest"; 964 case DOCUMENTREFERENCE: return "DocumentReference"; 965 case DOMAINRESOURCE: return "DomainResource"; 966 case ENCOUNTER: return "Encounter"; 967 case ENDPOINT: return "Endpoint"; 968 case ENROLLMENTREQUEST: return "EnrollmentRequest"; 969 case ENROLLMENTRESPONSE: return "EnrollmentResponse"; 970 case EPISODEOFCARE: return "EpisodeOfCare"; 971 case EVENTDEFINITION: return "EventDefinition"; 972 case EXAMPLESCENARIO: return "ExampleScenario"; 973 case EXPLANATIONOFBENEFIT: return "ExplanationOfBenefit"; 974 case FAMILYMEMBERHISTORY: return "FamilyMemberHistory"; 975 case FLAG: return "Flag"; 976 case GOAL: return "Goal"; 977 case GRAPHDEFINITION: return "GraphDefinition"; 978 case GROUP: return "Group"; 979 case GUIDANCERESPONSE: return "GuidanceResponse"; 980 case HEALTHCARESERVICE: return "HealthcareService"; 981 case IMAGINGSTUDY: return "ImagingStudy"; 982 case IMMUNIZATION: return "Immunization"; 983 case IMMUNIZATIONEVALUATION: return "ImmunizationEvaluation"; 984 case IMMUNIZATIONRECOMMENDATION: return "ImmunizationRecommendation"; 985 case IMPLEMENTATIONGUIDE: return "ImplementationGuide"; 986 case INSURANCEPLAN: return "InsurancePlan"; 987 case INVOICE: return "Invoice"; 988 case ITEMINSTANCE: return "ItemInstance"; 989 case LIBRARY: return "Library"; 990 case LINKAGE: return "Linkage"; 991 case LIST: return "List"; 992 case LOCATION: return "Location"; 993 case MEASURE: return "Measure"; 994 case MEASUREREPORT: return "MeasureReport"; 995 case MEDIA: return "Media"; 996 case MEDICATION: return "Medication"; 997 case MEDICATIONADMINISTRATION: return "MedicationAdministration"; 998 case MEDICATIONDISPENSE: return "MedicationDispense"; 999 case MEDICATIONKNOWLEDGE: return "MedicationKnowledge"; 1000 case MEDICATIONREQUEST: return "MedicationRequest"; 1001 case MEDICATIONSTATEMENT: return "MedicationStatement"; 1002 case MEDICINALPRODUCT: return "MedicinalProduct"; 1003 case MEDICINALPRODUCTAUTHORIZATION: return "MedicinalProductAuthorization"; 1004 case MEDICINALPRODUCTCLINICALS: return "MedicinalProductClinicals"; 1005 case MEDICINALPRODUCTCONTRAINDICATION: return "MedicinalProductContraindication"; 1006 case MEDICINALPRODUCTDEVICESPEC: return "MedicinalProductDeviceSpec"; 1007 case MEDICINALPRODUCTINDICATION: return "MedicinalProductIndication"; 1008 case MEDICINALPRODUCTINGREDIENT: return "MedicinalProductIngredient"; 1009 case MEDICINALPRODUCTINTERACTION: return "MedicinalProductInteraction"; 1010 case MEDICINALPRODUCTMANUFACTURED: return "MedicinalProductManufactured"; 1011 case MEDICINALPRODUCTPACKAGED: return "MedicinalProductPackaged"; 1012 case MEDICINALPRODUCTPHARMACEUTICAL: return "MedicinalProductPharmaceutical"; 1013 case MEDICINALPRODUCTUNDESIRABLEEFFECT: return "MedicinalProductUndesirableEffect"; 1014 case MESSAGEDEFINITION: return "MessageDefinition"; 1015 case MESSAGEHEADER: return "MessageHeader"; 1016 case NAMINGSYSTEM: return "NamingSystem"; 1017 case NUTRITIONORDER: return "NutritionOrder"; 1018 case OBSERVATION: return "Observation"; 1019 case OBSERVATIONDEFINITION: return "ObservationDefinition"; 1020 case OPERATIONDEFINITION: return "OperationDefinition"; 1021 case OPERATIONOUTCOME: return "OperationOutcome"; 1022 case ORGANIZATION: return "Organization"; 1023 case ORGANIZATIONAFFILIATION: return "OrganizationAffiliation"; 1024 case PARAMETERS: return "Parameters"; 1025 case PATIENT: return "Patient"; 1026 case PAYMENTNOTICE: return "PaymentNotice"; 1027 case PAYMENTRECONCILIATION: return "PaymentReconciliation"; 1028 case PERSON: return "Person"; 1029 case PLANDEFINITION: return "PlanDefinition"; 1030 case PRACTITIONER: return "Practitioner"; 1031 case PRACTITIONERROLE: return "PractitionerRole"; 1032 case PROCEDURE: return "Procedure"; 1033 case PROCESSREQUEST: return "ProcessRequest"; 1034 case PROCESSRESPONSE: return "ProcessResponse"; 1035 case PROVENANCE: return "Provenance"; 1036 case QUESTIONNAIRE: return "Questionnaire"; 1037 case QUESTIONNAIRERESPONSE: return "QuestionnaireResponse"; 1038 case RELATEDPERSON: return "RelatedPerson"; 1039 case REQUESTGROUP: return "RequestGroup"; 1040 case RESEARCHSTUDY: return "ResearchStudy"; 1041 case RESEARCHSUBJECT: return "ResearchSubject"; 1042 case RESOURCE: return "Resource"; 1043 case RISKASSESSMENT: return "RiskAssessment"; 1044 case SCHEDULE: return "Schedule"; 1045 case SEARCHPARAMETER: return "SearchParameter"; 1046 case SEQUENCE: return "Sequence"; 1047 case SERVICEREQUEST: return "ServiceRequest"; 1048 case SLOT: return "Slot"; 1049 case SPECIMEN: return "Specimen"; 1050 case SPECIMENDEFINITION: return "SpecimenDefinition"; 1051 case STRUCTUREDEFINITION: return "StructureDefinition"; 1052 case STRUCTUREMAP: return "StructureMap"; 1053 case SUBSCRIPTION: return "Subscription"; 1054 case SUBSTANCE: return "Substance"; 1055 case SUBSTANCEPOLYMER: return "SubstancePolymer"; 1056 case SUBSTANCEREFERENCEINFORMATION: return "SubstanceReferenceInformation"; 1057 case SUBSTANCESPECIFICATION: return "SubstanceSpecification"; 1058 case SUPPLYDELIVERY: return "SupplyDelivery"; 1059 case SUPPLYREQUEST: return "SupplyRequest"; 1060 case TASK: return "Task"; 1061 case TERMINOLOGYCAPABILITIES: return "TerminologyCapabilities"; 1062 case TESTREPORT: return "TestReport"; 1063 case TESTSCRIPT: return "TestScript"; 1064 case USERSESSION: return "UserSession"; 1065 case VALUESET: return "ValueSet"; 1066 case VERIFICATIONRESULT: return "VerificationResult"; 1067 case VISIONPRESCRIPTION: return "VisionPrescription"; 1068 default: return "?"; 1069 } 1070 } 1071 public String getSystem() { 1072 return "http://hl7.org/fhir/resource-types"; 1073 } 1074 public String getDefinition() { 1075 switch (this) { 1076 case ACCOUNT: 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."; 1077 case ACTIVITYDEFINITION: return "This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context."; 1078 case ADVERSEEVENT: 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."; 1079 case ALLERGYINTOLERANCE: return "Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance."; 1080 case APPOINTMENT: 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)."; 1081 case APPOINTMENTRESPONSE: return "A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection."; 1082 case AUDITEVENT: 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."; 1083 case BASIC: 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."; 1084 case BINARY: 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."; 1085 case BIOLOGICALLYDERIVEDPRODUCT: return "A material substance originating from a biological entity intended to be transplanted or infused\ninto another (possibly the same) biological entity."; 1086 case BODYSTRUCTURE: 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."; 1087 case BUNDLE: return "A container for a collection of resources."; 1088 case CAPABILITYSTATEMENT: return "A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation."; 1089 case CAREPLAN: 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."; 1090 case CARETEAM: return "The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient."; 1091 case CATALOGENTRY: return "Catalog entries are wrappers that contextualize items included in a catalog."; 1092 case CHARGEITEM: 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."; 1093 case CHARGEITEMDEFINITION: 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."; 1094 case CLAIM: return "A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery."; 1095 case CLAIMRESPONSE: return "This resource provides the adjudication details from the processing of a Claim resource."; 1096 case CLINICALIMPRESSION: 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."; 1097 case CODESYSTEM: 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."; 1098 case COMMUNICATION: return "An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency was notified about a reportable condition."; 1099 case COMMUNICATIONREQUEST: 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."; 1100 case COMPARTMENTDEFINITION: return "A compartment definition that defines how resources are accessed on a server."; 1101 case COMPOSITION: 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.)."; 1102 case CONCEPTMAP: 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."; 1103 case CONDITION: return "A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern."; 1104 case CONSENT: 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."; 1105 case CONTRACT: return "Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement."; 1106 case COVERAGE: return "Financial instrument which may be used to reimburse or pay for health care products and services."; 1107 case COVERAGEELIGIBILITYREQUEST: 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."; 1108 case COVERAGEELIGIBILITYRESPONSE: return "This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource."; 1109 case DETECTEDISSUE: 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."; 1110 case DEVICE: return "This resource identifies 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. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc. This is the catalog description of a device (not the specific instance)."; 1111 case DEVICEDEFINITION: return "The characteristics, operational status and capabilities of a medical-related component of a medical device."; 1112 case DEVICEMETRIC: return "Describes a measurement, calculation or setting capability of a medical device."; 1113 case DEVICEREQUEST: 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."; 1114 case DEVICEUSESTATEMENT: 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."; 1115 case DIAGNOSTICREPORT: 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."; 1116 case DOCUMENTMANIFEST: return "A collection of documents compiled for a purpose together with metadata that applies to the collection."; 1117 case DOCUMENTREFERENCE: return "A reference to a document."; 1118 case DOMAINRESOURCE: return "A resource that includes narrative, extensions, and contained resources."; 1119 case ENCOUNTER: 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."; 1120 case ENDPOINT: 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."; 1121 case ENROLLMENTREQUEST: return "This resource provides the insurance enrollment details to the insurer regarding a specified coverage."; 1122 case ENROLLMENTRESPONSE: return "This resource provides enrollment and plan details from the processing of an Enrollment resource."; 1123 case EPISODEOFCARE: 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."; 1124 case EVENTDEFINITION: return "The EventDefinition resource provides a reusable description of when a particular event can occur."; 1125 case EXAMPLESCENARIO: return "Example of workflow instance."; 1126 case EXPLANATIONOFBENEFIT: 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."; 1127 case FAMILYMEMBERHISTORY: return "Significant health conditions for a person related to the patient relevant in the context of care for the patient."; 1128 case FLAG: return "Prospective warnings of potential issues when providing care to the patient."; 1129 case GOAL: 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."; 1130 case GRAPHDEFINITION: 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."; 1131 case GROUP: 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."; 1132 case GUIDANCERESPONSE: 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."; 1133 case HEALTHCARESERVICE: return "The details of a healthcare service available at a location."; 1134 case IMAGINGSTUDY: 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."; 1135 case IMMUNIZATION: 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."; 1136 case IMMUNIZATIONEVALUATION: return "Describes a comparison of an immunization event against published recommendations to determine if the administration is \"valid\" in relation to those recommendations."; 1137 case IMMUNIZATIONRECOMMENDATION: return "A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification."; 1138 case IMPLEMENTATIONGUIDE: return "A set of rules of how FHIR is used to solve a particular problem. 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."; 1139 case INSURANCEPLAN: return "Details of a Health Insurance product/plan provided by an organization."; 1140 case INVOICE: return "Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose."; 1141 case ITEMINSTANCE: return "A physical, countable instance of an item, for example one box or one unit."; 1142 case LIBRARY: 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."; 1143 case LINKAGE: return "Identifies two or more records (resource instances) that are referring to the same real-world \"occurrence\"."; 1144 case LIST: return "A set of information summarized from a list of other resources."; 1145 case LOCATION: return "Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated."; 1146 case MEASURE: return "The Measure resource provides the definition of a quality measure."; 1147 case MEASUREREPORT: return "The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation."; 1148 case MEDIA: return "A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference."; 1149 case MEDICATION: 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."; 1150 case MEDICATIONADMINISTRATION: 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."; 1151 case MEDICATIONDISPENSE: 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."; 1152 case MEDICATIONKNOWLEDGE: return "Information about a medication that is used to support knowledge."; 1153 case MEDICATIONREQUEST: 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."; 1154 case MEDICATIONSTATEMENT: 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. \r\rThe 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."; 1155 case MEDICINALPRODUCT: return "Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use)."; 1156 case MEDICINALPRODUCTAUTHORIZATION: return "The regulatory authorization of a medicinal product."; 1157 case MEDICINALPRODUCTCLINICALS: return "The clinical particulars - indications, contraindications etc. of a medicinal product, including for regulatory purposes."; 1158 case MEDICINALPRODUCTCONTRAINDICATION: return "The clinical particulars - indications, contraindications etc. of a medicinal product, including for regulatory purposes."; 1159 case MEDICINALPRODUCTDEVICESPEC: return "A detailed description of a device, typically as part of a regulated medicinal product. It is not intended to replace the Device resource, which covers use of device instances."; 1160 case MEDICINALPRODUCTINDICATION: return "Indication for the Medicinal Product."; 1161 case MEDICINALPRODUCTINGREDIENT: return "An ingredient of a manufactured item or pharmaceutical product."; 1162 case MEDICINALPRODUCTINTERACTION: return "The interactions of the medicinal product with other medicinal products, or other forms of interactions."; 1163 case MEDICINALPRODUCTMANUFACTURED: return "The manufactured item as contained in the packaged medicinal product."; 1164 case MEDICINALPRODUCTPACKAGED: return "A medicinal product in a container or package."; 1165 case MEDICINALPRODUCTPHARMACEUTICAL: return "A pharmaceutical product described in terms of its composition and dose form."; 1166 case MEDICINALPRODUCTUNDESIRABLEEFFECT: return "Describe the undesirable effects of the medicinal product."; 1167 case MESSAGEDEFINITION: 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."; 1168 case MESSAGEHEADER: 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."; 1169 case NAMINGSYSTEM: 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."; 1170 case NUTRITIONORDER: return "A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident."; 1171 case OBSERVATION: return "Measurements and simple assertions made about a patient, device or other subject."; 1172 case OBSERVATIONDEFINITION: return "Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service."; 1173 case OPERATIONDEFINITION: return "A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction)."; 1174 case OPERATIONOUTCOME: return "A collection of error, warning or information messages that result from a system action."; 1175 case ORGANIZATION: 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."; 1176 case ORGANIZATIONAFFILIATION: return "Defines an affiliation/assotiation/relationship between 2 distinct oganizations, that is not a part-of relationship/sub-division relationship."; 1177 case PARAMETERS: return "This special resource type is used to represent an operation request and response (operations.html). It has no other use, and there is no RESTful endpoint associated with it."; 1178 case PATIENT: return "Demographics and other administrative information about an individual or animal receiving care or other health-related services."; 1179 case PAYMENTNOTICE: return "This resource provides the status of the payment for goods and services rendered, and the request and response resource references."; 1180 case PAYMENTRECONCILIATION: return "This resource provides payment details and claim references supporting a bulk payment."; 1181 case PERSON: return "Demographics and administrative information about a person independent of a specific health-related context."; 1182 case PLANDEFINITION: 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."; 1183 case PRACTITIONER: return "A person who is directly or indirectly involved in the provisioning of healthcare."; 1184 case PRACTITIONERROLE: return "A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time."; 1185 case PROCEDURE: 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."; 1186 case PROCESSREQUEST: return "This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources."; 1187 case PROCESSRESPONSE: return "This resource provides processing status, errors and notes from the processing of a resource."; 1188 case PROVENANCE: 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."; 1189 case QUESTIONNAIRE: 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."; 1190 case QUESTIONNAIRERESPONSE: 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."; 1191 case RELATEDPERSON: 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."; 1192 case REQUESTGROUP: 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\"."; 1193 case RESEARCHSTUDY: 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."; 1194 case RESEARCHSUBJECT: return "A physical entity which is the primary unit of operational and/or administrative interest in a study."; 1195 case RESOURCE: return "This is the base resource type for everything."; 1196 case RISKASSESSMENT: return "An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome."; 1197 case SCHEDULE: return "A container for slots of time that may be available for booking appointments."; 1198 case SEARCHPARAMETER: return "A search parameter that defines a named search item that can be used to search/filter on a resource."; 1199 case SEQUENCE: return "Raw data describing a biological sequence."; 1200 case SERVICEREQUEST: return "A record of a request for service such as diagnostic investigations, treatments, or operations to be performed."; 1201 case SLOT: return "A slot of time on a schedule that may be available for booking appointments."; 1202 case SPECIMEN: return "A sample to be used for analysis."; 1203 case SPECIMENDEFINITION: return "A kind of specimen with associated set of requirements."; 1204 case STRUCTUREDEFINITION: 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."; 1205 case STRUCTUREMAP: return "A Map of relationships between 2 structures that can be used to transform data."; 1206 case SUBSCRIPTION: 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."; 1207 case SUBSTANCE: return "A homogeneous material with a definite composition."; 1208 case SUBSTANCEPOLYMER: return "Todo."; 1209 case SUBSTANCEREFERENCEINFORMATION: return "Todo."; 1210 case SUBSTANCESPECIFICATION: return "The detailed description of a substance, typically at a level beyond what is used for prescribing."; 1211 case SUPPLYDELIVERY: return "Record of delivery of what is supplied."; 1212 case SUPPLYREQUEST: return "A record of a request for a medication, substance or device used in the healthcare setting."; 1213 case TASK: return "A task to be performed."; 1214 case TERMINOLOGYCAPABILITIES: return "A Terminology Capabilities documents a set of capabilities (behaviors) of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation."; 1215 case TESTREPORT: return "A summary of information based on the results of executing a TestScript."; 1216 case TESTSCRIPT: return "A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification."; 1217 case USERSESSION: return "Information about a user's current session."; 1218 case VALUESET: return "A ValueSet resource instances 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)."; 1219 case VERIFICATIONRESULT: return "Describes validation requirements, source(s), status and dates for one or more elements."; 1220 case VISIONPRESCRIPTION: return "An authorization for the supply of glasses and/or contact lenses to a patient."; 1221 default: return "?"; 1222 } 1223 } 1224 public String getDisplay() { 1225 switch (this) { 1226 case ACCOUNT: return "Account"; 1227 case ACTIVITYDEFINITION: return "ActivityDefinition"; 1228 case ADVERSEEVENT: return "AdverseEvent"; 1229 case ALLERGYINTOLERANCE: return "AllergyIntolerance"; 1230 case APPOINTMENT: return "Appointment"; 1231 case APPOINTMENTRESPONSE: return "AppointmentResponse"; 1232 case AUDITEVENT: return "AuditEvent"; 1233 case BASIC: return "Basic"; 1234 case BINARY: return "Binary"; 1235 case BIOLOGICALLYDERIVEDPRODUCT: return "BiologicallyDerivedProduct"; 1236 case BODYSTRUCTURE: return "BodyStructure"; 1237 case BUNDLE: return "Bundle"; 1238 case CAPABILITYSTATEMENT: return "CapabilityStatement"; 1239 case CAREPLAN: return "CarePlan"; 1240 case CARETEAM: return "CareTeam"; 1241 case CATALOGENTRY: return "CatalogEntry"; 1242 case CHARGEITEM: return "ChargeItem"; 1243 case CHARGEITEMDEFINITION: return "ChargeItemDefinition"; 1244 case CLAIM: return "Claim"; 1245 case CLAIMRESPONSE: return "ClaimResponse"; 1246 case CLINICALIMPRESSION: return "ClinicalImpression"; 1247 case CODESYSTEM: return "CodeSystem"; 1248 case COMMUNICATION: return "Communication"; 1249 case COMMUNICATIONREQUEST: return "CommunicationRequest"; 1250 case COMPARTMENTDEFINITION: return "CompartmentDefinition"; 1251 case COMPOSITION: return "Composition"; 1252 case CONCEPTMAP: return "ConceptMap"; 1253 case CONDITION: return "Condition"; 1254 case CONSENT: return "Consent"; 1255 case CONTRACT: return "Contract"; 1256 case COVERAGE: return "Coverage"; 1257 case COVERAGEELIGIBILITYREQUEST: return "CoverageEligibilityRequest"; 1258 case COVERAGEELIGIBILITYRESPONSE: return "CoverageEligibilityResponse"; 1259 case DETECTEDISSUE: return "DetectedIssue"; 1260 case DEVICE: return "Device"; 1261 case DEVICEDEFINITION: return "DeviceDefinition"; 1262 case DEVICEMETRIC: return "DeviceMetric"; 1263 case DEVICEREQUEST: return "DeviceRequest"; 1264 case DEVICEUSESTATEMENT: return "DeviceUseStatement"; 1265 case DIAGNOSTICREPORT: return "DiagnosticReport"; 1266 case DOCUMENTMANIFEST: return "DocumentManifest"; 1267 case DOCUMENTREFERENCE: return "DocumentReference"; 1268 case DOMAINRESOURCE: return "DomainResource"; 1269 case ENCOUNTER: return "Encounter"; 1270 case ENDPOINT: return "Endpoint"; 1271 case ENROLLMENTREQUEST: return "EnrollmentRequest"; 1272 case ENROLLMENTRESPONSE: return "EnrollmentResponse"; 1273 case EPISODEOFCARE: return "EpisodeOfCare"; 1274 case EVENTDEFINITION: return "EventDefinition"; 1275 case EXAMPLESCENARIO: return "ExampleScenario"; 1276 case EXPLANATIONOFBENEFIT: return "ExplanationOfBenefit"; 1277 case FAMILYMEMBERHISTORY: return "FamilyMemberHistory"; 1278 case FLAG: return "Flag"; 1279 case GOAL: return "Goal"; 1280 case GRAPHDEFINITION: return "GraphDefinition"; 1281 case GROUP: return "Group"; 1282 case GUIDANCERESPONSE: return "GuidanceResponse"; 1283 case HEALTHCARESERVICE: return "HealthcareService"; 1284 case IMAGINGSTUDY: return "ImagingStudy"; 1285 case IMMUNIZATION: return "Immunization"; 1286 case IMMUNIZATIONEVALUATION: return "ImmunizationEvaluation"; 1287 case IMMUNIZATIONRECOMMENDATION: return "ImmunizationRecommendation"; 1288 case IMPLEMENTATIONGUIDE: return "ImplementationGuide"; 1289 case INSURANCEPLAN: return "InsurancePlan"; 1290 case INVOICE: return "Invoice"; 1291 case ITEMINSTANCE: return "ItemInstance"; 1292 case LIBRARY: return "Library"; 1293 case LINKAGE: return "Linkage"; 1294 case LIST: return "List"; 1295 case LOCATION: return "Location"; 1296 case MEASURE: return "Measure"; 1297 case MEASUREREPORT: return "MeasureReport"; 1298 case MEDIA: return "Media"; 1299 case MEDICATION: return "Medication"; 1300 case MEDICATIONADMINISTRATION: return "MedicationAdministration"; 1301 case MEDICATIONDISPENSE: return "MedicationDispense"; 1302 case MEDICATIONKNOWLEDGE: return "MedicationKnowledge"; 1303 case MEDICATIONREQUEST: return "MedicationRequest"; 1304 case MEDICATIONSTATEMENT: return "MedicationStatement"; 1305 case MEDICINALPRODUCT: return "MedicinalProduct"; 1306 case MEDICINALPRODUCTAUTHORIZATION: return "MedicinalProductAuthorization"; 1307 case MEDICINALPRODUCTCLINICALS: return "MedicinalProductClinicals"; 1308 case MEDICINALPRODUCTCONTRAINDICATION: return "MedicinalProductContraindication"; 1309 case MEDICINALPRODUCTDEVICESPEC: return "MedicinalProductDeviceSpec"; 1310 case MEDICINALPRODUCTINDICATION: return "MedicinalProductIndication"; 1311 case MEDICINALPRODUCTINGREDIENT: return "MedicinalProductIngredient"; 1312 case MEDICINALPRODUCTINTERACTION: return "MedicinalProductInteraction"; 1313 case MEDICINALPRODUCTMANUFACTURED: return "MedicinalProductManufactured"; 1314 case MEDICINALPRODUCTPACKAGED: return "MedicinalProductPackaged"; 1315 case MEDICINALPRODUCTPHARMACEUTICAL: return "MedicinalProductPharmaceutical"; 1316 case MEDICINALPRODUCTUNDESIRABLEEFFECT: return "MedicinalProductUndesirableEffect"; 1317 case MESSAGEDEFINITION: return "MessageDefinition"; 1318 case MESSAGEHEADER: return "MessageHeader"; 1319 case NAMINGSYSTEM: return "NamingSystem"; 1320 case NUTRITIONORDER: return "NutritionOrder"; 1321 case OBSERVATION: return "Observation"; 1322 case OBSERVATIONDEFINITION: return "ObservationDefinition"; 1323 case OPERATIONDEFINITION: return "OperationDefinition"; 1324 case OPERATIONOUTCOME: return "OperationOutcome"; 1325 case ORGANIZATION: return "Organization"; 1326 case ORGANIZATIONAFFILIATION: return "OrganizationAffiliation"; 1327 case PARAMETERS: return "Parameters"; 1328 case PATIENT: return "Patient"; 1329 case PAYMENTNOTICE: return "PaymentNotice"; 1330 case PAYMENTRECONCILIATION: return "PaymentReconciliation"; 1331 case PERSON: return "Person"; 1332 case PLANDEFINITION: return "PlanDefinition"; 1333 case PRACTITIONER: return "Practitioner"; 1334 case PRACTITIONERROLE: return "PractitionerRole"; 1335 case PROCEDURE: return "Procedure"; 1336 case PROCESSREQUEST: return "ProcessRequest"; 1337 case PROCESSRESPONSE: return "ProcessResponse"; 1338 case PROVENANCE: return "Provenance"; 1339 case QUESTIONNAIRE: return "Questionnaire"; 1340 case QUESTIONNAIRERESPONSE: return "QuestionnaireResponse"; 1341 case RELATEDPERSON: return "RelatedPerson"; 1342 case REQUESTGROUP: return "RequestGroup"; 1343 case RESEARCHSTUDY: return "ResearchStudy"; 1344 case RESEARCHSUBJECT: return "ResearchSubject"; 1345 case RESOURCE: return "Resource"; 1346 case RISKASSESSMENT: return "RiskAssessment"; 1347 case SCHEDULE: return "Schedule"; 1348 case SEARCHPARAMETER: return "SearchParameter"; 1349 case SEQUENCE: return "Sequence"; 1350 case SERVICEREQUEST: return "ServiceRequest"; 1351 case SLOT: return "Slot"; 1352 case SPECIMEN: return "Specimen"; 1353 case SPECIMENDEFINITION: return "SpecimenDefinition"; 1354 case STRUCTUREDEFINITION: return "StructureDefinition"; 1355 case STRUCTUREMAP: return "StructureMap"; 1356 case SUBSCRIPTION: return "Subscription"; 1357 case SUBSTANCE: return "Substance"; 1358 case SUBSTANCEPOLYMER: return "SubstancePolymer"; 1359 case SUBSTANCEREFERENCEINFORMATION: return "SubstanceReferenceInformation"; 1360 case SUBSTANCESPECIFICATION: return "SubstanceSpecification"; 1361 case SUPPLYDELIVERY: return "SupplyDelivery"; 1362 case SUPPLYREQUEST: return "SupplyRequest"; 1363 case TASK: return "Task"; 1364 case TERMINOLOGYCAPABILITIES: return "TerminologyCapabilities"; 1365 case TESTREPORT: return "TestReport"; 1366 case TESTSCRIPT: return "TestScript"; 1367 case USERSESSION: return "UserSession"; 1368 case VALUESET: return "ValueSet"; 1369 case VERIFICATIONRESULT: return "VerificationResult"; 1370 case VISIONPRESCRIPTION: return "VisionPrescription"; 1371 default: return "?"; 1372 } 1373 } 1374 1375 1376} 1377