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.

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

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.

Wersja systemu ustawiana przez system.

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

Referencja przyjmuje wartość: CarePlan/x gdzie x oznacza identyfikator zasobu CarePlan z (CarePlan.id).

Status świadczenia

Kod typu świadczenia. Przyjmuje wartość: phc (świadczenie realizowane w ramach POZ) | amb (świadczenie realizowane w ramach AOS) | imp (świadczenie realizowane w szpitalu)

Referencja do zasobu z danymi pacjenta. Przyjmuje wartość: https://ezdrowie.gov.pl/zm/fhir/Patient/x gdzie x oznacza identyfikator zasobu Patient (Patient.id) z danymi pacjenta.

Typ zasobu z danymi pacjenta. Przyjmuje wartość: Patient.

Nazwisko pracownika medycznego.

Nazwisko pracownika medycznego

Imiona pracownika medycznego.

pracownika medycznego.

Referencja przyjmuje wartość: PractitionerRole/x gdzie x oznacza identyfikator zasobu PractitionerRole z (PractitionerRole.id).

Kod techniczny miejsca udzielania świadczeń

Kod techniczny

Identyfikator miejsce udzielenia świadczenia.

OID systemu identyfikacji Miejsca Udzielania Świadczeń. Przyjmuje wartość: Dla jednostki organizacyjnej: “urn:oid:2.16.840.1.113883.3.4424.2.3.2”; Dla komórki organizacyjnej: “urn:oid:2.16.840.1.113883.3.4424.2.3.3”; Dla praktyki lekarskiej: “urn:oid:2.16.840.1.113883.3.4424.2.4.{xx}.1” gdzie “xx” identyfikuje izbę lekarską; Dla praktyki pielęgniarskiej: “urn:oid:2.16.840.1.113883.3.4424.2.5.{x(x)}.1”; gdzie “x(x)” identyfikuje izbę pielęgniarek i położnych realizującą wpis Dla praktyki fizjoterapeutycznej: “urn:oid:2.16.840.1.113883.3.4424.2.9.1.1”.

Identyfikator Miejsca Udzielania Świadczeń. Przyjmuje wartość: Dla jednostki organizacyjnej: "{cz. I kodu resortowego}-{cz. V kodu resortowego}”; Dla komórki organizacyjnej: "{cz. I kodu resortowego}-{cz. VII kodu resortowego}”; Dla praktyki lekarskiej/pielęgniarskiej/fizjoterapeutycznej: “{Numer księgi rejestrowej w rejestrze podmiotów wykonujących działalność leczniczą}-{3-cyfrowy identyfikator Miejsca Udzielania Świadczeń}” .

Nazwa Miejsca Udzielania Świadczeń

Identyfikator umowy NFZ

Identyfikator umowy NFZ

Przyjmuje wartość: uri: ‘urn:oid:2.16.840.1.113883.3.4424.8.6.{x}.{y}‘ gdzie ‘x‘ identyfikuje rodzaj umowy: Numery umów świadczeniodawców z NFZ zawierane w oddziale: ‘urn:oid:2.16.840.1.113883.3.4424.8.6.1.{y}‘ Numery umów lekarzy z NFZ zawierane w oddziale: ‘urn:oid:2.16.840.1.113883.3.4424.8.6.2.{y}‘ gdzie ‘y‘ identyfikuje oddział NFZ: np. numery umów świadczeniodawców z NFZ zawierane w oddziale Łódzkim (5) ‘urn:oid:2.16.840.1.113883.3.4424.8.6.1.5‘

Numer umowy NFZ

Oddział Wojewódzki NFZ

Oddział Wojewódzki NFZ

Kod OW NFZ

Nazwa OW NFZ odpowiadająca kodowi

OID systemu identyfikacji świadczeniodawcy. Przyjmuje wartość: Dla podmiotu leczniczego: "urn:oid:2.16.840.1.113883.3.4424.2.3.1”; Dla praktyki lekarskiej: “urn:oid:2.16.840.1.113883.3.4424.2.4.{xx}” gdzie “xx” identyfikuje izbę lekarską realizującą wpis; Dla praktyki pielęgniarskiej: “urn:oid:2.16.840.1.113883.3.4424.2.5.{x(x)}”; gdzie “x(x)” identyfikuje izbę pielęgniarek i położnych realizującą wpis Dla praktyki fizjoterapeutycznej: “urn:oid:2.16.840.1.113883.3.4424.2.9.1”.

Identyfikator świadczeniodawcy Przyjmuje wartość: Dla podmiotu leczniczego: "{cz. I kodu resortowego}”; Dla praktyki lekarskiej/pielęgniarskiej/fizjoterapeutycznej: "{numer księgi rejestrowej w rejestrze podmiotów wykonujących działalność leczniczą}”.

Nazwa świadczeniodawcy

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. Przyjmuje wartość: '{liczba naturalna}'

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

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

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. Przyjmuje wartość: '{liczba naturalna}'.

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

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.

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.

An Extension

Rozszerzenie zasobu zawierające referencję do zasobu CarePlan

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

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.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

Referencja przyjmuje wartość: CarePlan/x gdzie x oznacza identyfikator zasobu CarePlan z (CarePlan.id).

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

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

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

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.

Rozszerzenie zawierające dane o przyczynie aktualnego statusu

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.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

A reference to a code defined by a terminology system.

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.

An Extension

The identification of the code system that defines the meaning of the symbol in the code.

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.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

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.

An Extension

Identifier(s) by which this encounter is known.

Status świadczenia

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

The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.

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

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

An Extension

Rozszerzenie zawierające dane o przyczynie aktualnego statusu

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.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

A reference to a code defined by a terminology system.

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.

An Extension

The identification of the code system that defines the meaning of the symbol in the code.

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.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

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.

An Extension

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

The time that the episode was in the specified status.

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

An Extension

The start of the period. The boundary is inclusive.

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

The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

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.

Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.

An Extension

The identification of the code system that defines the meaning of the symbol in the code.

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 świadczenia. Przyjmuje wartość: phc (świadczenie realizowane w ramach POZ) | amb (świadczenie realizowane w ramach AOS) | imp (świadczenie realizowane w szpitalu)

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.

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.

Broad categorization of the service that is to be provided (e.g. cardiology).

Broad categorization of the service that is to be provided.

Indicates the urgency of the encounter.

Indicates the urgency of the encounter.