We’ve spent a decade building and running the external interfaces of the National Cancer Screening Register — every connection from the central register to pathology labs, Medicare, OCR, mail house systems and the client portal. Registers at that scale teach you lessons that apply to every chronic disease register, at every scale. Three stand out.
1. The register is only as good as its inbound interfaces
A register’s value is completeness and accuracy, and both are decided at the edges — where pathology results, claims data and correspondence enter the system. Interface engineering isn’t plumbing around the “real” system; on a register, the interfaces are the system. Design them for validation, reconciliation and replay from day one, because the question is never whether a feed will misbehave, only when.
2. Identity is the hard problem
Matching records to the right person across pathology systems, Medicare data and self-reported details is where registers succeed or quietly fail. Deterministic matching alone won’t cut it; you need probabilistic matching with clinical-safety guardrails and human review queues for the grey zone. This is precisely the problem HealthShare Patient Index exists to solve, and why we build with it.
3. Boring reliability beats clever features
A national register is infrastructure. Nobody thanks it for existing; everybody notices the moment a result is late. The engineering culture that keeps a register trusted is one of unglamorous discipline — monitoring, idempotent processing, graceful degradation, and maintenance as a first-class activity rather than an afterthought. It’s why “design, build, deliver and maintain” is one sentence in our contracts, not two.
Scoping a register — cancer, chronic disease or screening? We’ve built the national one.