import { Account } from './Account.js';
import { Appointment } from './Appointment.js';
import { CarePlan } from './CarePlan.js';
import { CareTeam } from './CareTeam.js';
import { CodeableConcept } from './CodeableConcept.js';
import { CodeableReference } from './CodeableReference.js';
import { DeviceRequest } from './DeviceRequest.js';
import { Duration } from './Duration.js';
import { Encounter_Admission } from './Encounter_Admission.js';
import { Encounter_Diagnosis } from './Encounter_Diagnosis.js';
import { Encounter_Location } from './Encounter_Location.js';
import { Encounter_Participant } from './Encounter_Participant.js';
import { Encounter_Reason } from './Encounter_Reason.js';
import { EpisodeOfCare } from './EpisodeOfCare.js';
import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
import { Group } from './Group.js';
import { HealthcareService } from './HealthcareService.js';
import { Identifier } from './Identifier.js';
import { MedicationRequest } from './MedicationRequest.js';
import { Meta } from './Meta.js';
import { Narrative } from './Narrative.js';
import { Organization } from './Organization.js';
import { Patient } from './Patient.js';
import { Period } from './Period.js';
import { Reference } from './Reference.js';
import { Resource } from './Resource.js';
import { ServiceRequest } from './ServiceRequest.js';
import { VirtualServiceDetail } from './VirtualServiceDetail.js';
export interface Encounter {
    /**
     * @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 Identifier(s) by which this encounter is known.
     * @short Identifier(s) by which this encounter is known
     */
    identifier?: Identifier[];
    /**
     * @description The current state of the encounter (not the state of the patient within the encounter - that is subjectState).
     * @comment Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).
     * @short planned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown
     */
    status: FhirPrimitive<string>;
    /**
     * @description Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.
     * @short Classification of patient encounter context - e.g. Inpatient, outpatient
     */
    class?: CodeableConcept[];
    /**
     * @description Indicates the urgency of the encounter.
     * @short Indicates the urgency of the encounter
     */
    priority?: CodeableConcept;
    /**
     * @description Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).
     * @comment Since there are many ways to further classify encounters, this element is 0...
     * @short Specific type of encounter (e.g. e-mail consultation, surgical day-care, ...)
     */
    type?: CodeableConcept[];
    /**
     * @description Broad categorization of the service that is to be provided (e.g. cardiology).
     * @short Specific type of service
     */
    serviceType?: CodeableReference<HealthcareService>[];
    /**
     * @description The patient or group related to this encounter. In some use-cases the patient MAY not be present, such as a case meeting about a patient between several practitioners or a careteam.
     * @comment While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of peoplestaff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).
     * @short The patient or group related to this encounter
     */
    subject?: Reference<Patient | Group>;
    /**
     * @description The subjectStatus value can be used to track the patient's status within the encounter. It details whether the patient has arrived or departed, has been triaged or is currently in a waiting status.
     * @comment Different use-cases are likely to have different permitted transitions between states, such as an Emergency department could use `arrived` when the patient first presents, then `triaged` once has been assessed by a nurse, then `receiving-care` once treatment begins, however other sectors may use a different set of these values, or their own custom set in place of this example valueset provided.
     * @short The current status of the subject in relation to the Encounter
     */
    subjectStatus?: CodeableConcept;
    /**
     * @description Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem.  The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).
     * @short Episode(s) of care that this encounter should be recorded against
     */
    episodeOfCare?: Reference<EpisodeOfCare>[];
    /**
     * @description The request this encounter satisfies (e.g. incoming referral or procedure request).
     * @short The request that initiated this encounter
     */
    basedOn?: Reference<CarePlan | DeviceRequest | MedicationRequest | ServiceRequest>[];
    /**
     * @description The group(s) of individuals, organizations that are allocated to participate in this encounter. The participants backbone will record the actuals of when these individuals participated during the encounter.
     * @short The group(s) that are allocated to participate in this encounter
     */
    careTeam?: Reference<CareTeam>[];
    /**
     * @description Another Encounter of which this encounter is a part of (administratively or in time).
     * @comment This is also used for associating a child's encounter back to the mother's encounter.
  
  Refer to the Notes section in the Patient resource for further details.
     * @short Another Encounter this encounter is part of
     */
    partOf?: Reference<Encounter>;
    /**
     * @description The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation.  Refer to the colonoscopy example on the Encounter examples tab.
     * @short The organization (facility) responsible for this encounter
     */
    serviceProvider?: Reference<Organization>;
    /**
     * @backbone Nested BackboneElement: participant [0..*]
     */
    participant?: Encounter_Participant[];
    /**
     * @description The appointment that scheduled this encounter.
     * @short The appointment that scheduled this encounter
     */
    appointment?: Reference<Appointment>[];
    /**
     * @description Connection details of a virtual service (e.g. conference call).
     * @comment There are two types of virtual meetings that often exist:
  
   a persistent, virtual meeting room that can only be used for a single purpose at a time,
   and a dynamic virtual meeting room that is generated on demand for a specific purpose.
  
  Implementers may consider using Location.virtualService for persistent meeting rooms.
  
  If each participant would have a different meeting link, an extension using the VirtualServiceContactDetail  can be applied to the Encounter.participant BackboneElement.
     * @short Connection details of a virtual service (e.g. conference call)
     */
    virtualService?: VirtualServiceDetail[];
    /**
     * @description The actual start and end time of the encounter.
     * @comment If not (yet) known, the end of the Period may be omitted.
     * @short The actual start and end time of the encounter
     */
    actualPeriod?: Period;
    /**
     * @description The planned start datetime (or admission date) of the encounter.
     * @short The planned start datetime (or admission date) of the encounter
     */
    plannedStartDate?: FhirPrimitive<string>;
    /**
     * @description The planned end datetime (or discharge date) of the encounter.
     * @short The planned end datetime (or discharge date) of the encounter
     */
    plannedEndDate?: FhirPrimitive<string>;
    /**
     * @description Actual quantity of time the encounter lasted. This excludes the time during leaves of absence.
  
  When missing it is the time in between the start and end values.
     * @comment If the precision on these values is low (e.g. to the day only) then this may be considered was an all day (or multi-day) encounter, unless the duration is included, where that amount of time occurred sometime during the interval.
  
  May differ from the time in `Encounter.period` due to leave of absence(s).
     * @short Actual quantity of time the encounter lasted (less time absent)
     */
    length?: Duration;
    /**
     * @backbone Nested BackboneElement: reason [0..*]
     */
    reason?: Encounter_Reason[];
    /**
     * @backbone Nested BackboneElement: diagnosis [0..*]
     */
    diagnosis?: Encounter_Diagnosis[];
    /**
     * @description The set of accounts that may be used for billing for this Encounter.
     * @comment The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.
     * @short The set of accounts that may be used for billing for this Encounter
     */
    account?: Reference<Account>[];
    /**
     * @description Diet preferences reported by the patient.
     * @comment For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).
     * @short Diet preferences reported by the patient
     */
    dietPreference?: CodeableConcept[];
    /**
     * @description Any special requests that have been made for this encounter, such as the provision of specific equipment or other things.
     * @short Wheelchair, translator, stretcher, etc
     */
    specialArrangement?: CodeableConcept[];
    /**
     * @description Special courtesies that may be provided to the patient during the encounter (VIP, board member, professional courtesy).
     * @comment Although the specialCourtesy property can contain values like VIP, the purpose of this field is intended to be used for flagging additional `benefits` that might occur for the patient during the encounter.
  
  It could include things like the patient is to have a private room, special room features, receive a friendly visit from hospital adminisitration, or should be briefed on treatment by senior staff during the stay.
  
  It is not specifically intended to be used for securing the specific record - that is the purpose of the security meta tag, and where appropriate, both fields could be used.
     * @short Special courtesies (VIP, board member)
     */
    specialCourtesy?: CodeableConcept[];
    /**
     * @backbone Nested BackboneElement: admission [0..1]
     */
    admission?: Encounter_Admission;
    /**
     * @backbone Nested BackboneElement: location [0..*]
     */
    location?: Encounter_Location[];
    /**
     * @const Auto-injected fixed value: Encounter
     */
    resourceType: "Encounter";
}
//# sourceMappingURL=Encounter.d.ts.map