Scientific Research
Client
PR Calabria FESR FSE 2021–2027 — partners: IRCCS San Raffaele, Università Magna Graecia, Romolo Hospital, More Care
Role
Lead Data Architect
SUN IN SEAD
Bio-Clinical Data Platform
Integrates clinical data, biobank provenance, NGS ground truth, Raman spectra and ML validation into a pseudonymised, traceable research platform.
Architecture Flow
§ 01 Context
The platform separates direct patient identity from laboratory sample identity through pseudonymised identifiers, and integrates biobanks and external systems through REST, Kafka, JSON, XML, CSV and controlled file exchange, with authentication, API contracts, response codes and OpenAPI documentation.
§ 02 Designed System
◆Patient → Clinical Request → Sample → Biobank → NGS and Raman Acquisition → Prediction → Validation
◆Pseudonymised identifiers separating patient and laboratory-sample identity
◆Integration through REST, Kafka, JSON, XML, CSV and controlled file exchange
◆GDPR compliance, auditability and traceability between clinical requirements, software development and validation
§ 03 Capabilities
- —Provenance from patient to prediction
- —AI validation against NGS molecular ground truth
- —Traceable Raman spectrum preprocessing, feature extraction and model outputs
§ 04 Objects & Stack
Data Objects
- Test definition
- Biological samples
- Biobank and reagent information
- NGS molecular ground truth
- Raman acquisition parameters
- Raw and extracted spectral data
- Predictions, confidence scores and concordance
- Corrective actions and validation results
Technologies
PythonPostgreSQLKafkaRESTOpenAPISpark
§ 05 Outcome
Privacy
Pseudonymisation, GDPR compliance, auditability across clinical, engineering and validation domains.
§ 06 Related Reading
Essay 18
Determinism Is Not Repetition: The Conditions of Reproducible Data
Data platforms frequently promise that the same input will produce the same output. The promise is attractive, but often false because “the same input” is defined too narrowly. A computation depends not only on source records but on code, configuration, reference data, library versions, execution engines, clocks, seeds, policies, and hidden environmental state. This essay distinguishes repetition, determinism, reproducibility, replicability, and auditability. It formalises a data computation as a function over an extended state space, examines sources of non-determinism in distributed and temporal systems, and proposes an evidence model for reproducible outputs. The philosophical question is one of identity through time: when are two executions instances of the same computation, and when is a numerically equal result merely accidental? The essay argues that reproducibility is not achieved by rerunning code but by preserving the computational world in which a claim was produced.
Essay 28
Governance by Design: Rules That Execute