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)
DocumentReference
A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. (Foundation-Documents-3)
CatalogEntry
Catalog entries are wrappers that contextualize items included in a catalog.(Foundation-Documents-0)
Basic
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. (Foundation-Other-1)
Binary
A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc. (Foundation-Other-N)
Bundle
A container for a collection of resources.(Foundation-Other-N)
Linkage
Identifies two or more records (resource instances) that refer to the same real-world “occurrence”. (Foundation-Other-0)
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.(Foundation-Other-4)
OperationOutcome
A collection of error, warning, or information messages that result from a system action. (Foundation-Other-N)
Parameters
This resource is a non-persisted resource used to pass information into and back from an operation. It has no other use, and there is no RESTful endpoint associated with it. (Foundation-Other-N)
Subscription
The subscription resource is used to define a 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 can take an appropriate action. (Foundation-Other-3)
Patient
Demographics and other administrative information about an individual or animal receiving care or other health-related services.(Base-Individuals-N)
Practitioner
A person who is directly or indirectly involved in the provisioning of healthcare.(Base-Individuals-3)
PractitionerRole
A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.(Base-Individuals-2)
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. (Base-Individuals-2)
Person
Demographics and administrative information about a person independent of a specific health-related context.(Base-Individuals-2)
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. (Base-Individuals-1)
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, payer/insurer, etc. (Base-Entities #1-3)
OrganizationAffiliation
Defines an affiliation/assotiation/relationship between 2 distinct oganizations, that is not a part-of relationship/sub-division relationship. (Base-Entities #1-0)
HealthcareService
The details of a healthcare service available at a location.(Base-Entities #1-2)
Endpoint
The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b or a REST endpoint for another FHIR server. This may include any security context information. (Base-Entities #1-2)
Location
Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated. (Base-Entities #1-3)
Substance
A homogeneous material with a definite composition.(Base-Entities #2-2)
BiologicallyDerivedProduct
A material substance originating from a biological entity intended to be transplanted or infusedinto another (possibly the same) biological entity.(Base-Entities #2-0)
Device
A type 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.(Base-Entities #2-2)
DeviceMetric
Describes a measurement, calculation or setting capability of a medical device. (Base-Entities #2-1)
Task
A task to be performed.(Base-Workflow-2)
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). (Base-Workflow-3)
AppointmentResponse
A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection. (Base-Workflow-3)
Schedule
A container for slots of time that may be available for booking appointments.(Base-Workflow-3)
Slot
A slot of time on a schedule that may be available for booking appointments.(Base-Workflow-3)
VerificationResult
Describes validation requirements, source(s), status and dates for one or more elements. (Base-Workflow-0)
Encounter
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.(Base-Management-2)
EpisodeOfCare
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.(Base-Management-2)
Flag
Prospective warnings of potential issues when providing care to the patient.(Base-Management-1)
List
A list is a curated collection of resources.(Base-Management-1)
Library
The Library resource is a general-purpose container for knowledge asset definitions. It can be used to describe and expose existing knowledge assets such as logic libraries and information model descriptions, as well as to describe a collection of knowledge assets. (Base-Management-2)
AllergyIntolerance
Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. (Clinical-Summary-3)
AdverseEvent
Actual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death. (Clinical-Summary-0)
Condition
A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. (Clinical-Summary-3)
Procedure
An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy. (Clinical-Summary-3)