Struct ConceptMapGroup

pub struct ConceptMapGroup {
    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub source: Option<String>,
    pub source_ext: Option<FieldExtension>,
    pub target: Option<String>,
    pub target_ext: Option<FieldExtension>,
    pub element: Vec<Option<ConceptMapGroupElement>>,
    pub element_ext: Vec<Option<FieldExtension>>,
    pub unmapped: Option<ConceptMapGroupUnmapped>,
    pub unmapped_ext: Option<FieldExtension>,
}

Sub-fields of the group field in ConceptMap

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.

source: Option<String>

Source system where concepts to be mapped are defined

An absolute URI that identifies the source system where the concepts to be mapped are defined.

This is not needed if the source value set is specified and it contains concepts from only a single system.

source_ext: Option<FieldExtension>

Extension field.

target: Option<String>

Target system that the concepts are to be mapped to

An absolute URI that identifies the target system that the concepts will be mapped to.

This is not needed if the target value set is specified and it contains concepts from only a single system. The group target may also be omitted if all of the target element relationship values are ‘not-related-to’.

target_ext: Option<FieldExtension>

Extension field.

element: Vec<Option<ConceptMapGroupElement>>

Mappings for a concept from the source set

Mappings for an individual concept in the source to one or more concepts in the target.

Generally, the ideal is that there would only be one mapping for each concept in the source value set, but a given concept may be mapped multiple times with different comments or dependencies.

element_ext: Vec<Option<FieldExtension>>

Extension field.

unmapped: Option<ConceptMapGroupUnmapped>

What to do when there is no mapping target for the source concept and ConceptMap.group.element.noMap is not true

What to do when there is no mapping to a target concept from the source concept and ConceptMap.group.element.noMap is not true. This provides the “default” to be applied when there is no target concept mapping specified or the expansion of ConceptMap.group.element.target.valueSet is empty.

The ‘unmapped’ element is ignored if a code is specified to have relationship = not-related-to or if ConceptMap.group.element.noMap = true.

unmapped_ext: Option<FieldExtension>

Extension field.

Implementations

impl ConceptMapGroup

pub fn builder() -> ConceptMapGroupBuilder

Start building a new instance

Trait Implementations

impl Clone for ConceptMapGroup

fn clone(&self) -> ConceptMapGroup

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ConceptMapGroup

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ConceptMapGroup

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ConceptMapGroup

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

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 ConceptMapGroup