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