A randomised A/B trial for one patient, with its uncertainty stated.
The clinician names two treatments, the outcome, the length of a period and the number of pairs; the order inside each pair is drawn at random when the trial is saved and the database freezes the design. The outcome is either a daily score the patient logs on their portal link (which also tells them which treatment this period is) or the portal’s own “How are you doing today?”, read from the rows it already writes. The result is computed on every read: the mean of each period, the mean on each treatment, the paired B − A difference and an exact randomisation-test p-value over the pairs, printed beside the smallest p-value the design could ever give and a caution in words — one patient’s pattern, not proof.
What it does not do, by design. A listing with only benefits is an advertisement.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.