Clinical oversight

AI can propose a hypothesis. The doctor makes the decision.

BIOS retains sources, identifies missing data and separates machine-generated conclusions from clinical decisions.

A use case is launched only after its rules and responsibilities have been agreed.

FactSource and version

Documents, measurements and observations retain their provenance and time.

HypothesisEvidence and gaps

A possible association does not conceal uncertainty or missing data.

ReviewThe responsible doctor's decision

Confirmation or rejection is recorded separately from the system's conclusion.

ReleaseOnly a reviewed result

The patient is not given a system response as a final medical assessment.

Decision model

Four independent stages

The path from fact to release can be traced.

01 · Data
Source
Normalisation
Fact version
02 · Analysis
Supporting evidence
Possible association
Missing data
03 · Review
Awaiting review
Confirmed / rejected
Reason for the decision
04 · Release
Access rights
Safe wording
Release log

Review policy

What must not be released automatically

Higher risk requires stricter stop rules.

01 / Significance

Clinically significant conclusion

Requires a doctor's review.

02 / Urgency

Potential urgency signal

Referred to a separate review procedure.

03 / Gap

Insufficient data

The system stops.

04 / Conflict

Sources contradict one another

The discrepancy remains visible.

05 / Policy

Permission absent

Release is blocked.

06 / Explanation

The conclusion cannot be explained

It is not assigned clinical status.

Change control

Every change has a version

An AI update must not silently change medical meaning.

01

Source

The rule's provenance.

02

Version

Revision and owner.

03

Review

Accuracy and safety.

04

Approval for use

Use case and audience.

05

Monitoring

Deviations and incidents.

Current stage

Oversight is tested alongside the product

Activation depends on the use case, clinic and completed review.

01

Accountability

Each use case has a clinical and a technical owner.

02

Traceability

The fact, hypothesis and decision are recorded separately.

03

Incident

An event can be stopped and linked to a version.

04

Rejection

A rejected conclusion does not become a fact.

Oversight begins with a specific use case.

Owners, rules and stop conditions are defined before launch.