Struct ValueSetExpansionContains 

pub struct ValueSetExpansionContains {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub system: Option<String>,
    pub system_ext: Option<FieldExtension>,
    pub abstract: Option<bool>,
    pub abstract_ext: Option<FieldExtension>,
    pub inactive: Option<bool>,
    pub inactive_ext: Option<FieldExtension>,
    pub version: Option<String>,
    pub version_ext: Option<FieldExtension>,
    pub code: Option<String>,
    pub code_ext: Option<FieldExtension>,
    pub display: Option<String>,
    pub display_ext: Option<FieldExtension>,
    pub designation: Vec<Option<ValueSetComposeIncludeConceptDesignation>>,
    pub designation_ext: Vec<Option<FieldExtension>>,
    pub property: Vec<Option<ValueSetExpansionContainsProperty>>,
    pub property_ext: Vec<Option<FieldExtension>>,
    pub contains: Vec<Option<ValueSetExpansionContains>>,
    pub contains_ext: Vec<Option<FieldExtension>>,
}

Sub-fields of the contains field in ValueSetExpansion

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.

system: Option<String>

System value for the code

An absolute URI which is the code system in which the code for this item in the expansion is defined.

system_ext: Option<FieldExtension>

Extension field.

abstract: Option<bool>

If user cannot select this entry

If true, this entry is included in the expansion for navigational purposes, and the user cannot select the code directly as a proper value.

This should not be understood to exclude its use for searching (e.g. by subsumption testing). The client should know whether it is appropriate for the user to select an abstract code or not.

abstract_ext: Option<FieldExtension>

Extension field.

inactive: Option<bool>

If concept is inactive in the code system

If the concept is inactive in the code system that defines it. Inactive codes are those that are no longer to be used, but are maintained by the code system for understanding legacy data. It might not be known or specified whether a concept is inactive (and it may depend on the context of use).

This should only have a value if the concept is inactive.

inactive_ext: Option<FieldExtension>

Extension field.

version: Option<String>

Version in which this code/display is defined

The version of the code system from this code was taken. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

The exact value of the version string is specified by the system from which the code is derived.

version_ext: Option<FieldExtension>

Extension field.

code: Option<String>

Code - if blank, this is not a selectable code

The code for this item in the expansion hierarchy. If this code is missing the entry in the hierarchy is a place holder (abstract) and does not represent a valid code in the value set.

code_ext: Option<FieldExtension>

Extension field.

display: Option<String>

User display for the concept

The recommended display for this item in the expansion.

display_ext: Option<FieldExtension>

Extension field.

designation: Vec<Option<ValueSetComposeIncludeConceptDesignation>>

Additional representations for this item

Additional representations for this item - other languages, aliases, specialized purposes, used for particular purposes, etc. These are relevant when the conditions of the expansion do not fix to a single correct representation.

The designations provided must be based on the value set and code system definitions.

designation_ext: Vec<Option<FieldExtension>>

Extension field.

property: Vec<Option<ValueSetExpansionContainsProperty>>

Property value for the concept

A property value for this concept.

property_ext: Vec<Option<FieldExtension>>

Extension field.

contains: Vec<Option<ValueSetExpansionContains>>

Codes contained under this entry

Other codes and entries contained under this entry in the hierarchy.

If the expansion uses this element, there is no implication about the logical relationship between them, and the structure cannot be used for logical inferencing. The structure exists to provide navigational assistance for helping human users to locate codes in the expansion.

contains_ext: Vec<Option<FieldExtension>>

Extension field.

Implementations

impl ValueSetExpansionContains

pub fn builder() -> ValueSetExpansionContainsBuilder

Start building a new instance

Trait Implementations

impl Clone for ValueSetExpansionContains

fn clone(&self) -> ValueSetExpansionContains

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ValueSetExpansionContains

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ValueSetExpansionContains

fn deserialize<__D>( __deserializer: __D, ) -> Result<ValueSetExpansionContains, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ValueSetExpansionContains

fn eq(&self, other: &ValueSetExpansionContains) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for ValueSetExpansionContains

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for ValueSetExpansionContains