|
Information
Tracking
Information Tracking
|
Collecting
information,
and
tracking
change
to
the
information
Collecting information, and tracking change to the information
|
|
Name
|
Aliases
|
Description
|
|
Questionnaire
|
Form,
CRF
Form, CRF
|
A
structured
set
of
questions
intended
to
guide
the
collection
of
answers.
The
questions
are
ordered
and
grouped
into
coherent
subsets,
corresponding
to
the
structure
of
the
grouping
of
the
underlying
questions.
A structured set of questions intended to guide the collection of answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions.
|
|
QuestionnaireResponse
|
Form
|
A
structured
set
of
questions
and
their
answers.
The
questions
are
ordered
and
grouped
into
coherent
subsets,
corresponding
to
the
structure
of
the
grouping
of
the
underlying
questions.
A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions.
|
|
Provenance
|
History,
Event
History, Event
|
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.
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.
|
|
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.
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.
|
|
Documents
&
Lists
Documents & Lists
|
Management
of
documents
and
other
organizing
structures
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.
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
DocumentManifest
|
|
A
reference
to
a
document
.
A manifest that defines a set of documents.
|
DocumentManifest
DocumentReference
|
|
A
manifest
that
defines
a
set
of
documents.
A reference to a document .
|
|
List
|
Collection,
WorkingList
Collection, WorkingList
|
A
set
of
information
summarized
from
a
list
of
other
resources.
A set of information summarized from a list of other resources.
|
|
Structure
Structure
|
Resources
that
provide
basic
structural
support
for
other
usages
Resources that provide basic structural support for other usages
|
|
Name
|
Aliases
|
Description
|
Binary
Media
|
|
Pure
Binary
Content
-
opaque
to
FHIR
A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference.
|
Basic
Bundle
|
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.
A container for a collection of resources.
|
Binary
Basic
|
Z-resource, Extension-resource
|
A
binary
resource
can
contain
any
content,
whether
text,
image,
pdf,
zip
archive,
etc.
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.
|
Bundle
Binary
|
|
A
container
for
a
collection
of
resources.
A binary resource can contain any content, whether text, image, pdf, zip archive, etc.
|
Media
Linkage
|
|
A
photo,
video,
or
audio
recording
acquired
or
used
in
healthcare.
The
actual
content
may
be
inline
or
provided
by
direct
reference.
Identifies two or more records (resource instances) that are referring to the same real-world "occurrence".
|
|
|
Exchange
|
Used
to
support
the
process
of
exchanging
data
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.
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.
A collection of error, warning or information messages that result from a system action.
|
Parameters
(Not
defined
yet)
|
|
This special resource type is used to represent an operation request and response (operations.html). It has no other use, and there is no RESTful endpoint associated with it.
|
|
Subscription
|
WebHook,
Hook
WebHook, Hook
|
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
is
able
to
take
an
appropriate
action.
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 is able to take an appropriate action.
|
|
|
Terminology
|
The
terminology
sub-system
The terminology sub-system
|
|
Name
|
Aliases
|
Description
|
|
CodeSystem
| |
A code system resource specifies a set of codes drawn from one or more code systems.
|
|
ValueSet
|
|
A
value
set
specifies
a
set
of
codes
drawn
from
one
or
more
code
systems.
A value set specifies a set of 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.
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.
|
|
ExpansionProfile
|
ValueSetExpansionProfile
|
Resource to define constraints on the Expansion of a FHIR ValueSet.
|
|
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.
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.
|
|
|
Content
|
Specifying
allowable
content
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.
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.
|
|
StrutureMap
|
(Not defined yet)
| | |
|
DataElement
|
Master
Observation,
Data
Element
Master Observation, Data Element
|
The
formal
description
of
a
single
piece
of
information
that
can
be
gathered
and
reported.
The formal description of a single piece of information that can be gathered and reported.
|
|
Operations
Control
Operations Control
|
Specifying
the
behavior
of
operational
systems
Specifying the behavior of operational systems
|
|
Name
|
Aliases
|
Description
|
|
Conformance
|
|
A
conformance
statement
is
a
set
of
capabilities
of
a
FHIR
Server
that
may
be
used
as
a
statement
of
actual
server
functionality
or
a
statement
of
required
or
desired
server
implementation.
A conformance statement is a set of capabilities of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
|
|
OperationDefinition
|
|
A
formal
computable
definition
of
an
operation
(on
the
RESTful
interface)
or
a
named
query
(using
the
search
interaction).
A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction).
|
|
SearchParameter
|
|
A
search
parameter
that
defines
a
named
search
item
that
can
be
used
to
search/filter
on
a
resource.
A search parameter that defines a named search item that can be used to search/filter on a resource.
|
|
CompartmentDefinition
| |
A compartment definition that defines how resources are accessed on a server.
|
|
Miscellaineous
Miscellaneous
|
Managing
specification
and
testing
Managing specification and testing
|
|
Name
|
Aliases
|
Description
|
|
ImplementationGuide
|
|
A
set
of
rules
or
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.
A set of rules or 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.
|
|
TestScript
|
|
TestScript
is
a
resource
that
specifies
a
suite
of
tests
against
a
FHIR
server
implementation
to
determine
compliance
against
the
FHIR
specification.
TestScript is a resource that specifies a suite of tests against a FHIR server implementation to 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
