import { CodeableConcept } from './CodeableConcept.js';
import { Device } from './Device.js';
import { Extension } from './Extension.js';
import { Group } from './Group.js';
import { HealthcareService } from './HealthcareService.js';
import { Patient } from './Patient.js';
import { Period } from './Period.js';
import { Practitioner } from './Practitioner.js';
import { PractitionerRole } from './PractitionerRole.js';
import { Reference } from './Reference.js';
import { RelatedPerson } from './RelatedPerson.js';
export interface Encounter_Participant {
    /**
     * @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 Role of participant in encounter.
     * @comment The participant type indicates how an individual actor participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.
     * @short Role of participant in encounter
     */
    type?: CodeableConcept[];
    /**
     * @description The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period.
     * @short Period of time during the encounter that the participant participated
     */
    period?: Period;
    /**
     * @description Person involved in the encounter, the patientgroup is also included here to indicate that the patient was actually participating in the encounter. Not including the patient here covers use cases such as a case meeting between practitioners about a patient - non contact times.
     * @comment For planning purposes, Appointments may include a CareTeam participant to indicate that one specific person from the CareTeam will be assigned, but that assignment might not happen until the Encounter begins. Hence CareTeam is not included in Encounter.participant, as the specific individual should be assigned and represented as a Practitioner or other person resource.
  
  Similarly, Location can be included in Appointment.participant to assist with planning.  However, the patient location is tracked on the Encounter in the Encounter.location property to allow for additional metadata and history to be recorded.
  
  The role of the participant can be used to declare what the actor will be doing in the scope of this encounter participation.
  
  If the individual is not specified during planning, then it is expected that the individual will be filled in at a later stage prior to the encounter commencing.
     * @short The individual, device, or service participating in the encounter
     */
    actor?: Reference<Patient | Group | RelatedPerson | Practitioner | PractitionerRole | Device | HealthcareService>;
}
//# sourceMappingURL=Encounter_Participant.d.ts.map