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