Skip to main content

CompositionEventCreateInput

No description

input CompositionEventCreateInput {
code: [CodeableConceptCreateInput!]
period: PeriodCreateInput
detail: [ReferenceCreateInput!]
modifierExtension: [FhirExtensionCreateInput!]
extension: [FhirExtensionCreateInput!]
id: String
}

Fields

CompositionEventCreateInput.code ● [CodeableConceptCreateInput!] list input

This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a History and Physical Report in which the procedure being documented is necessarily a History and Physical act.

CompositionEventCreateInput.period ● PeriodCreateInput input

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.

CompositionEventCreateInput.detail ● [ReferenceCreateInput!] list input

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.

CompositionEventCreateInput.modifierExtension ● [FhirExtensionCreateInput!] list input

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

CompositionEventCreateInput.extension ● [FhirExtensionCreateInput!] list input

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

CompositionEventCreateInput.id ● String scalar

null

Member Of

CompositionCreateInput input