abstractbaseDefinitioncopyrightdate- Values Differ
description- Values Differ
experimentalfhirVersion- Values Differ
jurisdiction
jurisdiction[0]kindnamepublisherpurposestatus- Values Differ
titletypeurlversion- Values Differ
| Left: | EvidenceReport (http://hl7.org/fhir/uv/ebm/StructureDefinition/evidence-report) |
| Right: | EvidenceReport (http://hl7.org/fhir/uv/ebm/StructureDefinition/evidence-report) |
| Error | StructureDefinition.version | Values for version differ: '1.0.0-ballot2' vs '1.0.0-ballot3' |
| Information | StructureDefinition.status | Values for status differ: 'draft' vs 'active' |
| Information | StructureDefinition.date | Values for date differ: '2025-03-28T17:11:38+00:00' vs '2026-09-10T16:38:22+00:00' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '6.0.0-ballot2' vs '6.0.0-ballot5' |
| Information | StructureDefinition.definition | Values for definition differ: 'A set of healthcare-related information that is assembled together into a single logical package 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. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).' vs 'Composition provides the structural backbone for assembling a set of healthcare-related information into a single logical package that provides a single coherent statement of meaning, establishes its own context and has traceability to the author who is making the statement.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resource id depends on the given use case.' |
| Information | StructureDefinition.definition | Values for definition differ: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. For DomainResources, if more than one implicitRules policy applies, additional policies may be conveyed using the [additionalImplicitRules](https://build.fhir.org/ig/HL7/fhir-extensions/StructureDefinition-additionalImplicitRules.html) extension.' |
| Information | StructureDefinition.comment | Values for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. Contained resources may be a resource type defined in the FHIR specification, or an [additional resource](http://build.fhir.org/resource.html#additional).' |
| Information | StructureDefinition.short | Values for short differ: 'Extension' vs 'Additional content defined by implementations' |
| Information | StructureDefinition.definition | Values for definition differ: 'An Extension' vs 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/6.0.0-ballot2/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.comment | Values for comment differ: 'While each resource, including the composition itself, has its own version identifier, this is a formal identifier for the logical version of the Composition as a whole. It would remain constant if the resources were moved to a new server, and all got new individual resource versions, for example.' vs 'This element is the author-assigned business version of the Composition (analogous to CDA ClinicalDocument.versionNumber). It is distinct from Resource.meta.versionId, which is a server-assigned technical version that every resource carries and that may change whenever the resource is updated on a server. Composition.version reflects the version of a logical document's content and remains constant even if the Composition or its referenced resources are moved between servers and receive new meta.versionId values.' |
| Information | StructureDefinition.comment | Values for comment differ: '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 'entered-in-error' 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.' vs 'See section 2.8.3.2, The workflow/clinical status of the composition, for guidance. Because the entered-in-error flag changes how this resource and its related elements must be interpreted, status is labeled as a modifier element. Some reporting workflows 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 noting whether this business rule is in effect; this would be handled by an extension if required.' |
| Information | Composition.type | Example/preferred bindings differ at Composition.type using binding from EvidenceReport |
| Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'A categorization for the type of the composition - helps with indexing and searching. This may be implied by or derived from the code specified in the Composition Type.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Reference a Citation Resource, ArtifactAssessment Resource (Classification Profile), Group Resource (EvidenceReportSubject Profile), ReserchStudy Resource, or any Resource to define a subject of this EvidenceReport.' vs 'Reference a PublicationRecord Resource, ArtifactAssessment Resource (Classification Profile), Group Resource (EvidenceReportSubject Profile), ReserchStudy Resource, or any Resource to define a subject of this EvidenceReport.' |
| Information | StructureDefinition.comment | Values for comment differ: 'The Last Modified Date on the composition may be after the date of the document was attested without being changed. This means that the date on an amended document is the date of the amendment, not the date of original authorship.' vs 'The Last Modified Date on the composition may be after the date the document was attested without being changed. This means that the date on an amended document is the date of the amendment, not the date of original authorship.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'dateTime is used for tracking, organizing versions and searching. Note that this is the time of authoring this version of the Composition. When packaged in a document, [Bundle.timestamp](http://hl7.org/fhir/R5/bundle-definitions.html#Bundle.timestamp) is the date of packaging.' vs 'dateTime is used for tracking, organizing versions and searching. Note that this is the time of authoring this version of the Composition. When packaged in a document, [Bundle.timestamp](http://build.fhir.org/bundle-definitions.html#Bundle.timestamp) is the date of packaging.' |
| Information | Composition.author | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.short | Values for short differ: 'Name for this Composition (computer friendly)' vs 'Computer friendly name' |
| Information | StructureDefinition.definition | Values for definition differ: 'A natural language name identifying the {{title}}. This name should be usable as an identifier for the module by machine processing applications such as code generation.' vs 'A machine-friendly identifier suitable for code generation. For example, 'ClinicalDocument' or 'Composition_v2'. See the Constraint description.' |
| Information | StructureDefinition.comment | Values for comment differ: 'The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.' vs 'The name is not expected to be globally unique. This field is used primarily by computers while the title field includes information for human-display. Composition.type is used to provide a CodeableConcept for the document type when available while Composition.name is an uncoded string. Composition.identifier is used to identify the specific instance of a document.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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').' |
| Information | Composition.title | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/6.0.0-ballot2/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | Composition.attester.mode | Example/preferred bindings differ at Composition.attester.mode using binding from EvidenceReport |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Identifies when the information in the composition was deemed accurate. (Things may have changed since then.).' vs 'Identifies when the information in the composition was deemed accurate. (Things may have changed since then.)' |
| Information | StructureDefinition.definition | Values for definition differ: 'Relationships that this composition has with other compositions or documents that already exist.' vs 'Relationships that this composition has with other compositions or documents (FHIR or non-FHIR resources) that already exist.' |
| Information | StructureDefinition.comment | Values for comment differ: 'To reference (using relatesTo) a Bundle of type 'document' or another Composition where you only have the identifier, use a resourceReference with an identifier.\ When a Composition is an alternate representation of another type of document e.g. CDA, the other document could be referenced in a DocumentReference resource. Here is an example of using relatesTo to reference another Bundle of type 'document' or Composition where you only have the identifier: ``` 'relatesTo': [{ 'type': 'replaces', 'resourceReference': { 'identifier': { 'system': '...', 'value': '...' } } }] ```' vs 'To reference (using relatesTo) a Bundle of type 'document' or another Composition where you only have the identifier, use a targetReference with an identifier.\ When a Composition is an alternate representation of another type of document e.g. CDA, the other document could be referenced in a DocumentReference resource. Here is an example of using relatesTo to reference another Bundle of type 'document' or Composition where you only have the identifier: ``` 'relatesTo': [{ 'type': 'replaces', 'targetReference': { 'identifier': { 'system': '...', 'value': '...' } } }] ```' |
| Information | StructureDefinition.short | Values for short differ: 'documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of | amends | amended-with | appends | appended-with | cites | cited-by | comments-on | comment-in | contains | contained-in | corrects | correction-in | replaces | replaced-with | retracts | retracted-by | signs | similar-to | supports | supported-with | transforms | transformed-into | transformed-with | documents | specification-of | created-with | cite-as' vs 'documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of | amends | amended-with | appends | appended-with | cites | cited-by | comments-on | comment-in | contains | contained-in | corrects | correction-in | replaces | replaced-with | retracts | retracted-by | signs | similar-to | supports | supported-with | transforms | transformed-into | transformed-with | documents | specification-of | created-with | cite-as | reprint | reprint-of | summarizes' |
| Information | StructureDefinition.comment | Values for comment differ: 'The event needs to be consistent with the type element, though can provide further information if desired.' vs 'The event needs to be consistent with the type element, though it can provide further information if desired.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/6.0.0-ballot2/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.definition | Values for definition differ: '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 case the procedure being documented is necessarily a 'History and Physical' act. The events may be included as a code or as a reference to an other resource.' vs '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 case the procedure being documented is necessarily a 'History and Physical' act. The events may be included as a code or as a reference to another resource.' |
| Information | StructureDefinition.comment | Values for comment differ: '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 events 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.' vs 'An event can further specialize the act inherent in Composition.type, such as where it is simply 'Procedure Report' and the procedure was a 'colonoscopy'. If one or more events are included, they SHALL NOT conflict with the values inherent in Composition.type 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.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/6.0.0-ballot2/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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 a required element.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Who and/or what authored the section' vs 'Who and/or what authored the section, when the section is authored by someone other than the composition.author' |
| Information | StructureDefinition.definition | Values for definition differ: 'Identifies who is responsible for the information in this section, not necessarily who typed it in.' vs 'Identifies who is responsible for the information in this section, not necessarily who typed it in. The actual author of the section when it is not the author of the composition. If author is not specified, the author is assumed to be the author of the parent section or the author of the composition.' |
| Information | StructureDefinition.short | Values for short differ: 'Who/what the section is about, when it is not about the subject of composition' vs 'Who/what the section is about, when it is not about the subject of the composition' |
| Information | StructureDefinition.definition | Values for definition differ: 'The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources).' vs 'The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If no focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources).' |
| Information | StructureDefinition.comment | Values for comment differ: 'Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.' vs 'Typically, sections in a document are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kinds of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.' |
| Information | Composition.section.orderedBy | Example/preferred bindings differ at Composition.section.orderedBy using binding from EvidenceReport |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs 'The various reasons for an empty section make a significant difference 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.' |
| Information | Composition.section.emptyReason | Example/preferred bindings differ at Composition.section.emptyReason using binding from EvidenceReport |
| Name | Value | Comments | |
|---|---|---|---|
| abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/Composition | ||
| copyright | |||
| date | 2025-03-28T17:11:38+00:00 | 2026-09-10T16:38:22+00:00 |
|
| description | Profile of Composition for Evidence Based Medicine IG. The EvidenceReport Profile is used for a base structure (canonical resource management) for a report combining any number of Citation, Evidence, EvidenceVariable, EvidenceReport, and related Resources. | Profile of Composition for Evidence Based Medicine IG. The EvidenceReport Profile is used for a base structure (canonical resource management) for a report combining any number of PublicationRecord, Evidence, EvidenceVariable, EvidenceReport, and related Resources. |
|
| experimental | |||
| fhirVersion | 6.0.0-ballot2 | 6.0.0-ballot5 |
|
| jurisdiction | |||
| jurisdiction[0] | http://unstats.un.org/unsd/methods/m49/m49.htm#001 | ||
| kind | resource | ||
| name | EvidenceReport | ||
| publisher | HL7 International / Clinical Decision Support | ||
| purpose | |||
| status | draft | active |
|
| title | |||
| type | Composition | ||
| url | http://hl7.org/fhir/uv/ebm/StructureDefinition/evidence-report | ||
| version | 1.0.0-ballot2 | 1.0.0-ballot3 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Composition | 0..* | Composition | A set of resources composed into a single coherent clinical statement with clinical attestation | 0..* | Composition | A set of resources composed into a single coherent clinical statement with clinical attestation | |||||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (required): IETF language tag for a human language
| 0..1 | code | Language of the resource content Binding: ?? (required): IETF language tag for a human language
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 Slices for extension | 0..* | Extension | Extension Slice: Unordered, Open by value:url | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | |||||||||||
 modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored Slice: Unordered, Open by value:url | |||||||||
| url | Σ | 0..1 | uri | Canonical identifier for this Composition, represented as a URI (globally unique) | Σ | 0..1 | uri | Canonical identifier for this Composition, represented as a URI (globally unique) | |||||||||
| identifier | Σ | 0..* | Identifier | Version-independent identifier for the Composition | Σ | 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 | Σ | 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: ?? (required): The workflow/clinical status of the composition. | ?!Σ | 1..1 | code | registered | partial | preliminary | final | amended | corrected | appended | cancelled | entered-in-error | deprecated | unknown Binding: ?? (required): The workflow status of the composition. | |||||||||
| type | Σ | 1..1 | CodeableConcept | Kind of composition (LOINC if possible) Binding: ?? (preferred): Type of a composition. | Σ | 1..1 | CodeableConcept | Kind of composition (LOINC if possible) Binding: ?? (preferred): Type of a composition. |
| ||||||||
| category | Σ | 0..* | CodeableConcept | Categorization of Composition Binding: ?? (example): High-level kind of a clinical document at a macro level. | Σ | 0..* | CodeableConcept | Categorization of Composition Binding: ?? (example): High-level kind of a clinical document at a macro level. | |||||||||
| subject | Σ | 0..* | Reference(Resource) | Who and/or what the composition is about | Σ | 0..* | Reference(Resource) | Who and/or what the composition is about | |||||||||
| encounter | Σ | 0..1 | Reference(Encounter) | Context of the Composition | Σ | 0..1 | Reference(Encounter) | Context of the Composition | |||||||||
| date | Σ | 1..1 | dateTime | Composition editing time | Σ | 1..1 | dateTime | Composition editing time | |||||||||
| useContext | Σ | 0..* | UsageContext | The context that the content is intended to support | Σ | 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 | Σ | 0..* | Reference(Practitioner | PractitionerRole | CareTeam | Device | Patient | RelatedPerson | Organization) | Who and/or what authored the composition |
| ||||||||
| name | Σ | 0..1 | string | Name for this Composition (computer friendly) | ΣC | 0..1 | string | Computer friendly name | |||||||||
| title | Σ | 1..1 | string | Human Readable name/title | Σ | 0..1 | string | Human Readable name/title |
| ||||||||
| note | 0..* | Annotation | For any additional notes | 0..* | Annotation | For any additional notes | |||||||||||
 attester | 0..* | BackboneElement | Attests to accuracy of composition | C | 0..* | BackboneElement | Attests to accuracy of composition | ||||||||||
 id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized Slice: Unordered, Open by value:url | |||||||||
| mode | 1..1 | CodeableConcept | reviewer | editor | endorser | informant | recorder Binding: ?? (preferred) | 1..1 | CodeableConcept | reviewer | editor | endorser | informant | recorder Binding: ?? (preferred) |
| ||||||||||
| time | 0..1 | dateTime | When the composition was attested | 0..1 | dateTime | When the composition was attested | |||||||||||
| party | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization) | Who attested the composition | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | Group) | Who attested the composition | |||||||||||
| custodian | Σ | 0..1 | Reference(Organization) | Organization which maintains the composition | Σ | 0..1 | Reference(Organization | Patient | Group) | Organization which maintains the composition | |||||||||
| Slices for relatesTo | 0..* | RelatedArtifact | Relationships to other compositions/documents Slice: Unordered, Open by value:type | 0..* | BackboneElement | Relationships to other compositions/documents Slice: Unordered, Open by value:type | |||||||||||
| id | 0..1 | id | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| Slices for extension | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | |||||||||||
| type | 1..1 | code | documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of | amends | amended-with | appends | appended-with | cites | cited-by | comments-on | comment-in | contains | contained-in | corrects | correction-in | replaces | replaced-with | retracts | retracted-by | signs | similar-to | supports | supported-with | transforms | transformed-into | transformed-with | documents | specification-of | created-with | cite-as Binding: ?? (required): The type of relationship to the related artifact. | 1..1 | CodeableConcept | documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of | amends | amended-with | appends | appended-with | cites | cited-by | comments-on | comment-in | contains | contained-in | corrects | correction-in | replaces | replaced-with | retracts | retracted-by | signs | similar-to | supports | supported-with | transforms | transformed-into | transformed-with | documents | specification-of | created-with | cite-as | reprint | reprint-of | summarizes Binding: ?? (extensible): The type of relationship to the related artifact. | |||||||||||
| classifier | 0..* | CodeableConcept | Additional classifiers Binding: ?? (example): Additional classifiers for the related artifact. |
| |||||||||||||
| label | 0..1 | string | Short label |
| |||||||||||||
| display | 0..1 | string | Brief description of the related artifact |
| |||||||||||||
| citation | 0..1 | markdown | Bibliographic citation for the artifact |
| |||||||||||||
| document | 0..1 | Attachment | What document is being referenced |
| |||||||||||||
| resource | 0..1 | canonical(Resource) | What artifact is being referenced |
| |||||||||||||
| resourceReference | 0..1 | Reference(Resource) | What artifact, if not a conformance resource |
| |||||||||||||
| publicationStatus | 0..1 | code | draft | active | retired | unknown Binding: ?? (required): Publication status of an artifact being referred to. |
| |||||||||||||
| publicationDate | 0..1 | date | Date of publication of the artifact being referred to |
| |||||||||||||
| Slices for modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized Slice: Unordered, Open by value:url |
| ||||||||||||
| target[x] | 1..1 | uri, Attachment, canonical(Resource), Reference(Resource), markdown | The artifact that is related to this Composition |
| |||||||||||||
| event | Σ | 0..* | BackboneElement | The clinical service(s) being documented | Σ | 0..* | BackboneElement | The clinical service(s) being documented | |||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized Slice: Unordered, Open by value:url | |||||||||
| period | Σ | 0..1 | Period | The period covered by the documentation | Σ | 0..1 | Period | The period covered by the documentation | |||||||||
| detail | Σ | 0..* | CodeableReference(Resource) | The event(s) being documented, as code(s), reference(s), or both Binding: ?? (example): This list of codes represents the main clinical acts being documented. | Σ | 0..* | CodeableReference(Resource) | The event(s) being documented, as code(s), reference(s), or both Binding: ?? (example): This list of codes represents the main clinical acts being documented. | |||||||||
| section | C | 0..* | BackboneElement | Composition is broken into sections | C | 0..* | BackboneElement | Composition is broken into sections | |||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized Slice: Unordered, Open by value:url | |||||||||
| title | 0..1 | string | Label for section (e.g. for ToC) | 0..1 | string | Label for section (e.g. for ToC) | |||||||||||
| code | 0..1 | CodeableConcept | Classification of section (recommended) Binding: ?? (extensible) | 0..1 | CodeableConcept | Classification of section (recommended) Binding: ?? (extensible) | |||||||||||
| author | 0..* | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) | Who and/or what authored the section | 0..* | Reference(Practitioner | PractitionerRole | CareTeam | Device | Patient | RelatedPerson | Organization) | Who and/or what authored the section, when the section is authored by someone other than the composition.author | |||||||||||
| focus | 0..1 | Reference(Resource) | Who/what the section is about, when it is not about the subject of composition | 0..1 | Reference(Resource) | Who/what the section is about, when it is not about the subject of the composition | |||||||||||
| text | C | 0..1 | Narrative | Text summary of the section, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | C | 0..1 | Narrative | Text summary of the section, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | |||||||||
| orderedBy | 0..1 | CodeableConcept | Order of section entries Binding: ?? (preferred): What order applies to the items in the entry. | 0..1 | CodeableConcept | Order of section entries Binding: ?? (preferred): What order applies to the items in the entry. |
| ||||||||||
| entry | C | 0..* | Reference(Resource) | A reference to data that supports this section | C | 0..* | Reference(Resource) | A reference to data that supports this section | |||||||||
| emptyReason | C | 0..1 | CodeableConcept | Why the section is empty Binding: ?? (preferred): If a section is empty, why it is empty. | C | 0..1 | CodeableConcept | Why the section is empty Binding: ?? (preferred): If a section is empty, why it is empty. |
| ||||||||
 section | 0..* | See section (Composition) | Nested Section | 0..* | See section (Composition) | Nested Section | |||||||||||
| note | 0..* | Annotation | Information about the section contents that is not represented by any of the section entries |
| |||||||||||||
| consent | 0..* | Reference(Consent) | Represents informed consents and medico-legal transactions |
| |||||||||||||
| basedOn | 0..* | Reference(Appointment | AppointmentResponse | CarePlan | Claim | CommunicationRequest | CoverageEligibilityRequest | DeviceRequest | MedicationRequest | NutritionOrder | RequestOrchestration | ServiceRequest | Task | VisionPrescription) | Fulfills plan, proposal or order |
| |||||||||||||
| participant | 0..* | BackboneElement | Identifies supporting entities, including parents, relatives, caregivers, insurance policyholders, guarantors, and others related in some way to the patient |
| |||||||||||||
| classification | Σ | 0..* | BackboneElement | The assignment to an organizing scheme |
| ||||||||||||
| Documentation for this format | |||||||||||||||||