Module 02 / safety data monitoring
Safety Data Monitor
A condensed re-implementation of the platform's safety-data change monitor. One baseline extract is stored in full, exactly once. Every daily export after that is compared record by record against the reconstructed previous state, and only the differences are appended to an immutable change log — new records, field-level modifications, and deletions, per SDTM domain.
Any historical state can be rebuilt on demand by replaying the log over the baseline: store once, reconstruct many. A daily reconciliation job proves that fidelity by replaying the log and comparing the result against the export actually received. In the production validation this mechanism replayed 100% of 56,265 records across five SDTM domains and matched the source data on every date — the numbers on this page are demo-scale synthetic data.
Daily change volume
Record-level changes per daily export, stacked by change type.
■ new ■ modified ■ deleted · the bars summarize all 14 exports; pick a date in the selector above to update the detail panels below.
Alerts
Replay verification
Daily reconciliation of the reconstructed state against the export received.
Field-level changes
Storage footprint
Fourteen daily exports: keeping every full snapshot versus one baseline plus the append-only change log.
All snapshots, records, changes, and alerts on this page are synthetic, generated by a seeded script (tools/platform-demo/generate-data.mjs) and embedded at build time. No patient data, no network calls.