2nd DSTU Draft For Comment

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 . Page versions: R5 R4B R4 R3 R2

6.9 Resource Composition - Content

This resource maintained by the Structured Documents Work Group

A set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement.

6.9.1 Scope and Usage

A Composition is also the basic structure from which FHIR Documents - immutable bundles with attested narrative - are built. A single logical composition may be associated with a series of derived documents, each of which is a frozen copy of the composition.

Note: EN 13606 uses the term "Composition" to refer to a single commit to an EHR system, and offers some common examples: a consultation note, a progress note, a report or a letter, an investigation report, a prescription form and a set of bedside nursing observations. These logical examples are all valid uses of a Composition resource, but it is not required that all the resources are updated in a single commit.

6.9.2 Background and Context

6.9.2.1 Composition Status Codes

Every composition has a status, which describes the status of the content of the composition, taken from this list of codes:

Code Definition
preliminary This is a preliminary composition (also known as initial or interim). The content may be incomplete or unverified.
final The composition is complete and verified by an appropriate person and no further work is planned
appended The composition has been modified subsequent to being marked and/or released as "final" and is complete and verified by an authorized person. The modifications added new information to the composition, but did not revise existing content
amended The composition content or the referenced resources have been modified subsequent to being released as "final" and the composition is complete and verified by an authorized person
retracted The composition was originally created/issued in error and this is an amendment that marks that the entire composition and any past versions or copies should not be considered as valid

Composition status generally only moves down through this list - it moves from preliminary to final and then it may progress to either appended or amended. Note that in many workflows, only final compositions are made available and the preliminary status is not used.

A very few compositions are created entirely in error in the workflow - usually the composition concerns the wrong patient or is written by the wrong author, and the error is only detected after the composition has been used or documents have been derived from it. To support resolution of this case, the composition is updated to be marked as "retracted" and a new derived document can be created. This means that the entire series of derived documents is now considered to be created in error and systems receiving derived documents based on retracted compositions SHOULD remove data taken from earlier documents from routine use and/or take other appropriate actions. Systems are not required to provide this workflow or support documents derived from retracted compositions, but they SHALL not ignore a status of retracted. Note that systems that handle compositions or derived documents and don't support the retracted status need to define some other way of handling compositions that are created in error; while this is not a common occurrence, some clinical systems have no provision for removing erroneous information from a patient's record and there is no way for a user to know that it is not fit for use - this is not safe.

6.9.2.2 Note for CDA aware readers

May uesrs of this specification are familiar with the Clinical Document Architecture (CDA) and related specifications. CDA is a primary design input to the composition resource (other principle inputs are other HL7 document specifications, and EN13606). There are two important structural differences between CDA and the composition resource:

  • A composition is a logical construct- it's identifier matches to the CDA ClinicalDocument.setId. Composition resources are wrapped into Document structures, for exchange of the whole package (the composition and it's parts), and this wrapped, sealed entity is equivalent to a CDA document
  • The composition section defines a section (or sub-section) of the document, but unlike in CDA, the section content is actually a reference to another resource that actually holds both the narrative and data content for the section. This design means that the narrative and data can be reused in many other ways. Note that the most common resource to use for the content of a section is the List resource.

In addition, note that both the code lists (e.g. Composition status) and the composition resource are mapped to v3 and/or CDA.

6.9.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition DomainResourceA set of resources composed into a single coherent clinical statement with clinical attestation
... identifier Σ0..1IdentifierLogical identifier of composition (version-independent)
... date Σ1..1dateTimeComposition editing time
... type Σ1..1CodeableConceptKind of composition (LOINC if possible)
DocumentType (Incomplete)
... class Σ0..1CodeableConceptCategorization of Composition
DocumentClass (Example)
... title Σ0..1stringHuman Readable name/title
... status M Σ1..1codepreliminary | final | appended | amended | entered-in-error
CompositionStatus (Required)
... confidentiality M Σ1..1CodingAs defined by affinity domain
DocumentConfidentiality (Incomplete)
... subject Σ1..1Patient | Practitioner | Group | Device | LocationWho and/or what the composition is about
... author Σ1..*Practitioner | Device | Patient | RelatedPersonWho and/or what authored the composition
... attester Σ0..*ElementAttests to accuracy of composition
.... mode Σ1..*codepersonal | professional | legal | official
CompositionAttestationMode (Required)
.... time Σ0..1dateTimeWhen composition attested
.... party Σ0..1Patient | Practitioner | OrganizationWho attested the composition
... custodian Σ0..1OrganizationOrg which maintains the composition
... event Σ0..*ElementThe clinical service(s) being documented
.... code Σ0..*CodeableConceptCode(s) that apply to the event being documented
DocumentEventType (Incomplete)
.... period Σ0..1PeriodThe period covered by the documentation
.... detail Σ0..*AnyFull details for the event(s) the composition consents
... encounter Σ0..1EncounterContext of the conposition
... section I0..*ElementComposition is broken into sections
A section must have either subsections or content
A section can only have a code if it has no content
.... title 0..1stringLabel for section (e.g. for ToC)
.... code I0..1CodeableConceptClassification of section (recommended)
CompositionSectionType (Incomplete)
.... section 0..*see sectionNested Section
.... content I0..1AnyThe Content of the section

UML Diagram

Composition (DomainResource)Logical Identifier for the composition, assigned when created. This identifier stays constant as the composition is changed over timeidentifier : Identifier 0..1The composition editing time, when the composition was last logically changed by the authordate : dateTime 1..1Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the compositiontype : CodeableConcept 1..1 « Type of a compositionDocumentType+ »A categorization for the type of the composition. This may be implied by or derived from the code specified in the Composition Typeclass : CodeableConcept 0..1 « (SubType of a clinical documentDocumentClass) »Official human-readable label for the compositiontitle : string 0..1The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document (this element modifies the meaning of other elements)status : code 1..1 « The workflow/clinical status of the compositionCompositionStatus »The code specifying the level of confidentiality of the Composition (this element modifies the meaning of other elements)confidentiality : Coding 1..1 « Codes specifying the level of confidentiality of the compositionDocumentConfidentiality+ »Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (I.e. machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure)subject : Reference(Patient|Practitioner|Group| Device|Location) 1..1Identifies who is responsible for the information in the composition. (Not necessarily who typed it in.)author : Reference(Practitioner|Device|Patient| RelatedPerson) 1..*Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document informationcustodian : Reference(Organization) 0..1Describes the clinical encounter or type of care this documentation is associated withencounter : Reference(Encounter) 0..1AttesterThe type of attestation the authenticator offersmode : code 1..* « The way in which a person authenticated a compositionCompositionAttestationMode »When composition was attested by the partytime : dateTime 0..1Who attested the composition in the specified wayparty : Reference(Patient|Practitioner| Organization) 0..1EventThis list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" actcode : CodeableConcept 0..* « This list of codes represents the main clinical acts being documentedDocumentEventType+ »The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this timeperiod : Period 0..1Full details for the event(s) the composition/documentation consentsdetail : Reference(Any) 0..*SectionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contentstitle : string 0..1A code identifying the kind of content contained within the section. This must be consistent with the section titlecode : CodeableConcept 0..1 « Classification of a composition / documentCompositionSectionType+ »The content (narrative and data) associated with the sectioncontent : Reference(Any) 0..1A participant who has attested to the accuracy of the composition/documentattester0..*The clinical service, such as a colonoscopy or an appendectomy, being documentedevent0..*A nested sub-section within this sectionsection0..*The root of the sections that make up the compositionsection0..*

XML Template

<Composition xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..1 Identifier 
     Logical identifier of composition (version-independent) --></identifier>
 <date value="[dateTime]"/><!-- 1..1 Composition editing time -->
 <type><!-- 1..1 CodeableConcept Kind of composition (LOINC if possible) --></type>
 <class><!-- 0..1 CodeableConcept Categorization of Composition --></class>
 <title value="[string]"/><!-- 0..1 Human Readable name/title -->
 <status value="[code]"/><!-- 1..1 preliminary | final | appended | amended | entered-in-error -->
 <confidentiality><!-- 1..1 Coding As defined by affinity domain --></confidentiality>
 <subject><!-- 1..1 Reference(Patient|Practitioner|Group|Device|Location) 
     Who and/or what the composition is about --></subject>
 <author><!-- 1..* Reference(Practitioner|Device|Patient|RelatedPerson) 
     Who and/or what authored the composition --></author>
 <attester>  <!-- 0..* Attests to accuracy of composition -->
  <mode value="[code]"/><!-- 1..* personal | professional | legal | official -->
  <time value="[dateTime]"/><!-- 0..1 When composition attested -->
  <party><!-- 0..1 Reference(Patient|Practitioner|Organization) Who attested the composition --></party>
 </attester>
 <custodian><!-- 0..1 Reference(Organization) Org which maintains the composition --></custodian>
 <event>  <!-- 0..* The clinical service(s) being documented -->
  <code><!-- 0..* CodeableConcept Code(s) that apply to the event being documented --></code>
  <period><!-- 0..1 Period The period covered by the documentation --></period>
  <detail><!-- 0..* Reference(Any) Full details for the event(s) the composition consents --></detail>
 </event>
 <encounter><!-- 0..1 Reference(Encounter) Context of the conposition --></encounter>
 <section>  <!-- 0..* Composition is broken into sections -->
  <title value="[string]"/><!-- 0..1 Label for section (e.g. for ToC) -->
  <code><!-- ?? 0..1 CodeableConcept Classification of section (recommended) --></code>
  <section><!-- 0..* Content as for Composition.section Nested Section --></section>
  <content><!-- ?? 0..1 Reference(Any) The Content of the section --></content>
 </section>
</Composition>

JSON Template

{doco
  "resourceType" : "Composition",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : { Identifier }, // 
     Logical identifier of composition (version-independent)
  "date" : "<dateTime>", // R! Composition editing time
  "type" : { CodeableConcept }, // R! Kind of composition (LOINC if possible)
  "class" : { CodeableConcept }, // Categorization of Composition
  "title" : "<string>", // Human Readable name/title
  "status" : "<code>", // R! preliminary | final | appended | amended | entered-in-error
  "confidentiality" : { Coding }, // R! As defined by affinity domain
  "subject" : { Reference(Patient|Practitioner|Group|Device|Location) }, // R! 
     Who and/or what the composition is about
  "author" : [{ Reference(Practitioner|Device|Patient|RelatedPerson) }], // R! 
     Who and/or what authored the composition
  "attester" : [{ // Attests to accuracy of composition
    "mode" : ["<code>"], // R! personal | professional | legal | official
    "time" : "<dateTime>", // When composition attested
    "party" : { Reference(Patient|Practitioner|Organization) } // Who attested the composition
  }],
  "custodian" : { Reference(Organization) }, // Org which maintains the composition
  "event" : [{ // The clinical service(s) being documented
    "code" : [{ CodeableConcept }], // Code(s) that apply to the event being documented
    "period" : { Period }, // The period covered by the documentation
    "detail" : [{ Reference(Any) }] // Full details for the event(s) the composition consents
  }],
  "encounter" : { Reference(Encounter) }, // Context of the conposition
  "section" : [{ // Composition is broken into sections
    "title" : "<string>", // Label for section (e.g. for ToC)
    "code" : { CodeableConcept }, // C? Classification of section (recommended)
    "section" : [{ Content as for Composition.section }], // Nested Section
    "content" : { Reference(Any) } // C? The Content of the section
  }]
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition DomainResourceA set of resources composed into a single coherent clinical statement with clinical attestation
... identifier Σ0..1IdentifierLogical identifier of composition (version-independent)
... date Σ1..1dateTimeComposition editing time
... type Σ1..1CodeableConceptKind of composition (LOINC if possible)
DocumentType (Incomplete)
... class Σ0..1CodeableConceptCategorization of Composition
DocumentClass (Example)
... title Σ0..1stringHuman Readable name/title
... status M Σ1..1codepreliminary | final | appended | amended | entered-in-error
CompositionStatus (Required)
... confidentiality M Σ1..1CodingAs defined by affinity domain
DocumentConfidentiality (Incomplete)
... subject Σ1..1Patient | Practitioner | Group | Device | LocationWho and/or what the composition is about
... author Σ1..*Practitioner | Device | Patient | RelatedPersonWho and/or what authored the composition
... attester Σ0..*ElementAttests to accuracy of composition
.... mode Σ1..*codepersonal | professional | legal | official
CompositionAttestationMode (Required)
.... time Σ0..1dateTimeWhen composition attested
.... party Σ0..1Patient | Practitioner | OrganizationWho attested the composition
... custodian Σ0..1OrganizationOrg which maintains the composition
... event Σ0..*ElementThe clinical service(s) being documented
.... code Σ0..*CodeableConceptCode(s) that apply to the event being documented
DocumentEventType (Incomplete)
.... period Σ0..1PeriodThe period covered by the documentation
.... detail Σ0..*AnyFull details for the event(s) the composition consents
... encounter Σ0..1EncounterContext of the conposition
... section I0..*ElementComposition is broken into sections
A section must have either subsections or content
A section can only have a code if it has no content
.... title 0..1stringLabel for section (e.g. for ToC)
.... code I0..1CodeableConceptClassification of section (recommended)
CompositionSectionType (Incomplete)
.... section 0..*see sectionNested Section
.... content I0..1AnyThe Content of the section

UML Diagram

Composition (DomainResource)Logical Identifier for the composition, assigned when created. This identifier stays constant as the composition is changed over timeidentifier : Identifier 0..1The composition editing time, when the composition was last logically changed by the authordate : dateTime 1..1Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the compositiontype : CodeableConcept 1..1 « Type of a compositionDocumentType+ »A categorization for the type of the composition. This may be implied by or derived from the code specified in the Composition Typeclass : CodeableConcept 0..1 « (SubType of a clinical documentDocumentClass) »Official human-readable label for the compositiontitle : string 0..1The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document (this element modifies the meaning of other elements)status : code 1..1 « The workflow/clinical status of the compositionCompositionStatus »The code specifying the level of confidentiality of the Composition (this element modifies the meaning of other elements)confidentiality : Coding 1..1 « Codes specifying the level of confidentiality of the compositionDocumentConfidentiality+ »Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (I.e. machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure)subject : Reference(Patient|Practitioner|Group| Device|Location) 1..1Identifies who is responsible for the information in the composition. (Not necessarily who typed it in.)author : Reference(Practitioner|Device|Patient| RelatedPerson) 1..*Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document informationcustodian : Reference(Organization) 0..1Describes the clinical encounter or type of care this documentation is associated withencounter : Reference(Encounter) 0..1AttesterThe type of attestation the authenticator offersmode : code 1..* « The way in which a person authenticated a compositionCompositionAttestationMode »When composition was attested by the partytime : dateTime 0..1Who attested the composition in the specified wayparty : Reference(Patient|Practitioner| Organization) 0..1EventThis list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" actcode : CodeableConcept 0..* « This list of codes represents the main clinical acts being documentedDocumentEventType+ »The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this timeperiod : Period 0..1Full details for the event(s) the composition/documentation consentsdetail : Reference(Any) 0..*SectionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contentstitle : string 0..1A code identifying the kind of content contained within the section. This must be consistent with the section titlecode : CodeableConcept 0..1 « Classification of a composition / documentCompositionSectionType+ »The content (narrative and data) associated with the sectioncontent : Reference(Any) 0..1A participant who has attested to the accuracy of the composition/documentattester0..*The clinical service, such as a colonoscopy or an appendectomy, being documentedevent0..*A nested sub-section within this sectionsection0..*The root of the sections that make up the compositionsection0..*

XML Template

<Composition xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..1 Identifier 
     Logical identifier of composition (version-independent) --></identifier>
 <date value="[dateTime]"/><!-- 1..1 Composition editing time -->
 <type><!-- 1..1 CodeableConcept Kind of composition (LOINC if possible) --></type>
 <class><!-- 0..1 CodeableConcept Categorization of Composition --></class>
 <title value="[string]"/><!-- 0..1 Human Readable name/title -->
 <status value="[code]"/><!-- 1..1 preliminary | final | appended | amended | entered-in-error -->
 <confidentiality><!-- 1..1 Coding As defined by affinity domain --></confidentiality>
 <subject><!-- 1..1 Reference(Patient|Practitioner|Group|Device|Location) 
     Who and/or what the composition is about --></subject>
 <author><!-- 1..* Reference(Practitioner|Device|Patient|RelatedPerson) 
     Who and/or what authored the composition --></author>
 <attester>  <!-- 0..* Attests to accuracy of composition -->
  <mode value="[code]"/><!-- 1..* personal | professional | legal | official -->
  <time value="[dateTime]"/><!-- 0..1 When composition attested -->
  <party><!-- 0..1 Reference(Patient|Practitioner|Organization) Who attested the composition --></party>
 </attester>
 <custodian><!-- 0..1 Reference(Organization) Org which maintains the composition --></custodian>
 <event>  <!-- 0..* The clinical service(s) being documented -->
  <code><!-- 0..* CodeableConcept Code(s) that apply to the event being documented --></code>
  <period><!-- 0..1 Period The period covered by the documentation --></period>
  <detail><!-- 0..* Reference(Any) Full details for the event(s) the composition consents --></detail>
 </event>
 <encounter><!-- 0..1 Reference(Encounter) Context of the conposition --></encounter>
 <section>  <!-- 0..* Composition is broken into sections -->
  <title value="[string]"/><!-- 0..1 Label for section (e.g. for ToC) -->
  <code><!-- ?? 0..1 CodeableConcept Classification of section (recommended) --></code>
  <section><!-- 0..* Content as for Composition.section Nested Section --></section>
  <content><!-- ?? 0..1 Reference(Any) The Content of the section --></content>
 </section>
</Composition>

JSON Template

{doco
  "resourceType" : "Composition",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : { Identifier }, // 
     Logical identifier of composition (version-independent)
  "date" : "<dateTime>", // R! Composition editing time
  "type" : { CodeableConcept }, // R! Kind of composition (LOINC if possible)
  "class" : { CodeableConcept }, // Categorization of Composition
  "title" : "<string>", // Human Readable name/title
  "status" : "<code>", // R! preliminary | final | appended | amended | entered-in-error
  "confidentiality" : { Coding }, // R! As defined by affinity domain
  "subject" : { Reference(Patient|Practitioner|Group|Device|Location) }, // R! 
     Who and/or what the composition is about
  "author" : [{ Reference(Practitioner|Device|Patient|RelatedPerson) }], // R! 
     Who and/or what authored the composition
  "attester" : [{ // Attests to accuracy of composition
    "mode" : ["<code>"], // R! personal | professional | legal | official
    "time" : "<dateTime>", // When composition attested
    "party" : { Reference(Patient|Practitioner|Organization) } // Who attested the composition
  }],
  "custodian" : { Reference(Organization) }, // Org which maintains the composition
  "event" : [{ // The clinical service(s) being documented
    "code" : [{ CodeableConcept }], // Code(s) that apply to the event being documented
    "period" : { Period }, // The period covered by the documentation
    "detail" : [{ Reference(Any) }] // Full details for the event(s) the composition consents
  }],
  "encounter" : { Reference(Encounter) }, // Context of the conposition
  "section" : [{ // Composition is broken into sections
    "title" : "<string>", // Label for section (e.g. for ToC)
    "code" : { CodeableConcept }, // C? Classification of section (recommended)
    "section" : [{ Content as for Composition.section }], // Nested Section
    "content" : { Reference(Any) } // C? The Content of the section
  }]
}

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

6.9.3.1 Terminology Bindings

PathDefinitionTypeReference
Composition.type Type of a compositionIncompletehttp://hl7.org/fhir/vs/doc-codes
Composition.class SubType of a clinical documentExamplehttp://hl7.org/fhir/vs/xds-typecodes
Composition.status The workflow/clinical status of the compositionFixedhttp://hl7.org/fhir/composition-status
Composition.confidentiality Codes specifying the level of confidentiality of the compositionIncompletehttp://hl7.org/fhir/v3/vs/Confidentiality
Composition.attester.mode The way in which a person authenticated a compositionFixedhttp://hl7.org/fhir/composition-attestation-mode
Composition.event.code This list of codes represents the main clinical acts being documentedIncompletehttp://hl7.org/fhir/v3/vs/ActCode
Composition.section.code Classification of a composition / documentIncompletehttp://hl7.org/fhir/vs/doc-section-codes

6.9.3.2 Constraints

  • cmp-1: On Composition.section: A section can only have a code if it has no content (xpath on f:Composition/f:section: not(exists(f:code)) or not(exists(f:content)))
  • cmp-2: On Composition.section: A section must have either subsections or content (xpath on f:Composition/f:section: (exists(f:content) and not(exists(f:section))) or (exists(f:section) and not(exists(f:content))))

6.9.4 Notes:

  • The author and the attester are often the same person, but this may not be the case in some clinical workflows
  • The attester attests contents of the document resource, the subject resource and the resources referred to in the Composition.section.content references. Because documents are often derived Compositions and the attestation from the composition is held to apply to the document, the method for presenting a document should be used when/if attesters review the content of the composition
  • The custodian is responsible for the maintenance of the composition and any documents derived from it. With regard to the documents, they are responsible for the policy regarding persistence of the documents. Although they need not actually retain a copy of the document, they SHOULD do so.
  • Narrative only sections can be created by setting Content to a resource of the appropriate type and only populating the narrative portion of the resource. If the meaning of the section is such that an appropriate resource does not exist, the Other resource should be used. (In some cases, the a resource may have mandatory elements that preclude the resource containing only narrative. This will be addressed in a future release, but for now, Other should be used in these circumstances as well.)

6.9.5 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
attesterreferenceWho attested the compositionComposition.attester.party
(Organization, Patient, Practitioner)
authorreferenceWho and/or what authored the compositionComposition.author
(Device, Patient, Practitioner, RelatedPerson)
classtokenCategorization of CompositionComposition.class
confidentialitytokenAs defined by affinity domainComposition.confidentiality
contexttokenCode(s) that apply to the event being documentedComposition.event.code
datedateComposition editing timeComposition.date
identifiertokenLogical identifier of composition (version-independent)Composition.identifier
patientreferenceWho and/or what the composition is aboutComposition.subject
(Patient)
perioddateThe period covered by the documentationComposition.event.period
sectionreferenceThe Content of the sectionComposition.section.content
(Any)
section-codetokenClassification of section (recommended)Composition.section.code
statustokenpreliminary | final | appended | amended | entered-in-errorComposition.status
subjectreferenceWho and/or what the composition is aboutComposition.subject
(Device, Location, Patient, Practitioner, Group)
titlestringHuman Readable name/titleComposition.title
typetokenKind of composition (LOINC if possible)Composition.type