pub struct ContractTerm {Show 27 fields
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub identifier: Option<Identifier>,
pub identifier_ext: Option<FieldExtension>,
pub issued: Option<DateTime>,
pub issued_ext: Option<FieldExtension>,
pub applies: Option<Period>,
pub applies_ext: Option<FieldExtension>,
pub topic: Option<ContractTermTopic>,
pub topic_ext: Option<ContractTermTopicExtension>,
pub type: Option<CodeableConcept>,
pub type_ext: Option<FieldExtension>,
pub sub_type: Option<CodeableConcept>,
pub sub_type_ext: Option<FieldExtension>,
pub text: Option<String>,
pub text_ext: Option<FieldExtension>,
pub security_label: Vec<Option<ContractTermSecurityLabel>>,
pub security_label_ext: Vec<Option<FieldExtension>>,
pub offer: ContractTermOffer,
pub offer_ext: Option<FieldExtension>,
pub asset: Vec<Option<ContractTermAsset>>,
pub asset_ext: Vec<Option<FieldExtension>>,
pub action: Vec<Option<ContractTermAction>>,
pub action_ext: Vec<Option<FieldExtension>>,
pub group: Vec<Option<ContractTerm>>,
pub group_ext: Vec<Option<FieldExtension>>,
}
Expand description
Sub-fields of the term field in Contract
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.
identifier: Option<Identifier>
Contract Term Number
Unique identifier for this particular Contract Provision.
identifier_ext: Option<FieldExtension>
Extension field.
issued: Option<DateTime>
Contract Term Issue Date Time
When this Contract Provision was issued.
issued_ext: Option<FieldExtension>
Extension field.
applies: Option<Period>
Contract Term Effective Time
Relevant time or time-period when this Contract Provision is applicable.
applies_ext: Option<FieldExtension>
Extension field.
topic: Option<ContractTermTopic>
Term Concern
The entity that the term applies to.
topic_ext: Option<ContractTermTopicExtension>
Extension field.
type: Option<CodeableConcept>
ContractTermType; Contract Term Type or Form
A legal clause or condition contained within a contract that requires one or both parties to perform a particular requirement by some specified time or prevents one or both parties from performing a particular requirement by some specified time.
type_ext: Option<FieldExtension>
Extension field.
sub_type: Option<CodeableConcept>
ContractTermSubType; Contract Term Type specific classification
A specialized legal clause or condition based on overarching contract type.
sub_type_ext: Option<FieldExtension>
Extension field.
text: Option<String>
Term Statement
Statement of a provision in a policy or a contract.
text_ext: Option<FieldExtension>
Extension field.
security_label: Vec<Option<ContractTermSecurityLabel>>
Protection for the Term
Security labels that protect the handling of information about the term and its elements, which may be specifically identified.
Within a Contract, a security label may apply to the one to many nested group of terms or to a term, whether inside a group or a singleton. The security label on the entire set of term provision elements may be different from the security labels on a contained offer, asset, valuedItem, or data such as sensitive information, and must be the high water mark of all security labels within the term. Rationale is that a labelled term, which may be disaggregated from the Contract, and must persist the label on the term and on contained elements within other contexts. If more than one policy dictates a level of confidentiality of the term, then each applicable policy may be represented by a security label specific to its requirements.
A Security Label is comprised of 1..1 confidentiality code and 0..* other security label codes (aka “privacy tags”. A Security Label is metadata assigned (aka “tagged”) to Resources and Resource elements, which specify the confidentiality and sensitivity of the Resource or element and their related attributes, the purposes for which tagged items may be collected, access, used or disclosed, any limitation on the type of entities authorized to engage in permitted purposes, and handling instructions that obligate or prohibit certain actions on the tagged items.
security_label_ext: Vec<Option<FieldExtension>>
Extension field.
offer: ContractTermOffer
Context of the Contract term
The matter of concern in the context of this provision of the agrement.
offer_ext: Option<FieldExtension>
Extension field.
asset: Vec<Option<ContractTermAsset>>
Contract Term Asset List
Contract Term Asset List.
asset_ext: Vec<Option<FieldExtension>>
Extension field.
action: Vec<Option<ContractTermAction>>
Entity being ascribed responsibility
An actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place.
Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa. For example, in cases of actions initiated by one user for other users, or in events that involve more than one user, hardware device, software, or system process. However, only one user may be the initiator/requestor for the event.
action_ext: Vec<Option<FieldExtension>>
Extension field.
group: Vec<Option<ContractTerm>>
Nested Contract Term Group
Nested group of Contract Provisions.
group_ext: Vec<Option<FieldExtension>>
Extension field.
Implementations§
Source§impl ContractTerm
impl ContractTerm
Sourcepub fn builder() -> ContractTermBuilder
pub fn builder() -> ContractTermBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for ContractTerm
impl Clone for ContractTerm
Source§fn clone(&self) -> ContractTerm
fn clone(&self) -> ContractTerm
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more