Research and validation

Publish what the system has proved—and make the unproved boundary equally visible

Current evidence in this release is engineering verification and software checks, including checks against synthetic cases. The public materials reviewed here do not provide a dated, version-specific clinical-validation statement or report clinical study results; software checks do not establish diagnostic accuracy or patient benefit.

A question for your current workflow

Which claim is supported by a test, which by a simulation and which still needs a real clinical study?

What current checks can establish

Software tests can check that implemented functions behave as specified. Synthetic cases can exercise software paths and expose technical failure modes. Neither is evidence that a clinician makes more accurate diagnoses or that patients benefit.

Evaluate the human-system interaction

Measure whether clinicians find sources, notice conflict, resist unsupported suggestions, correct drafts and understand what the system has not established.

Keep limitations current

Known failure modes, excluded populations, unavailable features, data constraints and regulatory scope should change as the product changes—not remain a static reassurance page.

Questions worth answering before a demo

Is SheldonDx clinically validated?

The public materials reviewed here do not provide a dated, version-specific clinical-validation statement or clinical study results. Engineering tests and synthetic-case checks do not establish clinical validity, diagnostic accuracy or patient benefit.

Can clinicians discuss an evaluation?

Contact SheldonDx to discuss a proposed evaluation. Any participation, data use and publication would need to be agreed in advance.

Review the evidence boundary

Discuss the current evaluation state, known limitations and an appropriately governed pilot.

Email to request the research brief