Limited tasks and predefined criteria.
Science and validation
We test more than accuracy. We test usefulness and safety.
We assess data quality, algorithm performance, the clinical process and whether people understand the result correctly as separate questions.
Testing the process and safety before claiming an effect.
With methods, limitations and conflicts of interest.
Claims must not get ahead of evidence.
Validation framework
Four independent levels
Strength at one level cannot conceal weakness at another.
Does the system work correctly?
Versions, access, resilience and audit.
Has the data been extracted correctly?
Completeness, units, timing and reproducibility.
Is the result useful to a doctor?
Relevance, safety and supporting evidence.
Is the result understandable?
Limitations must not create false confidence.
Approval stages
From code to a clinical use case
Technical testing
The feature exists and passes tests.
Expert review
The intended use and hazardous operating modes are defined.
Evaluation study
The sample, reference standard and criteria are defined before the study begins.
Clinical pilot
We test operation within a real workflow under specialist supervision.
Launch
Users, monitoring and a rollback method are defined.
What we measure
A pilot tests the process
Metrics are agreed before it starts.
Transparency
Evidence will be published
Protocols, versions, results and limitations — after review. No public effectiveness data is available yet.
BIOS welcomes independent validation.
One use case. One owner. Measurable criteria.