This page explains the concept of referential integrity as it relates to resources within a FHIR store in the Cloud Healthcare API.
The FHIR store enforces referential integrity on references to other resources within the same store:
- When creating, updating, or patching a resource, the operation will fail if the resulting content of the resource contains a reference to a resource or resource version that does not exist.
- When deleting a resource, the operation will fail if there are other resources in the store that reference that resource.
Referential integrity can be disabled by setting the
disableReferentialIntegrity option at the time of store creation.
Exclusions and limitations
The FHIR specification allows various forms of references, some of which are not covered by referential integrity:
- An external reference specified by a URL that does not match the base URL of the FHIR store.
- A logical reference specified by a business identifier.
- A reference containing only a human-readable display string.
- Known issue: References inside FHIR extensions are not subject to referential integrity.
Certain API methods can cause referential integrity to be violated under some conditions:
- FHIR allows references to point to a specific history version of a resource using the form
[resource type]/[resource ID]/_history/[version ID]. Referential integrity is applied to these references when created or updated, but when using the
Resource-purgemethod to remove historical versions of a resource, incoming references are not checked.
- The FHIR
importmethod does not enforce referential integrity. The method may be used either in cases where referential integrity is not required, or where the input is known to satisfy referential integrity. In the latter case, the references inside the FHIR store will reach eventual consistency after every resource is successfully imported.
deidentifymethod can potentially create a FHIR store in a state that does not satisfy referential integrity temporarily during the operation, or permanently if filters are used to select a subset of resources.
A state where integrity is being enforced but has been violated by one of the previous cases will cause resource updates to be rejected on a resource that contains an invalid reference, unless the update fixes or removes all invalid references. Such a state might also create difficulties for applications using the store that assume integrity.
The FHIR specification contains a constraint that every contained resource must be referenced from somewhere within its containing resource (including references from other contained resources), and every reference to a contained resource must be valid. This constraint is enforced separately from referential integrity and cannot be disabled as it is defined in the FHIRPath invariants on each individual resource.