# Loading Existing Data

Loading existing FHIR data into a remote system can be done with a batch job.

It's triggered by the following request:

```none
POST {fhir_endpoint}/$sdh.bootstrap-rte
```

Copy

## Required Permissions

Users must have either the `FHIR_EXTENDED_OPERATION_ON_SERVER $sdh.bootstrap-rte`
or admin permissions.

# Limitations

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.

**Turn off referential integrity**
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.
**Only a snapshot of the current system will be submitted**
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.

[Realtime Export Overview](/content/docs/realtime_export/realtime_export_overview.html)

Bootstrapping RTE Data

Realtime Export

[Realtime Export Overview](/content/docs/realtime_export/realtime_export_overview.html)
[Bootstrapping RTE Data](/content/docs/realtime_export/bootstrap_loading_rte.html)
[Realtime Export Rules Definition](/content/docs/realtime_export/realtime_export_rules_definition.html)
[Using FHIRPath](/content/docs/realtime_export/using_fhirpath.html)
[Delta Lake Export --EAP--](/content/docs/realtime_export/delta_lake_export.html)
[Bulk Batch Replication --EAP--](/content/docs/realtime_export/bulk_batch_replication.html)

[Realtime Export Rules Definition](/content/docs/realtime_export/realtime_export_rules_definition.html)