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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained.

To support documents, and also to capture the EN13606 notion of an attested commit to the patient EHR, and to allow a set of disparate resources at the information/engineering level to be gathered into a clinical statement. To support documents, and also to capture the EN13606 notion of an attested commit to the patient EHR, and to allow a set of disparate resources at the information/engineering level to be gathered into a clinical statement.

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. 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 identifier for the composition, assigned when created. This identifier stays constant as the composition is changed over time. Logical identifier for the composition, assigned when created. This identifier stays constant as the composition is changed over time.

See discussion in resource definition for how these relate. See discussion in resource definition for how these relate.

The composition editing time, when the composition was last logically changed by the author. The composition editing time, when the composition was last logically changed by the author.

dateTime is used for tracking, organizing versions and searching. dateTime is used for tracking, organizing versions and searching.

The Last Modified Date on the composition may be after the date of the document was attested without being changed. The Last Modified Date on the composition may be after the date of the document was attested without being changed.

Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition. Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition.

Key metadata element describing the composition, used in searching/filtering. Key metadata element describing the composition, used in searching/filtering.

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. 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.

A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type. A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type.

Helps humans to assess whether the composition is of interest when viewing an index of compositions or documents. Helps humans to assess whether the composition is of interest when viewing an index of compositions or documents.

This is a metadata field from XDS/MHD This is a metadata field from XDS/MHD .

Official human-readable label for the composition. Official human-readable label for the composition.

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. 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.

The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.

Need to be able to mark interim, amended, or withdrawn compositions or documents. Need to be able to mark interim, amended, or withdrawn compositions or documents.

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. 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.

The code specifying the level of confidentiality of the Composition. The code specifying the level of confidentiality of the Composition.

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). 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).

Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a 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). Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a 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).

Essential metadata for searching for the composition. Identifies who and/or what the composition/document is about. Essential metadata for searching for the composition. Identifies who and/or what the composition/document is about.

For clinical documents, this is usually the patient. For clinical documents, this is usually the patient.

Identifies who is responsible for the information in the composition, not necessarily who typed it in. Identifies who is responsible for the information in the composition, not necessarily who typed it in.

Identifies who is responsible for the content. Identifies who is responsible for the content.

A participant who has attested to the accuracy of the composition/document. A participant who has attested to the accuracy of the composition/document.

Identifies responsibility for the accuracy of the composition content. Identifies responsibility for the accuracy of the composition content.

Only list each attester once. Only list each attester once.

The type of attestation the authenticator offers. The type of attestation the authenticator offers.

Indicates the level of authority of the attestation. Indicates the level of authority of the attestation.

Use more than one code where a single attester has more than one mode (professional and legal are often paired). Use more than one code where a single attester has more than one mode (professional and legal are often paired).

When composition was attested by the party. When composition was attested by the party.

Identifies when the information in the composition was deemed accurate. (Things may have changed since then.). Identifies when the information in the composition was deemed accurate. (Things may have changed since then.).

Who attested the composition in the specified way. Who attested the composition in the specified way.

Identifies who has taken on the responsibility for accuracy of the composition content. Identifies who has taken on the responsibility for accuracy of the composition content.

Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information.

Identifies where to go to find the current version, where to report issues, etc. Identifies where to go to find the current version, where to report issues, etc.

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. 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.

The clinical service, such as a colonoscopy or an appendectomy, being documented. The clinical service, such as a colonoscopy or an appendectomy, being documented.

Provides context for the composition and creates a linkage between a resource describing an event and the composition created describing the event. Provides context for the composition and creates a linkage between a resource describing an event and the composition created describing the event.

The event needs to be consistent with the type element, though can provide further information if desired. The event needs to be consistent with the type element, though can provide further information if desired.

This 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" act. This 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" act.

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. 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.

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 time. 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 time.

The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy. The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy.

Describes the clinical encounter or type of care this documentation is associated with. Describes the clinical encounter or type of care this documentation is associated with.

Provides context for the composition and supports searching. Provides context for the composition and supports searching.

The root of the sections that make up the composition. The root of the sections that make up the composition.

The 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 contents. The 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 contents.

Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.

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. 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.

A code identifying the kind of content contained within the section. This must be consistent with the section title. A code identifying the kind of content contained within the section. This must be consistent with the section title.

Provides computable standardized labels to topics within the document. Provides computable standardized labels to topics within the document.

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. 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.

A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative.

Document profiles may define what content should be represented in the narrative to ensure clinical safety. Document profiles may define what content should be represented in the narrative to ensure clinical safety.

How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted.

Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.

Specifies the order applied to the items in the section entries. Specifies the order applied to the items in the section entries.

Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries.

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. 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.

A reference to the actual resource from which the narrative in the section is derived. A reference to the actual resource from which the narrative in the section is derived.

If there are no entries in the list, an emptyReason SHOULD be provided. If there are no entries in the list, an emptyReason SHOULD be provided.

If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.

Allows capturing things like "none exist" or "not asked" which can be important for most lists. Allows capturing things like "none exist" or "not asked" which can be important for most lists.

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. 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.

A nested sub-section within this section. A nested sub-section within this section.

Nested sections are primarily used to help human readers navigate to particular portions of the document. Nested sections are primarily used to help human readers navigate to particular portions of the document.