001package org.hl7.fhir.dstu2016may.model.codesystems; 002 003 004 005 006/* 007 Copyright (c) 2011+, HL7, Inc. 008 All rights reserved. 009 010 Redistribution and use in source and binary forms, with or without modification, 011 are permitted provided that the following conditions are met: 012 013 * Redistributions of source code must retain the above copyright notice, this 014 list of conditions and the following disclaimer. 015 * Redistributions in binary form must reproduce the above copyright notice, 016 this list of conditions and the following disclaimer in the documentation 017 and/or other materials provided with the distribution. 018 * Neither the name of HL7 nor the names of its contributors may be used to 019 endorse or promote products derived from this software without specific 020 prior written permission. 021 022 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 023 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 024 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 025 IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 026 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 027 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 028 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, 029 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 030 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 031 POSSIBILITY OF SUCH DAMAGE. 032 033*/ 034 035// Generated on Sun, May 8, 2016 03:05+1000 for FHIR v1.4.0 036 037 038import org.hl7.fhir.exceptions.FHIRException; 039 040public enum ResourceTypes { 041 042 /** 043 * A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centres, etc. 044 */ 045 ACCOUNT, 046 /** 047 * Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. 048 */ 049 ALLERGYINTOLERANCE, 050 /** 051 * 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). 052 */ 053 APPOINTMENT, 054 /** 055 * A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection. 056 */ 057 APPOINTMENTRESPONSE, 058 /** 059 * 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. 060 */ 061 AUDITEVENT, 062 /** 063 * 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. 064 */ 065 BASIC, 066 /** 067 * A binary resource can contain any content, whether text, image, pdf, zip archive, etc. 068 */ 069 BINARY, 070 /** 071 * 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. 072 */ 073 BODYSITE, 074 /** 075 * A container for a collection of resources. 076 */ 077 BUNDLE, 078 /** 079 * 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. 080 */ 081 CAREPLAN, 082 /** 083 * The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. 084 */ 085 CARETEAM, 086 /** 087 * 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. 088 */ 089 CLAIM, 090 /** 091 * This resource provides the adjudication details from the processing of a Claim resource. 092 */ 093 CLAIMRESPONSE, 094 /** 095 * 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. 096 */ 097 CLINICALIMPRESSION, 098 /** 099 * A code system resource specifies a set of codes drawn from one or more code systems. 100 */ 101 CODESYSTEM, 102 /** 103 * 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. 104 */ 105 COMMUNICATION, 106 /** 107 * 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. 108 */ 109 COMMUNICATIONREQUEST, 110 /** 111 * A compartment definition that defines how resources are accessed on a server. 112 */ 113 COMPARTMENTDEFINITION, 114 /** 115 * 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. 116 */ 117 COMPOSITION, 118 /** 119 * 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. 120 */ 121 CONCEPTMAP, 122 /** 123 * Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses including: recording a diagnosis during an encounter; populating a problem list or a summary statement, such as a discharge summary. 124 */ 125 CONDITION, 126 /** 127 * A conformance statement is a set of capabilities of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. 128 */ 129 CONFORMANCE, 130 /** 131 * A formal agreement between parties regarding the conduct of business, exchange of information or other matters. 132 */ 133 CONTRACT, 134 /** 135 * Financial instrument which may be used to pay for or reimburse health care products and services. 136 */ 137 COVERAGE, 138 /** 139 * The formal description of a single piece of information that can be gathered and reported. 140 */ 141 DATAELEMENT, 142 /** 143 * This resource defines a decision support rule of the form [on Event] if Condition then Action. It is intended to be a shareable, computable definition of a actions that should be taken whenever some condition is met in response to a particular event or events. 144 */ 145 DECISIONSUPPORTRULE, 146 /** 147 * The DecisionSupportServiceModule describes a unit of decision support functionality that is made available as a service, such as immunization modules or drug-drug interaction checking. 148 */ 149 DECISIONSUPPORTSERVICEMODULE, 150 /** 151 * 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. 152 */ 153 DETECTEDISSUE, 154 /** 155 * 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 includes 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. 156 */ 157 DEVICE, 158 /** 159 * Describes the characteristics, operational status and capabilities of a medical-related component of a medical device. 160 */ 161 DEVICECOMPONENT, 162 /** 163 * Describes a measurement, calculation or setting capability of a medical device. 164 */ 165 DEVICEMETRIC, 166 /** 167 * 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. 168 */ 169 DEVICEUSEREQUEST, 170 /** 171 * 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. 172 */ 173 DEVICEUSESTATEMENT, 174 /** 175 * A record of a request for a diagnostic investigation service to be performed. 176 */ 177 DIAGNOSTICORDER, 178 /** 179 * 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. 180 */ 181 DIAGNOSTICREPORT, 182 /** 183 * A manifest that defines a set of documents. 184 */ 185 DOCUMENTMANIFEST, 186 /** 187 * A reference to a document . 188 */ 189 DOCUMENTREFERENCE, 190 /** 191 * A resource that includes narrative, extensions, and contained resources. 192 */ 193 DOMAINRESOURCE, 194 /** 195 * This resource provides the insurance eligibility details from the insurer regarding a specified coverage and optionally some class of service. 196 */ 197 ELIGIBILITYREQUEST, 198 /** 199 * This resource provides eligibility and plan details from the processing of an Eligibility resource. 200 */ 201 ELIGIBILITYRESPONSE, 202 /** 203 * 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. 204 */ 205 ENCOUNTER, 206 /** 207 * This resource provides the insurance enrollment details to the insurer regarding a specified coverage. 208 */ 209 ENROLLMENTREQUEST, 210 /** 211 * This resource provides enrollment and plan details from the processing of an Enrollment resource. 212 */ 213 ENROLLMENTRESPONSE, 214 /** 215 * 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. 216 */ 217 EPISODEOFCARE, 218 /** 219 * Resource to define constraints on the Expansion of a FHIR ValueSet. 220 */ 221 EXPANSIONPROFILE, 222 /** 223 * 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. 224 */ 225 EXPLANATIONOFBENEFIT, 226 /** 227 * Significant health events and conditions for a person related to the patient relevant in the context of care for the patient. 228 */ 229 FAMILYMEMBERHISTORY, 230 /** 231 * Prospective warnings of potential issues when providing care to the patient. 232 */ 233 FLAG, 234 /** 235 * 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. 236 */ 237 GOAL, 238 /** 239 * 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. 240 */ 241 GROUP, 242 /** 243 * 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. 244 */ 245 GUIDANCERESPONSE, 246 /** 247 * The details of a healthcare service available at a location. 248 */ 249 HEALTHCARESERVICE, 250 /** 251 * A manifest of a set of DICOM Service-Object Pair Instances (SOP Instances). The referenced SOP Instances (images or other content) are for a single patient, and may be from one or more studies. The referenced SOP Instances have been selected for a purpose, such as quality assurance, conference, or consult. Reflecting that range of purposes, typical ImagingExcerpt resources may include all SOP Instances in a study (perhaps for sharing through a Health Information Exchange); key images from multiple studies (for reference by a referring or treating physician); a multi-frame ultrasound instance ("cine" video clip) and a set of measurements taken from that instance (for inclusion in a teaching file); and so on. 252 */ 253 IMAGINGEXCERPT, 254 /** 255 * A manifest of a set of DICOM Service-Object Pair Instances (SOP Instances). The referenced SOP Instances (images or other content) are for a single patient, and may be from one or more studies. The referenced SOP Instances have been selected for a purpose, such as quality assurance, conference, or consult. Reflecting that range of purposes, typical ImagingObjectSelection resources may include all SOP Instances in a study (perhaps for sharing through a Health Information Exchange); key images from multiple studies (for reference by a referring or treating physician); a multi-frame ultrasound instance ("cine" video clip) and a set of measurements taken from that instance (for inclusion in a teaching file); and so on. 256 */ 257 IMAGINGOBJECTSELECTION, 258 /** 259 * 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. 260 */ 261 IMAGINGSTUDY, 262 /** 263 * 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. 264 */ 265 IMMUNIZATION, 266 /** 267 * 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. 268 */ 269 IMMUNIZATIONRECOMMENDATION, 270 /** 271 * A set of rules or 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. 272 */ 273 IMPLEMENTATIONGUIDE, 274 /** 275 * The Library resource provides a representation container for knowledge artifact component definitions. It is effectively an exposure of the header information for a CQL/ELM library. 276 */ 277 LIBRARY, 278 /** 279 * Identifies two or more records (resource instances) that are referring to the same real-world "occurrence". 280 */ 281 LINKAGE, 282 /** 283 * A set of information summarized from a list of other resources. 284 */ 285 LIST, 286 /** 287 * Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated. 288 */ 289 LOCATION, 290 /** 291 * The Measure resource provides the definition of a quality measure. 292 */ 293 MEASURE, 294 /** 295 * The MeasureReport resource contains the results of evaluating a measure. 296 */ 297 MEASUREREPORT, 298 /** 299 * A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference. 300 */ 301 MEDIA, 302 /** 303 * This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication. 304 */ 305 MEDICATION, 306 /** 307 * 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. 308 */ 309 MEDICATIONADMINISTRATION, 310 /** 311 * 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. 312 */ 313 MEDICATIONDISPENSE, 314 /** 315 * An order for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationOrder" rather than "MedicationPrescription" to generalize the use across inpatient and outpatient settings as well as for care plans, etc. 316 */ 317 MEDICATIONORDER, 318 /** 319 * 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 e.g. the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains 320 321The 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. 322 */ 323 MEDICATIONSTATEMENT, 324 /** 325 * 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. 326 */ 327 MESSAGEHEADER, 328 /** 329 * The ModuleDefinition resource defines the data requirements for a quality artifact. 330 */ 331 MODULEDEFINITION, 332 /** 333 * 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. 334 */ 335 NAMINGSYSTEM, 336 /** 337 * A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. 338 */ 339 NUTRITIONORDER, 340 /** 341 * Measurements and simple assertions made about a patient, device or other subject. 342 */ 343 OBSERVATION, 344 /** 345 * A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). 346 */ 347 OPERATIONDEFINITION, 348 /** 349 * A collection of error, warning or information messages that result from a system action. 350 */ 351 OPERATIONOUTCOME, 352 /** 353 * A request to perform an action. 354 */ 355 ORDER, 356 /** 357 * A response to an order. 358 */ 359 ORDERRESPONSE, 360 /** 361 * This resource allows for the definition of an order set as a sharable, consumable, and executable artifact in support of clinical decision support. 362 */ 363 ORDERSET, 364 /** 365 * 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. 366 */ 367 ORGANIZATION, 368 /** 369 * 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. 370 */ 371 PARAMETERS, 372 /** 373 * Demographics and other administrative information about an individual or animal receiving care or other health-related services. 374 */ 375 PATIENT, 376 /** 377 * This resource provides the status of the payment for goods and services rendered, and the request and response resource references. 378 */ 379 PAYMENTNOTICE, 380 /** 381 * This resource provides payment details and claim references supporting a bulk payment. 382 */ 383 PAYMENTRECONCILIATION, 384 /** 385 * Demographics and administrative information about a person independent of a specific health-related context. 386 */ 387 PERSON, 388 /** 389 * A person who is directly or indirectly involved in the provisioning of healthcare. 390 */ 391 PRACTITIONER, 392 /** 393 * A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. 394 */ 395 PRACTITIONERROLE, 396 /** 397 * 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. 398 */ 399 PROCEDURE, 400 /** 401 * A request for a procedure to be performed. May be a proposal or an order. 402 */ 403 PROCEDUREREQUEST, 404 /** 405 * 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. 406 */ 407 PROCESSREQUEST, 408 /** 409 * This resource provides processing status, errors and notes from the processing of a resource. 410 */ 411 PROCESSRESPONSE, 412 /** 413 * A definition of behaviors to be taken in particular circumstances, often including conditions, options and other decision points. 414 */ 415 PROTOCOL, 416 /** 417 * 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. 418 */ 419 PROVENANCE, 420 /** 421 * A structured set of questions intended to guide the collection of answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions. 422 */ 423 QUESTIONNAIRE, 424 /** 425 * 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 underlying questions. 426 */ 427 QUESTIONNAIRERESPONSE, 428 /** 429 * 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. 430 */ 431 REFERRALREQUEST, 432 /** 433 * 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. 434 */ 435 RELATEDPERSON, 436 /** 437 * This is the base resource type for everything. 438 */ 439 RESOURCE, 440 /** 441 * An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. 442 */ 443 RISKASSESSMENT, 444 /** 445 * A container for slot(s) of time that may be available for booking appointments. 446 */ 447 SCHEDULE, 448 /** 449 * A search parameter that defines a named search item that can be used to search/filter on a resource. 450 */ 451 SEARCHPARAMETER, 452 /** 453 * Variation and Sequence data. 454 */ 455 SEQUENCE, 456 /** 457 * A slot of time on a schedule that may be available for booking appointments. 458 */ 459 SLOT, 460 /** 461 * A sample to be used for analysis. 462 */ 463 SPECIMEN, 464 /** 465 * 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. 466 */ 467 STRUCTUREDEFINITION, 468 /** 469 * A Map of relationships between 2 structures that can be used to transform data. 470 */ 471 STRUCTUREMAP, 472 /** 473 * 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. 474 */ 475 SUBSCRIPTION, 476 /** 477 * A homogeneous material with a definite composition. 478 */ 479 SUBSTANCE, 480 /** 481 * Record of delivery of what is supplied. 482 */ 483 SUPPLYDELIVERY, 484 /** 485 * A record of a request for a medication, substance or device used in the healthcare setting. 486 */ 487 SUPPLYREQUEST, 488 /** 489 * A task to be performed. 490 */ 491 TASK, 492 /** 493 * TestScript is a resource that specifies a suite of tests against a FHIR server implementation to determine compliance against the FHIR specification. 494 */ 495 TESTSCRIPT, 496 /** 497 * A value set specifies a set of codes drawn from one or more code systems. 498 */ 499 VALUESET, 500 /** 501 * An authorization for the supply of glasses and/or contact lenses to a patient. 502 */ 503 VISIONPRESCRIPTION, 504 /** 505 * added to help the parsers 506 */ 507 NULL; 508 public static ResourceTypes fromCode(String codeString) throws FHIRException { 509 if (codeString == null || "".equals(codeString)) 510 return null; 511 if ("Account".equals(codeString)) 512 return ACCOUNT; 513 if ("AllergyIntolerance".equals(codeString)) 514 return ALLERGYINTOLERANCE; 515 if ("Appointment".equals(codeString)) 516 return APPOINTMENT; 517 if ("AppointmentResponse".equals(codeString)) 518 return APPOINTMENTRESPONSE; 519 if ("AuditEvent".equals(codeString)) 520 return AUDITEVENT; 521 if ("Basic".equals(codeString)) 522 return BASIC; 523 if ("Binary".equals(codeString)) 524 return BINARY; 525 if ("BodySite".equals(codeString)) 526 return BODYSITE; 527 if ("Bundle".equals(codeString)) 528 return BUNDLE; 529 if ("CarePlan".equals(codeString)) 530 return CAREPLAN; 531 if ("CareTeam".equals(codeString)) 532 return CARETEAM; 533 if ("Claim".equals(codeString)) 534 return CLAIM; 535 if ("ClaimResponse".equals(codeString)) 536 return CLAIMRESPONSE; 537 if ("ClinicalImpression".equals(codeString)) 538 return CLINICALIMPRESSION; 539 if ("CodeSystem".equals(codeString)) 540 return CODESYSTEM; 541 if ("Communication".equals(codeString)) 542 return COMMUNICATION; 543 if ("CommunicationRequest".equals(codeString)) 544 return COMMUNICATIONREQUEST; 545 if ("CompartmentDefinition".equals(codeString)) 546 return COMPARTMENTDEFINITION; 547 if ("Composition".equals(codeString)) 548 return COMPOSITION; 549 if ("ConceptMap".equals(codeString)) 550 return CONCEPTMAP; 551 if ("Condition".equals(codeString)) 552 return CONDITION; 553 if ("Conformance".equals(codeString)) 554 return CONFORMANCE; 555 if ("Contract".equals(codeString)) 556 return CONTRACT; 557 if ("Coverage".equals(codeString)) 558 return COVERAGE; 559 if ("DataElement".equals(codeString)) 560 return DATAELEMENT; 561 if ("DecisionSupportRule".equals(codeString)) 562 return DECISIONSUPPORTRULE; 563 if ("DecisionSupportServiceModule".equals(codeString)) 564 return DECISIONSUPPORTSERVICEMODULE; 565 if ("DetectedIssue".equals(codeString)) 566 return DETECTEDISSUE; 567 if ("Device".equals(codeString)) 568 return DEVICE; 569 if ("DeviceComponent".equals(codeString)) 570 return DEVICECOMPONENT; 571 if ("DeviceMetric".equals(codeString)) 572 return DEVICEMETRIC; 573 if ("DeviceUseRequest".equals(codeString)) 574 return DEVICEUSEREQUEST; 575 if ("DeviceUseStatement".equals(codeString)) 576 return DEVICEUSESTATEMENT; 577 if ("DiagnosticOrder".equals(codeString)) 578 return DIAGNOSTICORDER; 579 if ("DiagnosticReport".equals(codeString)) 580 return DIAGNOSTICREPORT; 581 if ("DocumentManifest".equals(codeString)) 582 return DOCUMENTMANIFEST; 583 if ("DocumentReference".equals(codeString)) 584 return DOCUMENTREFERENCE; 585 if ("DomainResource".equals(codeString)) 586 return DOMAINRESOURCE; 587 if ("EligibilityRequest".equals(codeString)) 588 return ELIGIBILITYREQUEST; 589 if ("EligibilityResponse".equals(codeString)) 590 return ELIGIBILITYRESPONSE; 591 if ("Encounter".equals(codeString)) 592 return ENCOUNTER; 593 if ("EnrollmentRequest".equals(codeString)) 594 return ENROLLMENTREQUEST; 595 if ("EnrollmentResponse".equals(codeString)) 596 return ENROLLMENTRESPONSE; 597 if ("EpisodeOfCare".equals(codeString)) 598 return EPISODEOFCARE; 599 if ("ExpansionProfile".equals(codeString)) 600 return EXPANSIONPROFILE; 601 if ("ExplanationOfBenefit".equals(codeString)) 602 return EXPLANATIONOFBENEFIT; 603 if ("FamilyMemberHistory".equals(codeString)) 604 return FAMILYMEMBERHISTORY; 605 if ("Flag".equals(codeString)) 606 return FLAG; 607 if ("Goal".equals(codeString)) 608 return GOAL; 609 if ("Group".equals(codeString)) 610 return GROUP; 611 if ("GuidanceResponse".equals(codeString)) 612 return GUIDANCERESPONSE; 613 if ("HealthcareService".equals(codeString)) 614 return HEALTHCARESERVICE; 615 if ("ImagingExcerpt".equals(codeString)) 616 return IMAGINGEXCERPT; 617 if ("ImagingObjectSelection".equals(codeString)) 618 return IMAGINGOBJECTSELECTION; 619 if ("ImagingStudy".equals(codeString)) 620 return IMAGINGSTUDY; 621 if ("Immunization".equals(codeString)) 622 return IMMUNIZATION; 623 if ("ImmunizationRecommendation".equals(codeString)) 624 return IMMUNIZATIONRECOMMENDATION; 625 if ("ImplementationGuide".equals(codeString)) 626 return IMPLEMENTATIONGUIDE; 627 if ("Library".equals(codeString)) 628 return LIBRARY; 629 if ("Linkage".equals(codeString)) 630 return LINKAGE; 631 if ("List".equals(codeString)) 632 return LIST; 633 if ("Location".equals(codeString)) 634 return LOCATION; 635 if ("Measure".equals(codeString)) 636 return MEASURE; 637 if ("MeasureReport".equals(codeString)) 638 return MEASUREREPORT; 639 if ("Media".equals(codeString)) 640 return MEDIA; 641 if ("Medication".equals(codeString)) 642 return MEDICATION; 643 if ("MedicationAdministration".equals(codeString)) 644 return MEDICATIONADMINISTRATION; 645 if ("MedicationDispense".equals(codeString)) 646 return MEDICATIONDISPENSE; 647 if ("MedicationOrder".equals(codeString)) 648 return MEDICATIONORDER; 649 if ("MedicationStatement".equals(codeString)) 650 return MEDICATIONSTATEMENT; 651 if ("MessageHeader".equals(codeString)) 652 return MESSAGEHEADER; 653 if ("ModuleDefinition".equals(codeString)) 654 return MODULEDEFINITION; 655 if ("NamingSystem".equals(codeString)) 656 return NAMINGSYSTEM; 657 if ("NutritionOrder".equals(codeString)) 658 return NUTRITIONORDER; 659 if ("Observation".equals(codeString)) 660 return OBSERVATION; 661 if ("OperationDefinition".equals(codeString)) 662 return OPERATIONDEFINITION; 663 if ("OperationOutcome".equals(codeString)) 664 return OPERATIONOUTCOME; 665 if ("Order".equals(codeString)) 666 return ORDER; 667 if ("OrderResponse".equals(codeString)) 668 return ORDERRESPONSE; 669 if ("OrderSet".equals(codeString)) 670 return ORDERSET; 671 if ("Organization".equals(codeString)) 672 return ORGANIZATION; 673 if ("Parameters".equals(codeString)) 674 return PARAMETERS; 675 if ("Patient".equals(codeString)) 676 return PATIENT; 677 if ("PaymentNotice".equals(codeString)) 678 return PAYMENTNOTICE; 679 if ("PaymentReconciliation".equals(codeString)) 680 return PAYMENTRECONCILIATION; 681 if ("Person".equals(codeString)) 682 return PERSON; 683 if ("Practitioner".equals(codeString)) 684 return PRACTITIONER; 685 if ("PractitionerRole".equals(codeString)) 686 return PRACTITIONERROLE; 687 if ("Procedure".equals(codeString)) 688 return PROCEDURE; 689 if ("ProcedureRequest".equals(codeString)) 690 return PROCEDUREREQUEST; 691 if ("ProcessRequest".equals(codeString)) 692 return PROCESSREQUEST; 693 if ("ProcessResponse".equals(codeString)) 694 return PROCESSRESPONSE; 695 if ("Protocol".equals(codeString)) 696 return PROTOCOL; 697 if ("Provenance".equals(codeString)) 698 return PROVENANCE; 699 if ("Questionnaire".equals(codeString)) 700 return QUESTIONNAIRE; 701 if ("QuestionnaireResponse".equals(codeString)) 702 return QUESTIONNAIRERESPONSE; 703 if ("ReferralRequest".equals(codeString)) 704 return REFERRALREQUEST; 705 if ("RelatedPerson".equals(codeString)) 706 return RELATEDPERSON; 707 if ("Resource".equals(codeString)) 708 return RESOURCE; 709 if ("RiskAssessment".equals(codeString)) 710 return RISKASSESSMENT; 711 if ("Schedule".equals(codeString)) 712 return SCHEDULE; 713 if ("SearchParameter".equals(codeString)) 714 return SEARCHPARAMETER; 715 if ("Sequence".equals(codeString)) 716 return SEQUENCE; 717 if ("Slot".equals(codeString)) 718 return SLOT; 719 if ("Specimen".equals(codeString)) 720 return SPECIMEN; 721 if ("StructureDefinition".equals(codeString)) 722 return STRUCTUREDEFINITION; 723 if ("StructureMap".equals(codeString)) 724 return STRUCTUREMAP; 725 if ("Subscription".equals(codeString)) 726 return SUBSCRIPTION; 727 if ("Substance".equals(codeString)) 728 return SUBSTANCE; 729 if ("SupplyDelivery".equals(codeString)) 730 return SUPPLYDELIVERY; 731 if ("SupplyRequest".equals(codeString)) 732 return SUPPLYREQUEST; 733 if ("Task".equals(codeString)) 734 return TASK; 735 if ("TestScript".equals(codeString)) 736 return TESTSCRIPT; 737 if ("ValueSet".equals(codeString)) 738 return VALUESET; 739 if ("VisionPrescription".equals(codeString)) 740 return VISIONPRESCRIPTION; 741 throw new FHIRException("Unknown ResourceTypes code '"+codeString+"'"); 742 } 743 public String toCode() { 744 switch (this) { 745 case ACCOUNT: return "Account"; 746 case ALLERGYINTOLERANCE: return "AllergyIntolerance"; 747 case APPOINTMENT: return "Appointment"; 748 case APPOINTMENTRESPONSE: return "AppointmentResponse"; 749 case AUDITEVENT: return "AuditEvent"; 750 case BASIC: return "Basic"; 751 case BINARY: return "Binary"; 752 case BODYSITE: return "BodySite"; 753 case BUNDLE: return "Bundle"; 754 case CAREPLAN: return "CarePlan"; 755 case CARETEAM: return "CareTeam"; 756 case CLAIM: return "Claim"; 757 case CLAIMRESPONSE: return "ClaimResponse"; 758 case CLINICALIMPRESSION: return "ClinicalImpression"; 759 case CODESYSTEM: return "CodeSystem"; 760 case COMMUNICATION: return "Communication"; 761 case COMMUNICATIONREQUEST: return "CommunicationRequest"; 762 case COMPARTMENTDEFINITION: return "CompartmentDefinition"; 763 case COMPOSITION: return "Composition"; 764 case CONCEPTMAP: return "ConceptMap"; 765 case CONDITION: return "Condition"; 766 case CONFORMANCE: return "Conformance"; 767 case CONTRACT: return "Contract"; 768 case COVERAGE: return "Coverage"; 769 case DATAELEMENT: return "DataElement"; 770 case DECISIONSUPPORTRULE: return "DecisionSupportRule"; 771 case DECISIONSUPPORTSERVICEMODULE: return "DecisionSupportServiceModule"; 772 case DETECTEDISSUE: return "DetectedIssue"; 773 case DEVICE: return "Device"; 774 case DEVICECOMPONENT: return "DeviceComponent"; 775 case DEVICEMETRIC: return "DeviceMetric"; 776 case DEVICEUSEREQUEST: return "DeviceUseRequest"; 777 case DEVICEUSESTATEMENT: return "DeviceUseStatement"; 778 case DIAGNOSTICORDER: return "DiagnosticOrder"; 779 case DIAGNOSTICREPORT: return "DiagnosticReport"; 780 case DOCUMENTMANIFEST: return "DocumentManifest"; 781 case DOCUMENTREFERENCE: return "DocumentReference"; 782 case DOMAINRESOURCE: return "DomainResource"; 783 case ELIGIBILITYREQUEST: return "EligibilityRequest"; 784 case ELIGIBILITYRESPONSE: return "EligibilityResponse"; 785 case ENCOUNTER: return "Encounter"; 786 case ENROLLMENTREQUEST: return "EnrollmentRequest"; 787 case ENROLLMENTRESPONSE: return "EnrollmentResponse"; 788 case EPISODEOFCARE: return "EpisodeOfCare"; 789 case EXPANSIONPROFILE: return "ExpansionProfile"; 790 case EXPLANATIONOFBENEFIT: return "ExplanationOfBenefit"; 791 case FAMILYMEMBERHISTORY: return "FamilyMemberHistory"; 792 case FLAG: return "Flag"; 793 case GOAL: return "Goal"; 794 case GROUP: return "Group"; 795 case GUIDANCERESPONSE: return "GuidanceResponse"; 796 case HEALTHCARESERVICE: return "HealthcareService"; 797 case IMAGINGEXCERPT: return "ImagingExcerpt"; 798 case IMAGINGOBJECTSELECTION: return "ImagingObjectSelection"; 799 case IMAGINGSTUDY: return "ImagingStudy"; 800 case IMMUNIZATION: return "Immunization"; 801 case IMMUNIZATIONRECOMMENDATION: return "ImmunizationRecommendation"; 802 case IMPLEMENTATIONGUIDE: return "ImplementationGuide"; 803 case LIBRARY: return "Library"; 804 case LINKAGE: return "Linkage"; 805 case LIST: return "List"; 806 case LOCATION: return "Location"; 807 case MEASURE: return "Measure"; 808 case MEASUREREPORT: return "MeasureReport"; 809 case MEDIA: return "Media"; 810 case MEDICATION: return "Medication"; 811 case MEDICATIONADMINISTRATION: return "MedicationAdministration"; 812 case MEDICATIONDISPENSE: return "MedicationDispense"; 813 case MEDICATIONORDER: return "MedicationOrder"; 814 case MEDICATIONSTATEMENT: return "MedicationStatement"; 815 case MESSAGEHEADER: return "MessageHeader"; 816 case MODULEDEFINITION: return "ModuleDefinition"; 817 case NAMINGSYSTEM: return "NamingSystem"; 818 case NUTRITIONORDER: return "NutritionOrder"; 819 case OBSERVATION: return "Observation"; 820 case OPERATIONDEFINITION: return "OperationDefinition"; 821 case OPERATIONOUTCOME: return "OperationOutcome"; 822 case ORDER: return "Order"; 823 case ORDERRESPONSE: return "OrderResponse"; 824 case ORDERSET: return "OrderSet"; 825 case ORGANIZATION: return "Organization"; 826 case PARAMETERS: return "Parameters"; 827 case PATIENT: return "Patient"; 828 case PAYMENTNOTICE: return "PaymentNotice"; 829 case PAYMENTRECONCILIATION: return "PaymentReconciliation"; 830 case PERSON: return "Person"; 831 case PRACTITIONER: return "Practitioner"; 832 case PRACTITIONERROLE: return "PractitionerRole"; 833 case PROCEDURE: return "Procedure"; 834 case PROCEDUREREQUEST: return "ProcedureRequest"; 835 case PROCESSREQUEST: return "ProcessRequest"; 836 case PROCESSRESPONSE: return "ProcessResponse"; 837 case PROTOCOL: return "Protocol"; 838 case PROVENANCE: return "Provenance"; 839 case QUESTIONNAIRE: return "Questionnaire"; 840 case QUESTIONNAIRERESPONSE: return "QuestionnaireResponse"; 841 case REFERRALREQUEST: return "ReferralRequest"; 842 case RELATEDPERSON: return "RelatedPerson"; 843 case RESOURCE: return "Resource"; 844 case RISKASSESSMENT: return "RiskAssessment"; 845 case SCHEDULE: return "Schedule"; 846 case SEARCHPARAMETER: return "SearchParameter"; 847 case SEQUENCE: return "Sequence"; 848 case SLOT: return "Slot"; 849 case SPECIMEN: return "Specimen"; 850 case STRUCTUREDEFINITION: return "StructureDefinition"; 851 case STRUCTUREMAP: return "StructureMap"; 852 case SUBSCRIPTION: return "Subscription"; 853 case SUBSTANCE: return "Substance"; 854 case SUPPLYDELIVERY: return "SupplyDelivery"; 855 case SUPPLYREQUEST: return "SupplyRequest"; 856 case TASK: return "Task"; 857 case TESTSCRIPT: return "TestScript"; 858 case VALUESET: return "ValueSet"; 859 case VISIONPRESCRIPTION: return "VisionPrescription"; 860 case NULL: return null; 861 default: return "?"; 862 } 863 } 864 public String getSystem() { 865 return "http://hl7.org/fhir/resource-types"; 866 } 867 public String getDefinition() { 868 switch (this) { 869 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 centres, etc."; 870 case ALLERGYINTOLERANCE: return "Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance."; 871 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)."; 872 case APPOINTMENTRESPONSE: return "A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection."; 873 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."; 874 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."; 875 case BINARY: return "A binary resource can contain any content, whether text, image, pdf, zip archive, etc."; 876 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."; 877 case BUNDLE: return "A container for a collection of resources."; 878 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."; 879 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."; 880 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."; 881 case CLAIMRESPONSE: return "This resource provides the adjudication details from the processing of a Claim resource."; 882 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."; 883 case CODESYSTEM: return "A code system resource specifies a set of codes drawn from one or more code systems."; 884 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."; 885 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."; 886 case COMPARTMENTDEFINITION: return "A compartment definition that defines how resources are accessed on a server."; 887 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."; 888 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."; 889 case CONDITION: return "Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses including: recording a diagnosis during an encounter; populating a problem list or a summary statement, such as a discharge summary."; 890 case CONFORMANCE: return "A conformance statement is a set of capabilities of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation."; 891 case CONTRACT: return "A formal agreement between parties regarding the conduct of business, exchange of information or other matters."; 892 case COVERAGE: return "Financial instrument which may be used to pay for or reimburse health care products and services."; 893 case DATAELEMENT: return "The formal description of a single piece of information that can be gathered and reported."; 894 case DECISIONSUPPORTRULE: return "This resource defines a decision support rule of the form [on Event] if Condition then Action. It is intended to be a shareable, computable definition of a actions that should be taken whenever some condition is met in response to a particular event or events."; 895 case DECISIONSUPPORTSERVICEMODULE: return "The DecisionSupportServiceModule describes a unit of decision support functionality that is made available as a service, such as immunization modules or drug-drug interaction checking."; 896 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."; 897 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 includes 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."; 898 case DEVICECOMPONENT: return "Describes the characteristics, operational status and capabilities of a medical-related component of a medical device."; 899 case DEVICEMETRIC: return "Describes a measurement, calculation or setting capability of a medical device."; 900 case DEVICEUSEREQUEST: 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."; 901 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."; 902 case DIAGNOSTICORDER: return "A record of a request for a diagnostic investigation service to be performed."; 903 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."; 904 case DOCUMENTMANIFEST: return "A manifest that defines a set of documents."; 905 case DOCUMENTREFERENCE: return "A reference to a document ."; 906 case DOMAINRESOURCE: return "A resource that includes narrative, extensions, and contained resources."; 907 case ELIGIBILITYREQUEST: return "This resource provides the insurance eligibility details from the insurer regarding a specified coverage and optionally some class of service."; 908 case ELIGIBILITYRESPONSE: return "This resource provides eligibility and plan details from the processing of an Eligibility resource."; 909 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."; 910 case ENROLLMENTREQUEST: return "This resource provides the insurance enrollment details to the insurer regarding a specified coverage."; 911 case ENROLLMENTRESPONSE: return "This resource provides enrollment and plan details from the processing of an Enrollment resource."; 912 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."; 913 case EXPANSIONPROFILE: return "Resource to define constraints on the Expansion of a FHIR ValueSet."; 914 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."; 915 case FAMILYMEMBERHISTORY: return "Significant health events and conditions for a person related to the patient relevant in the context of care for the patient."; 916 case FLAG: return "Prospective warnings of potential issues when providing care to the patient."; 917 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."; 918 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."; 919 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."; 920 case HEALTHCARESERVICE: return "The details of a healthcare service available at a location."; 921 case IMAGINGEXCERPT: return "A manifest of a set of DICOM Service-Object Pair Instances (SOP Instances). The referenced SOP Instances (images or other content) are for a single patient, and may be from one or more studies. The referenced SOP Instances have been selected for a purpose, such as quality assurance, conference, or consult. Reflecting that range of purposes, typical ImagingExcerpt resources may include all SOP Instances in a study (perhaps for sharing through a Health Information Exchange); key images from multiple studies (for reference by a referring or treating physician); a multi-frame ultrasound instance (\"cine\" video clip) and a set of measurements taken from that instance (for inclusion in a teaching file); and so on."; 922 case IMAGINGOBJECTSELECTION: return "A manifest of a set of DICOM Service-Object Pair Instances (SOP Instances). The referenced SOP Instances (images or other content) are for a single patient, and may be from one or more studies. The referenced SOP Instances have been selected for a purpose, such as quality assurance, conference, or consult. Reflecting that range of purposes, typical ImagingObjectSelection resources may include all SOP Instances in a study (perhaps for sharing through a Health Information Exchange); key images from multiple studies (for reference by a referring or treating physician); a multi-frame ultrasound instance (\"cine\" video clip) and a set of measurements taken from that instance (for inclusion in a teaching file); and so on."; 923 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."; 924 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."; 925 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."; 926 case IMPLEMENTATIONGUIDE: return "A set of rules or 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."; 927 case LIBRARY: return "The Library resource provides a representation container for knowledge artifact component definitions. It is effectively an exposure of the header information for a CQL/ELM library."; 928 case LINKAGE: return "Identifies two or more records (resource instances) that are referring to the same real-world \"occurrence\"."; 929 case LIST: return "A set of information summarized from a list of other resources."; 930 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."; 931 case MEASURE: return "The Measure resource provides the definition of a quality measure."; 932 case MEASUREREPORT: return "The MeasureReport resource contains the results of evaluating a measure."; 933 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."; 934 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."; 935 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."; 936 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."; 937 case MEDICATIONORDER: return "An order for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called \"MedicationOrder\" rather than \"MedicationPrescription\" to generalize the use across inpatient and outpatient settings as well as for care plans, etc."; 938 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 e.g. 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."; 939 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."; 940 case MODULEDEFINITION: return "The ModuleDefinition resource defines the data requirements for a quality artifact."; 941 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."; 942 case NUTRITIONORDER: return "A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident."; 943 case OBSERVATION: return "Measurements and simple assertions made about a patient, device or other subject."; 944 case OPERATIONDEFINITION: return "A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction)."; 945 case OPERATIONOUTCOME: return "A collection of error, warning or information messages that result from a system action."; 946 case ORDER: return "A request to perform an action."; 947 case ORDERRESPONSE: return "A response to an order."; 948 case ORDERSET: return "This resource allows for the definition of an order set as a sharable, consumable, and executable artifact in support of clinical decision support."; 949 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."; 950 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."; 951 case PATIENT: return "Demographics and other administrative information about an individual or animal receiving care or other health-related services."; 952 case PAYMENTNOTICE: return "This resource provides the status of the payment for goods and services rendered, and the request and response resource references."; 953 case PAYMENTRECONCILIATION: return "This resource provides payment details and claim references supporting a bulk payment."; 954 case PERSON: return "Demographics and administrative information about a person independent of a specific health-related context."; 955 case PRACTITIONER: return "A person who is directly or indirectly involved in the provisioning of healthcare."; 956 case PRACTITIONERROLE: return "A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time."; 957 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."; 958 case PROCEDUREREQUEST: return "A request for a procedure to be performed. May be a proposal or an order."; 959 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."; 960 case PROCESSRESPONSE: return "This resource provides processing status, errors and notes from the processing of a resource."; 961 case PROTOCOL: return "A definition of behaviors to be taken in particular circumstances, often including conditions, options and other decision points."; 962 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."; 963 case QUESTIONNAIRE: return "A structured set of questions intended to guide the collection of answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions."; 964 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 underlying questions."; 965 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."; 966 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."; 967 case RESOURCE: return "This is the base resource type for everything."; 968 case RISKASSESSMENT: return "An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome."; 969 case SCHEDULE: return "A container for slot(s) of time that may be available for booking appointments."; 970 case SEARCHPARAMETER: return "A search parameter that defines a named search item that can be used to search/filter on a resource."; 971 case SEQUENCE: return "Variation and Sequence data."; 972 case SLOT: return "A slot of time on a schedule that may be available for booking appointments."; 973 case SPECIMEN: return "A sample to be used for analysis."; 974 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."; 975 case STRUCTUREMAP: return "A Map of relationships between 2 structures that can be used to transform data."; 976 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."; 977 case SUBSTANCE: return "A homogeneous material with a definite composition."; 978 case SUPPLYDELIVERY: return "Record of delivery of what is supplied."; 979 case SUPPLYREQUEST: return "A record of a request for a medication, substance or device used in the healthcare setting."; 980 case TASK: return "A task to be performed."; 981 case TESTSCRIPT: return "TestScript is a resource that specifies a suite of tests against a FHIR server implementation to determine compliance against the FHIR specification."; 982 case VALUESET: return "A value set specifies a set of codes drawn from one or more code systems."; 983 case VISIONPRESCRIPTION: return "An authorization for the supply of glasses and/or contact lenses to a patient."; 984 case NULL: return null; 985 default: return "?"; 986 } 987 } 988 public String getDisplay() { 989 switch (this) { 990 case ACCOUNT: return "Account"; 991 case ALLERGYINTOLERANCE: return "AllergyIntolerance"; 992 case APPOINTMENT: return "Appointment"; 993 case APPOINTMENTRESPONSE: return "AppointmentResponse"; 994 case AUDITEVENT: return "AuditEvent"; 995 case BASIC: return "Basic"; 996 case BINARY: return "Binary"; 997 case BODYSITE: return "BodySite"; 998 case BUNDLE: return "Bundle"; 999 case CAREPLAN: return "CarePlan"; 1000 case CARETEAM: return "CareTeam"; 1001 case CLAIM: return "Claim"; 1002 case CLAIMRESPONSE: return "ClaimResponse"; 1003 case CLINICALIMPRESSION: return "ClinicalImpression"; 1004 case CODESYSTEM: return "CodeSystem"; 1005 case COMMUNICATION: return "Communication"; 1006 case COMMUNICATIONREQUEST: return "CommunicationRequest"; 1007 case COMPARTMENTDEFINITION: return "CompartmentDefinition"; 1008 case COMPOSITION: return "Composition"; 1009 case CONCEPTMAP: return "ConceptMap"; 1010 case CONDITION: return "Condition"; 1011 case CONFORMANCE: return "Conformance"; 1012 case CONTRACT: return "Contract"; 1013 case COVERAGE: return "Coverage"; 1014 case DATAELEMENT: return "DataElement"; 1015 case DECISIONSUPPORTRULE: return "DecisionSupportRule"; 1016 case DECISIONSUPPORTSERVICEMODULE: return "DecisionSupportServiceModule"; 1017 case DETECTEDISSUE: return "DetectedIssue"; 1018 case DEVICE: return "Device"; 1019 case DEVICECOMPONENT: return "DeviceComponent"; 1020 case DEVICEMETRIC: return "DeviceMetric"; 1021 case DEVICEUSEREQUEST: return "DeviceUseRequest"; 1022 case DEVICEUSESTATEMENT: return "DeviceUseStatement"; 1023 case DIAGNOSTICORDER: return "DiagnosticOrder"; 1024 case DIAGNOSTICREPORT: return "DiagnosticReport"; 1025 case DOCUMENTMANIFEST: return "DocumentManifest"; 1026 case DOCUMENTREFERENCE: return "DocumentReference"; 1027 case DOMAINRESOURCE: return "DomainResource"; 1028 case ELIGIBILITYREQUEST: return "EligibilityRequest"; 1029 case ELIGIBILITYRESPONSE: return "EligibilityResponse"; 1030 case ENCOUNTER: return "Encounter"; 1031 case ENROLLMENTREQUEST: return "EnrollmentRequest"; 1032 case ENROLLMENTRESPONSE: return "EnrollmentResponse"; 1033 case EPISODEOFCARE: return "EpisodeOfCare"; 1034 case EXPANSIONPROFILE: return "ExpansionProfile"; 1035 case EXPLANATIONOFBENEFIT: return "ExplanationOfBenefit"; 1036 case FAMILYMEMBERHISTORY: return "FamilyMemberHistory"; 1037 case FLAG: return "Flag"; 1038 case GOAL: return "Goal"; 1039 case GROUP: return "Group"; 1040 case GUIDANCERESPONSE: return "GuidanceResponse"; 1041 case HEALTHCARESERVICE: return "HealthcareService"; 1042 case IMAGINGEXCERPT: return "ImagingExcerpt"; 1043 case IMAGINGOBJECTSELECTION: return "ImagingObjectSelection"; 1044 case IMAGINGSTUDY: return "ImagingStudy"; 1045 case IMMUNIZATION: return "Immunization"; 1046 case IMMUNIZATIONRECOMMENDATION: return "ImmunizationRecommendation"; 1047 case IMPLEMENTATIONGUIDE: return "ImplementationGuide"; 1048 case LIBRARY: return "Library"; 1049 case LINKAGE: return "Linkage"; 1050 case LIST: return "List"; 1051 case LOCATION: return "Location"; 1052 case MEASURE: return "Measure"; 1053 case MEASUREREPORT: return "MeasureReport"; 1054 case MEDIA: return "Media"; 1055 case MEDICATION: return "Medication"; 1056 case MEDICATIONADMINISTRATION: return "MedicationAdministration"; 1057 case MEDICATIONDISPENSE: return "MedicationDispense"; 1058 case MEDICATIONORDER: return "MedicationOrder"; 1059 case MEDICATIONSTATEMENT: return "MedicationStatement"; 1060 case MESSAGEHEADER: return "MessageHeader"; 1061 case MODULEDEFINITION: return "ModuleDefinition"; 1062 case NAMINGSYSTEM: return "NamingSystem"; 1063 case NUTRITIONORDER: return "NutritionOrder"; 1064 case OBSERVATION: return "Observation"; 1065 case OPERATIONDEFINITION: return "OperationDefinition"; 1066 case OPERATIONOUTCOME: return "OperationOutcome"; 1067 case ORDER: return "Order"; 1068 case ORDERRESPONSE: return "OrderResponse"; 1069 case ORDERSET: return "OrderSet"; 1070 case ORGANIZATION: return "Organization"; 1071 case PARAMETERS: return "Parameters"; 1072 case PATIENT: return "Patient"; 1073 case PAYMENTNOTICE: return "PaymentNotice"; 1074 case PAYMENTRECONCILIATION: return "PaymentReconciliation"; 1075 case PERSON: return "Person"; 1076 case PRACTITIONER: return "Practitioner"; 1077 case PRACTITIONERROLE: return "PractitionerRole"; 1078 case PROCEDURE: return "Procedure"; 1079 case PROCEDUREREQUEST: return "ProcedureRequest"; 1080 case PROCESSREQUEST: return "ProcessRequest"; 1081 case PROCESSRESPONSE: return "ProcessResponse"; 1082 case PROTOCOL: return "Protocol"; 1083 case PROVENANCE: return "Provenance"; 1084 case QUESTIONNAIRE: return "Questionnaire"; 1085 case QUESTIONNAIRERESPONSE: return "QuestionnaireResponse"; 1086 case REFERRALREQUEST: return "ReferralRequest"; 1087 case RELATEDPERSON: return "RelatedPerson"; 1088 case RESOURCE: return "Resource"; 1089 case RISKASSESSMENT: return "RiskAssessment"; 1090 case SCHEDULE: return "Schedule"; 1091 case SEARCHPARAMETER: return "SearchParameter"; 1092 case SEQUENCE: return "Sequence"; 1093 case SLOT: return "Slot"; 1094 case SPECIMEN: return "Specimen"; 1095 case STRUCTUREDEFINITION: return "StructureDefinition"; 1096 case STRUCTUREMAP: return "StructureMap"; 1097 case SUBSCRIPTION: return "Subscription"; 1098 case SUBSTANCE: return "Substance"; 1099 case SUPPLYDELIVERY: return "SupplyDelivery"; 1100 case SUPPLYREQUEST: return "SupplyRequest"; 1101 case TASK: return "Task"; 1102 case TESTSCRIPT: return "TestScript"; 1103 case VALUESET: return "ValueSet"; 1104 case VISIONPRESCRIPTION: return "VisionPrescription"; 1105 case NULL: return null; 1106 default: return "?"; 1107 } 1108 } 1109 1110 1111}