Generated Narrative: StructureDefinition ext-R4B-ExampleScenario.process Name Flags Card. Type Description & Constraints Extension 0..* Extension R4B: Each major process - a group of operations (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:title 1..1 Extension R4B: The diagram title of the group of operations (new) #xD; url 1..1 uri "title" #xD; value[x] 1..1 string The diagram title of the group of operations #xD; extension:description 0..1 Extension R4B: A longer description of the group of operations (new) #xD; url 1..1 uri "description" #xD; value[x] 0..1 markdown A longer description of the group of operations #xD; extension:preConditions 0..1 Extension R4B: Description of initial status before the process starts (new) #xD; url 1..1 uri "preConditions" #xD; value[x] 0..1 markdown Description of initial status before the process starts #xD; extension:postConditions 0..1 Extension R4B: Description of final status after the process ends (new) #xD; url 1..1 uri "postConditions" #xD; value[x] 0..1 markdown Description of final status after the process ends #xD; extension:step 0..* Extension R4B: Each step of the process (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:process 0..* Extension R4B: Nested process (new) #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process" #xD; value[x] 0..0 Value of extension #xD; extension:pause 0..1 Extension R4B: If there is a pause in the flow (new) #xD; url 1..1 uri "pause" #xD; value[x] 0..1 boolean If there is a pause in the flow #xD; extension:operation 0..1 Extension R4B: Each interaction or action (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:number 1..1 Extension R4B: The sequential number of the interaction (new) #xD; url 1..1 uri "number" #xD; value[x] 1..1 string The sequential number of the interaction #xD; extension:type 0..1 Extension R4B: The type of operation - CRUD (new) #xD; url 1..1 uri "type" #xD; value[x] 0..1 string The type of operation - CRUD #xD; extension:name 0..1 Extension R4B: The human-friendly name of the interaction (new) #xD; url 1..1 uri "name" #xD; value[x] 0..1 string The human-friendly name of the interaction #xD; extension:initiator 0..1 Extension R4B: Who starts the transaction (new) #xD; url 1..1 uri "initiator" #xD; value[x] 0..1 string Who starts the transaction #xD; extension:receiver 0..1 Extension R4B: Who receives the transaction (new) #xD; url 1..1 uri "receiver" #xD; value[x] 0..1 string Who receives the transaction #xD; extension:description 0..1 Extension R4B: A comment to be inserted in the diagram (new) #xD; url 1..1 uri "description" #xD; value[x] 0..1 markdown A comment to be inserted in the diagram #xD; extension:initiatorActive 0..1 Extension R4B: Whether the initiator is deactivated right after the transaction (new) #xD; url 1..1 uri "initiatorActive" #xD; value[x] 0..1 boolean Whether the initiator is deactivated right after the transaction #xD; extension:receiverActive 0..1 Extension R4B: Whether the receiver is deactivated right after the transaction (new) #xD; url 1..1 uri "receiverActive" #xD; value[x] 0..1 boolean Whether the receiver is deactivated right after the transaction #xD; extension:request 0..1 Extension R4B: Each resource instance used by the initiator (new) #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance.containedInstance" #xD; value[x] 0..0 Value of extension #xD; extension:response 0..1 Extension R4B: Each resource instance used by the responder (new) #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance.containedInstance" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "operation" #xD; value[x] 0..0 Value of extension #xD; extension:alternative 0..* Extension R4B: Alternate non-typical step action (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:title 1..1 Extension R4B: Label for alternative (new) #xD; url 1..1 uri "title" #xD; value[x] 1..1 string Label for alternative #xD; extension:description 0..1 Extension R4B: A human-readable description of each option (new) #xD; url 1..1 uri "description" #xD; value[x] 0..1 markdown A human-readable description of each option #xD; extension:step 0..* Extension R4B: What happens in each alternative option (new) #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "alternative" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "step" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R4B: Each major process - a group of operations (new)
R4B: `ExampleScenario.process` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `ExampleScenario.process` as defined in FHIR R4B in FHIR STU3. The source element is defined as: `ExampleScenario.process` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * R4B: `ExampleScenario.process` 0..* `BackboneElement` Following are the generation technical comments: Element `ExampleScenario.process` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `ExampleScenario.process` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
R4B: The diagram title of the group of operations (new)
R4B: `ExampleScenario.process.title` (new:string)
Element `ExampleScenario.process.title` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.title` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Additional Content defined by implementations
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.
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.
Source of the definition for the extension code - a logical name or a URL.
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.
The diagram title of the group of operations
The diagram title of the group of operations.
R4B: A longer description of the group of operations (new)
R4B: `ExampleScenario.process.description` (new:markdown)
Element `ExampleScenario.process.description` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
A longer description of the group of operations
A longer description of the group of operations.
R4B: Description of initial status before the process starts (new)
R4B: `ExampleScenario.process.preConditions` (new:markdown)
Element `ExampleScenario.process.preConditions` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.preConditions` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.preConditions` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Description of initial status before the process starts
Description of initial status before the process starts.
R4B: Description of final status after the process ends (new)
R4B: `ExampleScenario.process.postConditions` (new:markdown)
Element `ExampleScenario.process.postConditions` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.postConditions` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.postConditions` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Description of final status after the process ends
Description of final status after the process ends.
R4B: `ExampleScenario.process.step` (new:BackboneElement)
Element `ExampleScenario.process.step` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.step` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `ExampleScenario.process.step` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.step` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Creating extension because element `ExampleScenario.process.step` is a content reference and requires an extesion definition.
R4B: `ExampleScenario.process.step.process` (new:ExampleScenario.process)
Element `ExampleScenario.process.step.process` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.process` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.process` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).
R4B: If there is a pause in the flow (new)
R4B: `ExampleScenario.process.step.pause` (new:boolean)
Element `ExampleScenario.process.step.pause` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.pause` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.pause` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4B: `ExampleScenario.process.step.operation` (new:BackboneElement)
Element `ExampleScenario.process.step.operation` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.operation` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4B: The sequential number of the interaction (new)
R4B: `ExampleScenario.process.step.operation.number` (new:string)
Element `ExampleScenario.process.step.operation.number` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.number` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.number` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The sequential number of the interaction
The sequential number of the interaction, e.g. 1.2.5.
R4B: `ExampleScenario.process.step.operation.type` (new:string)
Element `ExampleScenario.process.step.operation.type` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.type` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4B: The human-friendly name of the interaction (new)
R4B: `ExampleScenario.process.step.operation.name` (new:string)
Element `ExampleScenario.process.step.operation.name` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.name` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The human-friendly name of the interaction
The human-friendly name of the interaction.
R4B: `ExampleScenario.process.step.operation.initiator` (new:string)
Element `ExampleScenario.process.step.operation.initiator` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.initiator` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.initiator` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4B: `ExampleScenario.process.step.operation.receiver` (new:string)
Element `ExampleScenario.process.step.operation.receiver` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.receiver` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.receiver` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4B: A comment to be inserted in the diagram (new)
R4B: `ExampleScenario.process.step.operation.description` (new:markdown)
Element `ExampleScenario.process.step.operation.description` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
A comment to be inserted in the diagram.
R4B: Whether the initiator is deactivated right after the transaction (new)
R4B: `ExampleScenario.process.step.operation.initiatorActive` (new:boolean)
Element `ExampleScenario.process.step.operation.initiatorActive` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.initiatorActive` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.initiatorActive` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Whether the initiator is deactivated right after the transaction
Whether the initiator is deactivated right after the transaction.
R4B: Whether the receiver is deactivated right after the transaction (new)
R4B: `ExampleScenario.process.step.operation.receiverActive` (new:boolean)
Element `ExampleScenario.process.step.operation.receiverActive` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.receiverActive` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.receiverActive` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Whether the receiver is deactivated right after the transaction
Whether the receiver is deactivated right after the transaction.
R4B: Each resource instance used by the initiator (new)
R4B: `ExampleScenario.process.step.operation.request` (new:ExampleScenario.instance.containedInstance)
Element `ExampleScenario.process.step.operation.request` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.request` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.request` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4B: Each resource instance used by the responder (new)
R4B: `ExampleScenario.process.step.operation.response` (new:ExampleScenario.instance.containedInstance)
Element `ExampleScenario.process.step.operation.response` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.response` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.response` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4B: Alternate non-typical step action (new)
R4B: `ExampleScenario.process.step.alternative` (new:BackboneElement)
Element `ExampleScenario.process.step.alternative` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.alternative` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4B: `ExampleScenario.process.step.alternative.title` (new:string)
Element `ExampleScenario.process.step.alternative.title` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.title` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The label to display for the alternative that gives a sense of the circumstance in which the alternative should be invoked.
R4B: A human-readable description of each option (new)
R4B: `ExampleScenario.process.step.alternative.description` (new:markdown)
Element `ExampleScenario.process.step.alternative.description` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
A human-readable description of each option
A human-readable description of the alternative explaining when the alternative should occur rather than the base step.
R4B: What happens in each alternative option (new)
R4B: `ExampleScenario.process.step.alternative.step` (new:ExampleScenario.process.step)
Element `ExampleScenario.process.step.alternative.step` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.step` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.step` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).