pub struct ExampleScenarioInstance {Show 21 fields
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub key: String,
pub key_ext: Option<FieldExtension>,
pub structure_type: Coding,
pub structure_type_ext: Option<FieldExtension>,
pub structure_version: Option<String>,
pub structure_version_ext: Option<FieldExtension>,
pub structure_profile: Option<ExampleScenarioInstanceStructureProfile>,
pub structure_profile_ext: Option<ExampleScenarioInstanceStructureProfileExtension>,
pub title: String,
pub title_ext: Option<FieldExtension>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub content: Option<Reference>,
pub content_ext: Option<FieldExtension>,
pub version: Vec<Option<ExampleScenarioInstanceVersion>>,
pub version_ext: Vec<Option<FieldExtension>>,
pub contained_instance: Vec<Option<ExampleScenarioInstanceContainedInstance>>,
pub contained_instance_ext: Vec<Option<FieldExtension>>,
}
Expand description
Sub-fields of the instance field in ExampleScenario
Fields§
§id: Option<String>
Unique id for inter-element referencing
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
extension: Vec<Extension>
Additional content defined by implementations
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 managable, 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.
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.
modifier_extension: Vec<Extension>
Extensions that cannot be ignored even if unrecognized
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 managable, 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).
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.
key: String
ID or acronym of the instance
A unique string within the scenario that is used to reference the instance.
key_ext: Option<FieldExtension>
Extension field.
structure_type: Coding
InstanceType; Data structure for example
A code indicating the kind of data structure (FHIR resource or some other standard) this is an instance of.
structure_type_ext: Option<FieldExtension>
Extension field.
structure_version: Option<String>
E.g. 4.0.1
Conveys the version of the data structure instantiated. I.e. what release of FHIR, X12, OpenEHR, etc. is instance compliant with.
structure_version_ext: Option<FieldExtension>
Extension field.
structure_profile: Option<ExampleScenarioInstanceStructureProfile>
Rules instance adheres to
Refers to a profile, template or other ruleset the instance adheres to.
structure_profile_ext: Option<ExampleScenarioInstanceStructureProfileExtension>
Extension field.
title: String
Label for instance
A short descriptive label the instance to be used in tables or diagrams.
title_ext: Option<FieldExtension>
Extension field.
description: Option<String>
Human-friendly description of the instance
An explanation of what the instance contains and what it’s for.
description_ext: Option<FieldExtension>
Extension field.
content: Option<Reference>
Example instance data
Points to an instance (typically an example) that shows the data that would corespond to this instance.
If not conveying FHIR data or not using the same version of FHIR as this ExampleScenario instance, the reference must be to a Binary.
content_ext: Option<FieldExtension>
Extension field.
version: Vec<Option<ExampleScenarioInstanceVersion>>
Snapshot of instance that changes
Represents the instance as it was at a specific time-point.
Not used if an instance doesn’t change
version_ext: Vec<Option<FieldExtension>>
Extension field.
contained_instance: Vec<Option<ExampleScenarioInstanceContainedInstance>>
Resources contained in the instance
References to other instances that can be found within this instance (e.g. the observations contained in a bundle).
contained_instance_ext: Vec<Option<FieldExtension>>
Extension field.
Implementations§
Source§impl ExampleScenarioInstance
impl ExampleScenarioInstance
Sourcepub fn builder() -> ExampleScenarioInstanceBuilder
pub fn builder() -> ExampleScenarioInstanceBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for ExampleScenarioInstance
impl Clone for ExampleScenarioInstance
Source§fn clone(&self) -> ExampleScenarioInstance
fn clone(&self) -> ExampleScenarioInstance
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more