Zasób zawierający dane osobowe i kontaktowe pacjenta.

Identyfikator logiczny zasobu nadawany przez system w ramach rejestracji zasobu. Przyjmuje wartość: '{liczba naturalna}'

Nadany identyfikator nie podlega aktualizacji. W ramach aktualizacji zasobu należy wskazać wartość identyfikatora zasobu, którego dotyczy aktualizacja.

Metadane zasobu

Wersja zasobu ustawiana przez system. Przyjmuje wartość: '{liczba naturalna}'.

W przypadku, jeśli ilość wersji zasobu Patient przekroczy założony limit zgodnie z regułą REG.WER.7164, błąd HTTP 422 nie zostanie zwrócony, natomiast zostanie zwrócony kod odpowiedzi HTTP 200 oraz ostatnia aktualna wersja zasobu Patient.

Data aktualizacji zasobu ustawiana przez system. Przyjmuje wartość: '{Data i czas w formacie YYYY-MM-DDThh:mm:ss.sss+zz:zz}'.

W ramach rejestracji pierwszej wersji zasobu jest to data rejestracji zasobu, w ramach rejestracji kolejnych wersji zasobu jest to data ostatniej aktualizacji zasobu.

Identyfikator źródła zasobu ustawiany przez system.

Url profilu wg. którego zasób jest walidowany: https://ezdrowie.gov.pl/fhir/StructureDefinition/PLPatient.

Poziom poufności zasobu.

System kodowania poziomów poufności. Przyjmuje wartość: '{urn:oid:2.16.840.1.113883.3.4424.11.1.83}'

Kod poziomu poufności. Przyjmuje wartość: '{kod ze słownika PLSecurityLabels}'

Wersja systemu ustawiana przez system.

Wartość wskazuje na wersję systemu w momencie rejestracji/aktualizacji zasobu.

Identyfikator biznesowy pacjenta.

Przyjmuje się, że pacjent identyfikowany jest przez osobisty numer identyfikacyjny, seria i numer dowodu osobistego, seria i numer paszportu, niepowtarzalny identyfikator nadany przez państwo członkowskie Unii Europejskiej dla celów transgranicznej identyfikacji, o którym mowa w rozporządzeniu wykonawczym Komisji (UE) 2015/1501 z dnia 8 września 2015 r. w sprawie ram interoperacyjności na podstawie art. 12 ust. 8 rozporządzenia Parlamentu Europejskiego i Rady (UE) nr 910/2014 z dnia 23 lipca 2014 r. w sprawie identyfikacji elektronicznej i usług zaufania w odniesieniu do transakcji elektronicznych na rynku wewnętrznym oraz uchylające dyrektywę 1999/93/WE (Dz. Urz. UE L 257 z 28. 8.2014, str. 74, z późn. zm), nazwa, seria i numer innego dokumentu stwierdzającego tożsamość, numer nadany według formatu: XXXXX-RRRR-NN, gdzie XXXXX - kolejny unikalny numer osoby w ramach kodu identyfikatora i roku RRRR – rok. W przypadku noworodka, identyfikowany jest on poprzez wskazanie identyfikatora jednego z rodziców albo opiekuna prawnego wraz z informacją o dacie urodzenia noworodka oraz numerem kolejnego urodzenia z ciąży mnogiej. W przypadku kiedy identyfikator przedstawiciela ustawowego nie jest możliwy do ustalenia, identyfikatorem noworodka jest numer wg formatu: XXXXX-RRRR-NW, gdzie XXXXX - kolejny unikalny numer osoby w ramach kodu identyfikatora i roku RRRR – rok.

OID systemu identyfikacji, w ramach którego nadany został nadany identyfikator. Przyjmuje wartość: W przypadku PESEL: “urn:oid:2.16.840.1.113883.3.4424.1.1.616”; W przypadku paszportu: “urn:oid:2.16.840.1.113883.4.330.{kod kraju}”; W przypadku innego dokumentu stwierdzającego tożsamość pacjenta: “urn:oid:{OID rodzaju dokumentu tożsamości}”; W przypadku noworodka, dla którego znany jest identyfikator jednego z rodziców albo opiekuna prawnego: “urn:oid:{zgodnie z listą rozszerzeń drzewa OID, gałąź od węzła 2.16.840.1.113883.3.4424.1.7}”; W przypadku noworodka, dla którego nie jest znany identyfikator przedstawiciela ustawowego: “urn:oid:2.16.840.1.113883.3.4424.2.7.{x}.17.3” gdzie “x” identyfikuje Usługodawcę; W przypadku osoby o nieznanych danych: “urn:oid:2.16.840.1.113883.3.4424.2.7.{x}.17.2” gdzie “x” identyfikuje Usługodawcę.

Identyfikator pacjenta. Przyjmuje wartość: W przypadku PESEL: “{PESEL pacjenta}”; W przypadku paszportu: “{seria i numer paszportu}”; W przypadku innego dokumentu stwierdzającego tożsamość pacjenta: „{seria i numer innego dokumentu stwierdzającego tożsamość}”; W przypadku noworodka, dla którego znany jest identyfikator jednego z rodziców albo opiekuna prawnego: “{identyfikator będący konkatenacją wartości identyfikatora jednego z rodziców albo opiekuna prawnego, daty urodzenia noworodka oraz numeru kolejnego urodzenia (separatorem jest znak: ‘-‘)}”; W przypadku noworodka, dla którego nie jest znany identyfikator przedstawiciela ustawowego: “XXXXX-RRRR-NW” gdzie “XXXXX” oznacza kolejny numer przypisany do konkretnej osoby, a „RRRR" rok; W przypadku osoby o nieznanych danych: “XXXXX-RRRR-NN” gdzie “XXXXX” oznacza kolejny numer przypisany do konkretnej osoby, a „RRRR" rok.

Dane osobowe pacjenta

Nazwisko pacjenta. Przyjmuje wartość: '{Nazwisko pacjenta}'.

Imię pacjenta. Przyjmuje wartość: '{Imię pacjenta}'.

Uwaga: Jeżeli pacjent posiada kilka imion, to każde z tych imion należy podać w osobnym polu 'Patient.name.given', a nie należy podawać wszystkich imion w jednym polu 'Patient.name.given' oddzielonych spacjami. Kolejność imion nie ma znaczenia.

Dane kontaktowe pacjenta.

Rodzaj danych kontaktowych. Przyjmuje wartość: '{kod ze słownika PLContactPointSystem}'.

Rzeczywiste dane kontaktowe pacjenta. Przyjmuje wartość: '{dane kontaktowe pacjenta}'.

UWAGA: w przypadku numeru telefonu wymagane jest minimum 9 cyfr. Wymagany format numeru telefonu: +(numer kierunkowy kraju)XXXXXXXXX, gdzie X - cyfra np. +48602600600.

Płeć pacjenta. Przyjmuje wartość: '{kod ze słownika PLGender}'.

Data urodzenia pacjenta. Przyjmuje wartość: '{data urodzenia pacjenta}'.

Wskazanie na ciążę pojedynczą. Przyjmuje wartość: 'false'.

Element wymagany w przypadku kiedy pacjentem jest noworodek, w przypadku ciąży pojedynczej. W przypadku ciąży mnogiej element nie występuje (wymagana wartość “false”).

Informacja o numerze kolejnym urodzenia z ciąży mnogiej. Przyjmuje wartość: '{Numer kolejny urodzenia z ciąży mnogiej}'.

Element wymagany w przypadku kiedy pacjentem jest noworodek, w przypadku ciąży mnogiej. W przypadku ciąży pojedynczej element nie występuje.

Dane przedstawiciela ustawowego albo opiekuna faktycznego.

Dane kontaktowe przedstawiciela ustawowego albo opiekuna faktycznego.

Rodzaj danych kontaktowych przedstawiciela ustawowego albo opiekuna faktycznego. Przyjmuje wartość: '{Kod ze słownika PLContactPointSystem}'.

Dane kontaktowe przedstawiciela ustawowego albo opiekuna faktycznego.

Zasób zawierający dane osobowe i kontaktowe pacjenta.

Identyfikator logiczny zasobu nadawany przez system w ramach rejestracji zasobu. Przyjmuje wartość: '{liczba naturalna}'

Nadany identyfikator nie podlega aktualizacji. W ramach aktualizacji zasobu należy wskazać wartość identyfikatora zasobu, którego dotyczy aktualizacja.

Metadane zasobu

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Wersja zasobu ustawiana przez system. Przyjmuje wartość: '{liczba naturalna}'.

W przypadku, jeśli ilość wersji zasobu Patient przekroczy założony limit zgodnie z regułą REG.WER.7164, błąd HTTP 422 nie zostanie zwrócony, natomiast zostanie zwrócony kod odpowiedzi HTTP 200 oraz ostatnia aktualna wersja zasobu Patient.

Data aktualizacji zasobu ustawiana przez system. Przyjmuje wartość: '{Data i czas w formacie YYYY-MM-DDThh:mm:ss.sss+zz:zz}'.

W ramach rejestracji pierwszej wersji zasobu jest to data rejestracji zasobu, w ramach rejestracji kolejnych wersji zasobu jest to data ostatniej aktualizacji zasobu.

Identyfikator źródła zasobu ustawiany przez system.

In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used.

This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.

Url profilu wg. którego zasób jest walidowany: https://ezdrowie.gov.pl/fhir/StructureDefinition/PLPatient.

It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.

Poziom poufności zasobu.

The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.

Security Labels from the Healthcare Privacy and Security Classification System.

System kodowania poziomów poufności. Przyjmuje wartość: '{urn:oid:2.16.840.1.113883.3.4424.11.1.83}'

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

Kod poziomu poufności. Przyjmuje wartość: '{kod ze słownika PLSecurityLabels}'

Need to refer to a particular code in the system.

Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.

The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.

Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".

Wersja systemu ustawiana przez system.

Wartość wskazuje na wersję systemu w momencie rejestracji/aktualizacji zasobu.

The base language in which the resource is written.

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

A human language.

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.

Contained resources do not have 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.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

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.

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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identyfikator biznesowy pacjenta.

Przyjmuje się, że pacjent identyfikowany jest przez osobisty numer identyfikacyjny, seria i numer dowodu osobistego, seria i numer paszportu, niepowtarzalny identyfikator nadany przez państwo członkowskie Unii Europejskiej dla celów transgranicznej identyfikacji, o którym mowa w rozporządzeniu wykonawczym Komisji (UE) 2015/1501 z dnia 8 września 2015 r. w sprawie ram interoperacyjności na podstawie art. 12 ust. 8 rozporządzenia Parlamentu Europejskiego i Rady (UE) nr 910/2014 z dnia 23 lipca 2014 r. w sprawie identyfikacji elektronicznej i usług zaufania w odniesieniu do transakcji elektronicznych na rynku wewnętrznym oraz uchylające dyrektywę 1999/93/WE (Dz. Urz. UE L 257 z 28. 8.2014, str. 74, z późn. zm), nazwa, seria i numer innego dokumentu stwierdzającego tożsamość, numer nadany według formatu: XXXXX-RRRR-NN, gdzie XXXXX - kolejny unikalny numer osoby w ramach kodu identyfikatora i roku RRRR – rok. W przypadku noworodka, identyfikowany jest on poprzez wskazanie identyfikatora jednego z rodziców albo opiekuna prawnego wraz z informacją o dacie urodzenia noworodka oraz numerem kolejnego urodzenia z ciąży mnogiej. W przypadku kiedy identyfikator przedstawiciela ustawowego nie jest możliwy do ustalenia, identyfikatorem noworodka jest numer wg formatu: XXXXX-RRRR-NW, gdzie XXXXX - kolejny unikalny numer osoby w ramach kodu identyfikatora i roku RRRR – rok.

Patients are almost always assigned specific numerical identifiers.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

OID systemu identyfikacji, w ramach którego nadany został nadany identyfikator. Przyjmuje wartość: W przypadku PESEL: “urn:oid:2.16.840.1.113883.3.4424.1.1.616”; W przypadku paszportu: “urn:oid:2.16.840.1.113883.4.330.{kod kraju}”; W przypadku innego dokumentu stwierdzającego tożsamość pacjenta: “urn:oid:{OID rodzaju dokumentu tożsamości}”; W przypadku noworodka, dla którego znany jest identyfikator jednego z rodziców albo opiekuna prawnego: “urn:oid:{zgodnie z listą rozszerzeń drzewa OID, gałąź od węzła 2.16.840.1.113883.3.4424.1.7}”; W przypadku noworodka, dla którego nie jest znany identyfikator przedstawiciela ustawowego: “urn:oid:2.16.840.1.113883.3.4424.2.7.{x}.17.3” gdzie “x” identyfikuje Usługodawcę; W przypadku osoby o nieznanych danych: “urn:oid:2.16.840.1.113883.3.4424.2.7.{x}.17.2” gdzie “x” identyfikuje Usługodawcę.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

Identyfikator pacjenta. Przyjmuje wartość: W przypadku PESEL: “{PESEL pacjenta}”; W przypadku paszportu: “{seria i numer paszportu}”; W przypadku innego dokumentu stwierdzającego tożsamość pacjenta: „{seria i numer innego dokumentu stwierdzającego tożsamość}”; W przypadku noworodka, dla którego znany jest identyfikator jednego z rodziców albo opiekuna prawnego: “{identyfikator będący konkatenacją wartości identyfikatora jednego z rodziców albo opiekuna prawnego, daty urodzenia noworodka oraz numeru kolejnego urodzenia (separatorem jest znak: ‘-‘)}”; W przypadku noworodka, dla którego nie jest znany identyfikator przedstawiciela ustawowego: “XXXXX-RRRR-NW” gdzie “XXXXX” oznacza kolejny numer przypisany do konkretnej osoby, a „RRRR" rok; W przypadku osoby o nieznanych danych: “XXXXX-RRRR-NN” gdzie “XXXXX” oznacza kolejny numer przypisany do konkretnej osoby, a „RRRR" rok.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

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.

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

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

Dane osobowe pacjenta

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.

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

Identifies the purpose for this name.

Applications can assume that a name is current unless it explicitly says that it is temporary or old.

The use of a human name.

Allows the appropriate name for a particular context of use to be selected from among a set of names.

Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

Nazwisko pacjenta. Przyjmuje wartość: '{Nazwisko pacjenta}'.

Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).

Imię pacjenta. Przyjmuje wartość: '{Imię pacjenta}'.

Uwaga: Jeżeli pacjent posiada kilka imion, to każde z tych imion należy podać w osobnym polu 'Patient.name.given', a nie należy podawać wszystkich imion w jednym polu 'Patient.name.given' oddzielonych spacjami. Kolejność imion nie ma znaczenia.

Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.

Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.

Indicates the period of time when this name was valid for the named person.

Allows names to be placed in historical context.

Dane kontaktowe pacjenta.

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

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

Rodzaj danych kontaktowych. Przyjmuje wartość: '{kod ze słownika PLContactPointSystem}'.

Telecommunications form for contact point.

Rzeczywiste dane kontaktowe pacjenta. Przyjmuje wartość: '{dane kontaktowe pacjenta}'.

UWAGA: w przypadku numeru telefonu wymagane jest minimum 9 cyfr. Wymagany format numeru telefonu: +(numer kierunkowy kraju)XXXXXXXXX, gdzie X - cyfra np. +48602600600.

Need to support legacy numbers that are not in a tightly controlled format.

Identifies the purpose for the contact point.

Applications can assume that a contact is current unless it explicitly says that it is temporary or old.

Use of contact point.

Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.

Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.

Note that rank does not necessarily follow the order in which the contacts are represented in the instance.

Time period when the contact point was/is in use.

Płeć pacjenta. Przyjmuje wartość: '{kod ze słownika PLGender}'.

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 gender of a person used for administrative purposes.

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

Data urodzenia pacjenta. Przyjmuje wartość: '{data urodzenia pacjenta}'.

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 maternity/infant care systems).

Age of the individual drives many clinical processes.

Indicates if the individual is deceased or not.

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.

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.

An address for the individual.

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

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

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

The domestic partnership status of a person.

Most, if not all systems capture it.

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

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

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

Wskazanie na ciążę pojedynczą. Przyjmuje wartość: 'false'.

Element wymagany w przypadku kiedy pacjentem jest noworodek, w przypadku ciąży pojedynczej. W przypadku ciąży mnogiej element nie występuje (wymagana wartość “false”).

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

Informacja o numerze kolejnym urodzenia z ciąży mnogiej. Przyjmuje wartość: '{Numer kolejny urodzenia z ciąży mnogiej}'.

Element wymagany w przypadku kiedy pacjentem jest noworodek, w przypadku ciąży mnogiej. W przypadku ciąży pojedynczej element nie występuje.

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

Image of the patient.

Guidelines:

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

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

Dane przedstawiciela ustawowego albo opiekuna faktycznego.

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.

Need to track people you can contact about the patient.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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. 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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

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

The nature of the relationship between a patient and a contact person for that patient.

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

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.

Dane kontaktowe przedstawiciela ustawowego albo opiekuna faktycznego.

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.

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

Rodzaj danych kontaktowych przedstawiciela ustawowego albo opiekuna faktycznego. Przyjmuje wartość: '{Kod ze słownika PLContactPointSystem}'.

Telecommunications form for contact point.

Dane kontaktowe przedstawiciela ustawowego albo opiekuna faktycznego.

Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.

Need to support legacy numbers that are not in a tightly controlled format.

Identifies the purpose for the contact point.

Applications can assume that a contact is current unless it explicitly says that it is temporary or old.

Use of contact point.

Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.

Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.

Note that rank does not necessarily follow the order in which the contacts are represented in the instance.

Time period when the contact point was/is in use.

Address for the contact person.

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.

The gender of a person used for administrative 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 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.

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.

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.

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

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

Link to another patient resource that concerns the same actual patient.

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

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.

Zasób zawierający dane osobowe i kontaktowe pacjenta.

Identyfikator logiczny zasobu nadawany przez system w ramach rejestracji zasobu. Przyjmuje wartość: '{liczba naturalna}'

Nadany identyfikator nie podlega aktualizacji. W ramach aktualizacji zasobu należy wskazać wartość identyfikatora zasobu, którego dotyczy aktualizacja.

Metadane zasobu

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.

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.

Wersja zasobu ustawiana przez system. Przyjmuje wartość: '{liczba naturalna}'.

W przypadku, jeśli ilość wersji zasobu Patient przekroczy założony limit zgodnie z regułą REG.WER.7164, błąd HTTP 422 nie zostanie zwrócony, natomiast zostanie zwrócony kod odpowiedzi HTTP 200 oraz ostatnia aktualna wersja zasobu Patient.

Data aktualizacji zasobu ustawiana przez system. Przyjmuje wartość: '{Data i czas w formacie YYYY-MM-DDThh:mm:ss.sss+zz:zz}'.

W ramach rejestracji pierwszej wersji zasobu jest to data rejestracji zasobu, w ramach rejestracji kolejnych wersji zasobu jest to data ostatniej aktualizacji zasobu.

Identyfikator źródła zasobu ustawiany przez system.

In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used.

This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.

Url profilu wg. którego zasób jest walidowany: https://ezdrowie.gov.pl/fhir/StructureDefinition/PLPatient.

It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.

Poziom poufności zasobu.

The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.

Security Labels from the Healthcare Privacy and Security Classification System.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.

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.

System kodowania poziomów poufności. Przyjmuje wartość: '{urn:oid:2.16.840.1.113883.3.4424.11.1.83}'

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

Kod poziomu poufności. Przyjmuje wartość: '{kod ze słownika PLSecurityLabels}'

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.

The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.

Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".

Wersja systemu ustawiana przez system.

Wartość wskazuje na wersję systemu w momencie rejestracji/aktualizacji zasobu.

The base language in which the resource is written.

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

A human language.

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.

Contained resources do not have 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.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

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.

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

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.

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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, 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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identyfikator biznesowy pacjenta.

Przyjmuje się, że pacjent identyfikowany jest przez osobisty numer identyfikacyjny, seria i numer dowodu osobistego, seria i numer paszportu, niepowtarzalny identyfikator nadany przez państwo członkowskie Unii Europejskiej dla celów transgranicznej identyfikacji, o którym mowa w rozporządzeniu wykonawczym Komisji (UE) 2015/1501 z dnia 8 września 2015 r. w sprawie ram interoperacyjności na podstawie art. 12 ust. 8 rozporządzenia Parlamentu Europejskiego i Rady (UE) nr 910/2014 z dnia 23 lipca 2014 r. w sprawie identyfikacji elektronicznej i usług zaufania w odniesieniu do transakcji elektronicznych na rynku wewnętrznym oraz uchylające dyrektywę 1999/93/WE (Dz. Urz. UE L 257 z 28. 8.2014, str. 74, z późn. zm), nazwa, seria i numer innego dokumentu stwierdzającego tożsamość, numer nadany według formatu: XXXXX-RRRR-NN, gdzie XXXXX - kolejny unikalny numer osoby w ramach kodu identyfikatora i roku RRRR – rok. W przypadku noworodka, identyfikowany jest on poprzez wskazanie identyfikatora jednego z rodziców albo opiekuna prawnego wraz z informacją o dacie urodzenia noworodka oraz numerem kolejnego urodzenia z ciąży mnogiej. W przypadku kiedy identyfikator przedstawiciela ustawowego nie jest możliwy do ustalenia, identyfikatorem noworodka jest numer wg formatu: XXXXX-RRRR-NW, gdzie XXXXX - kolejny unikalny numer osoby w ramach kodu identyfikatora i roku RRRR – rok.

Patients are almost always assigned specific numerical identifiers.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.

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.

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

OID systemu identyfikacji, w ramach którego nadany został nadany identyfikator. Przyjmuje wartość: W przypadku PESEL: “urn:oid:2.16.840.1.113883.3.4424.1.1.616”; W przypadku paszportu: “urn:oid:2.16.840.1.113883.4.330.{kod kraju}”; W przypadku innego dokumentu stwierdzającego tożsamość pacjenta: “urn:oid:{OID rodzaju dokumentu tożsamości}”; W przypadku noworodka, dla którego znany jest identyfikator jednego z rodziców albo opiekuna prawnego: “urn:oid:{zgodnie z listą rozszerzeń drzewa OID, gałąź od węzła 2.16.840.1.113883.3.4424.1.7}”; W przypadku noworodka, dla którego nie jest znany identyfikator przedstawiciela ustawowego: “urn:oid:2.16.840.1.113883.3.4424.2.7.{x}.17.3” gdzie “x” identyfikuje Usługodawcę; W przypadku osoby o nieznanych danych: “urn:oid:2.16.840.1.113883.3.4424.2.7.{x}.17.2” gdzie “x” identyfikuje Usługodawcę.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

Identyfikator pacjenta. Przyjmuje wartość: W przypadku PESEL: “{PESEL pacjenta}”; W przypadku paszportu: “{seria i numer paszportu}”; W przypadku innego dokumentu stwierdzającego tożsamość pacjenta: „{seria i numer innego dokumentu stwierdzającego tożsamość}”; W przypadku noworodka, dla którego znany jest identyfikator jednego z rodziców albo opiekuna prawnego: “{identyfikator będący konkatenacją wartości identyfikatora jednego z rodziców albo opiekuna prawnego, daty urodzenia noworodka oraz numeru kolejnego urodzenia (separatorem jest znak: ‘-‘)}”; W przypadku noworodka, dla którego nie jest znany identyfikator przedstawiciela ustawowego: “XXXXX-RRRR-NW” gdzie “XXXXX” oznacza kolejny numer przypisany do konkretnej osoby, a „RRRR" rok; W przypadku osoby o nieznanych danych: “XXXXX-RRRR-NN” gdzie “XXXXX” oznacza kolejny numer przypisany do konkretnej osoby, a „RRRR" rok.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

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.

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

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

Dane osobowe pacjenta

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.

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

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.

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.

Identifies the purpose for this name.

Applications can assume that a name is current unless it explicitly says that it is temporary or old.

The use of a human name.

Allows the appropriate name for a particular context of use to be selected from among a set of names.

Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

Nazwisko pacjenta. Przyjmuje wartość: '{Nazwisko pacjenta}'.

Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).

Imię pacjenta. Przyjmuje wartość: '{Imię pacjenta}'.

Uwaga: Jeżeli pacjent posiada kilka imion, to każde z tych imion należy podać w osobnym polu 'Patient.name.given', a nie należy podawać wszystkich imion w jednym polu 'Patient.name.given' oddzielonych spacjami. Kolejność imion nie ma znaczenia.

Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.

Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.

Indicates the period of time when this name was valid for the named person.

Allows names to be placed in historical context.

Dane kontaktowe pacjenta.

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

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

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.

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.

Rodzaj danych kontaktowych. Przyjmuje wartość: '{kod ze słownika PLContactPointSystem}'.

Telecommunications form for contact point.

Rzeczywiste dane kontaktowe pacjenta. Przyjmuje wartość: '{dane kontaktowe pacjenta}'.

UWAGA: w przypadku numeru telefonu wymagane jest minimum 9 cyfr. Wymagany format numeru telefonu: +(numer kierunkowy kraju)XXXXXXXXX, gdzie X - cyfra np. +48602600600.

Need to support legacy numbers that are not in a tightly controlled format.

Identifies the purpose for the contact point.

Applications can assume that a contact is current unless it explicitly says that it is temporary or old.

Use of contact point.

Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.

Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.

Note that rank does not necessarily follow the order in which the contacts are represented in the instance.

Time period when the contact point was/is in use.

Płeć pacjenta. Przyjmuje wartość: '{kod ze słownika PLGender}'.

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 gender of a person used for administrative purposes.

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

Data urodzenia pacjenta. Przyjmuje wartość: '{data urodzenia pacjenta}'.

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 maternity/infant care systems).

Age of the individual drives many clinical processes.

Indicates if the individual is deceased or not.

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.

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.

An address for the individual.

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

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

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

The domestic partnership status of a person.

Most, if not all systems capture it.

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

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

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

Wskazanie na ciążę pojedynczą. Przyjmuje wartość: 'false'.

Element wymagany w przypadku kiedy pacjentem jest noworodek, w przypadku ciąży pojedynczej. W przypadku ciąży mnogiej element nie występuje (wymagana wartość “false”).

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

Informacja o numerze kolejnym urodzenia z ciąży mnogiej. Przyjmuje wartość: '{Numer kolejny urodzenia z ciąży mnogiej}'.

Element wymagany w przypadku kiedy pacjentem jest noworodek, w przypadku ciąży mnogiej. W przypadku ciąży pojedynczej element nie występuje.

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

Image of the patient.

Guidelines:

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

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

Dane przedstawiciela ustawowego albo opiekuna faktycznego.