pub struct CapabilityStatementDocument {
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub mode: DocumentMode,
pub mode_ext: Option<FieldExtension>,
pub documentation: Option<String>,
pub documentation_ext: Option<FieldExtension>,
pub profile: String,
pub profile_ext: Option<FieldExtension>,
}
Expand description
Sub-fields of the document field in CapabilityStatement
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.
mode: DocumentMode
DocumentMode; producer | consumer
Mode of this document declaration - whether an application is a producer or consumer.
mode_ext: Option<FieldExtension>
Extension field.
documentation: Option<String>
Description of document support
A description of how the application supports or uses the specified document profile. For example, when documents are created, what action is taken with consumed documents, etc.
documentation_ext: Option<FieldExtension>
Extension field.
profile: String
Constraint on the resources used in the document
A profile on the document Bundle that constrains which resources are present, and their contents.
The profile is actually on the Bundle.
profile_ext: Option<FieldExtension>
Extension field.
Implementations§
Source§impl CapabilityStatementDocument
impl CapabilityStatementDocument
Sourcepub fn builder() -> CapabilityStatementDocumentBuilder
pub fn builder() -> CapabilityStatementDocumentBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for CapabilityStatementDocument
impl Clone for CapabilityStatementDocument
Source§fn clone(&self) -> CapabilityStatementDocument
fn clone(&self) -> CapabilityStatementDocument
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more