FHIR Resources Flashcards
List Level 5 matured (Normative) Resources.
There are 13 such resources
- Binary (Foundation-Other-N)
- Bundle (Foundation-Other-N)
- CapabilityStatement (Foundation-Conformance-N)
- CodeSystem (Foundation-Terminology-N)
- DomainResource (Abstract)
- Observation (Clinical-Diagnostics-N)
- OperationDefinition (Foundation-Conformance-N)
- OperationOutcome (Foundation-Other-N)
- Parameters (Foundation-Other-N)
- Patient (Base-Individuals-N)
- Resource (Abstract)
- StructureDefinition (Foundation-Conformance-N)
- ValueSet (Foundation-Terminology-N)
List the Abstract resources
- Resource (Base Resource)
- DomainResource
DomainResource
This resource extends the base Resource.
All of the listed Resources except Bundle, Parameters and Binary extend this resource.
Resource (Base Resource)
A resource is an entity that:
- has a known identity (a URL) by which it can be addressed
- identifies itself as one of the types of resource defined in this specification
- contains a set of structured data items as described by the definition of the resource type
- has an identified version that changes if the contents of the resource change
CapabilityStatement
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
(Foundation-Conformance-N)
StructureDefinition
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.
(Foundation-Conformance-N)
ImplementationGuide
A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources.
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.
(Foundation-Conformance-1)
SearchParameter
A search parameter that defines a named search item that can be used to search/filter on a resource.
(Foundation-Conformance-3)
MessageDefinition
Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted.
(Foundation-Conformance-1)
OperationDefinition
A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction).
(Foundation-Conformance-N)
CompartmentDefinition
A compartment definition that defines how resources are accessed on a server.
(Foundation-Conformance-1)
StructureMap
A Map of relationships between 2 structures that can be used to transform data.
(Foundation-Conformance-2)
GraphDefinition
A formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references.
The Graph Definition resource defines a set and makes rules about the set.
(Foundation-Conformance-1)
ExampleScenario
Example of workflow instance.
(Foundation-Conformance-0)
CodeSystem
The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content.
(Foundation-Terminology-N)
ValueSet
A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context.
Value sets link between [CodeSystem] definitions and their use in [coded elements].
(Foundation-Terminology-N)
ConceptMap
A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models.
(Foundation-Terminology-3)
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.
(Foundation-Terminology-1)
TerminologyCapabilities
A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
(Foundation-Terminology-0)
Provenance
Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource.
Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance.
Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies.
(Foundation-Security-3)
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.
(Foundation-Security-3)
Consent
A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.
(Foundation-Security-2)
Composition
A set of healthcare-related information that is assembled together into a single logical package 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.
A Composition defines the structure and narrative content necessary for a document.
However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).
(Foundation-Documents-2)
DocumentManifest
A collection of documents compiled for a purpose together with metadata that applies to the collection.(Foundation-Documents-2)