IT Consulting & Software
We program the statistical analyses of clinical research in SAS and R, as we have for more than 20 years, and we build web applications for companies whose processes still depend on fragile spreadsheets or on software that nobody maintains any more.
01 Fields
SAS and R programming for clinical research: data brought into line with CDISC standards, then the analysis datasets, tables and listings used in study reports. Programs are documented and reproducible, so that each figure can be traced back to its source data.
Web applications designed around your processes, from the first prototype to production. Two examples we build and run: Kanseios, our quality and compliance platform, and Fertismart, a fertiliser calculation platform that is not openly accessible and is available on request.
Shared spreadsheets that break as soon as two people edit them, replaced by dependable tools: structured data entry and checks on each value as it is entered. Documents and dashboards are then generated from that single source.
Corrections, new features and support for applications already in use, including ones we did not write. The code we deliver is tested and documented, so that another team can take it over without depending on us.
Verascius also publishes Dropefo, a tool for interactive documents used online or on paper: dropefo.com
02 Approach
An assignment starts from what is already there: the scripts, the spreadsheets or the application in place, and the people who use them every day. We agree on a written scope, then deliver in stages that you can check against your own data.
The person who analyses the need writes the code and remains your contact once it is in production. Most of the work is done remotely; we come on site when a workshop with the users is worth it.
03 Examples
A
A team produced its statistical outputs with SAS and R scripts that had accumulated over the years. We took the scripts over and turned them into a reproducible chain, validated and documented, that regenerates the same outputs from each new data delivery.
B
Several people updated the same spreadsheet, with no way of knowing who had changed what. We built a web application with controlled data entry and access rights, which keeps a change history and exports in the formats the team already used.
C
The same data was typed twice, once in the ERP and once in a business tool. We set up an import or an API link between the two systems, which put an end to the double entry and to the differences between them.
D
A company depended on an application whose developer had left without documenting it. We audited the code and fixed the urgent defects, then wrote the documentation and a plan for further development.
04 Team
Chemical & bio-industry engineer, statistical programmer (SAS, R, CDISC)
Developer of Kanseios and Fertismart
05 Contact