NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition TUDomainResourceA 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..1uriCanonical identifier for this Composition, represented as a URI (globally unique)
... identifier Σ0..*IdentifierVersion-independent identifier for the Composition

... version Σ0..1stringAn explicitly assigned identifer of a variation of the content in the Composition
... status ?!Σ1..1coderegistered | partial | preliminary | final | amended | corrected | appended | cancelled | entered-in-error | deprecated | unknown
Binding: Composition Status (Required)
... type Σ1..1CodeableConceptKind of composition (LOINC if possible)
Binding: FHIR Document Type Codes (Preferred)
... category Σ0..*CodeableConceptCategorization of Composition
Binding: Referenced Item Category Value Set (Example)

... subject Σ0..*Reference(Any)Who and/or what the composition is about

... encounter Σ0..1Reference(Encounter)Context of the Composition
... date Σ1..1dateTimeComposition editing time
... useContext Σ0..*UsageContextThe 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..1stringName for this Composition (computer friendly)
... title Σ1..1stringHuman Readable name/title
... note 0..*AnnotationFor any additional notes

... attester 0..*BackboneElementAttests to accuracy of composition

.... mode 1..1CodeableConceptpersonal | professional | legal | official
Binding: Composition Attestation Mode (Preferred)
.... time 0..1dateTimeWhen the composition was attested
.... party 0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization)Who attested the composition
... custodian Σ0..1Reference(Organization)Organization which maintains the composition
... relatesTo 0..*RelatedArtifactRelationships to other compositions/documents

... event Σ0..*BackboneElementThe clinical service(s) being documented

.... period Σ0..1PeriodThe 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 C0..*BackboneElementComposition 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..1stringLabel for section (e.g. for ToC)
.... code 0..1CodeableConceptClassification 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..1Reference(Any)Who/what the section is about, when it is not about the subject of composition
.... text C0..1NarrativeText summary of the section, for human interpretation
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (Preferred)
.... entry C0..*Reference(Any)A reference to data that supports this section

.... emptyReason C0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (Preferred)
.... section 0..*see sectionNested Section


doco Documentation for this format