Loading existing FHIR data into a remote system can be done with a batch job.
It's triggered by the following request:
POST {fhir_endpoint}/$sdh.bootstrap-rte
Users must have either the FHIR_EXTENDED_OPERATION_ON_SERVER $sdh.bootstrap-rte
or admin permissions.
Loading existing resources is a powerful tool. But it is largely meant only to help initialize a system
But due to the nature of the job, there are a number limitations of which users should be aware.
Because of the nature of batch jobs, there's no way to ensure the ordering of resources arriving in the remote system.
For this reason, the remote system must have reference integrity turned off for the duration of the job.
Once the job is complete, referential integrity may be turned back on again.
Because the job is only meant to help initialize a remote system, the submitted resources will only be a snapshot of the current state of the FHIR system.
This means only the current version of the resources will be submitted to the remote database.
Deletes, updates, and other historical operations will not be preserved.
You are about to leave the Smile Digital Health documentation and navigate to the Open Source HAPI-FHIR Documentation.