Demographics and other administrative information about an individual or animal receiving care or other health-related services. Demographics and other administrative information about an individual or animal receiving care or other health-related services.

Tracking patient is the center of the healthcare process. Tracking patient is the center of the healthcare process.

An identifier for this patient. An identifier for this patient.

Patients are almost always assigned specific numerical identifiers. Patients are almost always assigned specific numerical identifiers.

Whether this patient record is in active use. Whether this patient record is in active use.

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

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

A name associated with the individual. 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. 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. 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.

A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. 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. 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 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). 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).

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

Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes. Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes.

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

The date of birth for the individual. The date of birth for the individual.

Age of the individual drives many clinical processes. Age of the individual drives many clinical processes.

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

Indicates if the individual is deceased or not. Indicates if the individual is deceased or not.

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

Addresses for the individual. Addresses for the individual.

May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification. 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. Patient may have multiple addresses with different uses or applicable periods.

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

Most, if not all systems capture it. Most, if not all systems capture it.

Indicates whether the patient is part of a multiple or indicates the actual birth order. Indicates whether the patient is part of a multiple (bool) or indicates the actual birth order (integer).

For disambiguation of multiple-birth children, especially relevant where the care provider doesn't meet the patient, such as labs. 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 tripplets would be valueInteger=2 and the third born would have valueInteger=3 If a bool value was provided for this tripplets examle, then all 3 patient records would have valueBool=true (the ordering is not indicated).

Image of the patient. Image of the patient.

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

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

Need to track people you can contact about 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. 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 relationship between the patient and the contact person. The nature of the relationship between the patient and the contact person.

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

A name associated with the contact person. A name associated with the contact person.

Contact persons need to be identified by name, but it is uncommon to need details about multiple other names for that contact person. Contact persons need to be identified by name, but it is uncommon to need details about multiple other names for that contact person.

A contact detail for the person, e.g. a telephone number or an email address. 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. 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. 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. Address for the contact person.

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

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

Needed to address the person correctly. Needed to address the person correctly.

Organization on behalf of which the contact is acting or for which the contact is working. 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. 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. The period during which this contact person or organization is valid to be contacted relating to this patient.

This patient is known to be an animal. This patient is known to be an animal.

Many clinical systems are extended to care for animal patients as well as human. Many clinical systems are extended to care for animal patients as well as human.

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

Identifies the high level taxonomic categorization of the kind of animal. Identifies the high level taxonomic categorization of the kind of animal.

Need to know what kind of animal. Need to know what kind of animal.

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

Identifies the detailed categorization of the kind of animal. Identifies the detailed categorization of the kind of animal.

May need to know the specific kind within the species. May need to know the specific kind within the species.

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

Indicates the current state of the animal's reproductive organs. Indicates the current state of the animal's reproductive organs.

Gender status can affect housing and animal behavior. Gender status can affect housing and animal behavior.

Languages which may be used to communicate with the patient about his or her health. Languages 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 is an important things to keep track of both for patient and other persons of interest. If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest.

If no language is specified, this 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. 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 the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English.

Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. 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 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. 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.

Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). 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. 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. This language is specifically identified for communicating healthcare information.

Patient's nominated care provider. 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/disablity 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.

Organization that is the custodian of the patient record. Organization that is the custodian of the patient record.

Need to know who recognizes this patient record, manages and updates it. 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). 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 resource that concerns the same actual patient. Link to another patient resource that concerns the same actual patient.

There are multiple usecases: 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 are multiple usecases:

• 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. There is no assumption that linked patient records have mutual links.

The other patient resource that the link refers to. The other patient resource that the link refers to.

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. The type of link between this patient resource and another patient resource.