Each comment is a time-stamped entry of arbitrary length that is not editable except by
anyone in the author group.
Each comment is a time-stamped entry of arbitrary length that is not editable except by
anyone in the author group.
May be used to represent additional information that is not part of the basic definition
of the element. In order to make the use of extensions safe and manageable, there is a
strict set of governance applied to the definition and use of extensions. Though any
implementer is allowed to define an extension, there is a set of requirements that SHALL
be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
May be used to represent additional information that is not part of the basic definition
of the element. In order to make the use of extensions safe and manageable, there is a
strict set of governance applied to the definition and use of extensions. Though any
implementer is allowed to define an extension, there is a set of requirements that SHALL
be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
The definition may point directly to a computable or human-readable definition of the
extensibility codes, or it may be a logical URI as declared in some other specification.
The definition should be version specific. This will ideally be the URI for the Resource
Profile defining the extension, with the code for the extension after a #.
Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).
May be used to represent additional information that is not part of the basic definition
of the element. In order to make the use of extensions safe and manageable, there is a
strict set of governance applied to the definition and use of extensions. Though any
implementer is allowed to define an extension, there is a set of requirements that SHALL
be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
The definition may point directly to a computable or human-readable definition of the
extensibility codes, or it may be a logical URI as declared in some other specification.
The definition should be version specific. This will ideally be the URI for the Resource
Profile defining the extension, with the code for the extension after a #.
Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).
The definition may point directly to a computable or human-readable definition of the
extensibility codes, or it may be a logical URI as declared in some other specification.
The definition should be version specific. This will ideally be the URI for the Resource
Profile defining the extension, with the code for the extension after a #.
Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).
Each comment is a time-stamped entry of arbitrary length that is not editable except by
anyone in the author group.
</StructureDefinition>
Explanation
of
the
specification.
columns
that
may
appear
on
this
page:
Level
A
few
code
lists
that
FHIR
defines
are
hierarchical
-
each
code
is
assigned
a
level.
See
Code
System
for
further
information.
Source
The
source
of
the
definition
of
the
code
(when
the
value
set
draws
in
codes
defined
elsewhere)
Code
The
code
(used
as
the
code
in
the
resource
instance).
If
the
code
is
in
italics,
this
indicates
that
the
code
is
not
selectable
('Abstract')
Display
The
display
(used
in
the
display
element
of
a
Coding
).
If
there
is
no
display,
implementers
should
not
simply
display
the
code,
but
map
the
concept
into
their
application
Terminology
|
Propose
a
change
