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 
| Support | ||
|---|---|---|
| Generally useful resources wherever resources are used | ||
| Name | Aliases | Description |
| Media | A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference. | |
| Other | Z-resource, Extension-resource | Other is a conformant for handling resource concepts not yet defined for FHIR or outside HL7's scope of interest. |
| Provenance | History, Event | Provenance information that describes the activity that led to the creation of a set of resources. This information can be used to help determine their reliability or trace where the information in them came from. The focus of the provenance resource is record keeping, audit and traceability, and not explicit statements of clinical significance. |
| SecurityEvent | 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. | |
| Binary | Pure Binary Content - opaque to FHIR | |
| Documents & Structure Handling | ||
| Supporting management of documents and other organizing structures | ||
| Name | Aliases | Description |
| List | Collection, WorkingList | A set of information summarized from a list of other resources. |
| 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. | |
| DocumentReference | A reference to a document. | |
| DocumentManifest | A manifest that defines a set of documents. | |
| Exchange | ||
| Used to support the process of exchanging data | ||
| Name | Aliases | Description |
| 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. | |
| OperationOutcome | A collection of error, warning or information messages that result from a system action. | |
| Subscription | WebHook, Hook | Todo. |
| Bundle | A container for a group of resources. | |
| Binary | A binary resource can contain any content, whether text, image, pdf, zip archive, etc. | |
| Conformance | ||
| Make statements about how resources are used | ||
| Name | Aliases | Description |
| Conformance | A conformance statement is a set of requirements for a desired implementation or a description of how a target application fulfills those requirements in a particular implementation. | |
| Profile | Template | A Resource Profile - a statement of use of one or more FHIR Resources. It may include constraints on Resources and Data Types, Terminology Binding Statements and Extension Definitions. |
| ExtensionDefinition | Extension | Defines an extension that can be used in resources. |
| DataElement | Master Observation, Data Element | The formal description of a single piece of information that can be gathered and reported. |
| SearchParameter | A Search Parameter that defines a named search item that can be used to search/filter on a resource. | |
| OperationDefinition | A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). | |
| ValueSet | A value set specifies a set of codes drawn from one or more code systems. | |
| 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. | |
| 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. | |
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