import { Address } from './Address.js';
import { Attachment } from './Attachment.js';
import { CodeableConcept } from './CodeableConcept.js';
import { ContactPoint } from './ContactPoint.js';
import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
import { HumanName } from './HumanName.js';
import { Identifier } from './Identifier.js';
import { Meta } from './Meta.js';
import { Narrative } from './Narrative.js';
import { Organization } from './Organization.js';
import { Patient_Communication } from './Patient_Communication.js';
import { Patient_Contact } from './Patient_Contact.js';
import { Patient_Link } from './Patient_Link.js';
import { Practitioner } from './Practitioner.js';
import { PractitionerRole } from './PractitionerRole.js';
import { Reference } from './Reference.js';
import { Resource } from './Resource.js';
export interface Patient {
    /**
     * @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 An identifier for this patient.
     * @short An identifier for this patient
     */
    identifier?: Identifier[];
    /**
     * @description Whether this patient record is in active use.
  Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules.
  
  It is often used to filter patient lists to exclude inactive patients
  
  Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death.
     * @comment If a record is inactive, and linked to an active record, then future patientrecord updates should occur on the other patient.
     * @short Whether this patient's record is in active use
     */
    active?: FhirPrimitive<boolean>;
    /**
     * @description A name associated with the individual.
     * @comment A patient may have multiple names with different uses or applicable periods. For animals, the name is a "HumanName" in the sense that is assigned and used by humans and has the same patterns. Animal names may be communicated as given names, and optionally may include a family name.
     * @short A name associated with the patient
     */
    name?: HumanName[];
    /**
     * @description A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted.
     * @comment A Patient may have multiple ways to be contacted with different uses or applicable periods.  May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).
     * @short A contact detail for the individual
     */
    telecom?: ContactPoint[];
    /**
     * @description Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes.
     * @comment The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female.  Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.)  However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice.  Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects.  For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a "hard" error.  See the Patient Gender and Sex section for additional information about communicating patient gender and sex.
     * @short male | female | other | unknown
     */
    gender?: FhirPrimitive<string>;
    /**
     * @description The date of birth for the individual.
     * @comment Partial dates are allowed if the specific date of birth is unknown. There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternityinfant care systems).
     * @short The date of birth for the individual
     */
    birthDate?: FhirPrimitive<string>;
    /**
     * @choice This is part of the deceased[x] choice.
     * @oneOf deceasedBoolean, deceasedDateTime
     */
    deceasedBoolean?: FhirPrimitive<boolean>;
    /**
     * @choice This is part of the deceased[x] choice.
     * @oneOf deceasedBoolean, deceasedDateTime
     */
    deceasedDateTime?: FhirPrimitive<string>;
    /**
     * @description An address for the individual.
     * @comment Patient may have multiple addresses with different uses or applicable periods.
     * @short An address for the individual
     */
    address?: Address[];
    /**
     * @description This field contains a patient's most recent marital (civil) status.
     * @short Marital (civil) status of a patient
     */
    maritalStatus?: CodeableConcept;
    /**
     * @choice This is part of the multipleBirth[x] choice.
     * @oneOf multipleBirthBoolean, multipleBirthInteger
     */
    multipleBirthBoolean?: FhirPrimitive<boolean>;
    /**
     * @choice This is part of the multipleBirth[x] choice.
     * @oneOf multipleBirthBoolean, multipleBirthInteger
     */
    multipleBirthInteger?: FhirPrimitive<number>;
    /**
     * @description Image of the patient.
     * @comment Guidelines:
   Use id photos, not clinical photos.
   Limit dimensions to thumbnail.
   Keep byte count low to ease resource updates.
     * @short Image of the patient
     */
    photo?: Attachment[];
    /**
     * @backbone Nested BackboneElement: contact [0..*]
     */
    contact?: Patient_Contact[];
    /**
     * @backbone Nested BackboneElement: communication [0..*]
     */
    communication?: Patient_Communication[];
    /**
     * @description Patient's nominated care provider.
     * @comment This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a communitydisability setting, or even organization that will provide people to perform the care provider roles.  It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources.
  Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a "fly-infly-out" worker that has the onsite GP also included with his home GP to remain aware of medical issues.
  
  Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type.
     * @short Patient's nominated primary care provider
     */
    generalPractitioner?: Reference<Organization | Practitioner | PractitionerRole>[];
    /**
     * @description Organization that is the custodian of the patient record.
     * @comment There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).
     * @short Organization that is the custodian of the patient record
     */
    managingOrganization?: Reference<Organization>;
    /**
     * @backbone Nested BackboneElement: link [0..*]
     */
    link?: Patient_Link[];
    /**
     * @const Auto-injected fixed value: Patient
     */
    resourceType: "Patient";
}
//# sourceMappingURL=Patient.d.ts.map