description: Base StructureDefinition for Patient Resource
package_name: hl7.fhir.r2.examples
name: Patient
type: null
elements:
  multipleBirthBoolean: {short: Whether patient is part of a multiple birth, type: boolean, choiceOf: multipleBirth, index: 14}
  address: {short: Addresses for the individual, comments: Patient may have multiple addresses with different uses or applicable periods., type: Address, array: true, isSummary: true, index: 10}
  deceasedDateTime: {isModifier: true, short: Indicates if the individual is deceased or not, comments: If there's no value in the instance it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive., type: dateTime, choiceOf: deceased, isSummary: true, index: 9}
  managingOrganization: {short: Organization that is the custodian of the patient record, comments: '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).', type: Reference, isSummary: true, index: 33}
  deceasedBoolean: {isModifier: true, short: Indicates if the individual is deceased or not, comments: If there's no value in the instance it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive., type: boolean, choiceOf: deceased, isSummary: true, index: 8}
  name: {short: A name associated with the patient, comments: '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.', type: HumanName, array: true, isSummary: true, index: 2}
  birthDate: {short: The date of birth for the individual, comments: At least an estimated year should be provided as a guess if the real DOB is unknown  There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternaty/infant care systems)., type: date, isSummary: true, index: 5}
  multipleBirthInteger: {short: Whether patient is part of a multiple birth, type: integer, choiceOf: multipleBirth, index: 15}
  careProvider: {type: Reference, short: Patient's nominated primary care provider, comments: 'This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disablity setting, or even organization that will provide people to perform the care provider roles.  This is not to be used to record Care Teams, these should be recorded on either the CarePlan or EpisodeOfCare resources.', array: true, index: 32}
  multipleBirth:
    short: Whether patient is part of a multiple birth
    choices: [multipleBirthBoolean, multipleBirthInteger]
    index: 13
  deceased:
    isModifier: true
    short: Indicates if the individual is deceased or not
    comments: If there's no value in the instance it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.
    choices: [deceasedBoolean, deceasedDateTime]
    isSummary: true
    index: 7
  photo: {type: Attachment, short: Image of the patient, array: true, index: 16}
  link:
    isModifier: true
    short: Link to another patient resource that concerns the same actual person
    comments: There is no assumption that linked patient records have mutual links.
    type: BackboneElement
    array: true
    index: 34
    elements:
      other: {type: Reference, short: The other patient resource that the link refers to, isModifier: true, index: 35}
      type: {isModifier: true, short: replace | refer | seealso - type of link, type: code, index: 36}
    required: [type, other]
  active: {isModifier: true, short: Whether this patient's record is in active use, comments: 'Default is true. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.', type: boolean, defaultValueBoolean: true, isSummary: true, index: 1}
  communication:
    short: A list of Languages which may be used to communicate with the patient about his or her health
    comments: If no language is specified, this *implies* that the default local language is spoken.  If you need to convey proficiency for multiple modes then you need multiple Patient.Communication associations.   For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
    type: BackboneElement
    array: true
    index: 29
    elements:
      language: {short: The language which can be used to communicate with the patient about his or her health, comments: The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type., type: CodeableConcept, index: 30}
      preferred: {short: Language preference indicator, comments: This language is specifically identified for communicating healthcare information., type: boolean, index: 31}
    required: [language]
  animal:
    isModifier: true
    short: This patient is known to be an animal (non-human)
    comments: The animal element is labeled "Is Modifier" since patients may be non-human. Systems SHALL either handle patient details appropriately (e.g. inform users patient is not human) or reject declared animal records.   The absense of the animal element does not imply that the patient is a human. If a system requires such a positive assertion that the patient is human, an extension will be required.  (Do not use a species of homo-sapiens in animal species, as this would incorrectly infer that the patient is an animal).
    type: BackboneElement
    isSummary: true
    index: 25
    elements:
      species: {short: 'E.g. Dog, Cow', comments: 'If the patient is non-human, at least a species SHALL be specified. Species SHALL be a widely recognised taxonomic classification.  It may or may not be Linnaean taxonomy and may or may not be at the level of species. If the level is finer than species--such as a breed code--the code system used SHALL allow inference of the species.  (The common example is that the word "Hereford" does not allow inference of the species Bos taurus, because there is a Hereford pig breed, but the SNOMED CT code for "Hereford Cattle Breed" does.).', type: CodeableConcept, isSummary: true, index: 26}
      breed: {short: 'E.g. Poodle, Angus', comments: Breed MAY be used to provide further taxonomic or non-taxonomic classification.  It may involve local or proprietary designation--such as commercial strain--and/or additional information such as production type., type: CodeableConcept, isSummary: true, index: 27}
      genderStatus: {short: 'E.g. Neutered, Intact', type: CodeableConcept, isSummary: true, index: 28}
    required: [species]
  identifier: {short: An identifier for this patient, type: Identifier, array: true, isSummary: true, index: 0}
  telecom: {short: A contact detail for the individual, comments: '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 may 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).', type: ContactPoint, array: true, isSummary: true, index: 3}
  gender: {short: male | female | other | unknown, comments: 'The gender may 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 M and F, though the vast majority of systems and contexts only support M and F.  Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific gender aspect of interest (anatomical, chromosonal, 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, chromosonal and other gender aspects.  For example, an alert about a hysterectomy on a male should be handled as a warning or overrideable error, not a "hard" error.', type: code, isSummary: true, index: 4}
  maritalStatus: {short: Marital (civil) status of a patient, type: CodeableConcept, index: 11}
  contact:
    constraint:
      pat-1: {human: SHALL at least contain a contact's details or a reference to an organization, severity: error}
    short: A contact party (e.g. guardian, partner, friend) for the patient
    comments: 'Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.'
    type: BackboneElement
    array: true
    index: 17
    elements:
      relationship: {short: The kind of relationship, type: CodeableConcept, array: true, index: 18}
      name: {type: HumanName, short: A name associated with the contact person, index: 19}
      telecom: {short: A contact detail for the person, comments: 'Contact 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.', type: ContactPoint, array: true, index: 20}
      address: {type: Address, short: Address for the contact person, index: 21}
      gender: {short: male | female | other | unknown, type: code, index: 22}
      organization: {short: Organization that is associated with the contact, type: Reference, index: 23}
      period: {type: Period, short: The period during which this contact person or organization is valid to be contacted relating to this patient, index: 24}
package_version: 1.0.2
class: resource
kind: resource
url: http://hl7.org/fhir/StructureDefinition/Patient
version: null