import { CarePlan } from './CarePlan.js';
import { CodeableConcept } from './CodeableConcept.js';
import { CodeableReference } from './CodeableReference.js';
import { DeviceRequest } from './DeviceRequest.js';
import { Encounter } from './Encounter.js';
import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
import { ImmunizationRecommendation } from './ImmunizationRecommendation.js';
import { Location } from './Location.js';
import { MedicationRequest } from './MedicationRequest.js';
import { Meta } from './Meta.js';
import { Narrative } from './Narrative.js';
import { NutritionOrder } from './NutritionOrder.js';
import { Patient } from './Patient.js';
import { Period } from './Period.js';
import { Provenance_Agent } from './Provenance_Agent.js';
import { Provenance_Entity } from './Provenance_Entity.js';
import { Reference } from './Reference.js';
import { Resource } from './Resource.js';
import { ServiceRequest } from './ServiceRequest.js';
import { Signature } from './Signature.js';
import { Task } from './Task.js';
export interface Provenance {
    /**
     * @description The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
     * @comment Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
     * @short Logical id of this artifact
     */
    id?: string;
    /**
     * @description The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
     * @short Metadata about the resource
     */
    meta?: Meta;
    /**
     * @description A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
     * @comment Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers andor specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
     * @short A set of rules under which this content was created
     */
    implicitRules?: FhirPrimitive<string>;
    /**
     * @description The base language in which the resource is written.
     * @comment Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
     * @short Language of the resource content
     */
    language?: FhirPrimitive<string>;
    /**
     * @description A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
     * @comment Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
     * @short Text summary of the resource, for human interpretation
     */
    text?: Narrative;
    /**
     * @description These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides contextmeaning.
     * @comment This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
     * @short Contained, inline Resources
     */
    contained?: Resource[];
    /**
     * @description May be used to represent additional information that is not part of the basic definition of the resource. 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 resource and that modifies the understanding of the element that contains it 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 is allowed to 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
     */
    modifierExtension?: Extension[];
    /**
     * @description The Reference(s) that were generated or updated by  the activity described in this resource. A provenance can point to more than one target if multiple resources were createdupdated by the same activity.
     * @comment Target references are usually version specific, but might not be, if a version has not been assigned or if the provenance information is part of the set of resources being maintained (i.e. a document). When using the RESTful API, the identity of the resource might not be known (especially not the version specific one); the client may either submit the resource first, and then the provenance, or it may submit both using a single transaction. See the notes on transaction for further discussion.
     * @short Target Reference(s) (usually version specific)
     */
    target: Reference<Resource>[];
    /**
     * @choice This is part of the occurred[x] choice.
     * @oneOf occurredPeriod, occurredDateTime
     */
    occurredPeriod?: Period;
    /**
     * @choice This is part of the occurred[x] choice.
     * @oneOf occurredPeriod, occurredDateTime
     */
    occurredDateTime?: FhirPrimitive<string>;
    /**
     * @description The instant of time at which the activity was recorded.
     * @comment This can be a little different from the time stamp on the resource if there is a delay between recording the event and updating the provenance and target resource.
     * @short When the activity was recorded  updated
     */
    recorded?: FhirPrimitive<string>;
    /**
     * @description Policy or plan the activity was defined by. Typically, a single activity may have multiple applicable policy documents, such as patient consent, guarantor funding, etc.
     * @comment For example: Where an OAuth token authorizes, the unique identifier from the OAuth token is placed into the policy element Where a policy engine (e.g. XACML) holds policy logic, the unique policy identifier is placed into the policy element.
     * @short Policy or plan the activity was defined by
     */
    policy?: FhirPrimitive<string>[];
    /**
     * @description Where the activity occurred, if relevant.
     * @short Where the activity occurred, if relevant
     */
    location?: Reference<Location>;
    /**
     * @description The authorization (e.g., PurposeOfUse) that was used during the event being recorded.
     * @short Authorization (purposeOfUse) related to the event
     */
    authorization?: CodeableReference<any>[];
    /**
     * @description An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.
     * @short Activity that occurred
     */
    activity?: CodeableConcept;
    /**
     * @description Allows tracing of authorizatino for the events and tracking whether proposalsrecommendations were acted upon.
     * @short Workflow authorization within which this event occurred
     */
    basedOn?: Reference<CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest | Task>[];
    /**
     * @description The patient element is available to enable deterministic tracking of activities that involve the patient as the subject of the data used in an activity.
     * @short The patient is the subject of the data createdupdated (.target) by the activity
     */
    patient?: Reference<Patient>;
    /**
     * @description This will typically be the encounter the event occurred, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission lab tests).
     * @short Encounter within which this event occurred or which the event is tightly associated
     */
    encounter?: Reference<Encounter>;
    /**
     * @backbone Nested BackboneElement: agent [1..*]
     */
    agent: Provenance_Agent[];
    /**
     * @backbone Nested BackboneElement: entity [0..*]
     */
    entity?: Provenance_Entity[];
    /**
     * @description A digital signature on the target Reference(s). The signer should match a Provenance.agent. The purpose of the signature is indicated.
     * @short Signature on target
     */
    signature?: Signature[];
    /**
     * @const Auto-injected fixed value: Provenance
     */
    resourceType: "Provenance";
}
//# sourceMappingURL=Provenance.d.ts.map