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