This page is part of the FHIR Specification (v0.06: DSTU 1 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
The FHIR specification presently defines the following resources:
The list of resources is growing as FHIR is developed. Over the coming months, the number of resources and the number of those that have been vetted by HL7 committees will grow. A list of hypothesized list of resources can be found on the HL7 wiki. Feel free to add any you feel are missing or engage with one of the HL7 Work Groups to submit a proposal to define a resource of particular interest.
Foundation | |
---|---|
Basic resources that provide definitional and functional support for using resources | |
Profile | A statement of use of FHIR. May include constraints on Resources, Terminology Binding Statements and Extension Definitions |
Conformance | A conformance statement about how an application or implementation supports FHIR or the set of requirements for a desired implementation |
ValueSet | A set of defined codes from one or more code systems that may be bound to a context. |
Provenance | Information associated with another resource that can be used to help determine its reliability or trace where the information in it came from |
SecurityEvent | A record of an event suitable for tracking in a security log |
List | A summary built from a list of other resources |
XdsFolder | A folder belonging to a patient to which resources may add themselves (derived from XDS) |
Technical | |
Resources defined to support particular implementation contexts. These are generally not made available directly through a RESTful service | |
Message | Describes a transmission requesting action on a bundle of one or more resources or a response to such a request. |
Document | A documentation of healthcare-related information that is assembled together into a single statement of meaning that establishes its own context. |
IssueReport | A set of error, warning or information messages that result from a system action. |
XdsEntry | A reference to a document in a document registry or repository (derived from XDS) |
Administration | |
Administrative resources tie clinical processes to the administrative process that support them - patient and provider management. These resources are also known as the attribution layer | |
Person | Identifies a person - basic demographics. |
Animal | Identifies an animal - basic demographics, species etc, as well as other animals or people that are related to it by birth or ownership arrangements |
Patient | A person or animal receiving care administratively linked with an organization |
Organization | Identifies an organization, its formal accreditations and sub, super and partner organizations |
Agent | A person who represents an organization in some capacity (role) |
Device | A manufactured entity that is used in the provision of healthcare. The device may be a machine, an insert, a computer, an application, etc. |
Group | A group of other administrative resources. The group can be listed, or identified by some trait |
Financial | |
Resources that address the question of payments, insurance etc | |
Coverage | A statement that the cost of a patient's care is covered by some arrangement with another party |
Medications | |
Resources defined to support the medication administration and management process | |
Prescription | An instruction to supply and/or administer a medication to a patient |
MedicationAdministration | A record of actually administering a medication to a patient |
Clinical | |
General Clinical resources | |
Observation | Used to record simple observations of a patient by a clinician |
Problem | Used to record detailed information about problems or diagnoses recognised by a clinician |
LabReport | Lab A provides a report (text and/or structured data with analysis and specimen details) concerning Patient B as requested by Agent C for reason D |
This is an old version of FHIR retained for archive purposes. Do not use for anything else
Implementers are welcome to experiment with the content defined here, but should note that the contents are subject to change without prior notice.
© HL7.org 2011 - 2012. FHIR v0.06 generated on Tue, Dec 4, 2012 00:04+1100. License