Demographics and other administrative information about an individual or animal receiving care that is the subject of potential, past, current, or other future health-related services. care, services, or processes.

Tracking patient is the center of the healthcare process.

An identifier for this patient.

Patients are almost always assigned specific numerical identifiers.

Systems MAY use identifier for user identities (using the type='USER'). Refer to the Security and Privacy section for additional guidance on representing user identities.

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.

Need to be able to mark a patient record as not to be used because it was created in error.

If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.

A name associated with the individual.

Need to be able to track the patient by multiple names. Examples are your official name and a partner name.

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.

A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted.

People have (primary) ways to contact them in some way such as phone, email.

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).

DO NOT use .telecom properties to represent user identities. Refer to the Security and Privacy section for additional guidance on representing user identities.

Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes.

See the Patient Gender and Sex section for additional information about communicating patient gender and sex.

Needed for identification of the individual, in combination with (at least) name and birth date.

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.

The date of birth for the individual.

Age of the individual drives many clinical processes.

At least an estimated year should be provided as a guess Partial dates are allowed if the real DOB specific date of birth is unknown unknown. There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternity/infant care systems).

Indicates if the date when the individual died, or, if the date is deceased not known or not. cannot be estimated, a flag indicating the patient is known to be deceased.

The fact that a patient is deceased influences the clinical process. Also, in human communication and relation management it is necessary to know whether the person is alive.

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.

An address for the individual.

May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification.

Patient may have multiple addresses with different uses or applicable periods.

This field contains a patient's most recent marital (civil) status.

Most, if not all systems capture it.

Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer). This count is relative to the total of live births and fetal losses, which MAY be tracked in the patient-multipleBirthTotal extension.

The boolean option for this property can also be used to track that there are known to be multiple fetuses prior to birth.

For disambiguation of multiple-birth children, especially relevant where the care provider doesn't meet the patient, such as labs.

Where the valueInteger is provided, the number is the birth number in the sequence.

E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3 valueInteger=3. If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).

valueBoolean can be used to track fetuses. valueInteger should only be used after live birth.

Image of the patient.

Many EHR systems have the capability to capture an image of the patient. Fits with newer social media usage too.

Guidelines:

• Use id photos, not clinical photos.
• Limit dimensions to thumbnail.
• Keep byte count low to ease resource updates.

A contact party (e.g. guardian, partner, friend) for the patient.

Need to track people you can contact about the patient.

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.

The nature of the personal relationship between the patient and the contact person.

Used to determine the nature of the personal relationship between the patient and the contact person.

This property is for personal relationships. Functional relationships would be represented in Patient.contact.role .

The nature of the functional role between the patient and the contact person.

Used to determine which contact person is the most relevant to approach, depending on circumstances.

This property is for functional relationships. Personal relationships would be represented in Patient.contact.relationship .

A name associated with the contact person. Alternate/additional names for this contact can be found in the additionalName property.

Contact persons need to be identified by name. Where multiple names are required, such as legal name and usual (Name to Use) name, but it is uncommon also refer to need the additionalName property.

Additional names for that the contact person.

To maintain backward compatibility, additionalName was added as a way to express names beyond the single name that can be represented in Patient.contact.name .

When looking for an name of a given type, implementers should inspect both Patient.contact.name and Patient.contact.additionalName , and treat those two properties as a single combined logical list of names.

A contact detail for the person, e.g. a telephone number or an email address.

People have (primary) ways to contact them in some way such as phone, email.

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.

Address for the contact person. Alternate/additional addresses for this contact can be found in the additionalAddress property.

Need to keep track where the contact person can be contacted per postal mail or visited.

Additional addresses for the contact person.

Need to keep track where the contact person can be contacted per postal mail or visited.

To maintain backward compatibility, additionalAddress was added as a way to express addresses beyond the single address that can be represented in Patient.contact.address.

When looking for an address of a given type, implementers should inspect both Patient.contact.address and Patient.contact.additionalAddress , and treat those two properties as a single combined logical list of addresses.

Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes.

Needed to address the person correctly.

Organization on behalf of which the contact is acting or for which the contact is working.

For guardians or business related contacts, the organization is relevant.

The period during which this contact person or organization is valid to be contacted relating to this patient.

A language which may be used to communicate with the patient about his or her health.

If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency are important things to keep track of both for patient and other persons of interest.

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.

The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and language which may be used to communicate with the ISO-3166-1 alpha 2 code for individual.

Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.

The structure aa-BB with this exact casing language is one commonly represented using the most widely used notations ISO-639-1 alpha code in lower case for locale. However not the language, optionally followed by a hyphen and the ISO-3166-1 alpha code for the region in upper case. For example, "en" for English, or "en-US" for American English versus "en-AU" for Australian English, sgn-US for American Sign Language, sgn-NL for Dutch Sign Language, etc.

Not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

Indicates whether or not the patient prefers this language (over other languages he masters up a certain level).

People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method.

This language is specifically identified for communicating healthcare information.

Patient's nominated care provider.

This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability 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-in/fly-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.

Organization that is the custodian of the patient record.

Need to know who recognizes this patient record, manages and updates it.

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).

Link to another patient a Patient or RelatedPerson resource that concerns the same actual patient. individual.

There are multiple use cases:

• Duplicate patient records due to the clerical errors associated with the difficulties of identifying humans consistently, and
• Distribution of patient information across multiple servers.

There is no assumption that linked patient records have mutual links.

Link to a Patient or RelatedPerson resource that concerns the same actual individual.

Referencing a RelatedPerson here removes the need to use a Person record to associate a Patient and RelatedPerson as the same individual.

The type of link between this patient resource and another patient resource.