Oura Ring Gen 4 sensor data, not clinical measurementsN=1 case study, not validated for clinical decisionsHEV diagnosed Mar 18; Day 205 post-ruxolitinibMore
Consumer wearable data can support exploratory review only. The HEV diagnosis, temporally confounded with treatment start, remains a material confounder.

What's Next

The question this site asked in March, answered by its own data
HONEST

What this is, and what it is not

One patient, one consumer ring, every night since January 8, 2026. I had an allogeneic stem-cell transplant in November 2023. On March 16, 2026 I started ruxolitinib (Jakavi) for chronic graft-versus-host disease. The pipeline behind this site re-runs 30 reports on the ring data every morning; this page was generated from data through October 6, 2026, day 205 on the drug. Claude Code wrote the code. I described what I needed in Norwegian and checked what came back.

What it is not: a medical device, a clinical trial, or evidence about anyone but me. Every page carries that caveat because it is true. How this was built lists who did what; Every number, checked is the pipeline auditing its own pages.

QUESTION

The question this page asked in March

Two things happened 2 days apart. Ruxolitinib started March 16, 2026. Hepatitis E was diagnosed March 18, 2026. At day 8 this page said the two could not be separated, and set a test:

“Time. HEV is acute. It resolves in weeks. Ruxolitinib is sustained. If the signals persist and strengthen at day 28 (~April 13), it is ruxolitinib. If they fade, it was HEV. We cannot know before then.”

This is the table the page showed then, day 8 on ruxolitinib, kept exactly as published:

SignalPre-ruxPost-rux (8 days)Could be rux?Could be HEV?
Temperature deviation+0.07 C-0.16 CYes (immunosuppression)Yes (acute viral fever resolving)
Sleep HR85.0 bpm81.8 bpmYes (reduced inflammation)Yes (acute phase resolving)
Resting HR (readiness)79.1 bpm84.2 bpmNo (went up, not down)Yes (HEV-driven tachycardia)
HRV (RMSSD)9.2 ms10.1 msMarginal (still severely depressed)Unclear

The reading in March: the resting heart rate had gone up, which fit acute hepatitis E better than a JAK-inhibitor response; the temperature drop could be either; the HRV change was within noise.

ANSWER

The answer at day 205

Data through October 6, 2026. Every number is a live query from the pipeline's own JSON.

HRV, ruxolitinib alone
Inside the twin's range
10.9ms
10.0 ms before → 10.9 ms · 22 nights · Tau-U -0.19
HRV, plus beta-blocker
Step at second medicine
28.1ms
10.9 → 28.1 ms · 181 nights · ITS step +19.1 ms, p<0.001
Lowest HR, plus beta-blocker
Step at second medicine
59.4bpm
76.7 before · 72.9 on ruxolitinib alone · ITS step -10.2 bpm, p=0.002
Nights above the twin's range
Info
173/182
since the beta-blocker · 1/23 on ruxolitinib alone · projected 10 ms, actual 24 ms

Did the signals fade? No.

All nights before treatment against all nights on treatment, the split the March page used:

SignalBeforeOn treatmentChangeCohen's dNights before / on
HRV (RMSSD)10.0 ms26.2 ms+16.2 ms+1.9567 / 203
Average HR85.2 bpm69.5 bpm-15.6 bpm-2.0464 / 197
Lowest HR76.7 bpm60.7 bpm-16.0 bpm-2.1864 / 197
Sleep Efficiency78.6 %83.1 %+4.4 %+0.8364 / 197

These are descriptions, not evidence. The pooled Mann-Whitney test behind them fires at 100% of 20 random pre-treatment dates in this pipeline's own placebo calibration, so its p-values are not shown here.

Was it ruxolitinib? The March test could not see the second medicine.

A beta-blocker was added on April 8, 2026, 23 days after ruxolitinib. Three phases: before treatment (67 nights), ruxolitinib alone (22 nights), ruxolitinib plus beta-blocker (181 nights). The piecewise interrupted time series fits a step at each medicine start with AR(1) errors; Tau-U is the trend-corrected single-case effect size between phases.

SignalBeforeRuxolitinib alonePlus beta-blockerITS step at ruxolitinibITS step at beta-blockerTau-U before → aloneTau-U alone → plus BB
HRV (RMSSD)10.010.928.1-1.5 (p=0.71)+19.1 (p<0.001)-0.19+0.95
Lowest HR76.772.959.4+1.9 (p=0.62)-10.2 (p=0.002)-0.11+0.89
Average sleeping HR85.281.468.3+2.2 (p=0.58)-9.8 (p=0.006)-0.16+0.87

By the test this page set itself, the signals did not fade. But the change the March page was waiting for did not arrive in the 22 nights on ruxolitinib alone: HRV moved from 10.0 to 10.9 ms, and the phase-corrected model finds no step there (-1.5 ms, p=0.71). It arrived after April 8, 2026: HRV averaged 28.1 ms on the two medicines together, with a step of +19.1 ms at the beta-blocker (p<0.001). The twin, trained only on the nights before treatment, projected HRV around 10 ms without it: 1 of 23 nights on ruxolitinib alone sat above that range, 173 of 182 nights since the beta-blocker did.

So the honest answer at day 205: the signal persisted, and by the pipeline's own phase analysis it sits with the second medicine, or with the two together. Whether that is a beta-blocker acting on heart rate, a delayed ruxolitinib effect, or both, is the open question. The Research Synthesis page holds the two-hit hypothesis; the Piecewise ITS, Tau-U and Sequential CI pages hold the models.

What time cannot settle: this is one person and an observational before-and-after. Hepatitis E was diagnosed two days after ruxolitinib started and resolved in the same window. The causal report runs the single-split methods and shows their own placebo check; read that before reading any paragraph here as proof.

The shortcut named in March still stands: Oura's own cohort contains users on ruxolitinib without hepatitis E, and users on beta-blockers without either. That comparison is impossible with N=1 and trivial at cohort scale.

SUBJECTS

Subjects

Primary subject
Info
270days of data
Post-HSCT · data January 8, 2026 to October 6, 2026
Family control
Info
23days of ring data
Healthy Control · age 61 · metrics dated 2026-10-06
Disease control
Info
594days of ring data
Post-Stroke / ALL Survivor · age 36 · metrics dated 2026-10-06
ROADMAP

Where the roadmap stands

PhaseStatusWhat
v1.0DoneSingle-patient pipeline. Live since March 2026; data through October 6, 2026.
v1.1RunningReports regenerate every morning at 06:15 from a fresh Oura import; last run 36/36 scripts passed.
v2.0RunningHealthy family control: 23 days of ring data, standalone dashboard live.
v2.1RunningPost-stroke control: 594 days of ring history, standalone dashboard and changepoint scan live.
v3.0Partly8 comparative reports and 4 single-case statistical reports are live. Between-subjects CausalImpact is not built yet.
ANALYSES

Planned analyses

Between-subjects CausalImpact

Same intervention window, three physiologies. Does ruxolitinib produce a detectable autonomic signal only in the immune-mediated patient? The controls make this answerable.

Family genetic control comparison

Mother and son, about half the genome shared. Baseline HRV, sleep architecture, circadian patterns. What is inherited and what is disease?

Disease-specific autonomic signatures

Immune-mediated (GVHD) against neurovascular (post-stroke). Different damage, same ring, same pipeline. Do the signatures separate?

Cohort-ready pipeline

Any Oura user, any condition. A config file and an OAuth token run the full report set. Open source.

OURA TEAM

For Oura's team

This pipeline needs a config file and an OAuth token. It runs end to end in 5 minutes on one CPU. If your cohort contains even 50 users on ruxolitinib, you can validate or falsify every finding on this site in an afternoon. The code is MIT-licensed. The tables above say exactly which comparisons resolve which questions.