ExampleScenarioOperationCreateInput
No description
input ExampleScenarioOperationCreateInput {
number: String!
type: String
name: String
initiator: String
receiver: String
description: String
initiatorActive: Boolean
receiverActive: Boolean
request: ExampleScenarioContainedInstanceCreateInput
response: ExampleScenarioContainedInstanceCreateInput
modifierExtension: [FhirExtensionCreateInput!]
extension: [FhirExtensionCreateInput!]
id: String
}
Fields
ExampleScenarioOperationCreateInput.number ● String! non-null scalar
The sequential number of the interaction, e.g. 1.2.5.
ExampleScenarioOperationCreateInput.type ● String scalar
The type of operation - CRUD.
ExampleScenarioOperationCreateInput.name ● String scalar
The human-friendly name of the interaction.
ExampleScenarioOperationCreateInput.initiator ● String scalar
Who starts the transaction.
ExampleScenarioOperationCreateInput.receiver ● String scalar
Who receives the transaction.
ExampleScenarioOperationCreateInput.description ● String scalar
A comment to be inserted in the diagram.
ExampleScenarioOperationCreateInput.initiatorActive ● Boolean scalar
Whether the initiator is deactivated right after the transaction.
ExampleScenarioOperationCreateInput.receiverActive ● Boolean scalar
Whether the receiver is deactivated right after the transaction.
ExampleScenarioOperationCreateInput.request ● ExampleScenarioContainedInstanceCreateInput input
Each resource instance used by the initiator.
ExampleScenarioOperationCreateInput.response ● ExampleScenarioContainedInstanceCreateInput input
Each resource instance used by the responder.
ExampleScenarioOperationCreateInput.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).
ExampleScenarioOperationCreateInput.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.
ExampleScenarioOperationCreateInput.id ● String scalar
null