description: Base StructureDefinition for Composition Resource
package_name: hl7.fhir.r2.core
name: Composition
type: null
elements:
  date: {short: Composition editing time, comments: The Last Modified Date on the composition may be after the date of the document was attested without being changed., type: dateTime, isSummary: true, index: 1}
  encounter: {short: Context of the Composition, type: Reference, isSummary: true, index: 18}
  section:
    constraint:
      cmp-2: {human: A section can only have an emptyReason if it is empty, severity: error}
      cmp-1: {human: 'A section must at least one of text, entries, or sub-sections', severity: error}
    short: Composition is broken into sections
    name: section
    type: BackboneElement
    array: true
    index: 19
    elements:
      title: {short: Label for section (e.g. for ToC), comments: 'The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.', type: string, index: 20}
      code: {short: Classification of section (recommended), comments: 'The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.   If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.', type: CodeableConcept, index: 21}
      text: {short: 'Text summary of the section, for human interpretation', comments: Document profiles may define what content should be represented in the narrative to ensure clinical safety., type: Narrative, index: 22}
      mode: {isModifier: true, short: working | snapshot | changes, type: code, isSummary: true, index: 23}
      orderedBy: {short: Order of section entries, comments: 'Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.', type: CodeableConcept, index: 24}
      entry: {short: A reference to data that supports this section, comments: 'If there are no entries in the list, an emptyReason SHOULD be provided.', type: Reference, array: true, index: 25}
      emptyReason: {short: Why the section is empty, comments: 'The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.', type: CodeableConcept, index: 26}
      section: {short: Nested Section, nameReference: section, comments: Nested sections are primarily used to help human readers navigate to particular portions of the document., array: true, index: 27}
  attester:
    short: Attests to accuracy of composition
    comments: Only list each attester once.
    type: BackboneElement
    array: true
    isSummary: true
    index: 9
    elements:
      mode: {min: 1, short: personal | professional | legal | official, comments: Use more than one code where a single attester has more than one mode (professional and legal are often paired)., type: code, array: true, isSummary: true, index: 10}
      time: {short: When composition attested, type: dateTime, isSummary: true, index: 11}
      party: {short: Who attested the composition, type: Reference, isSummary: true, index: 12}
    required: [mode]
  type: {short: Kind of composition (LOINC if possible), comments: 'For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding.', type: CodeableConcept, isSummary: true, index: 2}
  title: {short: Human Readable name/title, comments: 'For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period.', type: string, isSummary: true, index: 4}
  author: {min: 1, short: Who and/or what authored the composition, type: Reference, array: true, isSummary: true, index: 8}
  event:
    short: The clinical service(s) being documented
    comments: The event needs to be consistent with the type element, though can provide further information if desired.
    type: BackboneElement
    array: true
    isSummary: true
    index: 14
    elements:
      code: {short: Code(s) that apply to the event being documented, comments: 'An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.', type: CodeableConcept, array: true, isSummary: true, index: 15}
      period: {type: Period, short: The period covered by the documentation, isSummary: true, index: 16}
      detail: {type: Reference, short: The event(s) being documented, isSummary: true, array: true, index: 17}
  custodian: {short: Organization which maintains the composition, comments: 'This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However it is important that this information be known when working with a derived document, so providing a custodian is encouraged.', type: Reference, isSummary: true, index: 13}
  status: {isModifier: true, short: preliminary | final | amended | entered-in-error, comments: 'If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "withdrawn" is why this element is labeled as a modifier of other elements.   Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required.', type: code, isSummary: true, index: 5}
  class: {short: Categorization of Composition, comments: 'This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD)).', type: CodeableConcept, isSummary: true, index: 3}
  identifier: {short: Logical identifier of composition (version-independent), comments: See discussion in resource definition for how these relate., type: Identifier, isSummary: true, index: 0}
  subject: {short: Who and/or what the composition is about, comments: 'For clinical documents, this is usually the patient.', type: Reference, isSummary: true, index: 7}
  confidentiality: {isModifier: true, short: As defined by affinity domain, comments: 'The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section).', type: code, isSummary: true, index: 6}
package_version: 1.0.2
class: resource
kind: resource
url: http://hl7.org/fhir/StructureDefinition/Composition
version: null
required: [author, status, subject, title, type, date]