Most PACS projects start small: one department, one scanner room, one archive. Then the second site joins, then a private clinic wants to send studies for reading, then the health authority asks for a regional view. Each step, historically, meant a migration, and migrations are where years of studies get lost, IDs get duplicated and radiologists lose their hanging protocols.
It does not have to work that way. The difference is whether the archive was designed as a single product that scales, or as a small product that gets replaced.
Three things that make growth painless
1. One patient index from the start
The moment two sites share studies, the same person exists twice: once per hospital information system. A regional archive needs a master patient index that links those records without rewriting them, and a viewer that shows the combined history. If the archive treats the patient index as a first-class object on day one, adding a site is a mapping exercise, not a data cleanup.
2. Gateways at the edge, archive at the centre
A site should keep working when the link to the centre is down. In the RadImages design each facility runs a DICOM Uploader gateway that receives studies from local modalities, caches them, serves the local viewer and forwards to the central archive when the link allows. Readers at the site see no difference; the region sees a complete archive once the queue drains.
3. The same viewer everywhere
Nothing derails a regional project faster than three viewers with three sets of shortcuts. When the viewer runs in the browser, every site gets the same one, updated centrally, with the same hanging protocols and the same annotations. Teleradiology becomes a worklist setting rather than a separate system.
What the region gains
- A radiologist in the regional centre reads for a district hospital in the morning and a private clinic in the afternoon from one list.
- Prior studies from any site are available at any other site, which removes repeat scans.
- Utilisation and turnaround statistics cover the whole network, not one building.
- Registration with a national archive happens once, centrally, instead of at every hospital.
The RadImages path
RadImages Classic PACS and RadImages Regional PACS are the same core with different deployment shapes. A clinic that starts with Classic PACS keeps its archive, its viewer and its integrations when it becomes a node in a regional network; the central archive is added around it, not in place of it. That is the whole point: growth should be a configuration change, and nobody should have to migrate a decade of studies to get there.