pub struct NamingSystemUniqueId {Show 15 fields
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub type: NamingSystemIdentifierType,
pub type_ext: Option<FieldExtension>,
pub value: String,
pub value_ext: Option<FieldExtension>,
pub preferred: Option<bool>,
pub preferred_ext: Option<FieldExtension>,
pub comment: Option<String>,
pub comment_ext: Option<FieldExtension>,
pub period: Option<Period>,
pub period_ext: Option<FieldExtension>,
pub authoritative: Option<bool>,
pub authoritative_ext: Option<FieldExtension>,
}Expand description
Sub-fields of the uniqueId field in NamingSystem
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.
type: NamingSystemIdentifierTypeNamingSystemIdentifierType; oid | uuid | uri | iri-stem | v2csmnemonic | other
Identifies the unique identifier scheme used for this particular identifier.
Different identifier types may be used in different types of communications (OIDs for v3, URIs for FHIR, etc.). Other includes RUIDs from v3, standard v2 code name strings, etc. Preferred identifiers for the same identifier type SHOULD NOT overlap by period.
type_ext: Option<FieldExtension>Extension field.
value: StringThe unique identifier
The string that should be sent over the wire to identify the code system or identifier system.
If the value is a URI intended for use as FHIR system identifier, the URI should not contain “" or “?” or “,” since this makes escaping very difficult.
value_ext: Option<FieldExtension>Extension field.
preferred: Option<bool>Is this the id that should be used for this type
Indicates whether this identifier is the “preferred” identifier of this type.
preferred_ext: Option<FieldExtension>Extension field.
comment: Option<String>Notes about identifier usage
Notes about the past or intended usage of this identifier.
e.g. “must be used in Germany” or “was initially published in error with this value”.
comment_ext: Option<FieldExtension>Extension field.
period: Option<Period>When is identifier valid?
Identifies the period of time over which this identifier is considered appropriate to refer to the naming system. Outside of this window, the identifier might be non-deterministic.
Within a registry, a given identifier should only be “active” for a single namespace at a time. (Ideally, an identifier should only ever be associated with a single namespace across all time).
The nuance of identifier deprecation is not represented with a separate element. When a determination is made that an identifier should not be used, the validity period end date is updated with the date the identifier is deemed to be deprecated. The identifier should no longer be used once the period end date is reached.
period_ext: Option<FieldExtension>Extension field.
Whether the identifier is authoritative
Indicates whether this identifier ie endorsed by the official owner of the associated naming system.
Extension field.
Implementations§
Source§impl NamingSystemUniqueId
impl NamingSystemUniqueId
Sourcepub fn builder() -> NamingSystemUniqueIdBuilder
pub fn builder() -> NamingSystemUniqueIdBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for NamingSystemUniqueId
impl Clone for NamingSystemUniqueId
Source§fn clone(&self) -> NamingSystemUniqueId
fn clone(&self) -> NamingSystemUniqueId
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more