pub struct DocumentReferenceContent {
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub attachment: Attachment,
pub attachment_ext: Option<FieldExtension>,
pub profile: Vec<Option<DocumentReferenceContentProfile>>,
pub profile_ext: Vec<Option<FieldExtension>>,
}
Expand description
Sub-fields of the content field in DocumentReference
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.
attachment: Attachment
Where to access the document
The document or URL of the document along with critical metadata to prove content has integrity.
attachment_ext: Option<FieldExtension>
Extension field.
profile: Vec<Option<DocumentReferenceContentProfile>>
Content profile rules for the document
An identifier of the document constraints, encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType.
Note that IHE often issues URNs for formatCode codes, not all documents can be identified by a URI.
For FHIR content, .profile should indicate the structureDefinition profile canonical URI(s) that the content complies with.
profile_ext: Vec<Option<FieldExtension>>
Extension field.
Implementations§
Source§impl DocumentReferenceContent
impl DocumentReferenceContent
Sourcepub fn builder() -> DocumentReferenceContentBuilder
pub fn builder() -> DocumentReferenceContentBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for DocumentReferenceContent
impl Clone for DocumentReferenceContent
Source§fn clone(&self) -> DocumentReferenceContent
fn clone(&self) -> DocumentReferenceContent
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more