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