Designing a Repeatable Import That Survives Schema Changes
A one-off FHIR import runs once. A repeatable import runs weekly for years, and every schema change…
Recovering From a Failed Import Without Starting Over
A five-hour import that fails at hour four does not need to become a five-hour restart. Designing…
When an Import Needs a Staging Environment
Some FHIR imports are safe to run directly against production. Most are not. Deciding which category you…
Planning an Import Around Production Traffic Windows
The best-planned import that runs during clinic hours becomes the worst-planned incident. A FHIR server that sustains…
Monitoring an In-Flight Import for the Numbers That Matter
A long-running FHIR import that emits no metrics is a coin flip. Halfway through you have no…
Parallelizing an Import Without Corrupting References
Parallelizing a FHIR import is the single biggest lever for cutting duration. Running eight workers instead of…
The Four Dominant Drivers of Import Duration
FHIR import duration is not one number produced by one lever. It is a function of four…
Predicting How Long a FHIR Data Import Will Take
The first migration meeting where someone asks "how long will this take?" is where a lot of…
