This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/resource-types |
Name: | ResourceType |
Definition: | One of the resource types defined as part of FHIR. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.2.resource-types (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
This expansion generated 06 Dec 2016
This value set contains 117 concepts
Expansion based on http://hl7.org/fhir/resource-types version 1.8.0
All codes from system http://hl7.org/fhir/resource-types
Code | Display | Definition |
Account | Account | 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. |
ActivityDefinition | ActivityDefinition | This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context. |
AllergyIntolerance | AllergyIntolerance | Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. |
Appointment | Appointment | 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). |
AppointmentResponse | AppointmentResponse | A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection. |
AuditEvent | AuditEvent | 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. |
Basic | Basic | 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. |
Binary | Binary | A binary resource can contain any content, whether text, image, pdf, zip archive, etc. |
BodySite | BodySite | 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. |
Bundle | Bundle | A container for a collection of resources. |
CapabilityStatement | CapabilityStatement | 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. |
CarePlan | CarePlan | 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. |
CareTeam | CareTeam | The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. |
Claim | Claim | 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. |
ClaimResponse | ClaimResponse | This resource provides the adjudication details from the processing of a Claim resource. |
ClinicalImpression | ClinicalImpression | 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. |
CodeSystem | CodeSystem | A code system resource specifies a set of codes drawn from one or more code systems. |
Communication | Communication | 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. |
CommunicationRequest | CommunicationRequest | 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. |
CompartmentDefinition | CompartmentDefinition | A compartment definition that defines how resources are accessed on a server. |
Composition | Composition | 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. |
ConceptMap | ConceptMap | 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. |
Condition | Condition | 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. |
Consent | Consent | 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. |
Contract | Contract | A formal agreement between parties regarding the conduct of business, exchange of information or other matters. |
Coverage | Coverage | Financial instrument which may be used to pay for or reimburse health care products and services. |
DataElement | DataElement | The formal description of a single piece of information that can be gathered and reported. |
DetectedIssue | DetectedIssue | 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. |
Device | Device | 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. |
DeviceComponent | DeviceComponent | Describes the characteristics, operational status and capabilities of a medical-related component of a medical device. |
DeviceMetric | DeviceMetric | Describes a measurement, calculation or setting capability of a medical device. |
DeviceUseRequest | DeviceUseRequest | 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. |
DeviceUseStatement | DeviceUseStatement | 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. |
DiagnosticReport | DiagnosticReport | 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. |
DiagnosticRequest | DiagnosticRequest | A record of a request for a diagnostic investigation service to be performed. |
DocumentManifest | DocumentManifest | A manifest that defines a set of documents. |
DocumentReference | DocumentReference | A reference to a document . |
DomainResource | DomainResource | A resource that includes narrative, extensions, and contained resources. |
EligibilityRequest | EligibilityRequest | This resource provides the details from the insurer to identify a specified coverage and optionally some class of service. |
EligibilityResponse | EligibilityResponse | This resource provides eligibility and plan details from the processing of an Eligibility resource. |
Encounter | Encounter | 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. |
Endpoint | Endpoint | 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. |
EnrollmentRequest | EnrollmentRequest | This resource provides the insurance enrollment details to the insurer regarding a specified coverage. |
EnrollmentResponse | EnrollmentResponse | This resource provides enrollment and plan details from the processing of an Enrollment resource. |
EpisodeOfCare | EpisodeOfCare | 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. |
ExpansionProfile | ExpansionProfile | Resource to define constraints on the Expansion of a FHIR ValueSet. |
ExplanationOfBenefit | ExplanationOfBenefit | 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. |
FamilyMemberHistory | FamilyMemberHistory | Significant health events and conditions for a person related to the patient relevant in the context of care for the patient. |
Flag | Flag | Prospective warnings of potential issues when providing care to the patient. |
Goal | Goal | 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. |
Group | Group | 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. |
GuidanceResponse | GuidanceResponse | 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. |
HealthcareService | HealthcareService | The details of a healthcare service available at a location. |
ImagingManifest | ImagingManifest | 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 may have been selected for a purpose, such as conference, or consult. Reflecting a range of sharing purposes, typical ImagingManifest 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); both 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. |
ImagingStudy | ImagingStudy | 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. |
Immunization | Immunization | 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. |
ImmunizationRecommendation | ImmunizationRecommendation | 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. |
ImplementationGuide | ImplementationGuide | 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. |
Library | Library | The Library resource is a general-purpose container for knowledge asset definitions. It can be used to describe and expose exist knowledge assets such as logic libraries and information model descriptions, as well as to describe a collection of knowledge assets. |
Linkage | Linkage | Identifies two or more records (resource instances) that are referring to the same real-world "occurrence". |
List | List | A set of information summarized from a list of other resources. |
Location | Location | Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated. |
Measure | Measure | The Measure resource provides the definition of a quality measure. |
MeasureReport | MeasureReport | The MeasureReport resource contains the results of evaluating a measure. |
Media | Media | A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference. |
Medication | Medication | This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication. |
MedicationAdministration | MedicationAdministration | 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. |
MedicationDispense | MedicationDispense | 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. |
MedicationRequest | MedicationRequest | An order 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 as well as for care plans, etc and to harmonize with workflow patterns. |
MedicationStatement | MedicationStatement | 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 The 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. |
MessageDefinition | MessageDefinition | 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. |
MessageHeader | MessageHeader | 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. |
NamingSystem | NamingSystem | 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. |
NutritionRequest | NutritionRequest | A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. |
Observation | Observation | Measurements and simple assertions made about a patient, device or other subject. |
OperationDefinition | OperationDefinition | A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). |
OperationOutcome | OperationOutcome | A collection of error, warning or information messages that result from a system action. |
Organization | Organization | 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. |
Parameters | Parameters | 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. |
Patient | Patient | Demographics and other administrative information about an individual or animal receiving care or other health-related services. |
PaymentNotice | PaymentNotice | This resource provides the status of the payment for goods and services rendered, and the request and response resource references. |
PaymentReconciliation | PaymentReconciliation | This resource provides payment details and claim references supporting a bulk payment. |
Person | Person | Demographics and administrative information about a person independent of a specific health-related context. |
PlanDefinition | PlanDefinition | 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. |
Practitioner | Practitioner | A person who is directly or indirectly involved in the provisioning of healthcare. |
PractitionerRole | PractitionerRole | A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. |
Procedure | Procedure | 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. |
ProcedureRequest | ProcedureRequest | A request for a procedure to be performed. May be a proposal or an order. |
ProcessRequest | ProcessRequest | 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. |
ProcessResponse | ProcessResponse | This resource provides processing status, errors and notes from the processing of a resource. |
Provenance | Provenance | 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. |
Questionnaire | Questionnaire | 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. |
QuestionnaireResponse | QuestionnaireResponse | 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. |
ReferralRequest | ReferralRequest | 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. |
RelatedPerson | RelatedPerson | 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. |
RequestGroup | RequestGroup | 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". |
ResearchStudy | ResearchStudy | 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. ResearchStudies involve the gathering of information about human or animal subjects. |
ResearchSubject | ResearchSubject | 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. ResearchStudies involve the gathering of information about human or animal subjects. |
Resource | Resource | This is the base resource type for everything. |
RiskAssessment | RiskAssessment | An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. |
Schedule | Schedule | A container for slot(s) of time that may be available for booking appointments. |
SearchParameter | SearchParameter | A search parameter that defines a named search item that can be used to search/filter on a resource. |
Sequence | Sequence | Raw data describing a biological sequence. |
ServiceDefinition | ServiceDefinition | 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. |
Slot | Slot | A slot of time on a schedule that may be available for booking appointments. |
Specimen | Specimen | A sample to be used for analysis. |
StructureDefinition | StructureDefinition | 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. |
StructureMap | StructureMap | A Map of relationships between 2 structures that can be used to transform data. |
Subscription | Subscription | 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. |
Substance | Substance | A homogeneous material with a definite composition. |
SupplyDelivery | SupplyDelivery | Record of delivery of what is supplied. |
SupplyRequest | SupplyRequest | A record of a request for a medication, substance or device used in the healthcare setting. |
Task | Task | A task to be performed. |
TestReport | TestReport | TestReport is a resource that includes summary information on the results of executing a TestScript. |
TestScript | TestScript | TestScript is a resource that specifies a suite of tests against a FHIR server implementation to determine compliance against the FHIR specification. |
ValueSet | ValueSet | A value set specifies a set of codes drawn from one or more code systems. |
VisionPrescription | VisionPrescription | An authorization for the supply of glasses and/or contact lenses to a patient. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |