001package org.hl7.fhir.dstu3.model.codesystems; 002 003/*- 004 * #%L 005 * org.hl7.fhir.dstu3 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 Sat, Mar 25, 2017 21:03-0400 for FHIR v3.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 binary resource can contain any content, whether text, image, pdf, zip archive, etc. 094 */ 095 BINARY, 096 /** 097 * Record details about the anatomical location of a specimen or body part. This resource may be used when a coded concept does not provide the necessary detail needed for the use case. 098 */ 099 BODYSITE, 100 /** 101 * A container for a collection of resources. 102 */ 103 BUNDLE, 104 /** 105 * 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. 106 */ 107 CAPABILITYSTATEMENT, 108 /** 109 * 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. 110 */ 111 CAREPLAN, 112 /** 113 * The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. 114 */ 115 CARETEAM, 116 /** 117 * 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. 118 */ 119 CHARGEITEM, 120 /** 121 * 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. 122 */ 123 CLAIM, 124 /** 125 * This resource provides the adjudication details from the processing of a Claim resource. 126 */ 127 CLAIMRESPONSE, 128 /** 129 * 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. 130 */ 131 CLINICALIMPRESSION, 132 /** 133 * A code system resource specifies a set of codes drawn from one or more code systems. 134 */ 135 CODESYSTEM, 136 /** 137 * 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. 138 */ 139 COMMUNICATION, 140 /** 141 * 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. 142 */ 143 COMMUNICATIONREQUEST, 144 /** 145 * A compartment definition that defines how resources are accessed on a server. 146 */ 147 COMPARTMENTDEFINITION, 148 /** 149 * A set of healthcare-related information that is assembled together into a single logical document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. 150 */ 151 COMPOSITION, 152 /** 153 * 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. 154 */ 155 CONCEPTMAP, 156 /** 157 * A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. 158 */ 159 CONDITION, 160 /** 161 * A record of a healthcare consumer’s policy 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. 162 */ 163 CONSENT, 164 /** 165 * A formal agreement between parties regarding the conduct of business, exchange of information or other matters. 166 */ 167 CONTRACT, 168 /** 169 * Financial instrument which may be used to reimburse or pay for health care products and services. 170 */ 171 COVERAGE, 172 /** 173 * The formal description of a single piece of information that can be gathered and reported. 174 */ 175 DATAELEMENT, 176 /** 177 * 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. 178 */ 179 DETECTEDISSUE, 180 /** 181 * 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. 182 */ 183 DEVICE, 184 /** 185 * The characteristics, operational status and capabilities of a medical-related component of a medical device. 186 */ 187 DEVICECOMPONENT, 188 /** 189 * Describes a measurement, calculation or setting capability of a medical device. 190 */ 191 DEVICEMETRIC, 192 /** 193 * 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. 194 */ 195 DEVICEREQUEST, 196 /** 197 * 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. 198 */ 199 DEVICEUSESTATEMENT, 200 /** 201 * 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. 202 */ 203 DIAGNOSTICREPORT, 204 /** 205 * A collection of documents compiled for a purpose together with metadata that applies to the collection. 206 */ 207 DOCUMENTMANIFEST, 208 /** 209 * A reference to a document. 210 */ 211 DOCUMENTREFERENCE, 212 /** 213 * A resource that includes narrative, extensions, and contained resources. 214 */ 215 DOMAINRESOURCE, 216 /** 217 * 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. 218 */ 219 ELIGIBILITYREQUEST, 220 /** 221 * This resource provides eligibility and plan details from the processing of an Eligibility resource. 222 */ 223 ELIGIBILITYRESPONSE, 224 /** 225 * 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. 226 */ 227 ENCOUNTER, 228 /** 229 * 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. 230 */ 231 ENDPOINT, 232 /** 233 * This resource provides the insurance enrollment details to the insurer regarding a specified coverage. 234 */ 235 ENROLLMENTREQUEST, 236 /** 237 * This resource provides enrollment and plan details from the processing of an Enrollment resource. 238 */ 239 ENROLLMENTRESPONSE, 240 /** 241 * 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. 242 */ 243 EPISODEOFCARE, 244 /** 245 * Resource to define constraints on the Expansion of a FHIR ValueSet. 246 */ 247 EXPANSIONPROFILE, 248 /** 249 * 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. 250 */ 251 EXPLANATIONOFBENEFIT, 252 /** 253 * Significant health events and conditions for a person related to the patient relevant in the context of care for the patient. 254 */ 255 FAMILYMEMBERHISTORY, 256 /** 257 * Prospective warnings of potential issues when providing care to the patient. 258 */ 259 FLAG, 260 /** 261 * 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. 262 */ 263 GOAL, 264 /** 265 * 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. 266 */ 267 GRAPHDEFINITION, 268 /** 269 * 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. 270 */ 271 GROUP, 272 /** 273 * 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. 274 */ 275 GUIDANCERESPONSE, 276 /** 277 * The details of a healthcare service available at a location. 278 */ 279 HEALTHCARESERVICE, 280 /** 281 * A text description of the DICOM SOP instances selected in the ImagingManifest; or the reason for, or significance of, the selection. 282 */ 283 IMAGINGMANIFEST, 284 /** 285 * Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities. 286 */ 287 IMAGINGSTUDY, 288 /** 289 * Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed. 290 */ 291 IMMUNIZATION, 292 /** 293 * A patient's point-in-time immunization and recommendation (i.e. forecasting a patient's immunization eligibility according to a published schedule) with optional supporting justification. 294 */ 295 IMMUNIZATIONRECOMMENDATION, 296 /** 297 * 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. 298 */ 299 IMPLEMENTATIONGUIDE, 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 evaluating a measure. 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. It covers the ingredients and the packaging for a medication. 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 * 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. 342 */ 343 MEDICATIONREQUEST, 344 /** 345 * 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 346 347The 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. 348 */ 349 MEDICATIONSTATEMENT, 350 /** 351 * 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. 352 */ 353 MESSAGEDEFINITION, 354 /** 355 * 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. 356 */ 357 MESSAGEHEADER, 358 /** 359 * 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. 360 */ 361 NAMINGSYSTEM, 362 /** 363 * A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. 364 */ 365 NUTRITIONORDER, 366 /** 367 * Measurements and simple assertions made about a patient, device or other subject. 368 */ 369 OBSERVATION, 370 /** 371 * A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). 372 */ 373 OPERATIONDEFINITION, 374 /** 375 * A collection of error, warning or information messages that result from a system action. 376 */ 377 OPERATIONOUTCOME, 378 /** 379 * 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. 380 */ 381 ORGANIZATION, 382 /** 383 * 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. 384 */ 385 PARAMETERS, 386 /** 387 * Demographics and other administrative information about an individual or animal receiving care or other health-related services. 388 */ 389 PATIENT, 390 /** 391 * This resource provides the status of the payment for goods and services rendered, and the request and response resource references. 392 */ 393 PAYMENTNOTICE, 394 /** 395 * This resource provides payment details and claim references supporting a bulk payment. 396 */ 397 PAYMENTRECONCILIATION, 398 /** 399 * Demographics and administrative information about a person independent of a specific health-related context. 400 */ 401 PERSON, 402 /** 403 * 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. 404 */ 405 PLANDEFINITION, 406 /** 407 * A person who is directly or indirectly involved in the provisioning of healthcare. 408 */ 409 PRACTITIONER, 410 /** 411 * A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. 412 */ 413 PRACTITIONERROLE, 414 /** 415 * 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. 416 */ 417 PROCEDURE, 418 /** 419 * A record of a request for diagnostic investigations, treatments, or operations to be performed. 420 */ 421 PROCEDUREREQUEST, 422 /** 423 * 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. 424 */ 425 PROCESSREQUEST, 426 /** 427 * This resource provides processing status, errors and notes from the processing of a resource. 428 */ 429 PROCESSRESPONSE, 430 /** 431 * 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. 432 */ 433 PROVENANCE, 434 /** 435 * 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. 436 */ 437 QUESTIONNAIRE, 438 /** 439 * 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. 440 */ 441 QUESTIONNAIRERESPONSE, 442 /** 443 * Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization. 444 */ 445 REFERRALREQUEST, 446 /** 447 * 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. 448 */ 449 RELATEDPERSON, 450 /** 451 * 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". 452 */ 453 REQUESTGROUP, 454 /** 455 * 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. 456 */ 457 RESEARCHSTUDY, 458 /** 459 * 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. 460 */ 461 RESEARCHSUBJECT, 462 /** 463 * This is the base resource type for everything. 464 */ 465 RESOURCE, 466 /** 467 * An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. 468 */ 469 RISKASSESSMENT, 470 /** 471 * A container for slots of time that may be available for booking appointments. 472 */ 473 SCHEDULE, 474 /** 475 * A search parameter that defines a named search item that can be used to search/filter on a resource. 476 */ 477 SEARCHPARAMETER, 478 /** 479 * Raw data describing a biological sequence. 480 */ 481 SEQUENCE, 482 /** 483 * The ServiceDefinition describes a unit of decision support functionality that is made available as a service, such as immunization modules or drug-drug interaction checking. 484 */ 485 SERVICEDEFINITION, 486 /** 487 * A slot of time on a schedule that may be available for booking appointments. 488 */ 489 SLOT, 490 /** 491 * A sample to be used for analysis. 492 */ 493 SPECIMEN, 494 /** 495 * 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. 496 */ 497 STRUCTUREDEFINITION, 498 /** 499 * A Map of relationships between 2 structures that can be used to transform data. 500 */ 501 STRUCTUREMAP, 502 /** 503 * 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 is able to take an appropriate action. 504 */ 505 SUBSCRIPTION, 506 /** 507 * A homogeneous material with a definite composition. 508 */ 509 SUBSTANCE, 510 /** 511 * Record of delivery of what is supplied. 512 */ 513 SUPPLYDELIVERY, 514 /** 515 * A record of a request for a medication, substance or device used in the healthcare setting. 516 */ 517 SUPPLYREQUEST, 518 /** 519 * A task to be performed. 520 */ 521 TASK, 522 /** 523 * A summary of information based on the results of executing a TestScript. 524 */ 525 TESTREPORT, 526 /** 527 * A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. 528 */ 529 TESTSCRIPT, 530 /** 531 * A value set specifies a set of codes drawn from one or more code systems. 532 */ 533 VALUESET, 534 /** 535 * An authorization for the supply of glasses and/or contact lenses to a patient. 536 */ 537 VISIONPRESCRIPTION, 538 /** 539 * added to help the parsers 540 */ 541 NULL; 542 public static ResourceTypes fromCode(String codeString) throws FHIRException { 543 if (codeString == null || "".equals(codeString)) 544 return null; 545 if ("Account".equals(codeString)) 546 return ACCOUNT; 547 if ("ActivityDefinition".equals(codeString)) 548 return ACTIVITYDEFINITION; 549 if ("AdverseEvent".equals(codeString)) 550 return ADVERSEEVENT; 551 if ("AllergyIntolerance".equals(codeString)) 552 return ALLERGYINTOLERANCE; 553 if ("Appointment".equals(codeString)) 554 return APPOINTMENT; 555 if ("AppointmentResponse".equals(codeString)) 556 return APPOINTMENTRESPONSE; 557 if ("AuditEvent".equals(codeString)) 558 return AUDITEVENT; 559 if ("Basic".equals(codeString)) 560 return BASIC; 561 if ("Binary".equals(codeString)) 562 return BINARY; 563 if ("BodySite".equals(codeString)) 564 return BODYSITE; 565 if ("Bundle".equals(codeString)) 566 return BUNDLE; 567 if ("CapabilityStatement".equals(codeString)) 568 return CAPABILITYSTATEMENT; 569 if ("CarePlan".equals(codeString)) 570 return CAREPLAN; 571 if ("CareTeam".equals(codeString)) 572 return CARETEAM; 573 if ("ChargeItem".equals(codeString)) 574 return CHARGEITEM; 575 if ("Claim".equals(codeString)) 576 return CLAIM; 577 if ("ClaimResponse".equals(codeString)) 578 return CLAIMRESPONSE; 579 if ("ClinicalImpression".equals(codeString)) 580 return CLINICALIMPRESSION; 581 if ("CodeSystem".equals(codeString)) 582 return CODESYSTEM; 583 if ("Communication".equals(codeString)) 584 return COMMUNICATION; 585 if ("CommunicationRequest".equals(codeString)) 586 return COMMUNICATIONREQUEST; 587 if ("CompartmentDefinition".equals(codeString)) 588 return COMPARTMENTDEFINITION; 589 if ("Composition".equals(codeString)) 590 return COMPOSITION; 591 if ("ConceptMap".equals(codeString)) 592 return CONCEPTMAP; 593 if ("Condition".equals(codeString)) 594 return CONDITION; 595 if ("Consent".equals(codeString)) 596 return CONSENT; 597 if ("Contract".equals(codeString)) 598 return CONTRACT; 599 if ("Coverage".equals(codeString)) 600 return COVERAGE; 601 if ("DataElement".equals(codeString)) 602 return DATAELEMENT; 603 if ("DetectedIssue".equals(codeString)) 604 return DETECTEDISSUE; 605 if ("Device".equals(codeString)) 606 return DEVICE; 607 if ("DeviceComponent".equals(codeString)) 608 return DEVICECOMPONENT; 609 if ("DeviceMetric".equals(codeString)) 610 return DEVICEMETRIC; 611 if ("DeviceRequest".equals(codeString)) 612 return DEVICEREQUEST; 613 if ("DeviceUseStatement".equals(codeString)) 614 return DEVICEUSESTATEMENT; 615 if ("DiagnosticReport".equals(codeString)) 616 return DIAGNOSTICREPORT; 617 if ("DocumentManifest".equals(codeString)) 618 return DOCUMENTMANIFEST; 619 if ("DocumentReference".equals(codeString)) 620 return DOCUMENTREFERENCE; 621 if ("DomainResource".equals(codeString)) 622 return DOMAINRESOURCE; 623 if ("EligibilityRequest".equals(codeString)) 624 return ELIGIBILITYREQUEST; 625 if ("EligibilityResponse".equals(codeString)) 626 return ELIGIBILITYRESPONSE; 627 if ("Encounter".equals(codeString)) 628 return ENCOUNTER; 629 if ("Endpoint".equals(codeString)) 630 return ENDPOINT; 631 if ("EnrollmentRequest".equals(codeString)) 632 return ENROLLMENTREQUEST; 633 if ("EnrollmentResponse".equals(codeString)) 634 return ENROLLMENTRESPONSE; 635 if ("EpisodeOfCare".equals(codeString)) 636 return EPISODEOFCARE; 637 if ("ExpansionProfile".equals(codeString)) 638 return EXPANSIONPROFILE; 639 if ("ExplanationOfBenefit".equals(codeString)) 640 return EXPLANATIONOFBENEFIT; 641 if ("FamilyMemberHistory".equals(codeString)) 642 return FAMILYMEMBERHISTORY; 643 if ("Flag".equals(codeString)) 644 return FLAG; 645 if ("Goal".equals(codeString)) 646 return GOAL; 647 if ("GraphDefinition".equals(codeString)) 648 return GRAPHDEFINITION; 649 if ("Group".equals(codeString)) 650 return GROUP; 651 if ("GuidanceResponse".equals(codeString)) 652 return GUIDANCERESPONSE; 653 if ("HealthcareService".equals(codeString)) 654 return HEALTHCARESERVICE; 655 if ("ImagingManifest".equals(codeString)) 656 return IMAGINGMANIFEST; 657 if ("ImagingStudy".equals(codeString)) 658 return IMAGINGSTUDY; 659 if ("Immunization".equals(codeString)) 660 return IMMUNIZATION; 661 if ("ImmunizationRecommendation".equals(codeString)) 662 return IMMUNIZATIONRECOMMENDATION; 663 if ("ImplementationGuide".equals(codeString)) 664 return IMPLEMENTATIONGUIDE; 665 if ("Library".equals(codeString)) 666 return LIBRARY; 667 if ("Linkage".equals(codeString)) 668 return LINKAGE; 669 if ("List".equals(codeString)) 670 return LIST; 671 if ("Location".equals(codeString)) 672 return LOCATION; 673 if ("Measure".equals(codeString)) 674 return MEASURE; 675 if ("MeasureReport".equals(codeString)) 676 return MEASUREREPORT; 677 if ("Media".equals(codeString)) 678 return MEDIA; 679 if ("Medication".equals(codeString)) 680 return MEDICATION; 681 if ("MedicationAdministration".equals(codeString)) 682 return MEDICATIONADMINISTRATION; 683 if ("MedicationDispense".equals(codeString)) 684 return MEDICATIONDISPENSE; 685 if ("MedicationRequest".equals(codeString)) 686 return MEDICATIONREQUEST; 687 if ("MedicationStatement".equals(codeString)) 688 return MEDICATIONSTATEMENT; 689 if ("MessageDefinition".equals(codeString)) 690 return MESSAGEDEFINITION; 691 if ("MessageHeader".equals(codeString)) 692 return MESSAGEHEADER; 693 if ("NamingSystem".equals(codeString)) 694 return NAMINGSYSTEM; 695 if ("NutritionOrder".equals(codeString)) 696 return NUTRITIONORDER; 697 if ("Observation".equals(codeString)) 698 return OBSERVATION; 699 if ("OperationDefinition".equals(codeString)) 700 return OPERATIONDEFINITION; 701 if ("OperationOutcome".equals(codeString)) 702 return OPERATIONOUTCOME; 703 if ("Organization".equals(codeString)) 704 return ORGANIZATION; 705 if ("Parameters".equals(codeString)) 706 return PARAMETERS; 707 if ("Patient".equals(codeString)) 708 return PATIENT; 709 if ("PaymentNotice".equals(codeString)) 710 return PAYMENTNOTICE; 711 if ("PaymentReconciliation".equals(codeString)) 712 return PAYMENTRECONCILIATION; 713 if ("Person".equals(codeString)) 714 return PERSON; 715 if ("PlanDefinition".equals(codeString)) 716 return PLANDEFINITION; 717 if ("Practitioner".equals(codeString)) 718 return PRACTITIONER; 719 if ("PractitionerRole".equals(codeString)) 720 return PRACTITIONERROLE; 721 if ("Procedure".equals(codeString)) 722 return PROCEDURE; 723 if ("ProcedureRequest".equals(codeString)) 724 return PROCEDUREREQUEST; 725 if ("ProcessRequest".equals(codeString)) 726 return PROCESSREQUEST; 727 if ("ProcessResponse".equals(codeString)) 728 return PROCESSRESPONSE; 729 if ("Provenance".equals(codeString)) 730 return PROVENANCE; 731 if ("Questionnaire".equals(codeString)) 732 return QUESTIONNAIRE; 733 if ("QuestionnaireResponse".equals(codeString)) 734 return QUESTIONNAIRERESPONSE; 735 if ("ReferralRequest".equals(codeString)) 736 return REFERRALREQUEST; 737 if ("RelatedPerson".equals(codeString)) 738 return RELATEDPERSON; 739 if ("RequestGroup".equals(codeString)) 740 return REQUESTGROUP; 741 if ("ResearchStudy".equals(codeString)) 742 return RESEARCHSTUDY; 743 if ("ResearchSubject".equals(codeString)) 744 return RESEARCHSUBJECT; 745 if ("Resource".equals(codeString)) 746 return RESOURCE; 747 if ("RiskAssessment".equals(codeString)) 748 return RISKASSESSMENT; 749 if ("Schedule".equals(codeString)) 750 return SCHEDULE; 751 if ("SearchParameter".equals(codeString)) 752 return SEARCHPARAMETER; 753 if ("Sequence".equals(codeString)) 754 return SEQUENCE; 755 if ("ServiceDefinition".equals(codeString)) 756 return SERVICEDEFINITION; 757 if ("Slot".equals(codeString)) 758 return SLOT; 759 if ("Specimen".equals(codeString)) 760 return SPECIMEN; 761 if ("StructureDefinition".equals(codeString)) 762 return STRUCTUREDEFINITION; 763 if ("StructureMap".equals(codeString)) 764 return STRUCTUREMAP; 765 if ("Subscription".equals(codeString)) 766 return SUBSCRIPTION; 767 if ("Substance".equals(codeString)) 768 return SUBSTANCE; 769 if ("SupplyDelivery".equals(codeString)) 770 return SUPPLYDELIVERY; 771 if ("SupplyRequest".equals(codeString)) 772 return SUPPLYREQUEST; 773 if ("Task".equals(codeString)) 774 return TASK; 775 if ("TestReport".equals(codeString)) 776 return TESTREPORT; 777 if ("TestScript".equals(codeString)) 778 return TESTSCRIPT; 779 if ("ValueSet".equals(codeString)) 780 return VALUESET; 781 if ("VisionPrescription".equals(codeString)) 782 return VISIONPRESCRIPTION; 783 throw new FHIRException("Unknown ResourceTypes code '"+codeString+"'"); 784 } 785 public String toCode() { 786 switch (this) { 787 case ACCOUNT: return "Account"; 788 case ACTIVITYDEFINITION: return "ActivityDefinition"; 789 case ADVERSEEVENT: return "AdverseEvent"; 790 case ALLERGYINTOLERANCE: return "AllergyIntolerance"; 791 case APPOINTMENT: return "Appointment"; 792 case APPOINTMENTRESPONSE: return "AppointmentResponse"; 793 case AUDITEVENT: return "AuditEvent"; 794 case BASIC: return "Basic"; 795 case BINARY: return "Binary"; 796 case BODYSITE: return "BodySite"; 797 case BUNDLE: return "Bundle"; 798 case CAPABILITYSTATEMENT: return "CapabilityStatement"; 799 case CAREPLAN: return "CarePlan"; 800 case CARETEAM: return "CareTeam"; 801 case CHARGEITEM: return "ChargeItem"; 802 case CLAIM: return "Claim"; 803 case CLAIMRESPONSE: return "ClaimResponse"; 804 case CLINICALIMPRESSION: return "ClinicalImpression"; 805 case CODESYSTEM: return "CodeSystem"; 806 case COMMUNICATION: return "Communication"; 807 case COMMUNICATIONREQUEST: return "CommunicationRequest"; 808 case COMPARTMENTDEFINITION: return "CompartmentDefinition"; 809 case COMPOSITION: return "Composition"; 810 case CONCEPTMAP: return "ConceptMap"; 811 case CONDITION: return "Condition"; 812 case CONSENT: return "Consent"; 813 case CONTRACT: return "Contract"; 814 case COVERAGE: return "Coverage"; 815 case DATAELEMENT: return "DataElement"; 816 case DETECTEDISSUE: return "DetectedIssue"; 817 case DEVICE: return "Device"; 818 case DEVICECOMPONENT: return "DeviceComponent"; 819 case DEVICEMETRIC: return "DeviceMetric"; 820 case DEVICEREQUEST: return "DeviceRequest"; 821 case DEVICEUSESTATEMENT: return "DeviceUseStatement"; 822 case DIAGNOSTICREPORT: return "DiagnosticReport"; 823 case DOCUMENTMANIFEST: return "DocumentManifest"; 824 case DOCUMENTREFERENCE: return "DocumentReference"; 825 case DOMAINRESOURCE: return "DomainResource"; 826 case ELIGIBILITYREQUEST: return "EligibilityRequest"; 827 case ELIGIBILITYRESPONSE: return "EligibilityResponse"; 828 case ENCOUNTER: return "Encounter"; 829 case ENDPOINT: return "Endpoint"; 830 case ENROLLMENTREQUEST: return "EnrollmentRequest"; 831 case ENROLLMENTRESPONSE: return "EnrollmentResponse"; 832 case EPISODEOFCARE: return "EpisodeOfCare"; 833 case EXPANSIONPROFILE: return "ExpansionProfile"; 834 case EXPLANATIONOFBENEFIT: return "ExplanationOfBenefit"; 835 case FAMILYMEMBERHISTORY: return "FamilyMemberHistory"; 836 case FLAG: return "Flag"; 837 case GOAL: return "Goal"; 838 case GRAPHDEFINITION: return "GraphDefinition"; 839 case GROUP: return "Group"; 840 case GUIDANCERESPONSE: return "GuidanceResponse"; 841 case HEALTHCARESERVICE: return "HealthcareService"; 842 case IMAGINGMANIFEST: return "ImagingManifest"; 843 case IMAGINGSTUDY: return "ImagingStudy"; 844 case IMMUNIZATION: return "Immunization"; 845 case IMMUNIZATIONRECOMMENDATION: return "ImmunizationRecommendation"; 846 case IMPLEMENTATIONGUIDE: return "ImplementationGuide"; 847 case LIBRARY: return "Library"; 848 case LINKAGE: return "Linkage"; 849 case LIST: return "List"; 850 case LOCATION: return "Location"; 851 case MEASURE: return "Measure"; 852 case MEASUREREPORT: return "MeasureReport"; 853 case MEDIA: return "Media"; 854 case MEDICATION: return "Medication"; 855 case MEDICATIONADMINISTRATION: return "MedicationAdministration"; 856 case MEDICATIONDISPENSE: return "MedicationDispense"; 857 case MEDICATIONREQUEST: return "MedicationRequest"; 858 case MEDICATIONSTATEMENT: return "MedicationStatement"; 859 case MESSAGEDEFINITION: return "MessageDefinition"; 860 case MESSAGEHEADER: return "MessageHeader"; 861 case NAMINGSYSTEM: return "NamingSystem"; 862 case NUTRITIONORDER: return "NutritionOrder"; 863 case OBSERVATION: return "Observation"; 864 case OPERATIONDEFINITION: return "OperationDefinition"; 865 case OPERATIONOUTCOME: return "OperationOutcome"; 866 case ORGANIZATION: return "Organization"; 867 case PARAMETERS: return "Parameters"; 868 case PATIENT: return "Patient"; 869 case PAYMENTNOTICE: return "PaymentNotice"; 870 case PAYMENTRECONCILIATION: return "PaymentReconciliation"; 871 case PERSON: return "Person"; 872 case PLANDEFINITION: return "PlanDefinition"; 873 case PRACTITIONER: return "Practitioner"; 874 case PRACTITIONERROLE: return "PractitionerRole"; 875 case PROCEDURE: return "Procedure"; 876 case PROCEDUREREQUEST: return "ProcedureRequest"; 877 case PROCESSREQUEST: return "ProcessRequest"; 878 case PROCESSRESPONSE: return "ProcessResponse"; 879 case PROVENANCE: return "Provenance"; 880 case QUESTIONNAIRE: return "Questionnaire"; 881 case QUESTIONNAIRERESPONSE: return "QuestionnaireResponse"; 882 case REFERRALREQUEST: return "ReferralRequest"; 883 case RELATEDPERSON: return "RelatedPerson"; 884 case REQUESTGROUP: return "RequestGroup"; 885 case RESEARCHSTUDY: return "ResearchStudy"; 886 case RESEARCHSUBJECT: return "ResearchSubject"; 887 case RESOURCE: return "Resource"; 888 case RISKASSESSMENT: return "RiskAssessment"; 889 case SCHEDULE: return "Schedule"; 890 case SEARCHPARAMETER: return "SearchParameter"; 891 case SEQUENCE: return "Sequence"; 892 case SERVICEDEFINITION: return "ServiceDefinition"; 893 case SLOT: return "Slot"; 894 case SPECIMEN: return "Specimen"; 895 case STRUCTUREDEFINITION: return "StructureDefinition"; 896 case STRUCTUREMAP: return "StructureMap"; 897 case SUBSCRIPTION: return "Subscription"; 898 case SUBSTANCE: return "Substance"; 899 case SUPPLYDELIVERY: return "SupplyDelivery"; 900 case SUPPLYREQUEST: return "SupplyRequest"; 901 case TASK: return "Task"; 902 case TESTREPORT: return "TestReport"; 903 case TESTSCRIPT: return "TestScript"; 904 case VALUESET: return "ValueSet"; 905 case VISIONPRESCRIPTION: return "VisionPrescription"; 906 default: return "?"; 907 } 908 } 909 public String getSystem() { 910 return "http://hl7.org/fhir/resource-types"; 911 } 912 public String getDefinition() { 913 switch (this) { 914 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."; 915 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."; 916 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."; 917 case ALLERGYINTOLERANCE: return "Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance."; 918 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)."; 919 case APPOINTMENTRESPONSE: return "A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection."; 920 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."; 921 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."; 922 case BINARY: return "A binary resource can contain any content, whether text, image, pdf, zip archive, etc."; 923 case BODYSITE: return "Record details about the anatomical location of a specimen or body part. This resource may be used when a coded concept does not provide the necessary detail needed for the use case."; 924 case BUNDLE: return "A container for a collection of resources."; 925 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."; 926 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."; 927 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."; 928 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."; 929 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."; 930 case CLAIMRESPONSE: return "This resource provides the adjudication details from the processing of a Claim resource."; 931 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."; 932 case CODESYSTEM: return "A code system resource specifies a set of codes drawn from one or more code systems."; 933 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."; 934 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."; 935 case COMPARTMENTDEFINITION: return "A compartment definition that defines how resources are accessed on a server."; 936 case COMPOSITION: return "A set of healthcare-related information that is assembled together into a single logical document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained."; 937 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."; 938 case CONDITION: return "A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern."; 939 case CONSENT: return "A record of a healthcare consumer’s policy 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."; 940 case CONTRACT: return "A formal agreement between parties regarding the conduct of business, exchange of information or other matters."; 941 case COVERAGE: return "Financial instrument which may be used to reimburse or pay for health care products and services."; 942 case DATAELEMENT: return "The formal description of a single piece of information that can be gathered and reported."; 943 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."; 944 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."; 945 case DEVICECOMPONENT: return "The characteristics, operational status and capabilities of a medical-related component of a medical device."; 946 case DEVICEMETRIC: return "Describes a measurement, calculation or setting capability of a medical device."; 947 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."; 948 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."; 949 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."; 950 case DOCUMENTMANIFEST: return "A collection of documents compiled for a purpose together with metadata that applies to the collection."; 951 case DOCUMENTREFERENCE: return "A reference to a document."; 952 case DOMAINRESOURCE: return "A resource that includes narrative, extensions, and contained resources."; 953 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."; 954 case ELIGIBILITYRESPONSE: return "This resource provides eligibility and plan details from the processing of an Eligibility resource."; 955 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."; 956 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."; 957 case ENROLLMENTREQUEST: return "This resource provides the insurance enrollment details to the insurer regarding a specified coverage."; 958 case ENROLLMENTRESPONSE: return "This resource provides enrollment and plan details from the processing of an Enrollment resource."; 959 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."; 960 case EXPANSIONPROFILE: return "Resource to define constraints on the Expansion of a FHIR ValueSet."; 961 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."; 962 case FAMILYMEMBERHISTORY: return "Significant health events and conditions for a person related to the patient relevant in the context of care for the patient."; 963 case FLAG: return "Prospective warnings of potential issues when providing care to the patient."; 964 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."; 965 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."; 966 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."; 967 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."; 968 case HEALTHCARESERVICE: return "The details of a healthcare service available at a location."; 969 case IMAGINGMANIFEST: return "A text description of the DICOM SOP instances selected in the ImagingManifest; or the reason for, or significance of, the selection."; 970 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."; 971 case IMMUNIZATION: return "Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed."; 972 case IMMUNIZATIONRECOMMENDATION: return "A patient's point-in-time immunization and recommendation (i.e. forecasting a patient's immunization eligibility according to a published schedule) with optional supporting justification."; 973 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."; 974 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."; 975 case LINKAGE: return "Identifies two or more records (resource instances) that are referring to the same real-world \"occurrence\"."; 976 case LIST: return "A set of information summarized from a list of other resources."; 977 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."; 978 case MEASURE: return "The Measure resource provides the definition of a quality measure."; 979 case MEASUREREPORT: return "The MeasureReport resource contains the results of evaluating a measure."; 980 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."; 981 case MEDICATION: return "This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication."; 982 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."; 983 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."; 984 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."; 985 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."; 986 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."; 987 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."; 988 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."; 989 case NUTRITIONORDER: return "A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident."; 990 case OBSERVATION: return "Measurements and simple assertions made about a patient, device or other subject."; 991 case OPERATIONDEFINITION: return "A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction)."; 992 case OPERATIONOUTCOME: return "A collection of error, warning or information messages that result from a system action."; 993 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."; 994 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."; 995 case PATIENT: return "Demographics and other administrative information about an individual or animal receiving care or other health-related services."; 996 case PAYMENTNOTICE: return "This resource provides the status of the payment for goods and services rendered, and the request and response resource references."; 997 case PAYMENTRECONCILIATION: return "This resource provides payment details and claim references supporting a bulk payment."; 998 case PERSON: return "Demographics and administrative information about a person independent of a specific health-related context."; 999 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."; 1000 case PRACTITIONER: return "A person who is directly or indirectly involved in the provisioning of healthcare."; 1001 case PRACTITIONERROLE: return "A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time."; 1002 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."; 1003 case PROCEDUREREQUEST: return "A record of a request for diagnostic investigations, treatments, or operations to be performed."; 1004 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."; 1005 case PROCESSRESPONSE: return "This resource provides processing status, errors and notes from the processing of a resource."; 1006 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."; 1007 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."; 1008 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."; 1009 case REFERRALREQUEST: return "Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization."; 1010 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."; 1011 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\"."; 1012 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."; 1013 case RESEARCHSUBJECT: 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."; 1014 case RESOURCE: return "This is the base resource type for everything."; 1015 case RISKASSESSMENT: return "An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome."; 1016 case SCHEDULE: return "A container for slots of time that may be available for booking appointments."; 1017 case SEARCHPARAMETER: return "A search parameter that defines a named search item that can be used to search/filter on a resource."; 1018 case SEQUENCE: return "Raw data describing a biological sequence."; 1019 case SERVICEDEFINITION: return "The ServiceDefinition describes a unit of decision support functionality that is made available as a service, such as immunization modules or drug-drug interaction checking."; 1020 case SLOT: return "A slot of time on a schedule that may be available for booking appointments."; 1021 case SPECIMEN: return "A sample to be used for analysis."; 1022 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."; 1023 case STRUCTUREMAP: return "A Map of relationships between 2 structures that can be used to transform data."; 1024 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 is able to take an appropriate action."; 1025 case SUBSTANCE: return "A homogeneous material with a definite composition."; 1026 case SUPPLYDELIVERY: return "Record of delivery of what is supplied."; 1027 case SUPPLYREQUEST: return "A record of a request for a medication, substance or device used in the healthcare setting."; 1028 case TASK: return "A task to be performed."; 1029 case TESTREPORT: return "A summary of information based on the results of executing a TestScript."; 1030 case TESTSCRIPT: return "A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification."; 1031 case VALUESET: return "A value set specifies a set of codes drawn from one or more code systems."; 1032 case VISIONPRESCRIPTION: return "An authorization for the supply of glasses and/or contact lenses to a patient."; 1033 default: return "?"; 1034 } 1035 } 1036 public String getDisplay() { 1037 switch (this) { 1038 case ACCOUNT: return "Account"; 1039 case ACTIVITYDEFINITION: return "ActivityDefinition"; 1040 case ADVERSEEVENT: return "AdverseEvent"; 1041 case ALLERGYINTOLERANCE: return "AllergyIntolerance"; 1042 case APPOINTMENT: return "Appointment"; 1043 case APPOINTMENTRESPONSE: return "AppointmentResponse"; 1044 case AUDITEVENT: return "AuditEvent"; 1045 case BASIC: return "Basic"; 1046 case BINARY: return "Binary"; 1047 case BODYSITE: return "BodySite"; 1048 case BUNDLE: return "Bundle"; 1049 case CAPABILITYSTATEMENT: return "CapabilityStatement"; 1050 case CAREPLAN: return "CarePlan"; 1051 case CARETEAM: return "CareTeam"; 1052 case CHARGEITEM: return "ChargeItem"; 1053 case CLAIM: return "Claim"; 1054 case CLAIMRESPONSE: return "ClaimResponse"; 1055 case CLINICALIMPRESSION: return "ClinicalImpression"; 1056 case CODESYSTEM: return "CodeSystem"; 1057 case COMMUNICATION: return "Communication"; 1058 case COMMUNICATIONREQUEST: return "CommunicationRequest"; 1059 case COMPARTMENTDEFINITION: return "CompartmentDefinition"; 1060 case COMPOSITION: return "Composition"; 1061 case CONCEPTMAP: return "ConceptMap"; 1062 case CONDITION: return "Condition"; 1063 case CONSENT: return "Consent"; 1064 case CONTRACT: return "Contract"; 1065 case COVERAGE: return "Coverage"; 1066 case DATAELEMENT: return "DataElement"; 1067 case DETECTEDISSUE: return "DetectedIssue"; 1068 case DEVICE: return "Device"; 1069 case DEVICECOMPONENT: return "DeviceComponent"; 1070 case DEVICEMETRIC: return "DeviceMetric"; 1071 case DEVICEREQUEST: return "DeviceRequest"; 1072 case DEVICEUSESTATEMENT: return "DeviceUseStatement"; 1073 case DIAGNOSTICREPORT: return "DiagnosticReport"; 1074 case DOCUMENTMANIFEST: return "DocumentManifest"; 1075 case DOCUMENTREFERENCE: return "DocumentReference"; 1076 case DOMAINRESOURCE: return "DomainResource"; 1077 case ELIGIBILITYREQUEST: return "EligibilityRequest"; 1078 case ELIGIBILITYRESPONSE: return "EligibilityResponse"; 1079 case ENCOUNTER: return "Encounter"; 1080 case ENDPOINT: return "Endpoint"; 1081 case ENROLLMENTREQUEST: return "EnrollmentRequest"; 1082 case ENROLLMENTRESPONSE: return "EnrollmentResponse"; 1083 case EPISODEOFCARE: return "EpisodeOfCare"; 1084 case EXPANSIONPROFILE: return "ExpansionProfile"; 1085 case EXPLANATIONOFBENEFIT: return "ExplanationOfBenefit"; 1086 case FAMILYMEMBERHISTORY: return "FamilyMemberHistory"; 1087 case FLAG: return "Flag"; 1088 case GOAL: return "Goal"; 1089 case GRAPHDEFINITION: return "GraphDefinition"; 1090 case GROUP: return "Group"; 1091 case GUIDANCERESPONSE: return "GuidanceResponse"; 1092 case HEALTHCARESERVICE: return "HealthcareService"; 1093 case IMAGINGMANIFEST: return "ImagingManifest"; 1094 case IMAGINGSTUDY: return "ImagingStudy"; 1095 case IMMUNIZATION: return "Immunization"; 1096 case IMMUNIZATIONRECOMMENDATION: return "ImmunizationRecommendation"; 1097 case IMPLEMENTATIONGUIDE: return "ImplementationGuide"; 1098 case LIBRARY: return "Library"; 1099 case LINKAGE: return "Linkage"; 1100 case LIST: return "List"; 1101 case LOCATION: return "Location"; 1102 case MEASURE: return "Measure"; 1103 case MEASUREREPORT: return "MeasureReport"; 1104 case MEDIA: return "Media"; 1105 case MEDICATION: return "Medication"; 1106 case MEDICATIONADMINISTRATION: return "MedicationAdministration"; 1107 case MEDICATIONDISPENSE: return "MedicationDispense"; 1108 case MEDICATIONREQUEST: return "MedicationRequest"; 1109 case MEDICATIONSTATEMENT: return "MedicationStatement"; 1110 case MESSAGEDEFINITION: return "MessageDefinition"; 1111 case MESSAGEHEADER: return "MessageHeader"; 1112 case NAMINGSYSTEM: return "NamingSystem"; 1113 case NUTRITIONORDER: return "NutritionOrder"; 1114 case OBSERVATION: return "Observation"; 1115 case OPERATIONDEFINITION: return "OperationDefinition"; 1116 case OPERATIONOUTCOME: return "OperationOutcome"; 1117 case ORGANIZATION: return "Organization"; 1118 case PARAMETERS: return "Parameters"; 1119 case PATIENT: return "Patient"; 1120 case PAYMENTNOTICE: return "PaymentNotice"; 1121 case PAYMENTRECONCILIATION: return "PaymentReconciliation"; 1122 case PERSON: return "Person"; 1123 case PLANDEFINITION: return "PlanDefinition"; 1124 case PRACTITIONER: return "Practitioner"; 1125 case PRACTITIONERROLE: return "PractitionerRole"; 1126 case PROCEDURE: return "Procedure"; 1127 case PROCEDUREREQUEST: return "ProcedureRequest"; 1128 case PROCESSREQUEST: return "ProcessRequest"; 1129 case PROCESSRESPONSE: return "ProcessResponse"; 1130 case PROVENANCE: return "Provenance"; 1131 case QUESTIONNAIRE: return "Questionnaire"; 1132 case QUESTIONNAIRERESPONSE: return "QuestionnaireResponse"; 1133 case REFERRALREQUEST: return "ReferralRequest"; 1134 case RELATEDPERSON: return "RelatedPerson"; 1135 case REQUESTGROUP: return "RequestGroup"; 1136 case RESEARCHSTUDY: return "ResearchStudy"; 1137 case RESEARCHSUBJECT: return "ResearchSubject"; 1138 case RESOURCE: return "Resource"; 1139 case RISKASSESSMENT: return "RiskAssessment"; 1140 case SCHEDULE: return "Schedule"; 1141 case SEARCHPARAMETER: return "SearchParameter"; 1142 case SEQUENCE: return "Sequence"; 1143 case SERVICEDEFINITION: return "ServiceDefinition"; 1144 case SLOT: return "Slot"; 1145 case SPECIMEN: return "Specimen"; 1146 case STRUCTUREDEFINITION: return "StructureDefinition"; 1147 case STRUCTUREMAP: return "StructureMap"; 1148 case SUBSCRIPTION: return "Subscription"; 1149 case SUBSTANCE: return "Substance"; 1150 case SUPPLYDELIVERY: return "SupplyDelivery"; 1151 case SUPPLYREQUEST: return "SupplyRequest"; 1152 case TASK: return "Task"; 1153 case TESTREPORT: return "TestReport"; 1154 case TESTSCRIPT: return "TestScript"; 1155 case VALUESET: return "ValueSet"; 1156 case VISIONPRESCRIPTION: return "VisionPrescription"; 1157 default: return "?"; 1158 } 1159 } 1160 1161 1162} 1163