Profile 02 · Institutes and hospitals with a research unit
Your own cohort has to reach the committee, the reviewer and the funder without depending on one person.
The unit generates valuable data and depends on someone else's schedule to turn it into defensible results.
What cannot be solved today
The analysis depends on a bioinformatician the unit does not control.
When that person is busy, the project waits. When they leave, the judgement leaves with them.
The committee asks for traceability and there is nothing to answer with.
The results exist, but the path that produced them is not written down anywhere.
Peer review comes back with sensitivity questions.
Answering late costs months. Preparing those answers in advance costs a fraction.
What we deliver
The cohort processed under contract
Diversity, paired changes and differential abundance, with the sensitivity analysis already computed.
A report that separates observation, inference and interpretation
Written so that an ethics committee or a reviewer can assess it without opening the analysis.
Independence from a third party's schedule
The method contract stays with the unit and can be run again without us.
Available Computed today on public microbiome data. In genomics, the public demonstration uses synthetic annotation; real sources are agreed by contract.
The proof, checkable now
60
verifiable synthetic samples
Each row in metadata.tsv describes a generated sample. These are not human participants or clinical observations.
- Dataset
- nexalel-review-challenge.1729
- Method version
- Snakemake · microbiome-counts-analysis 1.0.0
- Run identifier
- Frozen example · verifiable scientific fingerprint
- Artifact hash
- 49a756dd4b79182add9b147727cc4781775a905f4e2473eb03b6ccdef077ab9e
- Seed
- 1729
The check runs in your browser and confirms file integrity. It does not replace scientific review or a fresh run.
What held up
A diversity signal holds under the documented depth check.
What did not hold up
Of the two significant contrasts, neither survived the sensitivity test. We publish that too.
We publish both. A method that only shows its successes cannot be evaluated.
Download the synthetic tables and test the analysis ↓ · 0.01 MB · No account, no form and no sales call.
Questions your procurement team will ask
Can we use patient data?
Only after reviewing the rights, purpose and controls of the specific dataset. Demonstrations always use public data.
Does this enter the clinical care pathway?
No. The intended use is research and is stated in writing in every agreement. Any use in care would require a different framework, which we do not offer today.
What do we need to have ready?
The question, the assay, the reference and the minimum metadata. The rest is agreed in the scoping session.
Who keeps the files, and for how long?
Location, access, retention and verifiable deletion are agreed before we start.
What does your next study have to demonstrate?
We first agree on the question, the assay, the data rights and the deliverable. Then we decide whether working together makes sense.