NVD FHIR API integrācijas apraksts

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.

©NHS: Value SHALL NOT be provided in CREATE and UPDATE requests. It is only available in READ response.

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.

When the resource last changed - e.g. when the version changed.

©NHS: Value SHALL NOT be provided in CREATE and UPDATE requests. It is only available in READ response.

This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.

A uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.

©NHS: Value SHALL NOT be provided in CREATE and UPDATE requests. It is only available in READ response when required by business.

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.

A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url.

©NHS: Profile SHALL be provided.

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.

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

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

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

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.

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

©NHS: ConceptCode from VVIS 1.3.6.1.4.1.38760.2.23 (Organization.identifier:medicalInstitutionIdentifier.value) is expected. Code SHALL be identical to "VIAuthorityCode" in JWT.

Need to refer to a particular code in the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

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

©NHS: ConceptCode displayText from VVIS 1.3.6.1.4.1.38760.2.23 (Organization.name) is expected. DisplayText SHALL be identical to "AuthorityFullName" in JWT.

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

Note that FHIR strings SHALL NOT exceed 1MB in size

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

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

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

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.

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

©NHS: Property id=4 from VVIS 1.3.6.1.4.1.38760.2.1 (Practitioner.identifier:HealthInspectorateIdentifier.value where system=1.3.6.1.4.1.38760.3.1.4) is expected. When provided SHALL be validated aigainst JWT VIMedicalCode.

Need to refer to a particular code in the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

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

©NHS: ConceptCode displayText from VVIS 1.3.6.1.4.1.38760.2.1 (Practitioner.name.text) is expected. Value SHALL be identical to displayText from VVIS 1.3.6.1.4.1.38760.2.1 (Practitioner.name.text) at the request time.

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

Note that FHIR strings SHALL NOT exceed 1MB in size

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

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

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

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.

©NHS: Health professional or patient personal identity number is expected.

Need to refer to a particular code in the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

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

©NHS: Person given and family name are expected.

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

Note that FHIR strings SHALL NOT exceed 1MB in size

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

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

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

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.

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

©NHS: Information system code from VVIS 1.3.6.1.4.1.38760.2.3 is expected. Code SHALL be identical to classifier code on the request dateTime.

Need to refer to a particular code in the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

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

©NHS: Information system code displayText from VVIS 1.3.6.1.4.1.38760.2.3 is expected. DisplayText SHALL be identical to classifier code displayText on the request dateTime.

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

Note that FHIR strings SHALL NOT exceed 1MB in size

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

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

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

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.

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

©NHS: Code from VVIS 1.3.6.1.4.1.38760.2.37 (PractitionerRole.identifier.value) is expected. Code SHALL be identical to "sub": "...-1.3.6.1.4.1.38760.2.37:ConceptCode" in JWT when medical person workplace is used for authorization in the VVIS.

Need to refer to a particular code in the system.

Note that FHIR strings SHALL NOT exceed 1MB in size

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

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

IETF language tag

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.

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

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

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

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

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

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

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

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

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.

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.

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

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.

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.

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