This
page
is
part
of
the
FHIR
Specification
(v3.3.0:
(v3.5.0:
R4
Ballot
2).
#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
.
Page
versions:
R5
R4B
R4
R3
R2
| http://www.hl7.org/Special/committees/fiwg/index.cfm | Maturity Level : 5 | Normative | Compartments : Not linked to any defined compartments |
Normative Candidate Note: This page is candidate normative content for R4 in the Infrastructure Package . Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made.
Detailed Descriptions for the elements in the DomainResource Resource.
| DomainResource | |||||||||||||||||||||||||
| Definition |
A resource that includes narrative, extensions, and contained resources. |
||||||||||||||||||||||||
| Control | 1..1 | ||||||||||||||||||||||||
| Type | Resource | ||||||||||||||||||||||||
| Invariants |
|
||||||||||||||||||||||||
| DomainResource.text | |||||||||||||||||||||||||
| Definition |
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
||||||||||||||||||||||||
| Control | 0..1 | ||||||||||||||||||||||||
| Type | Narrative | ||||||||||||||||||||||||
| Alternate Names | narrative; html; xhtml; display | ||||||||||||||||||||||||
| Comments |
Contained
resources
do
not
have
narrative.
Resources
that
are
not
contained
SHOULD
have
a
narrative.
In
some
cases,
a
resource
may
only
have
text
with
little
or
no
additional
discrete
data
(as
long
as
all
minOccurs=1
elements
are
satisfied).
This
may
be
necessary
for
data
from
legacy
systems
where
information
is
captured
as
a
"text
blob"
or
where
text
is
additionally
entered
raw
or
narrated
and
encoded
|
||||||||||||||||||||||||
| DomainResource.contained | |||||||||||||||||||||||||
| Definition |
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
||||||||||||||||||||||||
| Control | 0..* | ||||||||||||||||||||||||
| Type | Resource | ||||||||||||||||||||||||
| Alternate Names | inline resources; anonymous resources; contained resources | ||||||||||||||||||||||||
| Comments |
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
||||||||||||||||||||||||
| DomainResource.extension | |||||||||||||||||||||||||
| Definition |
May be used to represent additional information that is not part of the basic definition of the resource. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
||||||||||||||||||||||||
| Control | 0..* | ||||||||||||||||||||||||
| Type | Extension | ||||||||||||||||||||||||
| Alternate Names | extensions; user content | ||||||||||||||||||||||||
| Comments |
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. |
||||||||||||||||||||||||
| DomainResource.modifierExtension | |||||||||||||||||||||||||
| Definition |
May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
||||||||||||||||||||||||
| Control | 0..* | ||||||||||||||||||||||||
| Type | Extension | ||||||||||||||||||||||||
| Is Modifier |
true
(Reason:
|
||||||||||||||||||||||||
| Alternate Names | extensions; user content | ||||||||||||||||||||||||
| Comments |
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. |
||||||||||||||||||||||||