import { CodeableConcept } from './CodeableConcept.js';
import { Coding } from './Coding.js';
import { Consent_Provision_Actor } from './Consent_Provision_Actor.js';
import { Consent_Provision_Data } from './Consent_Provision_Data.js';
import { Expression } from './Expression.js';
import { Extension } from './Extension.js';
import { Period } from './Period.js';
export interface Consent_Provision {
    /**
     * @description Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
     * @short Unique id for inter-element referencing
     */
    id?: string;
    /**
     * @description 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.
     * @comment 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.
     * @short Additional content defined by implementations
     */
    extension?: Extension[];
    /**
     * @description 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 andor 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).
     * @comment 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.
     * @short Extensions that cannot be ignored even if unrecognized
     */
    modifierExtension?: Extension[];
    /**
     * @description Timeframe for this provision.
     * @comment This is the bound effective time of the consent and should be in the base provision in the Consent resource.
     * @short Timeframe for this provision
     */
    period?: Period;
    /**
     * @backbone Nested BackboneElement: actor [0..*]
     */
    actor?: Consent_Provision_Actor[];
    /**
     * @description Actions controlled by this provision.
     * @comment Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.
     * @short Actions controlled by this provision
     */
    action?: CodeableConcept[];
    /**
     * @description A security label, comprised of 0.. security label fields (Privacy tags), which define which resources are controlled by this exception.
     * @comment If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict.
     * @short Security Labels that define affected resources
     */
    securityLabel?: Coding[];
    /**
     * @description The context of the activities a user is taking - why the user is accessing the data - that are controlled by this provision.
     * @comment When the purpose of use tag is on the data, access request purpose of use shall not conflict.
     * @short Context of activities covered by this provision
     */
    purpose?: Coding[];
    /**
     * @description The documentType(s) covered by this provision. The type can be a CDA document, or some other type that indicates what sort of information the consent relates to.
     * @comment Multiple types are or'ed together. The intention of the documentType element is that the codes refer to document types defined in a standard somewhere.
     * @short e.g. Resource Type, Profile, CDA, etc
     */
    documentType?: Coding[];
    /**
     * @description The resourceType(s) covered by this provision. The type can be a FHIR resource type or a profile on a type that indicates what information the consent relates to.
     * @comment Multiple types are or'ed together. The intention of the resourceType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.
     * @short e.g. Resource Type, Profile, etc
     */
    resourceType?: Coding[];
    /**
     * @description If this code is found in an instance, then the provision applies.
     * @short e.g. LOINC or SNOMED CT code, etc. in the content
     */
    code?: CodeableConcept[];
    /**
     * @description Clinical or Operational Relevant period of time that bounds the data controlled by this provision.
     * @comment This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.
     * @short Timeframe for data controlled by this provision
     */
    dataPeriod?: Period;
    /**
     * @backbone Nested BackboneElement: data [0..*]
     */
    data?: Consent_Provision_Data[];
    /**
     * @description A computable (FHIRPath or other) definition of what is controlled by this consent.
     * @comment Constraining the expression type for a specific implementation via profile is recommended
     * @short A computable expression of the consent
     */
    expression?: Expression;
    /**
     * @description Provisions which provide exceptions to the base provision or subprovisions.
     * @short Nested Exception Provisions
     */
    provision?: any[];
}
//# sourceMappingURL=Consent_Provision.d.ts.map