import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
export interface SubscriptionTopic_ResourceTrigger_QueryCriteria {
    /**
     * @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 The FHIR query based rules are applied to the previous resource state (e.g., state before an update).
     * @comment The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading slash character (``).
     * @short Rule applied to previous resource state
     */
    previous?: FhirPrimitive<string>;
    /**
     * @description For `create` interactions, should the `previous` criteria count as an automatic pass or an automatic fail. If not present, the testing behavior during `create` interactions is unspecified (server discretion).
     * @short test-passes | test-fails
     */
    resultForCreate?: FhirPrimitive<string>;
    /**
     * @description The FHIR query based rules are applied to the current resource state (e.g., state after an update).
     * @comment The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading slash character (``).
     * @short Rule applied to current resource state
     */
    current?: FhirPrimitive<string>;
    /**
     * @description For 'delete' interactions, should the 'current' query criteria count as an automatic pass or an automatic fail. If not present, the testing behavior during `delete` interactions is unspecified (server discretion).
     * @short test-passes | test-fails
     */
    resultForDelete?: FhirPrimitive<string>;
    /**
     * @description If set to `true`, both the `current` and `previous` query criteria must evaluate `true` to trigger a notification for this topic.  If set to `false` or not present, a notification for this topic will be triggered if either the `current` or `previous` tests evaluate to `true`.
     * @comment Please note the interaction between this element and the `resultForCreate``resultForDelete` elements during `create` and `delete` interactions.  For example, if `resultForCreate` is set to `test-passes`, setting `requireBoth` to `false` means that every `create` will trigger a notification while setting `requireBoth` to `true` will result in notifications if the `current` test passes.  Similarly, if `resultForCreate` is set to `test-fails`, setting `requireBoth` to `true` means that no `create` will be able to generate a notification while setting `requireBoth` to `false` will result in notifications if the `current` test passes.
     * @short Both must be true flag
     */
    requireBoth?: FhirPrimitive<boolean>;
}
//# sourceMappingURL=SubscriptionTopic_ResourceTrigger_QueryCriteria.d.ts.map