Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.

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

Indicação se utente falecido

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.

Para moradas nacionais é obrigatória a utilização da estrutura de moradas previstas pelos CTT. O atributo address.text será utilizado para descrição de morada de países terceiros e o atributo address.line terá de conter a estrutura da morada nacional definida pelos CTT, tendo de cumprir com a ordenação definida no line.

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

Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).

Identificação se utente faz parte de parto múltiplo ou indicação da ordem de nascimento

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 If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).

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.

Identifica o idioma do utente.

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.

Identificação da equipa de saúde familiar (médico de família e enfermeiro de família) e entidade de inscrição do utente nos Cuidados de Saúde Primários.

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.

Patient.link tem de ser utilizado para identificar situações em que o recurso Patient e RelatedPerson correspondem ao mesmo utente:

a) tem de ser referenciado o recurso RelatedPerson para identificar casos em que o utente em causa é também considerado como uma pessoa relacionada. A título exemplificado e sem perda de generalidade considere-se o cenário em que o utente xpto é mãe, filha e tia de diferentes outros utentes. O elemento Patient.link RelatedPerson, tem de ser utilizado para relacionar cada um dos RelatedPerson mãe, filha e tia com o Patient xpto;

b) tem de ser referenciado o recurso Patient para identificar o registo histórico do utente ou diversos registos criados ao longo do tempo do mesmo utente;

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.