<

This page is part of the FHIR Specification (v1.0.2: DSTU 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 . For a full list of available versions, see the Directory of published versions h2>

h2> <span class="sectioncount"> 6.0 <a name="6.0"> Infrastructure Resources

FHIR Infrastructure Work Group

Maturity Level : N/A

Ballot Status : DSTU 2

Binary Pure Binary Content - opaque to FHIR Query

Support Information Tracking
Generally useful resources wherever resources are used Collecting information, and tracking change to the information
Name	Aliases	Description
List Questionnaire	Collection, WorkingList Form, CRF	A structured set of information summarized from a list questions intended to guide the collection of other resources. answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions.
Media QuestionnaireResponse	Form	A photo, video, or audio recording acquired or used in healthcare. structured set of questions and their answers. The actual content may be inline or provided by direct reference. questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions.
Other Provenance	Z-resource, Extension-resource History, Event	Other is Provenance of a conformant for handling resource concepts not yet defined for FHIR or outside HL7's scope of interest. Provenance Provenance information is a record that describes the activity entities and processes involved in producing and delivering or otherwise influencing that led to the creation of resource. Provenance provides a set critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of resources. This information contextual metadata and can be used to help determine themselves become important records with their reliability or trace where the information own provenance. Provenance statement indicates clinical significance in them came from. The focus terms of the provenance resource is record keeping, audit confidence in authenticity, reliability, and traceability, trustworthiness, integrity, and not explicit statements stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of clinical significance. which may impact security, privacy, and trust policies.
SecurityEvent 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.
Document Handling Documents & Lists
Supporting Management of documents and other organizing structures
Name	Aliases	Description
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.
DocumentReference		A reference to a document. document .
DocumentManifest		A manifest that defines a set of documents.
List	Collection, WorkingList	A set of information summarized from a list of other resources.
Structure
Resources that provide basic structural support for other usages
Name	Aliases	Description
Binary		Pure Binary Content - opaque to FHIR
Basic	Z-resource, Extension-resource	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		A binary resource can contain any content, whether text, image, pdf, zip archive, etc.
Bundle		A container for a collection of resources.
Media		A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference.
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 resource(s) reference(s) that are the subject of the action as well as other Information 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.
Parameters	(Not defined yet)
Subscription	WebHook, Hook	A description of The subscription resource is used to define a query 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.
Terminology
The terminology sub-system
Name	Aliases	Description
ValueSet		A value set specifies a set of parameters. codes drawn from one or more code systems.
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.
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.
Conformance Content
Make statements about how resources are Specifying allowable content
Name	Aliases	Description
StructureDefinition	Template	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.
DataElement	Master Observation, Data Element	The formal description of a single piece of information that can be gathered and reported.
Operations Control
Specifying the behavior of operational systems
Name	Aliases	Description
Conformance		A conformance statement is a set of requirements for capabilities of a desired implementation or FHIR Server that may be used as a description statement of how a target application fulfills those requirements in actual server functionality or a particular statement of required or desired server implementation.
Profile OperationDefinition		Template A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction).
SearchParameter		A Resource Profile - search parameter that defines a statement of use of one or more FHIR Resources. It may include constraints named search item that can be used to search/filter on Resources and Data Types, Terminology Binding Statements a resource.
Miscellaineous
Managing specification and Extension Definitions. testing
Name	Aliases	Description
ValueSet ImplementationGuide		A value set specifies a set of codes drawn from one rules or more code systems. 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.
ConceptMap TestScript		A statement of relationships from one set TestScript is a resource that specifies a suite of concepts tests against a FHIR server implementation to one or more other concept systems. determine compliance against the FHIR specification.

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.