This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
This is an example form generated from the questionnaire. See also the XML or JSON format.
This is an example form generated from the questionnaire. See also the XML or JSON format
While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.
Logical id of this artefact |
Metadata about the resource
A set of rules under which this content was created |
language |
Text summary of the resource, for human interpretation
Contained, inline Resources
Logical identifier of composition (version-independent)
label: | |
system: | |
value: |
Composition editing time |
Kind of composition (LOINC if possible)
code: | |
text: |
Categorization of Composition
code: | |
text: |
Human Readable name/title |
status |
As defined by affinity domain |
Who and/or what the composition is about
type |
Patient |
|
Practitioner |
|
Group |
|
Device |
|
Location |
|
Who and/or what authored the composition
type |
Practitioner |
|
Device |
|
Patient |
|
RelatedPerson |
|
Only list each attester once.
xml:id (or equivalent in JSON) |
mode |
When composition attested |
Who attested the composition
type |
Patient |
|
Practitioner |
|
Organization |
|
Org which maintains the composition |
|
The event needs to be consistent with the type element, though can provide further information if desired.
xml:id (or equivalent in JSON) |
Code(s) that apply to the event being documented
code: | |
text: |
The period covered by the documentation
start: | |
end: |
Full details for the event(s) the composition consents |
|
Context of the conposition |
|
xml:id (or equivalent in JSON) |
Label for section (e.g. for ToC) |
Classification of section (recommended)
code: | |
text: |
Nested sections are primarily used to help human readers navigate to particular portions of the document.
The Content of the section |
|