This page is part of the FHIR Specification (v1.2.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
Individuals:
Groups:
Entities:
Devices:
Patient Management:
Scheduling:
Workflow #1:
Workflow #2:
FHIR Infrastructure Work Group | Maturity Level: N/A | Ballot Status: DSTU 2 |
Individuals | |||
---|---|---|---|
Track individuals involved in the provision of healthcare | |||
Name | Aliases | Description | |
Patient | SubjectOfCare Client Resident | Demographics and other administrative information about an individual or animal receiving care or other health-related services. | |
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. | ||
Practitioner | A person who is directly or indirectly involved in the provisioning of healthcare. | ||
Groups | |||
Track grouping entities involved in the provision of healthcare | |||
Name | Aliases | Description | |
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. | ||
HealthcareService | The details of a healthcare service available at a location. | ||
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. | ||
Entities | |||
Track other kinds of entities used in the provision of healthcare | |||
Name | Aliases | Description | |
Location | Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated. | ||
Person | Demographics and administrative information about a person independent of a specific health-related context. | ||
Substance | A homogeneous material with a definite composition. | ||
Devices | |||
Devices and their capabilities | |||
Name | Aliases | Description | |
Device | This resource identifies an instance 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 | Describes the characteristics, operational status and capabilities of a medical-related component of a medical device. | ||
DeviceMetric | Describes a measurement, calculation or setting capability of a medical device. | ||
Patient Management | |||
Tracking the status of patients | |||
Name | Aliases | Description | |
Encounter | Visit | 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. | |
EpisodeOfCare | Case Program Problem | 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. | |
Flag | Barriers to Care, Alert | Prospective warnings of potential issues when providing care to the patient. | |
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. | ||
Scheduling/Ordering | |||
Creation and management of appointments as well as workflow around orders. | |||
Note: The PA work-group would appreciate contributions to enhance the appointment resource(s) to cover additional use-cases if required for implementations | |||
Name | Aliases | Description | |
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 | A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection. | ||
Schedule | Availability | A container for slot(s) of time that may be available for booking appointments. | |
Slot | A slot of time on a schedule that may be available for booking appointments. | ||
Workflow | |||
General healthcare provision workflow support | |||
Name | Aliases | Description | |
Order | Request | A request to perform an action. | |
OrderResponse | A response to an order. | ||
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 | 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. | ||
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. | ||
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. | ||
ProcessDelivery | (Not defined yet) | ||
SupplyRequest | A record of a request for a medication, substance or device used in the healthcare setting. | ||
SupplyDelivery | Record of delivery of what is supplied. |
Additional Resources will be added in the future. A list of hypothesized resources can be found on the HL7 wiki . Feel free to add any you think are missing or engage with one of the HL7 Work Groups to submit a proposal to define a resource of particular interest.