COFE-Composition-End-Of-Life-1
Composition | |
Definition | |
Control | 0..* |
Type | Composition |
Comments | |
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 | Id |
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. Bundles always have an id, though it is usually a generated UUID. |
Composition.meta | |
Definition |
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Control | 0..1 ? |
Type | Meta |
Comments | |
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. |
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 as much as possible. |
Composition.language | |
Definition |
The base language in which the resource is written. |
Control | 0..1 ? |
Binding |
A human language. The codes SHALL be taken from http://tools.ietf.org/html/bcp47 |
Type | Code |
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). |
Composition.text | |
Definition |
A human-readable narrative that contains a summary of the resource, and may 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 |
Aliases | narrative, html, xhtml, display |
Comments |
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. |
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 |
Aliases | 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. |
Composition.extension(Data Enterer Extension) | |
Definition | |
Control | 0..1 |
Type | Extension |
Comments | |
Composition.extension(Informant Extension) | |
Definition | |
Control | 0..* |
Type | Extension |
Comments | |
Composition.extension(Information Recipient Extension) | |
Definition | |
Control | 0..* |
Type | Extension |
Comments | |
Composition.extension(Participant Extension) | |
Definition | |
Control | 0..* |
Type | Extension |
Comments | |
Composition.extension(Performer Extension) | |
Definition | |
Control | 0..* |
Type | Extension |
Comments | |
Composition.extension(Authorization Extension) | |
Definition | |
Control | 0..* |
Type | Extension |
Comments | |
Composition.extension(CareSettingType) | |
Definition | |
Control | 0..1 |
Type | Extension |
Comments | |
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. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.identifier | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.identifier.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.identifier.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.identifier.value | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Example | 871985a7-45f9-435a-89fa-fcedd7afa7a3 |
Composition.date | |
Definition | |
Control | 0..* |
Must Support | True |
Comments | |
Composition.type | |
Definition | |
Control | 0..* |
Binding |
Type of document. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/document-type-1 ; other codes may be used where these codes are not suitable |
Must Support | True |
Comments | |
Composition.type.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.type.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.type.coding | |
Definition | |
Control | 1..1 |
Binding |
Type of a document. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/document-type-1 ; other codes may be used where these codes are not suitable |
Must Support | True |
Comments | |
Composition.type.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.type.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.type.coding.system | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.type.coding.code | |
Definition | |
Control | 1..* |
Binding |
A set of codes to classify the type of document. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/document-type-1 ; other codes may be used where these codes are not suitable |
Must Support | True |
Comments | |
Example | 861421000000109 |
Composition.type.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Example | End of Life Care Coordination Summary |
Composition.title | |
Definition | |
Control | 0..* |
Must Support | True |
Comments | |
Composition.status | |
Definition | |
Control | 0..* |
Must Support | True |
Comments | |
Composition.confidentiality | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.subject | |
Definition | |
Control | 0..* |
Type | https://fhir.hl7.org.uk/StructureDefinition/CareConnect-Patient-1 |
Must Support | True |
Comments | |
Composition.subject.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.subject.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.subject.reference | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.subject.display | |
Definition |
Plain text narrative that identifies the resource in addition to the resource reference. |
Control | 0..1 ? |
Type | String |
Comments |
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Composition.author | |
Definition | |
Control | 0..* |
Type | Choice of: |
Must Support | True |
Comments | |
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. |
Composition.attester.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.attester.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.attester.mode | |
Definition | |
Control | 0..* |
Must Support | True |
Comments | |
Composition.attester.time | |
Definition |
When 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.). |
Comments | |
Composition.attester.party | |
Definition | |
Control | 0..* |
Type | Choice of: |
Comments | |
Composition.custodian | |
Definition | |
Control | 1..* |
Type | https://fhir.hl7.org.uk/StructureDefinition/CareConnect-Organization-1 |
Must Support | True |
Comments | |
Composition.custodian.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.custodian.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.custodian.reference | |
Definition | |
Control | 1..* |
Comments | |
Composition.custodian.display | |
Definition |
Plain text narrative that identifies the resource in addition to the resource reference. |
Control | 0..1 ? |
Type | String |
Comments |
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
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. |
Composition.event.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.event.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.event.code | |
Definition | |
Control | 0..* |
Binding |
This list of codes represents the main clinical acts being documented. It uses a code from any vocabulary to describe the type of service event. The vocabulary SnomedCT is a preferred vocabulary. The codes SHOULD be taken from http://snomed.info/sct ; other codes may be used where these codes are not suitable |
Comments | |
Composition.event.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.event.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.event.code.coding | |
Definition | |
Control | 0..* |
Binding |
A code defined by SNOMED CT The codes SHOULD be taken from http://snomed.info/sct ; other codes may be used where these codes are not suitable |
Comments | |
Composition.event.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.event.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.event.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.event.code.coding.code | |
Definition |
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Control | 0..1 ? |
Type | Code |
Requirements |
Need to refer to a particular code in the system. |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.event.code.coding.display | |
Definition |
A representation of the meaning of the code in the system, following the rules of the system. |
Control | 0..1 ? |
Type | String |
Requirements |
Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.event.code.text | |
Definition |
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Control | 0..1 ? |
Type | String |
Requirements |
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments |
Very often the text is the same as a displayName of one of the codings. |
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 |
Comments |
This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Composition.event.period.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.event.period.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.event.period.start | |
Definition |
The start of the period. The boundary is inclusive. |
Control | 0..1 ? |
Type | DateTime |
Comments |
If the low element is missing, the meaning is that the low boundary is not known. |
Composition.event.period.end | |
Definition |
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. |
Control | 0..1 ? |
Type | DateTime |
Comments |
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. |
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 | Resource |
Comments | |
Composition.event.detail.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.event.detail.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.event.detail.reference | |
Definition |
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Control | 0..1 ? |
Type | String |
Comments |
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. |
Composition.event.detail.display | |
Definition |
Plain text narrative that identifies the resource in addition to the resource reference. |
Control | 0..1 ? |
Type | String |
Comments |
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Composition.encounter | |
Definition | |
Control | 0..* |
Type | https://fhir.hl7.org.uk/StructureDefinition/CareConnect-Encounter-1 |
Comments | |
Composition.encounter.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.encounter.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.encounter.reference | |
Definition | |
Control | 1..* |
Comments | |
Composition.encounter.display | |
Definition |
Plain text narrative that identifies the resource in addition to the resource reference. |
Control | 0..1 ? |
Type | String |
Comments |
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Composition.section(Individual requirements section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Diagnoses section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Relevant past medical, surgical and mental health history section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Problems and issues section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Medications and medical devices section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Allergies and adverse reactions section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Safety alerts section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Legal information section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Social context section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Person and carer concerns, expectations and wishes section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Crisis care plan section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(End of life section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Composition.section(Person completing record section) | |
Definition | |
Control | 0..1 |
Must Support | True |
Comments | |
Composition.section.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* ? |
Type | Extension |
Is Modifier | True |
Aliases | 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. |
Composition.section.title | |
Definition | |
Control | 0..* |
Comments | |
Composition.section.code | |
Definition | |
Control | 0..* |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding | |
Definition | |
Control | 0..1 |
Binding |
A code from the SNOMED Clinical Terminology UK coding system which represent the type of section. The codes SHOULD be taken from https://fhir.nhs.uk/ValueSet/section-type-snct-1 ; other codes may be used where these codes are not suitable |
Comments | |
Composition.section.code.coding.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.code.coding.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.code.coding.system | |
Definition | |
Control | 0..* |
Comments | |
Fixed Value | http://snomed.info/sct |
Composition.section.code.coding.code | |
Definition | |
Control | 1..* |
Binding |
A SNOMED CT Code to indicate the type of section. The codes SHALL be taken from http://snomed.info/sct |
Must Support | True |
Comments | |
Fixed Value | 886741000000100 |
Composition.section.code.coding.display | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Fixed Value | Individual requirements |
Composition.section.text | |
Definition | |
Control | 1..* |
Must Support | True |
Comments | |
Composition.section.text.id | |
Definition |
unique id for the element within a resource (for internal references). |
Control | 0..1 ? |
Type | Id |
Comments |
RFC 4122 |
Composition.section.text.extension | |
Definition |
May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Control | 0..* ? |
Type | Extension |
Aliases | 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. |
Composition.section.text.status | |
Definition |
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Control | 1..1 ? |
Binding |
The status of a resource narrative The codes SHALL be taken from http://hl7.org/fhir/ValueSet/narrative-status |
Type | Code |
Comments |
Note that FHIR strings may not exceed 1MB in size |
Composition.section.text.div | |
Definition |
The actual narrative content, a stripped down version of XHTML. |
Control | 1..1 ? |
Type | Xhtml |
Comments |
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |