Struct ValueSetCompose

pub struct ValueSetCompose {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub locked_date: Option<Date>,
    pub locked_date_ext: Option<FieldExtension>,
    pub inactive: Option<bool>,
    pub inactive_ext: Option<FieldExtension>,
    pub include: Vec<Option<ValueSetComposeInclude>>,
    pub include_ext: Vec<Option<FieldExtension>>,
    pub exclude: Vec<Option<ValueSetComposeInclude>>,
    pub exclude_ext: Vec<Option<FieldExtension>>,
    pub property: Vec<Option<String>>,
    pub property_ext: Vec<Option<FieldExtension>>,
}

Sub-fields of the compose field in ValueSet

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.

locked_date: Option<Date>

Fixed date for references with no specified version (transitive)

The Locked Date is the effective date that is used to determine the version of all referenced Code Systems and Value Set Definitions included in the compose that are not already tied to a specific version.

With a defined lockedDate the value set is considered “Locked”. Otherwise, the value set may have different expansions as underlying code systems and/or value sets evolve. The interpretation of lockedDate is often dependent on the context - e.g. a SNOMED CT derived value set with a lockedDate will have a different expansion in USA than in UK. If a value set specifies a version for include and exclude statements, and also specifies a locked date, the specified versions need to be available that date, or the value set will not be usable.

locked_date_ext: Option<FieldExtension>

Extension field.

inactive: Option<bool>

Whether inactive codes are in the value set

Whether inactive codes - codes that are not approved for current use - are in the value set. If inactive = true, inactive codes are to be included in the expansion, if inactive = false, the inactive codes will not be included in the expansion. If absent, the behavior is determined by the implementation, or by the applicable $expand parameters (but generally, inactive codes would be expected to be included).

Note that in the FHIR terminology framework, “deprecated” does not mean inactive, but in some code systems, e.g. LOINC, “deprecated” does mean inactive. Code systems should define what codes are considered to be inactive. If this is not clearly defined (including in the FHIR code system resource), then all codes are assumed to be active.

The Value Set Definition specification defines an ActiveOnly element, which is the reverse of this element e.g. (ValueSet.compose.inactive=FALSE) is the same as (VSD.ActiveOnly=TRUE).

inactive_ext: Option<FieldExtension>

Extension field.

include: Vec<Option<ValueSetComposeInclude>>

Include one or more codes from a code system or other value set(s)

Include one or more codes from a code system or other value set(s).

All the conditions in an include must be true. If a system is listed, all the codes from the system are listed. If one or more filters are listed, all of the filters must apply. If one or more value sets are listed, the codes must be in all the value sets. E.g. each include is ‘include all the codes that meet all these conditions’.

include_ext: Vec<Option<FieldExtension>>

Extension field.

exclude: Vec<Option<ValueSetComposeInclude>>

Explicitly exclude codes from a code system or other value sets

Exclude one or more codes from the value set based on code system filters and/or other value sets.

Usually this is used to selectively exclude codes that were included by subsumption in the inclusions. Any display names specified for the codes are ignored.

exclude_ext: Vec<Option<FieldExtension>>

Extension field.

property: Vec<Option<String>>

Property to return if client doesn’t override

A property to return in the expansion, if the client doesn’t ask for any particular properties. May be either a code from the code system definition (convenient) or a the formal URI that refers to the property. The special value ‘*’ means all properties known to the server.

Note that property names can clash, so using a URI is recommended.

property_ext: Vec<Option<FieldExtension>>

Extension field.

Implementations

impl ValueSetCompose

pub fn builder() -> ValueSetComposeBuilder

Start building a new instance

Trait Implementations

impl Clone for ValueSetCompose

fn clone(&self) -> ValueSetCompose

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ValueSetCompose

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ValueSetCompose

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ValueSetCompose

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

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 ValueSetCompose