pub struct ImplementationGuideManifest {Show 13 fields
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub rendering: Option<String>,
pub rendering_ext: Option<FieldExtension>,
pub resource: Vec<Option<ImplementationGuideManifestResource>>,
pub resource_ext: Vec<Option<FieldExtension>>,
pub page: Vec<Option<ImplementationGuideManifestPage>>,
pub page_ext: Vec<Option<FieldExtension>>,
pub image: Vec<Option<String>>,
pub image_ext: Vec<Option<FieldExtension>>,
pub other: Vec<Option<String>>,
pub other_ext: Vec<Option<FieldExtension>>,
}
Expand description
Sub-fields of the manifest field in ImplementationGuide
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.
rendering: Option<String>
Location of rendered implementation guide
A pointer to official web page, PDF or other rendering of the implementation guide.
rendering_ext: Option<FieldExtension>
Extension field.
resource: Vec<Option<ImplementationGuideManifestResource>>
Resource in the implementation guide
A resource that is part of the implementation guide. Conformance resources (value set, structure definition, capability statements etc.) are obvious candidates for inclusion, but any kind of resource can be included as an example resource.
resource_ext: Vec<Option<FieldExtension>>
Extension field.
page: Vec<Option<ImplementationGuideManifestPage>>
HTML page within the parent IG
Information about a page within the IG.
page_ext: Vec<Option<FieldExtension>>
Extension field.
image: Vec<Option<String>>
Image within the IG
Indicates a relative path to an image that exists within the IG.
image_ext: Vec<Option<FieldExtension>>
Extension field.
other: Vec<Option<String>>
Additional linkable file in IG
Indicates the relative path of an additional non-page, non-image file that is part of the IG - e.g. zip, jar and similar files that could be the target of a hyperlink in a derived IG.
other_ext: Vec<Option<FieldExtension>>
Extension field.
Implementations§
Source§impl ImplementationGuideManifest
impl ImplementationGuideManifest
Sourcepub fn builder() -> ImplementationGuideManifestBuilder
pub fn builder() -> ImplementationGuideManifestBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for ImplementationGuideManifest
impl Clone for ImplementationGuideManifest
Source§fn clone(&self) -> ImplementationGuideManifest
fn clone(&self) -> ImplementationGuideManifest
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more