/** * FHIR Version R5 * The following is auto generated resource definition. * * OpenAPI spec version: 3.0.1 * * * NOTE: This class is auto generated by the swagger code generator program. * https://github.com/swagger-api/swagger-codegen.git * Do not edit the class manually. */ import { Code } from './code'; import { CodeableConcept } from './codeableConcept'; import { CodeableReference } from './codeableReference'; import { DateTime } from './dateTime'; import { Duration } from './duration'; import { EncounterHistoryLocation } from './encounterHistoryLocation'; import { Extension } from './extension'; import { Id } from './id'; import { Identifier } from './identifier'; import { Meta } from './meta'; import { Narrative } from './narrative'; import { Period } from './period'; import { Reference } from './reference'; import { ResourceList } from './resourceList'; import { Uri } from './uri'; /** * A record of significant events/milestones key data throughout the history of an Encounter, often tracked for specific purposes such as billing. */ export interface EncounterHistory { /** * This is a EncounterHistory resource */ resourceType: 'EncounterHistory'; id?: Id; meta?: Meta; implicitRules?: Uri; language?: Code; text?: Narrative; /** * 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 context/meaning. */ contained?: Array; /** * 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. */ extension?: Array; /** * 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 and/or 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). */ modifierExtension?: Array; encounter?: Reference; /** * Identifier(s) by which this encounter is known. */ identifier?: Array; status?: Code; _class: CodeableConcept; /** * Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). */ type?: Array; /** * Broad categorization of the service that is to be provided (e.g. cardiology). */ serviceType?: Array; subject?: Reference; subjectStatus?: CodeableConcept; actualPeriod?: Period; plannedStartDate?: Date; plannedEndDate?: Date; length?: Duration; /** * The location of the patient at this point in the encounter, the multiple cardinality permits de-normalizing the levels of the location hierarchy, such as site/ward/room/bed. */ location?: Array; }