Skip to main content

TimingCreateInput

No description

input TimingCreateInput {
  event: [Date!]
  repeat: TimingRepeatCreateInput
  code: CodeableConceptCreateInput
  modifierExtension: [FhirExtensionCreateInput!]
  extension: [FhirExtensionCreateInput!]
  id: String
}

Fields​

TimingCreateInput.event ● [Date!] list scalar​

Identifies specific times when the event occurs.

TimingCreateInput.repeat ● TimingRepeatCreateInput input​

A set of rules that describe when the event is scheduled.

TimingCreateInput.code ● CodeableConceptCreateInput input​

A code for the timing schedule (or just text in code.text). Some codes such as BID are ubiquitous, but many institutions define their own additional codes. If a code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data, and either the code or the data may be used to interpret the Timing, with the exception that .repeat.bounds still applies over the code (and is not contained in the code).

TimingCreateInput.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).

TimingCreateInput.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.

TimingCreateInput.id ● String scalar​

null

Member Of​

ActivityDefinitionCreateInput input ● CarePlanDetailCreateInput input ● ChargeItemCreateInput input ● ContractActionCreateInput input ● DeviceMetricCreateInput input ● DeviceRequestCreateInput input ● DeviceUseStatementCreateInput input ● DosageCreateInput input ● ElementDefinitionCreateInput input ● ElementDefinitionExampleCreateInput input ● FhirExtensionCreateInput input ● NutritionOrderAdministrationCreateInput input ● NutritionOrderOralDietCreateInput input ● NutritionOrderSupplementCreateInput input ● ObservationCreateInput input ● PlanDefinitionActionCreateInput input ● RequestGroupActionCreateInput input ● ResearchElementDefinitionCharacteristicCreateInput input ● ServiceRequestCreateInput input ● StructureMapSourceCreateInput input ● SupplyDeliveryCreateInput input ● SupplyRequestCreateInput input ● TaskInputCreateInput input ● TaskOutputCreateInput input ● TriggerDefinitionCreateInput input ● VerificationResultCreateInput input