Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - Downloaded Version null See the Directory of published versions

Extension: ExtensionComposition_Event_Detail - Detailed Descriptions

Page standards status: Trial-use Maturity Level: 0

Definitions for the ext-R5-Composition.eve.detail extension.

Guidance on how to interpret the contents of this table can be foundhere

0. Extension
Definition

R5: Composition.event.detail additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Resource)) additional types from child elements (concept)


Optional Extension Element - found in all resources.

ShortR5: The event(s) being documented, as code(s), reference(s), or both additional typesOptional Extensions Element
Comments

Element Composition.event.detail is mapped to FHIR STU3 element Composition.event.detail as SourceIsBroaderThanTarget. The mappings for Composition.event.detail do not cover the following types: CodeableReference. The mappings for Composition.event.detail do not cover the following types based on type expansion: concept. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more events are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.

Control0..*
This element is affected by the following invariants: ele-1
Is Modifierfalse
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() | (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
ele-1: All FHIR elements must have a @value or children (hasValue() | (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
2. Extension.url
Definition

Source of the definition for the extension code - a logical name or a URL.

Shortidentifies the meaning of the extension
Comments

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Control1..1
Typeuri
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
XML FormatIn the XML format, this property is represented as an attribute.
Fixed Valuehttp://hl7.org/fhir/5.0/StructureDefinition/extension-Composition.event.detail
4. Extension.value[x]
Definition

Represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which case the procedure being documented is necessarily a "History and Physical" act. The events may be included as a code or as a reference to an other resource.


Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

ShortThe event(s) being documented, as code(s), reference(s), or bothValue of extension
Comments

An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more events are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.

Control0..1
BindingFor example codes, see For codes, see R5V3ActCodeForR3 (0.1.0)
(example to http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-ActCode-for-R3|0.1.0)

This list of codes represents the main clinical acts being documented.

TypeCodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal
[x] NoteSeeChoice of Data Typesfor further information about how to use [x]

Guidance on how to interpret the contents of this table can be foundhere

0. Extension
Definition

R5: Composition.event.detail additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Resource)) additional types from child elements (concept)

ShortR5: The event(s) being documented, as code(s), reference(s), or both additional types
Comments

Element Composition.event.detail is mapped to FHIR STU3 element Composition.event.detail as SourceIsBroaderThanTarget. The mappings for Composition.event.detail do not cover the following types: CodeableReference. The mappings for Composition.event.detail do not cover the following types based on type expansion: concept. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more events are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.

Control0..*
Is Modifierfalse
2. Extension.url
Control1..1
Fixed Valuehttp://hl7.org/fhir/5.0/StructureDefinition/extension-Composition.event.detail
4. Extension.value[x]
Definition

Represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which case the procedure being documented is necessarily a "History and Physical" act. The events may be included as a code or as a reference to an other resource.

ShortThe event(s) being documented, as code(s), reference(s), or both
Comments

An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more events are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.

Control0..1
BindingFor example codes, see R5V3ActCodeForR3 (0.1.0)
(example to http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-ActCode-for-R3|0.1.0)

This list of codes represents the main clinical acts being documented.

TypeCodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal
[x] NoteSeeChoice of Data Typesfor further information about how to use [x]

Guidance on how to interpret the contents of this table can be foundhere

0. Extension
Definition

R5: Composition.event.detail additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Resource)) additional types from child elements (concept)

ShortR5: The event(s) being documented, as code(s), reference(s), or both additional types
Comments

Element Composition.event.detail is mapped to FHIR STU3 element Composition.event.detail as SourceIsBroaderThanTarget. The mappings for Composition.event.detail do not cover the following types: CodeableReference. The mappings for Composition.event.detail do not cover the following types based on type expansion: concept. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more events are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.

Control0..*
This element is affected by the following invariants: ele-1
Is Modifierfalse
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() | (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
2. Extension.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Shortxml:id (or equivalent in JSON)
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
XML FormatIn the XML format, this property is represented as an attribute.
4. Extension.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.

ShortAdditional Content defined by implementations
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.

Control0..*
TypeExtension
Alternate Namesextensions, user content
SlicingThis element introduces a set of slices on Extension.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
  • value @ url
  • 6. Extension.url
    Definition

    Source of the definition for the extension code - a logical name or a URL.

    Shortidentifies the meaning of the extension
    Comments

    The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

    Control1..1
    Typeuri
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    XML FormatIn the XML format, this property is represented as an attribute.
    Fixed Valuehttp://hl7.org/fhir/5.0/StructureDefinition/extension-Composition.event.detail
    8. Extension.value[x]
    Definition

    Represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which case the procedure being documented is necessarily a "History and Physical" act. The events may be included as a code or as a reference to an other resource.

    ShortThe event(s) being documented, as code(s), reference(s), or both
    Comments

    An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more events are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.

    Control0..1
    BindingFor example codes, see R5V3ActCodeForR3 (0.1.0)
    (example to http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-ActCode-for-R3|0.1.0)

    This list of codes represents the main clinical acts being documented.

    TypeCodeableConcept
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]