The twelve questions that always come up.
Integration, documents, quality, data ownership, EDC and timelines. Direct answers, no hedging.
Does Latrikos need to integrate with the HIS?
Not to get started. It can work with the exports and clinical documentation the site already produces. Integration is optional and is considered when it adds further operational value.
What document types can it process?
Clinical reports, progress notes, tests, treatments, letters, PDF and Word documents and other exports defined in the project.
Can it combine data from hospitals with different systems?
Yes. A common clinical ontology is defined and processing is adapted to each site’s documentation, normalising the final result.
How is quality guaranteed?
Through expert validation, precision and coverage metrics, consistency rules and traceability of every value back to the original source.
Are the registries longitudinal?
Yes. Latrikos keeps dates, episodes, visits, tests, treatment changes and clinical progression, rather than settling for a static snapshot.
Who owns the data and the registry?
The client keeps control over the data, the model and the evidence asset, in line with the agreed contracts and governance.
Can it be used for a prospective registry?
Yes. A project can start with retrospective data and go on adding new patients, visits and variables prospectively.
Does it replace the EDC in a clinical trial?
Not necessarily. Latrikos complements the EDC by structuring source data, supporting capture, easing review and preparing traceable exports.
Can the data be downloaded?
Yes. Data and results can be exported in standard formats defined for the project, including Excel, CSV and other outputs for analysis or downstream systems.
How long does it take to get running?
It depends on the number of variables, sources and sites, but the no-integration approach lets clinical work and validation start far earlier than a traditional integration project.
Can the project grow?
Yes. Sites, patients, periods, variables, languages and new use cases can be added, reusing the ontology and the work already done.
How are privacy and access managed?
The model is defined per project and includes minimisation, pseudonymisation or de-identification, role-based permissions, technical controls and processing documentation.