A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. If the element is present, it must have either a @value, an @id, or extensions An absolute URI that is used to identify this example scenario when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this example scenario is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the example scenario is stored on different servers. A formal identifier that is used to identify this example scenario when it is represented in other formats, or referenced in a specification, model, design or an instance. The identifier that is used to identify this version of the example scenario when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the example scenario author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. Indicates the mechanism used to compare versions to determine which is more current. A natural language name identifying the ExampleScenario. This name should be usable as an identifier for the resource by machine processing applications such as code generation. A short, descriptive, user-friendly title for the ExampleScenario. The status of this example scenario. Enables tracking the life-cycle of the content. A Boolean value to indicate that this example scenario is authored for testing purposes (or education/evaluation/marketing) and no version of this resource will ever be intended for genuine usage. The date (and optionally time) when the example scenario was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the example scenario changes. (e.g. the 'content logical definition'). The name of the organization or individual responsible for the release and ongoing maintenance of the example scenario. Contact details to assist a user in finding and communicating with the publisher. A free text natural language description of the ExampleScenario from a consumer's perspective. The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate example scenario instances. A legal or geographic region in which the authority that maintains the resource is operating. In general, the jurisdiction is also found in the useContext. The useContext may reference additional jurisdictions because the defining jurisdiction does not necessarily limit the jurisdictions of use. What the example scenario resource is created for. This should not be used to show the business purpose of the scenario itself, but the purpose of documenting a scenario. A copyright statement relating to the example scenario and/or its contents. Copyright statements are notices of intellectual property ownership and can include restrictions on the use and publishing of the example scenario. A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are restricted. (e.g. 'All rights reserved', 'Some rights reserved'). A system or person who shares or receives an instance within the scenario. A single data collection that is shared as part of the scenario. A group of operations that represents a significant step within a scenario. A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. A unique string within the scenario that is used to reference the actor. The category of actor - person or system. The human-readable name for the actor used when rendering the scenario. An explanation of who/what the actor is and its role in the scenario. The formal definition of the actor in the scenario. A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. A unique string within the scenario that is used to reference the instance. A code indicating the kind of data structure (FHIR resource or some other standard) this is an instance of. Conveys the version of the data structure instantiated. I.e. what release of FHIR, X12, OpenEHR, etc. is instance compliant with. Refers to a profile, template or other ruleset the instance adheres to. A short descriptive label the instance to be used in tables or diagrams. An explanation of what the instance contains and what it's for. Points to an instance (typically an example) that shows the data that would corespond to this instance. Represents the instance as it was at a specific time-point. References to other instances that can be found within this instance (e.g. the observations contained in a bundle). A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. A unique string within the instance that is used to reference the version of the instance. A short descriptive label the version to be used in tables or diagrams. An explanation of what this specific version of the instance contains and represents. Points to an instance (typically an example) that shows the data that would flow at this point in the scenario. A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. A reference to the key of an instance found within this one. A reference to the key of a specific version of an instance in this instance. A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. A short descriptive label the process to be used in tables or diagrams. An explanation of what the process represents and what it does. Description of the initial state of the actors, environment and data before the process starts. Description of the final state of the actors, environment and data after the process has been successfully completed. A significant action that occurs as part of the process. A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. The sequence number of the step, e.g. 1.2.5. Indicates that the step is a complex sub-process with its own steps. Indicates that the step is defined by a seaparate scenario instance. The step represents a single operation invoked on receiver by sender. Indicates an alternative step that can be taken instead of the sub-process, scenario or operation. E.g. to represent non-happy-path/exceptional/atypical circumstances. If true, indicates that, following this step, there is a pause in the flow and the subsequent step will occur at some later time (triggered by some event). A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. The standardized type of action (FHIR or otherwise). A short descriptive label the step to be used in tables or diagrams. The system that invokes the action/transmits the data. The system on which the action is invoked/receives the data. An explanation of what the operation represents and what it does. If false, the initiator is deactivated right after the operation. If false, the receiver is deactivated right after the operation. A reference to the instance that is transmitted from requester to receiver as part of the invocation of the operation. A reference to the instance that is transmitted from receiver to requester as part of the operation's synchronous response (if any). A computable description of the actors, interactions between those actors that would occur, and concrete examples of the data that would be exchanged in a specific hypothetical exchange, typically used to help demonstrate the interoperability expectations of a specification. This resource is used to illustrate a specific time-based exchange, not to define in general terms how exchanges can/should occur. The label to display for the alternative that gives a sense of the circumstance in which the alternative should be invoked. A human-readable description of the alternative explaining when the alternative should occur rather than the base step. Indicates the operation, sub-process or scenario that happens if the alternative option is selected.