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