Skip to main content

ExampleScenarioOperation

Example of workflow instance.

type ExampleScenarioOperation implements Element {
  number: String
  type: String
  name: String
  initiator: String
  receiver: String
  description: String
  initiatorActive: Boolean
  receiverActive: Boolean
  request: ExampleScenarioContainedInstance
  response: ExampleScenarioContainedInstance
  modifierExtension: [Extension]
  extension: [Extension]
  id: String
}

Fields​

ExampleScenarioOperation.number ● String scalar​

The sequential number of the interaction, e.g. 1.2.5.

ExampleScenarioOperation.type ● String scalar​

The type of operation - CRUD.

ExampleScenarioOperation.name ● String scalar​

The human-friendly name of the interaction.

ExampleScenarioOperation.initiator ● String scalar​

Who starts the transaction.

ExampleScenarioOperation.receiver ● String scalar​

Who receives the transaction.

ExampleScenarioOperation.description ● String scalar​

A comment to be inserted in the diagram.

ExampleScenarioOperation.initiatorActive ● Boolean scalar​

Whether the initiator is deactivated right after the transaction.

ExampleScenarioOperation.receiverActive ● Boolean scalar​

Whether the receiver is deactivated right after the transaction.

ExampleScenarioOperation.request ● ExampleScenarioContainedInstance object​

Each resource instance used by the initiator.

ExampleScenarioOperation.response ● ExampleScenarioContainedInstance object​

Each resource instance used by the responder.

ExampleScenarioOperation.modifierExtension ● [Extension] list object​

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

ExampleScenarioOperation.extension ● [Extension] list object​

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.

ExampleScenarioOperation.id ● String scalar​

Interfaces​

Element interface​

Base definition for all elements in a resource. If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions

Member Of​

ExampleScenarioStep object