Dental Data Exchange
1.0.0 - STU 1

Publication Build: This will be filled in by the publication tooling

## Resource Profile: DentalConsultNote - Detailed Descriptions

Definitions for the dental-consult-note resource profile.

1. Composition
Definition | 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.).
Control | 0..*
Comments | 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.
Invariants | Defined on this element dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty()) dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource (: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()) dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated (: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()) dom-5: If a resource is contained in another resource, it SHALL NOT have a security label (: contained.meta.security.empty()) dom-6: A resource should have narrative for robust management (: text.`div`.exists())
2. Composition.id
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Control | 0..1
Type | string
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
3. Composition.meta
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
Control | 0..1
Type | Meta
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
4. Composition.implicitRules
Definition | 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.
Control | 0..1
Type | uri
Is Modifier | true
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
5. Composition.language
Definition | The base language in which the resource is written.
Control | 1..1
Binding | The codes SHOULD be taken from CommonLanguages Max Binding: AllLanguages A human language.
Type | code
Must Support | true
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
6. Composition.text
Definition | A human-readable narrative that contains a summary of the resource and can be 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. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Control | 0..1
Type | Narrative
Alternate Names | narrative, html, xhtml, display
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
7. Composition.contained
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
Control | 0..*
Type | Resource
Alternate Names | inline resources, anonymous resources, contained resources
Comments | 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.
8. Composition.extension
Definition | An Extension
Control | 0..*
Type | Extension
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
Slicing | This element introduces a set of slices on Composition.extension. The slices are unordered and Open, and can be differentiated using the following discriminators: value @ url
9. Composition.extension:versionNumber
SliceName | versionNumber
Definition | Version specific identifier for the composition, assigned when each version is created/updated.
Control | 0..* This element is affected by the following invariants: ele-1
Type | Extension(versionNumber) (Extension Type: string)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
10. Composition.extension:version_number_extension
SliceName | version_number_extension
Definition | An Extension
Control | 0..1
Type | Extension(VersionNumber) (Extension Type: integer)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
11. Composition.extension:data_enterer_extension
SliceName | data_enterer_extension
Definition | An Extension
Control | 0..1
Type | Extension(DataEntererExtension) (Extension Type: Reference)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
12. Composition.extension:informant_extension
SliceName | informant_extension
Definition | An Extension
Control | 0..*
Type | Extension(InformantExtension) (Extension Type: Reference)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
13. Composition.extension:information_recipient_extension
SliceName | information_recipient_extension
Definition | An Extension
Control | 0..*
Type | Extension(InformationRecipientExtension) (Extension Type: Reference)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
14. Composition.extension:participant_extension
SliceName | participant_extension
Definition | An Extension
Control | 0..*
Type | Extension(ParticipantExtension) (Extension Type: Reference)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
15. Composition.extension:performer_extension
SliceName | performer_extension
Definition | An Extension
Control | 0..*
Type | Extension(PerformerExtension) (Extension Type: Reference)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
16. Composition.extension:authorization_extension
SliceName | authorization_extension
Definition | An Extension
Control | 0..*
Type | Extension(AuthorizationExtension) (Extension Type: Reference)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
17. Composition.extension:order_extension
SliceName | order_extension
Definition | An Extension
Control | 0..* This element is affected by the following invariants: ele-1
Type | Extension(OrderExtension) (Extension Type: Reference)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
18. Composition.extension:order_extension.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
19. Composition.extension:order_extension.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
Slicing | This element introduces a set of slices on Composition.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators: value @ url
20. Composition.extension:order_extension.url
Definition | Source of the definition for the extension code - a logical name or a URL.
Control | 1..1
Type | uri
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Fixed Value | http://hl7.org/fhir/us/ccda/StructureDefinition/OrderExtension
21. Composition.extension:order_extension.value[x]
Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).
Control | 1..1
Type | Reference(DentalServiceRequest)
[x] Note | See Choice of Data Types for further information about how to use [x]
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators: type @ $this
22. Composition.extension:order_extension.value[x]:valueReference
SliceName | valueReference
Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).
Control | 1..1
Type | Reference(ServiceRequest)
[x] Note | See Choice of Data Types for further information about how to use [x]
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
23. Composition.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
24. Composition.identifier
Definition | A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time.
Note | This is a business identifier, not a resource identifier (see discussion)
Control | 1..1
Type | Identifier
Must Support | true
Comments | Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
25. Composition.status
Definition | The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.
Control | 1..1
Binding | The codes SHALL be taken from CompositionStatus The workflow/clinical status of the composition.
Type | code
Is Modifier | true
Requirements | Need to be able to mark interim, amended, or withdrawn compositions or documents.
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 "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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
26. Composition.type
Definition | 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.
Control | 1..1
Binding | The codes SHALL be taken from ConsultDocumentType
Type | CodeableConcept
Must Support | true
Requirements | Key metadata element describing the composition, used in searching/filtering.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="34756-7"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
27. Composition.category
Definition | 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.
Control | 0..*
Binding | For example codes, see DocumentClassValueSet High-level kind of a clinical document at a macro level.
Type | CodeableConcept
Requirements | Helps humans to assess whether the composition is of interest when viewing an index of compositions or documents.
Comments | This is a metadata field from XDS/MHD.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
28. Composition.subject
Definition | 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).
Control | 0..1
Type | Reference(USCorePatientProfile | Group)
Must Support | true
Must Support Types | No must-support rules about the choice of types/profiles
Requirements | Essential metadata for searching for the composition. Identifies who and/or what the composition/document is about.
Comments | For clinical documents, this is usually the patient.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
29. Composition.encounter
Definition | Describes the clinical encounter or type of care this documentation is associated with.
Control | 1..1
Type | Reference(USCoreEncounterProfile)
Must Support | true
Requirements | Provides context for the composition and supports searching.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
30. Composition.date
Definition | The composition editing time, when the composition was last logically changed by the author.
Control | 1..1
Type | dateTime
Must Support | true
Requirements | dateTime is used for tracking, organizing versions and searching. Note that this is the time of authoring. When packaged in a document, Bundle.timestamp is the date of packaging.
Comments | The Last Modified Date on the composition may be after the date of the document was attested without being changed.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
31. Composition.author
Definition | Identifies who is responsible for the information in the composition, not necessarily who typed it in.
Control | 1..*
Type | Reference(USCorePractitionerProfile | USCorePractitionerRoleProfile | PractitionerRole | USCorePatientProfile | Device | RelatedPerson)
Must Support | true
Must Support Types | No must-support rules about the choice of types/profiles
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
32. Composition.title
Definition | Official human-readable label for the composition.
Control | 1..1
Type | string
Must Support | true
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
33. Composition.confidentiality
Definition | Use the confidentiality codes in Meta.security (https://hl7.org/fhir/security-labels.html)
Control | 0..0
Binding | The codes SHALL be taken from v3.ConfidentialityClassification (2014-03-26) Codes specifying the level of confidentiality of the composition.
Type | code
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). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
34. Composition.attester
Definition | A participant who has attested to the accuracy of the composition/document.
Control | 0..*
Type | BackboneElement
Requirements | Identifies responsibility for the accuracy of the composition content.
Comments | Only list each attester once.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.attester. The slices are unordered and Open, and can be differentiated using the following discriminators: value @ mode
35. Composition.attester.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
36. Composition.attester.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
37. Composition.attester.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
38. Composition.attester.mode
Definition | The type of attestation the authenticator offers.
Control | 1..1
Binding | The codes SHALL be taken from CompositionAttestationMode The way in which a person authenticated a composition.
Type | code
Requirements | Indicates the level of authority of the attestation.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
39. Composition.attester.time
Definition | When the composition was attested by the party.
Control | 0..1
Type | dateTime
Requirements | Identifies when the information in the composition was deemed accurate. (Things may have changed since then.).
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
40. Composition.attester.party
Definition | Who attested the composition in the specified way.
Control | 0..1
Type | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization)
Requirements | Identifies who has taken on the responsibility for accuracy of the composition content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
41. Composition.attester:legal_attester
SliceName | legal_attester
Definition | A participant who has attested to the accuracy of the composition/document.
Control | 0..1
Type | BackboneElement
Must Support | true
Requirements | Identifies responsibility for the accuracy of the composition content.
Comments | Only list each attester once.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
42. Composition.attester:legal_attester.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
43. Composition.attester:legal_attester.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
44. Composition.attester:legal_attester.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
45. Composition.attester:legal_attester.mode
Definition | The type of attestation the authenticator offers.
Control | 1..1
Binding | The codes SHALL be taken from CompositionAttestationMode The way in which a person authenticated a composition.
Type | code
Must Support | true
Requirements | Indicates the level of authority of the attestation.
Fixed Value | legal
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
46. Composition.attester:legal_attester.time
Definition | When the composition was attested by the party.
Control | 0..1
Type | dateTime
Requirements | Identifies when the information in the composition was deemed accurate. (Things may have changed since then.).
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
47. Composition.attester:legal_attester.party
Definition | Who attested the composition in the specified way.
Control | 1..1
Type | Reference(USCorePractitionerProfile | USCorePractitionerRoleProfile)
Must Support | true
Must Support Types | No must-support rules about the choice of types/profiles
Requirements | Identifies who has taken on the responsibility for accuracy of the composition content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
48. Composition.attester:professional_attester
SliceName | professional_attester
Definition | A participant who has attested to the accuracy of the composition/document.
Control | 0..*
Type | BackboneElement
Must Support | true
Requirements | Identifies responsibility for the accuracy of the composition content.
Comments | Only list each attester once.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
49. Composition.attester:professional_attester.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
50. Composition.attester:professional_attester.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
51. Composition.attester:professional_attester.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
52. Composition.attester:professional_attester.mode
Definition | The type of attestation the authenticator offers.
Control | 1..1
Binding | The codes SHALL be taken from CompositionAttestationMode The way in which a person authenticated a composition.
Type | code
Must Support | true
Requirements | Indicates the level of authority of the attestation.
Fixed Value | professional
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
53. Composition.attester:professional_attester.time
Definition | When the composition was attested by the party.
Control | 0..1
Type | dateTime
Requirements | Identifies when the information in the composition was deemed accurate. (Things may have changed since then.).
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
54. Composition.attester:professional_attester.party
Definition | Who attested the composition in the specified way.
Control | 1..1
Type | Reference(USCorePractitionerProfile | USCorePractitionerRoleProfile)
Must Support | true
Must Support Types | No must-support rules about the choice of types/profiles
Requirements | Identifies who has taken on the responsibility for accuracy of the composition content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
55. Composition.attester:personal_attester
SliceName | personal_attester
Definition | A participant who has attested to the accuracy of the composition/document.
Control | 0..*
Type | BackboneElement
Must Support | true
Requirements | Identifies responsibility for the accuracy of the composition content.
Comments | Only list each attester once.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
56. Composition.attester:personal_attester.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
57. Composition.attester:personal_attester.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
58. Composition.attester:personal_attester.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
59. Composition.attester:personal_attester.mode
Definition | The type of attestation the authenticator offers.
Control | 1..1
Binding | The codes SHALL be taken from CompositionAttestationMode The way in which a person authenticated a composition.
Type | code
Must Support | true
Requirements | Indicates the level of authority of the attestation.
Fixed Value | personal
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
60. Composition.attester:personal_attester.time
Definition | When the composition was attested by the party.
Control | 0..1
Type | dateTime
Requirements | Identifies when the information in the composition was deemed accurate. (Things may have changed since then.).
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
61. Composition.attester:personal_attester.party
Definition | Who attested the composition in the specified way.
Control | 1..1
Type | Reference(USCorePatientProfile | RelatedPerson)
Must Support | true
Must Support Types | No must-support rules about the choice of types/profiles
Requirements | Identifies who has taken on the responsibility for accuracy of the composition content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
62. Composition.custodian
Definition | Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information.
Control | 1..1
Type | Reference(USCoreOrganizationProfile)
Must Support | true
Requirements | Identifies where to go to find the current version, where to report issues, etc.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
63. Composition.relatesTo
Definition | Relationships that this composition has with other compositions or documents that already exist.
Control | 0..*
Type | BackboneElement
Comments | A document is a version specific composition.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
64. Composition.relatesTo.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
65. Composition.relatesTo.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
66. Composition.relatesTo.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
67. Composition.relatesTo.code
Definition | The type of relationship that this composition has with anther composition or document.
Control | 1..1
Binding | The codes SHALL be taken from DocumentRelationshipType The type of relationship between documents.
Type | code
Comments | If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
68. Composition.relatesTo.target[x]
Definition | The target composition/document of this relationship.
Control | 1..1
Type | Choice of: Identifier, Reference(Composition)
[x] Note | See Choice of Data Types for further information about how to use [x]
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
69. Composition.event
Definition | The clinical service, such as a colonoscopy or an appendectomy, being documented.
Control | 0..*
Type | BackboneElement
Requirements | Provides context for the composition and creates a linkage between a resource describing an event and the composition created describing the event.
Comments | The event needs to be consistent with the type element, though can provide further information if desired.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
70. Composition.event.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
71. Composition.event.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
72. Composition.event.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
73. Composition.event.code
Definition | 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.
Control | 0..*
Binding | For example codes, see v3 Code System ActCode This list of codes represents the main clinical acts being documented.
Type | CodeableConcept
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
74. Composition.event.period
Definition | 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.
Control | 0..1
Type | Period
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
75. Composition.event.detail
Definition | 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.
Control | 0..*
Type | Reference(Resource)
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
76. Composition.section
Definition | The root of the sections that make up the composition.
Control | 0..*
Type | BackboneElement
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section. The slices are unordered and Open, and can be differentiated using the following discriminators: value @ code
77. Composition.section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
78. Composition.section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
79. Composition.section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
80. Composition.section.title
Definition | 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.
Control | 0..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
81. Composition.section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 0..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
82. Composition.section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
83. Composition.section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
84. Composition.section.text
Definition | 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.
Control | 0..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
85. Composition.section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
86. Composition.section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
87. Composition.section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
88. Composition.section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
89. Composition.section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
90. Composition.section:allergies_and_intolerances_section
SliceName | allergies_and_intolerances_section
Definition | The root of the sections that make up the composition.
Control | 1..1
Type | BackboneElement
Must Support | true
Comments | Allergies and Intolerances Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
91. Composition.section:allergies_and_intolerances_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
92. Composition.section:allergies_and_intolerances_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
93. Composition.section:allergies_and_intolerances_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
94. Composition.section:allergies_and_intolerances_section.title
Definition | 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.
Control | 1..1
Type | string
Must Support | true
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
95. Composition.section:allergies_and_intolerances_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Must Support | true
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="48765-2"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
96. Composition.section:allergies_and_intolerances_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
97. Composition.section:allergies_and_intolerances_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
98. Composition.section:allergies_and_intolerances_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Must Support | true
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
99. Composition.section:allergies_and_intolerances_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
100. Composition.section:allergies_and_intolerances_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
101. Composition.section:allergies_and_intolerances_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
102. Composition.section:allergies_and_intolerances_section.entry:allergy_intolerance_entry
SliceName | allergy_intolerance_entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreAllergyIntolerance)
Must Support | true
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
103. Composition.section:allergies_and_intolerances_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
104. Composition.section:allergies_and_intolerances_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
105. Composition.section:history_of_present_illness_section
SliceName | history_of_present_illness_section
Definition | The root of the sections that make up the composition.
Control | 1..1
Type | BackboneElement
Must Support | true
Comments | History of Present Illness Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
106. Composition.section:history_of_present_illness_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
107. Composition.section:history_of_present_illness_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
108. Composition.section:history_of_present_illness_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
109. Composition.section:history_of_present_illness_section.title
Definition | 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.
Control | 1..1
Type | string
Must Support | true
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
110. Composition.section:history_of_present_illness_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Must Support | true
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="10164-2"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
111. Composition.section:history_of_present_illness_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
112. Composition.section:history_of_present_illness_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
113. Composition.section:history_of_present_illness_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Must Support | true
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
114. Composition.section:history_of_present_illness_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
115. Composition.section:history_of_present_illness_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
116. Composition.section:history_of_present_illness_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
117. Composition.section:history_of_present_illness_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
118. Composition.section:history_of_present_illness_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
119. Composition.section:problem_section
SliceName | problem_section
Definition | The root of the sections that make up the composition.
Control | 1..1
Type | BackboneElement
Comments | Problem Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
120. Composition.section:problem_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
121. Composition.section:problem_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
122. Composition.section:problem_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
123. Composition.section:problem_section.title
Definition | 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.
Control | 1..1
Type | string
Must Support | true
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
124. Composition.section:problem_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Must Support | true
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="11450-4"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
125. Composition.section:problem_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
126. Composition.section:problem_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
127. Composition.section:problem_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
128. Composition.section:problem_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
129. Composition.section:problem_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
130. Composition.section:problem_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
131. Composition.section:problem_section.entry:problem_section_entry
SliceName | problem_section_entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreCondition)
Must Support | true
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
132. Composition.section:problem_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
133. Composition.section:problem_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
134. Composition.section:medications_section
SliceName | medications_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Medications Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
135. Composition.section:medications_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
136. Composition.section:medications_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
137. Composition.section:medications_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
138. Composition.section:medications_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
139. Composition.section:medications_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="10160-0"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
140. Composition.section:medications_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
141. Composition.section:medications_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
142. Composition.section:medications_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
143. Composition.section:medications_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
144. Composition.section:medications_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
145. Composition.section:medications_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
146. Composition.section:medications_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(MedicationStatement | USCoreMedicationProfile | USCoreMedicationRequestProfile)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
147. Composition.section:medications_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
148. Composition.section:medications_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
149. Composition.section:physical_exam_section
SliceName | physical_exam_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Physical Exam Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
150. Composition.section:physical_exam_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
151. Composition.section:physical_exam_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
152. Composition.section:physical_exam_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
153. Composition.section:physical_exam_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
154. Composition.section:physical_exam_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="29545-1"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
155. Composition.section:physical_exam_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
156. Composition.section:physical_exam_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
157. Composition.section:physical_exam_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
158. Composition.section:physical_exam_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
159. Composition.section:physical_exam_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
160. Composition.section:physical_exam_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
161. Composition.section:physical_exam_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Observation)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
162. Composition.section:physical_exam_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
163. Composition.section:physical_exam_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
164. Composition.section:results_section
SliceName | results_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Results Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
165. Composition.section:results_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
166. Composition.section:results_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
167. Composition.section:results_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
168. Composition.section:results_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
169. Composition.section:results_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="30954-2"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
170. Composition.section:results_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
171. Composition.section:results_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
172. Composition.section:results_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
173. Composition.section:results_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
174. Composition.section:results_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
175. Composition.section:results_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
176. Composition.section:results_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreLaboratoryResultObservationProfile)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
177. Composition.section:results_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
178. Composition.section:results_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
179. Composition.section:advance_directives_section
SliceName | advance_directives_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Must Support | true
Comments | Advance Directives Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
180. Composition.section:advance_directives_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
181. Composition.section:advance_directives_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
182. Composition.section:advance_directives_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
183. Composition.section:advance_directives_section.title
Definition | 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.
Control | 1..1
Type | string
Must Support | true
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
184. Composition.section:advance_directives_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Must Support | true
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="42348-3"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
185. Composition.section:advance_directives_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
186. Composition.section:advance_directives_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
187. Composition.section:advance_directives_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Must Support | true
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
188. Composition.section:advance_directives_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
189. Composition.section:advance_directives_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
190. Composition.section:advance_directives_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
191. Composition.section:advance_directives_section.entry:advance_directive_entry
SliceName | advance_directive_entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Consent)
Must Support | true
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
192. Composition.section:advance_directives_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
193. Composition.section:advance_directives_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
194. Composition.section:assessment_and_plan_section
SliceName | assessment_and_plan_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Assessment and Plan Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
195. Composition.section:assessment_and_plan_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
196. Composition.section:assessment_and_plan_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
197. Composition.section:assessment_and_plan_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
198. Composition.section:assessment_and_plan_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
199. Composition.section:assessment_and_plan_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="51847-2"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
200. Composition.section:assessment_and_plan_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
201. Composition.section:assessment_and_plan_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
202. Composition.section:assessment_and_plan_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
203. Composition.section:assessment_and_plan_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
204. Composition.section:assessment_and_plan_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
205. Composition.section:assessment_and_plan_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
206. Composition.section:assessment_and_plan_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreCondition | Observation | Communication)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
207. Composition.section:assessment_and_plan_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
208. Composition.section:assessment_and_plan_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
209. Composition.section:assessment_section
SliceName | assessment_section
Definition | The root of the sections that make up the composition.
Control | 1..1
Type | BackboneElement
Comments | Assessment Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
210. Composition.section:assessment_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
211. Composition.section:assessment_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
212. Composition.section:assessment_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
213. Composition.section:assessment_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
214. Composition.section:assessment_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="51848-0"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
215. Composition.section:assessment_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
216. Composition.section:assessment_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
217. Composition.section:assessment_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
218. Composition.section:assessment_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
219. Composition.section:assessment_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
220. Composition.section:assessment_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
221. Composition.section:assessment_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
222. Composition.section:assessment_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
223. Composition.section:chief_complaint_and_reason_for_visit_section
SliceName | chief_complaint_and_reason_for_visit_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Chief Complaint and Reason for Visit Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
224. Composition.section:chief_complaint_and_reason_for_visit_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
225. Composition.section:chief_complaint_and_reason_for_visit_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
226. Composition.section:chief_complaint_and_reason_for_visit_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
227. Composition.section:chief_complaint_and_reason_for_visit_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
228. Composition.section:chief_complaint_and_reason_for_visit_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="46239-0"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
229. Composition.section:chief_complaint_and_reason_for_visit_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
230. Composition.section:chief_complaint_and_reason_for_visit_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
231. Composition.section:chief_complaint_and_reason_for_visit_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
232. Composition.section:chief_complaint_and_reason_for_visit_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
233. Composition.section:chief_complaint_and_reason_for_visit_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
234. Composition.section:chief_complaint_and_reason_for_visit_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
235. Composition.section:chief_complaint_and_reason_for_visit_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
236. Composition.section:chief_complaint_and_reason_for_visit_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
237. Composition.section:chief_complaint_section
SliceName | chief_complaint_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Chief Complaint Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
238. Composition.section:chief_complaint_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
239. Composition.section:chief_complaint_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
240. Composition.section:chief_complaint_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
241. Composition.section:chief_complaint_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
242. Composition.section:chief_complaint_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="10154-3"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
243. Composition.section:chief_complaint_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
244. Composition.section:chief_complaint_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
245. Composition.section:chief_complaint_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
246. Composition.section:chief_complaint_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
247. Composition.section:chief_complaint_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
248. Composition.section:chief_complaint_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
249. Composition.section:chief_complaint_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
250. Composition.section:chief_complaint_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
251. Composition.section:family_history_section
SliceName | family_history_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Family History Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
252. Composition.section:family_history_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
253. Composition.section:family_history_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
254. Composition.section:family_history_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
255. Composition.section:family_history_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
256. Composition.section:family_history_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="10157-6"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
257. Composition.section:family_history_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
258. Composition.section:family_history_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
259. Composition.section:family_history_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
260. Composition.section:family_history_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
261. Composition.section:family_history_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
262. Composition.section:family_history_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
263. Composition.section:family_history_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(FamilyMemberHistory)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
264. Composition.section:family_history_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
265. Composition.section:family_history_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
266. Composition.section:functional_status_section
SliceName | functional_status_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Functional Status Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
267. Composition.section:functional_status_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
268. Composition.section:functional_status_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
269. Composition.section:functional_status_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
270. Composition.section:functional_status_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
271. Composition.section:functional_status_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="47420-5"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
272. Composition.section:functional_status_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
273. Composition.section:functional_status_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
274. Composition.section:functional_status_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
275. Composition.section:functional_status_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
276. Composition.section:functional_status_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
277. Composition.section:functional_status_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
278. Composition.section:functional_status_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Observation)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
279. Composition.section:functional_status_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
280. Composition.section:functional_status_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
281. Composition.section:general_status_section
SliceName | general_status_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | General Status Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
282. Composition.section:general_status_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
283. Composition.section:general_status_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
284. Composition.section:general_status_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
285. Composition.section:general_status_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
286. Composition.section:general_status_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="10210-3"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
287. Composition.section:general_status_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
288. Composition.section:general_status_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
289. Composition.section:general_status_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
290. Composition.section:general_status_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
291. Composition.section:general_status_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
292. Composition.section:general_status_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
293. Composition.section:general_status_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
294. Composition.section:general_status_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
295. Composition.section:past_medical_history_section
SliceName | past_medical_history_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Past Medical History Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
296. Composition.section:past_medical_history_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
297. Composition.section:past_medical_history_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
298. Composition.section:past_medical_history_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
299. Composition.section:past_medical_history_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
300. Composition.section:past_medical_history_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="11348-0"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
301. Composition.section:past_medical_history_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
302. Composition.section:past_medical_history_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
303. Composition.section:past_medical_history_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
304. Composition.section:past_medical_history_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
305. Composition.section:past_medical_history_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
306. Composition.section:past_medical_history_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
307. Composition.section:past_medical_history_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreCondition)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
308. Composition.section:past_medical_history_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
309. Composition.section:past_medical_history_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
310. Composition.section:immunizations_section
SliceName | immunizations_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Immunizations Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
311. Composition.section:immunizations_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
312. Composition.section:immunizations_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
313. Composition.section:immunizations_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
314. Composition.section:immunizations_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
315. Composition.section:immunizations_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="11369-6"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
316. Composition.section:immunizations_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
317. Composition.section:immunizations_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
318. Composition.section:immunizations_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
319. Composition.section:immunizations_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
320. Composition.section:immunizations_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
321. Composition.section:immunizations_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
322. Composition.section:immunizations_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreImmunizationProfile)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
323. Composition.section:immunizations_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
324. Composition.section:immunizations_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
325. Composition.section:medical_equipment_section
SliceName | medical_equipment_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Medical Equipment Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
326. Composition.section:medical_equipment_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
327. Composition.section:medical_equipment_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
328. Composition.section:medical_equipment_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
329. Composition.section:medical_equipment_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
330. Composition.section:medical_equipment_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="46264-8"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
331. Composition.section:medical_equipment_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
332. Composition.section:medical_equipment_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
333. Composition.section:medical_equipment_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
334. Composition.section:medical_equipment_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
335. Composition.section:medical_equipment_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
336. Composition.section:medical_equipment_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
337. Composition.section:medical_equipment_section.entry:medical_equipment_entry
SliceName | medical_equipment_entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Device | USCoreProcedureProfile)
Must Support | true
Must Support Types | No must-support rules about the choice of types/profiles
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
338. Composition.section:medical_equipment_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
339. Composition.section:medical_equipment_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
340. Composition.section:mental_status_section
SliceName | mental_status_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Mental Status Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
341. Composition.section:mental_status_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
342. Composition.section:mental_status_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
343. Composition.section:mental_status_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
344. Composition.section:mental_status_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
345. Composition.section:mental_status_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="10190-7"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
346. Composition.section:mental_status_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
347. Composition.section:mental_status_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
348. Composition.section:mental_status_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
349. Composition.section:mental_status_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
350. Composition.section:mental_status_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
351. Composition.section:mental_status_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
352. Composition.section:mental_status_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Observation)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
353. Composition.section:mental_status_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
354. Composition.section:mental_status_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
355. Composition.section:nutrition_section
SliceName | nutrition_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Nutrition Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
356. Composition.section:nutrition_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
357. Composition.section:nutrition_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
358. Composition.section:nutrition_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
359. Composition.section:nutrition_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
360. Composition.section:nutrition_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="61144-2"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
361. Composition.section:nutrition_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
362. Composition.section:nutrition_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
363. Composition.section:nutrition_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
364. Composition.section:nutrition_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
365. Composition.section:nutrition_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
366. Composition.section:nutrition_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
367. Composition.section:nutrition_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(NutritionOrder | ClinicalImpression)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
368. Composition.section:nutrition_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
369. Composition.section:nutrition_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
370. Composition.section:plan_of_treatment_section
SliceName | plan_of_treatment_section
Definition | The root of the sections that make up the composition.
Control | 1..1
Type | BackboneElement
Comments | Plan of Treatment Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
371. Composition.section:plan_of_treatment_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
372. Composition.section:plan_of_treatment_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
373. Composition.section:plan_of_treatment_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
374. Composition.section:plan_of_treatment_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
375. Composition.section:plan_of_treatment_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="18776-5"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
376. Composition.section:plan_of_treatment_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
377. Composition.section:plan_of_treatment_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
378. Composition.section:plan_of_treatment_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
379. Composition.section:plan_of_treatment_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
380. Composition.section:plan_of_treatment_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
381. Composition.section:plan_of_treatment_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(DentalServiceRequest | DentalCommunication | USCoreMedicationRequestProfile | USCoreEncounterProfile | Appointment | USCoreGoalProfile | CommunicationRequest | DeviceRequest | NutritionOrder | Task | VisionPrescription | RequestGroup)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
382. Composition.section:plan_of_treatment_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreGoalProfile | USCoreMedicationRequestProfile | USCoreEncounterProfile | Communication | Appointment | CommunicationRequest | DeviceRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription | RequestGroup)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
383. Composition.section:plan_of_treatment_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
384. Composition.section:plan_of_treatment_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
385. Composition.section:procedures_section
SliceName | procedures_section
Definition | The root of the sections that make up the composition.
Control | 1..1
Type | BackboneElement
Comments | Procedures Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
386. Composition.section:procedures_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
387. Composition.section:procedures_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
388. Composition.section:procedures_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
389. Composition.section:procedures_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
390. Composition.section:procedures_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="47519-4"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
391. Composition.section:procedures_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
392. Composition.section:procedures_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
393. Composition.section:procedures_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
394. Composition.section:procedures_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
395. Composition.section:procedures_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
396. Composition.section:procedures_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
397. Composition.section:procedures_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreProcedureProfile)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
398. Composition.section:procedures_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
399. Composition.section:procedures_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
400. Composition.section:reason_for_visit_section
SliceName | reason_for_visit_section
Definition | The root of the sections that make up the composition.
Control | 1..1
Type | BackboneElement
Comments | Reason for Visit Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
401. Composition.section:reason_for_visit_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
402. Composition.section:reason_for_visit_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
403. Composition.section:reason_for_visit_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
404. Composition.section:reason_for_visit_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
405. Composition.section:reason_for_visit_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="29299-5"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
406. Composition.section:reason_for_visit_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
407. Composition.section:reason_for_visit_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
408. Composition.section:reason_for_visit_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
409. Composition.section:reason_for_visit_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
410. Composition.section:reason_for_visit_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
411. Composition.section:reason_for_visit_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
412. Composition.section:reason_for_visit_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
413. Composition.section:reason_for_visit_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
414. Composition.section:review_of_systems_section
SliceName | review_of_systems_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Review of Systems Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
415. Composition.section:review_of_systems_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
416. Composition.section:review_of_systems_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
417. Composition.section:review_of_systems_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
418. Composition.section:review_of_systems_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
419. Composition.section:review_of_systems_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="10187-3"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
420. Composition.section:review_of_systems_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
421. Composition.section:review_of_systems_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
422. Composition.section:review_of_systems_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
423. Composition.section:review_of_systems_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
424. Composition.section:review_of_systems_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
425. Composition.section:review_of_systems_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
426. Composition.section:review_of_systems_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
427. Composition.section:review_of_systems_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
428. Composition.section:social_history_section
SliceName | social_history_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Social History Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
429. Composition.section:social_history_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
430. Composition.section:social_history_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
431. Composition.section:social_history_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
432. Composition.section:social_history_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
433. Composition.section:social_history_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="29762-2"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
434. Composition.section:social_history_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
435. Composition.section:social_history_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
436. Composition.section:social_history_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
437. Composition.section:social_history_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
438. Composition.section:social_history_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
439. Composition.section:social_history_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
440. Composition.section:social_history_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(USCoreSmokingStatusProfile)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
441. Composition.section:social_history_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
442. Composition.section:social_history_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
443. Composition.section:vital_signs_section
SliceName | vital_signs_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Comments | Vital Signs Section
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
444. Composition.section:vital_signs_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
445. Composition.section:vital_signs_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
446. Composition.section:vital_signs_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
447. Composition.section:vital_signs_section.title
Definition | 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.
Control | 1..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
448. Composition.section:vital_signs_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="8716-3"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
449. Composition.section:vital_signs_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
450. Composition.section:vital_signs_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
451. Composition.section:vital_signs_section.text
Definition | 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.
Control | 1..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
452. Composition.section:vital_signs_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
453. Composition.section:vital_signs_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
454. Composition.section:vital_signs_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
455. Composition.section:vital_signs_section.entry:sliceEntry
SliceName | sliceEntry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(observation-vitalsigns)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
456. Composition.section:vital_signs_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
457. Composition.section:vital_signs_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
458. Composition.section:instructions
SliceName | instructions
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Must Support | true
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
459. Composition.section:instructions.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
460. Composition.section:instructions.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
461. Composition.section:instructions.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
462. Composition.section:instructions.title
Definition | 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.
Control | 1..1
Type | string
Must Support | true
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
463. Composition.section:instructions.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Must Support | true
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="69730-0"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
464. Composition.section:instructions.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
465. Composition.section:instructions.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
466. Composition.section:instructions.text
Definition | 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.
Control | 0..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
467. Composition.section:instructions.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
468. Composition.section:instructions.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
469. Composition.section:instructions.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
470. Composition.section:instructions.entry:dental_instructions
SliceName | dental_instructions
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(DentalCommunication)
Must Support | true
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
471. Composition.section:instructions.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
472. Composition.section:instructions.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
473. Composition.section:payers_section
SliceName | payers_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
474. Composition.section:payers_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
475. Composition.section:payers_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
476. Composition.section:payers_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
477. Composition.section:payers_section.title
Definition | 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.
Control | 0..1
Type | string
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
478. Composition.section:payers_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 1..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="48768-6"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
479. Composition.section:payers_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
480. Composition.section:payers_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
481. Composition.section:payers_section.text
Definition | 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.
Control | 0..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
482. Composition.section:payers_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
483. Composition.section:payers_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
484. Composition.section:payers_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
485. Composition.section:payers_section.entry:payers_entry
SliceName | payers_entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(HRexCoverage)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
486. Composition.section:payers_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
487. Composition.section:payers_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
488. Composition.section:dental_findings_section
SliceName | dental_findings_section
Definition | The root of the sections that make up the composition.
Control | 0..1
Type | BackboneElement
Must Support | true
Invariants | Defined on this element cmp-1: A section must contain at least one of text, entries, or sub-sections (: text.exists() or entry.exists() or section.exists()) cmp-2: A section can only have an emptyReason if it is empty (: emptyReason.empty() or entry.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
489. Composition.section:dental_findings_section.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
490. Composition.section:dental_findings_section.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
Control | 0..*
Type | Extension
Alternate Names | extensions, user content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
491. Composition.section:dental_findings_section.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Control | 0..*
Type | Extension
Is Modifier | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
492. Composition.section:dental_findings_section.title
Definition | 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.
Control | 1..1
Type | string
Must Support | true
Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
Alternate Names | header, label, caption
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
493. Composition.section:dental_findings_section.code
Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title.
Control | 0..1
Binding | For example codes, see DocumentSectionCodes Classification of a section of a composition/document.
Type | CodeableConcept
Must Support | true
Requirements | Provides computable standardized labels to topics within the document.
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.
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="8704-9"/> </coding> </valueCodeableConcept>
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
494. Composition.section:dental_findings_section.author
Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in.
Control | 0..*
Type | Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)
Requirements | Identifies who is responsible for the content.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
495. Composition.section:dental_findings_section.focus
Definition | 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).
Control | 0..1
Type | Reference(Resource)
Comments | 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
496. Composition.section:dental_findings_section.text
Definition | 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.
Control | 0..1 This element is affected by the following invariants: cmp-1
Type | Narrative
Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
497. Composition.section:dental_findings_section.mode
Definition | 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.
Control | 0..1
Binding | The codes SHALL be taken from ListMode The processing mode that applies to this section.
Type | code
Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
498. Composition.section:dental_findings_section.orderedBy
Definition | Specifies the order applied to the items in the section entries.
Control | 0..1
Binding | The codes SHOULD be taken from ListOrderCodes What order applies to the items in the entry.
Type | CodeableConcept
Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
499. Composition.section:dental_findings_section.entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(Resource)
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
Slicing | This element introduces a set of slices on Composition.section.entry. The slices are unordered and Open, and can be differentiated using the following discriminators: profile @ resolve()
500. Composition.section:dental_findings_section.entry:dental_findings_entry
SliceName | dental_findings_entry
Definition | A reference to the actual resource from which the narrative in the section is derived.
Control | 0..* This element is affected by the following invariants: cmp-2
Type | Reference(DentalFindings | USCoreCondition)
Must Support | true
Must Support Types | No must-support rules about the choice of types/profiles
Comments | If there are no entries in the list, an emptyReason SHOULD be provided.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
501. Composition.section:dental_findings_section.emptyReason
Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
Control | 0..1 This element is affected by the following invariants: cmp-2
Binding | The codes SHOULD be taken from ListEmptyReasons If a section is empty, why it is empty.
Type | CodeableConcept
Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists.
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.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
502. Composition.section:dental_findings_section.section
Definition | A nested sub-section within this section.
Control | 0..* This element is affected by the following invariants: cmp-1
Type | See ttp://hl7.org/fhir/StructureDefinition/Composition#Composition.section
Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document.
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))