Struct ValueSetComposeIncludeConcept

pub struct ValueSetComposeIncludeConcept {
    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub code: 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>>,
}

Sub-fields of the concept field in ValueSetComposeInclude

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.

code: String

Code or expression from system

Specifies a code for the concept to be included or excluded.

Expressions are allowed if defined by the underlying code system.

code_ext: Option<FieldExtension>

Extension field.

display: Option<String>

Text to display for this code for this value set in this valueset

The text to display to the user for this concept in the context of this valueset. If no display is provided, then applications using the value set use the display specified for the code by the system.

The value set resource allows for an alternative display to be specified for when this concept is used in this particular value set. See notes in the value set narrative about the correct use of this element.

display_ext: Option<FieldExtension>

Extension field.

designation: Vec<Option<ValueSetComposeIncludeConceptDesignation>>

Additional representations for this concept

Additional representations for this concept when used in this value set - other languages, aliases, specialized purposes, used for particular purposes, etc.

Concepts have both a textdisplay and an array of textdesignation. The display is equivalent to a special designation with an implied textdesignation.use of “primary code” and a language equal to the Resource Language.

designation_ext: Vec<Option<FieldExtension>>

Extension field.

Implementations

impl ValueSetComposeIncludeConcept

pub fn builder() -> ValueSetComposeIncludeConceptBuilder

Start building a new instance

Trait Implementations

impl Clone for ValueSetComposeIncludeConcept

fn clone(&self) -> ValueSetComposeIncludeConcept

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ValueSetComposeIncludeConcept

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ValueSetComposeIncludeConcept

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ValueSetComposeIncludeConcept

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

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 ValueSetComposeIncludeConcept