import { Coding } from './Coding.js';
import { Expression } from './Expression.js';
import { Extension } from './Extension.js';
import { Period } from './Period.js';
import { Permission_Rule_Data_Resource } from './Permission_Rule_Data_Resource.js';
export interface Permission_Rule_Data {
    /**
     * @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[];
    /**
     * @backbone Nested BackboneElement: resource [0..*]
     */
    resource?: Permission_Rule_Data_Resource[];
    /**
     * @description The data in scope are those with the given codes present in that data .meta.security element.
     * @comment Note the ConfidentialityCode vocabulary indicates the highest value, thus 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 tag code on .meta.security
     */
    security?: Coding[];
    /**
     * @description Clinical or Operational Relevant period of time that bounds the data controlled by this rule.
     * @comment This has a different sense to the .validity.
     * @short Timeframe encompasing data createupdate
     */
    period?: Period[];
    /**
     * @description Used when other data selection elements are insufficient.
     * @short Expression identifying the data
     */
    expression?: Expression;
}
//# sourceMappingURL=Permission_Rule_Data.d.ts.map