Backfill your database before go-live

Last updated: Nov 18, 2026
IMPLEMENTATION
HEALTH TECH VENDOR

When you go live with an integration, you start receiving patient data from your connection’s system from then on. Depending on your unique workflow, you may need historical data to provide enough context for your system to do its job.

Let’s say you have a scheduling app that reminds patients about their upcoming appointments. You plan to start sending reminders to patients from your connection’s system once you go live with the integration. But some existing patients booked appointments before you started integrating with your connection. So you need a backfill of appointment and patient data so that your app can start sending reminders to existing patients with appointments.

Even if you don’t have a client-facing need, it might be useful to have historical data for patient searches from your system. Without a backfill, you can only search for new patients created after go-live.

Scoping

During the scoping process, we recommend that you work with your connection to define what historical data you may need. You can also discuss the best way to backfill your system before go-live.

Data on demand

You may also need a backfill if you’re using data on demand. If so, the same scoping considerations and backfill options apply. Learn more about data on demand.

Backfill options

We understand the importance of backfilling quickly and efficiently. To make sure you can go live as soon as possible, Redox processes more than 100K logs per hour. Actual throughput varies, of course, depending on several factors like the data exchange method and throughput capabilities of both the sending and receiving organizations. A Redoxer can help you pick the best backfill option based on your specific integration needs.

There are two common options for backfilling:

  1. Your connection uses an existing configuration to push historical data to Redox to populate your backfill before go-live. If your connection supports it, we recommend this option since it simplifies the effort to process the backfill and uses existing mechanisms for real-time integration. 
    Open beta: Child queues for subscriptions

    Worried about the high volume of messages and the time it takes to backfill? If so, you may want to think about using child queues for your data model subscriptions.

    Child queues allow you to have multiple queues for one subscription so that messages process in parallel. Using this option can speed up backfilling, as long as the destination can handle that volume of messages.

    Learn more about child queues for subscriptions and talk to your Redox technical account manager about setting up child queues for backfilling.

  2. Your connection populates one of Redox’s CSV flat file templates for historical patient and appointment data, then sends it to your system. You upload the file to a location Redox can poll or you push the file to us to populate your backfill. This option is sometimes easier for your connection.

How much data to include in a backfill

When deciding how much data to ask for, make sure to:

  • prioritize only the absolutely critical data elements for a backfill; and
  • consider how quickly your system can consume the amount of data you’re asking for.

What to consider also depends on whether you’re backfilling for a standard integration or a cloud implementation with Redox.

Backfilling for Redox

It’s typical to backfill an entire patient population, six months of future appointments (from the go-live date), or a current inpatient census. Whatever you decide, we recommend carefully considering the quantity and type of data that you backfill.

For example, it might be nice to have laboratory results from the past 10 years. However, it could extend your implementation timeline for your connection to compile the data—and for your system to consume all that data, too.

Backfilling for cloud

If you use cloud connectivity, you likely need a full longitudinal view of your patient population. So you might want patient- and encounter-level clinical summary documents or other supplemental data so you can link related patient records and identify gaps in patient care. To create that kind of patient picture, it’s likely you’ll need a backfill of tens of millions of records in your cloud provider’s repository. Learn more about cloud connectivity.

For large-scale backfills (e.g., more than 5M messages), we set up the system to separate backfill data from real-time data. That way we can process your data efficiently without disrupting other real-time traffic.

Where to find backfill logs

When you have backfill data, it’s kept separate from your go-live data. That way, you have access to historical data without cluttering up your main database.

You can view backfill-related logs on the Logs page of the Redox dashboard. Find the Database filter at the top of the page and select the Backfill option to search for backfill logs.

Database field

The Database drop-down isn’t visible if you don’t have any backfill data.

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.