Struct ValueSetComposeInclude

pub struct ValueSetComposeInclude {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub system: Option<String>,
    pub system_ext: Option<FieldExtension>,
    pub version: Option<String>,
    pub version_ext: Option<FieldExtension>,
    pub concept: Vec<Option<ValueSetComposeIncludeConcept>>,
    pub concept_ext: Vec<Option<FieldExtension>>,
    pub filter: Vec<Option<ValueSetComposeIncludeFilter>>,
    pub filter_ext: Vec<Option<FieldExtension>>,
    pub value_set: Vec<Option<String>>,
    pub value_set_ext: Vec<Option<FieldExtension>>,
    pub copyright: Option<String>,
    pub copyright_ext: Option<FieldExtension>,
}

Sub-fields of the include field in ValueSetCompose

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>

The system the codes come from

An absolute URI which is the code system from which the selected codes come from.

If there are no codes or filters, the entire code system is included. Note that the set of codes that are included may contain abstract codes. See ’‘Coding.system’’ for further documentation about the correct value for the system element.

system_ext: Option<FieldExtension>

Extension field.

version: Option<String>

Specific version of the code system referred to

The version of the code system that the codes are selected from, or the special version ‘*’ for all versions.

This is used when selecting the descendants of a concept - they may change between versions. If no version is specified, then the exact contents of the value set might not be known until a context of use binds it to a particular version. The special value ‘*’ means all versions; It is at server discretion regarding expansions and which versions must be supported.

version_ext: Option<FieldExtension>

Extension field.

concept: Vec<Option<ValueSetComposeIncludeConcept>>

A concept defined in the system

Specifies a concept to be included or excluded.

The list of concepts is considered ordered, though the order might not have any particular significance. Typically, the order of an expansion follows that defined in the compose element.

concept_ext: Vec<Option<FieldExtension>>

Extension field.

filter: Vec<Option<ValueSetComposeIncludeFilter>>

Select codes/concepts by their properties (including relationships)

Select concepts by specifying a matching criterion based on the properties (including relationships) defined by the system, or on filters defined by the system. If multiple filters are specified within the include, they SHALL all be true.

Selecting codes by specifying filters based on properties is only possible where the underlying code system defines appropriate properties. Note that in some cases, the underlying code system defines the logical concepts but not the literal codes for the concepts. In such cases, the literal definitions may be provided by a third party.

filter_ext: Vec<Option<FieldExtension>>

Extension field.

value_set: Vec<Option<String>>

Select the contents included in this value set

Selects the concepts found in this value set (based on its value set definition). This is an absolute URI that is a reference to ValueSet.url. If multiple value sets are specified this includes the intersection of the contents of all of the referenced value sets.

The value set URI is either a logical reference to a defined value set such as a SNOMED CT reference set, or a direct reference to a value set definition using ValueSet.url. The reference might not refer to an actual FHIR ValueSet resource; in this case, whatever is referred to is an implicit definition of a value set that needs to be clear about how versions are resolved.

value_set_ext: Vec<Option<FieldExtension>>

Extension field.

copyright: Option<String>

A copyright statement for the specific code system included in the value set

A copyright statement for the specific code system asserted by the containing ValueSet.compose.include element’s system value (if the associated ValueSet.compose.include.version element is not present); or the code system and version combination (if the associated ValueSet.compose.include.version element is present).

copyright_ext: Option<FieldExtension>

Extension field.

Implementations

impl ValueSetComposeInclude

pub fn builder() -> ValueSetComposeIncludeBuilder

Start building a new instance

Trait Implementations

impl Clone for ValueSetComposeInclude

fn clone(&self) -> ValueSetComposeInclude

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ValueSetComposeInclude

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ValueSetComposeInclude

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ValueSetComposeInclude

fn eq(&self, other: &ValueSetComposeInclude) -> 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 ValueSetComposeInclude

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 ValueSetComposeInclude