Identyfikator logiczny zasobu nadawany przez system w ramach rejestracji zasobu.

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.

Data aktualizacji zasobu ustawiana przez system.

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 - automatycznie ustawiany przez serwer, przy rejestracji lub aktualizacji zasobu.

Profil według którego zasób jest walidowany.

Poziom poufności danych.

System kodowania poziomów poufności danych.

Kod poziomu poufności danych.

Numer wersji aplikacji - automatycznie ustawiany przy rejestracji lub aktualizacji zasobu.

OID systemu identyfikacji Zdarzeń Medycznych w kontekście Usługodawcy.

Identyfikator Zdarzenia Medycznego w systemie identyfikacji.

Status Zdarzenia Medycznego.

Dane o przepustce Pacjenta.

Status Zdarzenia Medycznego wskazujący na przepustkę. Wymagany onleave

Okres obowiązywania przepustki.

Termin rozpoczęcia okresu przepustki.

Termin zakończenia okresu przepustki.

Klasyfikacja statystyczna Zdarzenia Medycznego.

OID systemu kodowania typów Zdarzeń Medycznych. Wymagany zbiór wartości utworzony na podstawie kodów jednostek statystycznych świadczeń (Załącznik nr 1), która znajduje się w Dzienniku Ustaw, dostępnym pod linkiem: http://prawo.sejm.gov.pl/isap.nsf/download.xsp/WDU20190002532/O/D20192532.pdf.

Kod typu Zdarzenia Medycznego w systemie kodowania.

Opis typu Zdarzenia Medycznego odpowiadający wartości kodu.

Zakres porady. Wartości zgodnie ze słownikiem typów i kodów porad pielęgniarek i położnych publikowanym przez NFZ (wersja 1.01 słownika dostępna pod adresem https://slowniki.nfz.gov.pl/PoradyPoz/Slownik/4794)..

Zakres porady w systemie kodowania.

Słownik kodowania zakresów porady wskazany przez NFZ.

Wersja słownika NFZ.

Kod zakresu porady.

Pacjent.

Ubezpieczenie pokrywające koszty świadczeń realizowanych w ramach Zdarzenia Medycznego.

Dane ubezpieczenia pokrywającego koszty świadczeń realizowanych w ramach Zdarzenia Medycznego.

Identyfikator ubezpieczenia.

OID systemu identyfikacji ubezpieczenia.

Identyfikator ubezpieczenia w systemie identyfikacji.

Identyfikator Pacjenta.

OID systemu identyfikacji Pacjenta.

Identyfikator Pacjenta.

Identyfikator korelacyjny wykorzystywany do wskazania powiązania między jednym bądź wieloma zdarzeniami medycznymi składającymi się na część danego etapu leczenia czy też korelowania zdarzeń w ramach jednego problemu zdrowotnego.

Identyfikator korelacyjny.

OID systemu identyfikacji korelacji.

Identyfikator korelacyjny w systemie identyfikacji.

Skierowanie/Zlecenie, które zainicjowało Zdarzenie medyczne.

Placówka wystawiająca zlecenie/skierowanie.

Identyfikator Miejsca Udzielania Świadczeń (placówki wystawiającej zlecenie/skierowanie).

OID systemu identyfikacji Miejsca Udzielania Świadczeń.

Identyfikator Miejsca Udzielania Świadczeń.

Identyfikator skierowania/zlecenia nadany w placówce wystawiającej.

OID systemu identyfikacji dokumentu skierowania/zlecenia.

Identyfikator dokumentu skierowania/zlecenia.

Data wystawienia skierowania/zlecenia.

Data wystawienia skierowania/zlecenia.

Dane pracownika medycznego udzielającego świadczenia zdrowotnego lub odpowiedzialnego za jego udzielenie, a w przypadku wykonania operacji lub zabiegu w oddziale szpitalnym – dane pracownika medycznego kierującego wykonaniem tej operacji albo zabiegu (operatora). W przypadku gdy jest to wyjazd ratowniczy albo akcja ratownicza dane wszystkich osób wchodzących w skład zespołu ratownictwa medycznego uprawnionych do wykonywania medycznych czynności ratunkowych.

Przynależność do danej grupy zawodowej określony zgodnie z tabelą nr 1 załącznika nr 3 do rozporządzenia w sprawie zakresu niezbędnych informacji.

Przynależność Pracownika Medycznego do danej grupy zawodowej w systemie kodowania.

System kodowania przynależności Pracownika Medycznego do danej grupy zawodowej.

Kod przynależności Pracownika Medycznego do danej grupy zawodowej w systemie kodowania.

Rola pracownika medycznego w Zdarzeniu Medycznym. Wymagana dla wskazania kierownika zespołu ratownictwa medycznego. W innych przypadkach atrybut nie występuje.

Rola pracownika medycznego w systemie kodowania.

System kodowania ról pracowników medycznych.

Kod roli pracownika medycznego w systemie kodowania.

Nazwa roli pracownika medycznego.

Dane Pracownika Medycznego.

Identyfikator Pracownika Medycznego.

OID systemu identyfikacji Pracownika Medycznego.

Identyfikator Pracownika Medycznego.

Data początku i końca Zdarzenia Medycznego. Dla zdarzeń medycznych innych niż hospitalizacja atrybut określa okres realizacji świadczeń w Miejscu Udzielania Świadczeń podanym w Encounter.location.location.

Termin rozpoczęcia Zdarzenia Medycznego

Termin zakończenia Zdarzenia Medycznego.

Dane dotyczące hospitalizacji.

Tryb przyjęcia.

Tryb przyjęcia w systemie kodowania.

System kodowania trybów przyjęć.

Kod trybu przyjęcia w systemie kodowania.

Kody trybu wypisu usługobiorcy ze szpitala muszą być zgodne z aktualnie obowiązującymi przepisami w tym zakresie określonymi w rozporządzeniu Ministra Zdrowia. Obecnie obowiązuje rozporządzenie Ministra Zdrowia z dnia 26 czerwca 2019 r. w sprawie zakresu niezbędnych informacji przetwarzanych przez świadczeniodawców, szczegółowego sposobu rejestrowania tych informacji oraz ich przekazywania podmiotom zobowiązanym do finansowania świadczeń ze środków publicznych (Dz. U. z 2019 r., poz. 1207, z poźn. zm.)

Tryb wypisu w systemie kodowania.

OID systemu kodowania trybów wypisu.

Kod trybu wypisu w systemie kodowania.

Miejsce Udzielania Świadczeń.

Dane miejsca Udzielania Świadczeń.

Identyfikator Miejsca Udzielania Świadczeń.

OID systemu identyfikacji Miejsca Udzielania Świadczeń.

Identyfikator Miejsca Udzielania Świadczeń w systemie identyfikacji.

Okres realizacji świadczeń w Miejscu Udzielania Świadczeń. Okres realizacji świadczeń w danym MUŚ musi być podany w przypadku hospitalizacji. Dla zdarzeń medycznych innych niż hospitalizacja okres realizacji świadczeń w MUŚ będzie identyfikowany na podstawie atrybutu Encounter.period.

Termin rozpoczęcia realizacji świadczeń w Miejscu Udzielania Świadczeń.

Termin zakończenia realizacji świadczenia w Miejscu Udzielania Świadczeń.

Usługodawca (praktyka lekarska/pielęgniarska/fizjoterapeutyczna, podmiot leczniczy) rejestrujący zdarzenie.

Dane płatnika.

Identyfikator płatnika.

OID systemu identyfikacji Płatnika.

Identyfikator płatnika w systemie identyfikacji.

Umowa z NFZ.

Identyfikator umowy NFZ.

OID systemu identyfikacji umowy NFZ.

Identyfikator umowy NFZ w systemie identyfikacji.

Numer REGON zakładu leczniczego.

Numer REGON zakładu leczniczego, w systemie identyfikacji.

OID systemu identyfikacji 14-sto znakowego numeru REGON

14-znakowy numer REGON zakładu leczniczego, w którym udzielono świadczenia zdrowotnego.

Identyfikator Usługodawcy.

OID systemu identyfikacji Usługodawcy

Identyfikator Usługodawcy w systemie identyfikacji.

An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.

Identyfikator logiczny zasobu nadawany przez system w ramach rejestracji zasobu.

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.

An Extension

Wersja zasobu ustawiana przez system.

The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.

Data aktualizacji zasobu ustawiana przez system.

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 - automatycznie ustawiany przez serwer, przy rejestracji lub aktualizacji zasobu.

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.

Profil według którego zasób jest walidowany.

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

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.

An Extension

System kodowania poziomów poufności danych.

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

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

Numer wersji aplikacji - automatycznie ustawiany przy rejestracji lub aktualizacji zasobu.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

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.

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.

Identifier(s) by which this encounter is known.

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 Zdarzeń Medycznych w kontekście Usługodawcy.

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 Zdarzenia Medycznego w systemie identyfikacji.

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.

Status Zdarzenia Medycznego.

Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

Current state of the encounter.

Dane o przepustce Pacjenta.

The current status is always found in the current version of the resource, not the status history.

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.

Status Zdarzenia Medycznego wskazujący na przepustkę. Wymagany onleave

Current state of the encounter.

Okres obowiązywania przepustki.

Termin rozpoczęcia okresu przepustki.

If the low element is missing, the meaning is that the low boundary is not known.

Termin zakończenia okresu przepustki.

The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.

Klasyfikacja statystyczna Zdarzenia Medycznego.

Classification of the encounter.

OID systemu kodowania typów Zdarzeń Medycznych. Wymagany zbiór wartości utworzony na podstawie kodów jednostek statystycznych świadczeń (Załącznik nr 1), która znajduje się w Dzienniku Ustaw, dostępnym pod linkiem: http://prawo.sejm.gov.pl/isap.nsf/download.xsp/WDU20190002532/O/D20192532.pdf.

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 typu Zdarzenia Medycznego w systemie kodowania.

Need to refer to a particular code in the system.

Opis typu Zdarzenia Medycznego odpowiadający wartości kodu.

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.

The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient.

Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).

Since there are many ways to further classify encounters, this element is 0..*.

The type of encounter.

Zakres porady. Wartości zgodnie ze słownikiem typów i kodów porad pielęgniarek i położnych publikowanym przez NFZ (wersja 1.01 słownika dostępna pod adresem https://slowniki.nfz.gov.pl/PoradyPoz/Slownik/4794)..

Broad categorization of the service that is to be provided.

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

Zakres porady w systemie kodowania.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

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

Słownik kodowania zakresów porady wskazany przez NFZ.

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.

Wersja słownika NFZ.

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

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.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Indicates the urgency of the encounter.

Indicates the urgency of the encounter.

Pacjent.

While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).

Ubezpieczenie pokrywające koszty świadczeń realizowanych w ramach Zdarzenia Medycznego.

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Dane ubezpieczenia pokrywającego koszty świadczeń realizowanych w ramach Zdarzenia Medycznego.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Aa resource (or, for logical models, the URI of the logical model).

Identyfikator ubezpieczenia.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

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

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 ubezpieczenia w systemie identyfikacji.

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.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Aa resource (or, for logical models, the URI of the logical model).

Identyfikator Pacjenta.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

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

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.

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.