2nd DSTU Draft For Comment
This page is part of the FHIR Specification (v0.4.0: DSTU 2 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 
| Attribution | ||
|---|---|---|
| Track individuals and organizations involved in the provision of healthcare | ||
| Name | Aliases | Description |
| Patient | SubjectOfCare Client Resident | Demographics and other administrative information about a person 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. | |
| Person | Demographics and administrative information about a person independent of a specific health-related context. | |
| Practitioner | A person who is directly or indirectly involved in the provisioning of healthcare. | |
| 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. | |
| HealthcareService | The details of a Healthcare Service available at a location. | |
| Resources | ||
| Track general support resources used when healthcare is provided | ||
| Name | Aliases | Description |
| Contract | A formal agreement between parties regarding the conduct of business, exchange of information or other matters. | |
| Device | This resource identifies an instance of a manufactured thing that is used in the provision of healthcare without being substantially changed through that activity. The device may be a machine, an insert, a computer, an application, etc. This includes durable (reusable) medical equipment as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. | |
| 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. | |
| Location | Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated. | |
| Substance | A homogeneous material with a definite composition. | |
| 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. | |
| Workflow Management | ||
| Support for the processes involved in healthcare | ||
| 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. |
| 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. | |
| 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. | |
| Supply | A supply - a request for something, and provision of what is supplied. | |
| 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 scheduled healthcare event for a patient and/or practitioner(s) where a service may take place at a specific date/time. | |
| 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. | |
| Order | Request | A request to perform an action. |
| OrderResponse | A response to an order. | |
| DeviceUseRequest | Represents a request for the use of a device. | |
| ProcedureRequest | A request for a procedure to be performed. May be a proposal or an order. | |
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.
© HL7.org 2011+. FHIR DSTU (v0.4.0-4167) generated on Mon, Feb 23, 2015 09:24+1100.
Links: What's a DSTU? |
Version History |
Compare to DSTU1 |
|
Propose a change