Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
Composition | TU | DomainResource | A set of resources composed into a single coherent clinical statement with clinical attestation Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension | |
url | Σ | 0..1 | uri | Canonical identifier for this Composition, represented as a URI (globally unique) |
identifier | Σ | 0..* | Identifier | Version-independent identifier for the Composition |
version | Σ | 0..1 | string | An explicitly assigned identifier of a variation of the content in the Composition |
status | ?!Σ | 1..1 | code | registered | partial | preliminary | final | amended | corrected | appended | cancelled | entered-in-error | deprecated | unknown Binding: Composition Status (Required) |
type | Σ | 1..1 | CodeableConcept | Kind of composition (LOINC if possible) Binding: FHIR Document Type Codes (Preferred) |
category | Σ | 0..* | CodeableConcept | Categorization of Composition Binding: Referenced Item Category Value Set (Example) |
subject | Σ | 0..* | Reference(Any) | Who and/or what the composition is about |
encounter | Σ | 0..1 | Reference(Encounter) | Context of the Composition |
date | Σ | 1..1 | dateTime | Composition editing time |
useContext | Σ | 0..* | UsageContext | The context that the content is intended to support |
author | Σ | 1..* | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) | Who and/or what authored the composition |
name | Σ | 0..1 | string | Name for this Composition (computer friendly) |
title | Σ | 1..1 | string | Human Readable name/title |
note | 0..* | Annotation | For any additional notes | |
attester | 0..* | BackboneElement | Attests to accuracy of composition | |
mode | 1..1 | CodeableConcept | personal | professional | legal | official Binding: Composition Attestation Mode (Preferred) | |
time | 0..1 | dateTime | When the composition was attested | |
party | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization) | Who attested the composition | |
custodian | Σ | 0..1 | Reference(Organization) | Organization which maintains the composition |
relatesTo | 0..* | RelatedArtifact | Relationships to other compositions/documents | |
event | Σ | 0..* | BackboneElement | The clinical service(s) being documented |
period | Σ | 0..1 | Period | The period covered by the documentation |
detail | Σ | 0..* | CodeableReference(Any) | The event(s) being documented, as code(s), reference(s), or both Binding: v3 Code System ActCode (Example) |
section | C | 0..* | BackboneElement | Composition is broken into sections + Rule: A section must contain at least one of text, entries, or sub-sections + Rule: A section can only have an emptyReason if it is empty |
title | 0..1 | string | Label for section (e.g. for ToC) | |
code | 0..1 | CodeableConcept | Classification of section (recommended) Binding: Document Section Codes (Example) | |
author | 0..* | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) | Who and/or what authored the section | |
focus | 0..1 | Reference(Any) | Who/what the section is about, when it is not about the subject of composition | |
text | C | 0..1 | Narrative | Text summary of the section, for human interpretation |
orderedBy | 0..1 | CodeableConcept | Order of section entries Binding: List Order Codes (Preferred) | |
entry | C | 0..* | Reference(Any) | A reference to data that supports this section |
emptyReason | C | 0..1 | CodeableConcept | Why the section is empty Binding: List Empty Reasons (Preferred) |
section | 0..* | see section | Nested Section | |
Documentation for this format |