pub struct CapabilityStatementRestResourceOperation {
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub name: String,
pub name_ext: Option<FieldExtension>,
pub definition: String,
pub definition_ext: Option<FieldExtension>,
pub documentation: Option<String>,
pub documentation_ext: Option<FieldExtension>,
}
Expand description
Sub-fields of the operation field in CapabilityStatementRestResource
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.
name: String
Name by which the operation/query is invoked
The name of the operation or query. For an operation, this name is prefixed with $ and used in the URL. For a query, this is the name used in the _query parameter when the query is called. This SHOULD be the same as the OperationDefinition.code of the defining OperationDefinition. However, it can sometimes differ if necessary to disambiguate when a server supports multiple OperationDefinition that happen to share the same code.
The name here SHOULD be the same as the OperationDefinition.code in the referenced OperationDefinition, unless there is a name clash and the OperationDefinition.code cannot be used. The name does not include the “$” portion that is always included in the URL. There is no correspondence whatsoever between CapabilityStatement’s operation.name and OperationDefinition.name - the latter is used as a class name when generating code for the operation. HL7 will never define operations that have conflicting names.
name_ext: Option<FieldExtension>
Extension field.
definition: String
The defined operation/query
Where the formal definition can be found. If a server references the base definition of an Operation (i.e. from the specification itself such as texthttp://hl7.org/fhir/OperationDefinition/ValueSet-expand
), that means it supports the full capabilities of the operation - e.g. both GET and POST invocation. If it only supports a subset, it must define its own custom OperationDefinition with a ‘base’ of the original OperationDefinition. The custom definition would describe the specific subset of functionality supported.
This can be used to build an HTML form to invoke the operation, for instance.
definition_ext: Option<FieldExtension>
Extension field.
documentation: Option<String>
Specific details about operation behavior
Documentation that describes anything special about the operation behavior, possibly detailing different behavior for system, type and instance-level invocation of the operation.
documentation_ext: Option<FieldExtension>
Extension field.
Implementations§
Source§impl CapabilityStatementRestResourceOperation
impl CapabilityStatementRestResourceOperation
Sourcepub fn builder() -> CapabilityStatementRestResourceOperationBuilder
pub fn builder() -> CapabilityStatementRestResourceOperationBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for CapabilityStatementRestResourceOperation
impl Clone for CapabilityStatementRestResourceOperation
Source§fn clone(&self) -> CapabilityStatementRestResourceOperation
fn clone(&self) -> CapabilityStatementRestResourceOperation
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl<'de> Deserialize<'de> for CapabilityStatementRestResourceOperation
impl<'de> Deserialize<'de> for CapabilityStatementRestResourceOperation
Source§fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
Source§impl PartialEq for CapabilityStatementRestResourceOperation
impl PartialEq for CapabilityStatementRestResourceOperation
Source§fn eq(&self, other: &CapabilityStatementRestResourceOperation) -> bool
fn eq(&self, other: &CapabilityStatementRestResourceOperation) -> bool
self
and other
values to be equal, and is used by ==
.