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