The Number Moved. What Changed?
A wearable catches a change. Heart rate is up. Oxygen saturation is down. Sleep fell apart. Steps disappeared. Recovery tanked.
Now everybody wants the dashboard to explain the Veteran.
It cannot—not by itself.
The number moved. The real question is: what changed around it?
A new medication. A bad night of sleep. A loose sensor. A hard workout. Travel. Alcohol. Pain. Stress. A missed CPAP session. A respiratory infection. Or a real clinical change that deserves attention.
That is the line between collecting data and understanding a signal.
A Signal Is a Question, Not a Verdict
A wearable signal can point in the right direction without delivering a diagnosis. Industry gets into trouble when it treats a change as a conclusion instead of the start of a better question.
Signal Before Symptom™ is not “let the algorithm practice medicine.” It is: notice a meaningful change early enough to ask what may be happening, compare it with the Veteran’s usual pattern, and decide whether the next step belongs to the Veteran, a caregiver, or the care team.
My Guy, if the number moved and nobody can explain the conditions around the reading, you do not have intelligence yet. You have a clue.
The Veteran’s Baseline Matters
Population ranges matter. Device specifications matter. Clinical thresholds matter.
But many wearable use cases also depend on change from the Veteran’s normal pattern.
For one Veteran, a resting heart rate of 78 may be ordinary. For another, it may be a meaningful departure. The same is true for sleep, activity, respiratory rate, oxygen saturation, glucose patterns, gait, and recovery.
GAO notes that wearables may help establish patient health baselines and add information to clinical decision-making, while also warning that reliability and workflow integration remain real challenges.
The responsible move is not to worship the baseline. It is to use it as context—alongside symptoms, history, device limitations, collection conditions, and the care plan.
VA Is Already Building Context Into the Data
VA’s patient-generated health data guidance tells Veterans to work with their care teams to decide which information is important, establish a review cadence, and agree on how the data will be used. VA also makes clear that sharing data does not automatically notify the care team.
That matters.
Data can be available without being actively watched. A dashboard can exist without being part of routine care. A number can be accurate without being meaningful to the decision in front of the clinician.
VA’s Patient Generated Health Data Code System goes even deeper. It says metadata should frame both the type of data collected and the conditions surrounding collection so the information can be understood clearly.
Plain English: what was measured, how was it measured, when was it measured, and what was happening at the time?
Give the Data a Job Before You Give It a Dashboard
Before a company tells VA it can deliver continuous insight, it should be able to answer:
Which signal are we collecting?
What Veteran problem or clinical question is it meant to support?
What is the Veteran’s usual pattern, and how is that baseline established?
What collection conditions can distort the reading?
Is the device measuring, estimating, scoring, or inferring?
How often should the information be reviewed?
What change is worth attention, and what change is expected noise?
What decision can this information actually help someone make?
How will the Veteran know what to do without being frightened by every deviation?
If the answer is “the clinician can look at the dashboard,” that dog will not hunt.
Clinicians already have history, labs, symptoms, medications, imaging, preferences, and a full day of decisions. More data is not automatically more clarity.
For Industry: Stop Selling More Data
The winning pitch is not “we collect everything.”
It is “we help the right person understand what changed, why it may matter, and what responsible decision the information can support.”
That requires:
a defined Veteran use case
a credible intended use
transparent device limitations
collection context and metadata
a personal baseline when appropriate
workflow fit
a review and response plan
a way to close the loop
The hardware may sit on the wrist. The product lives in the meaning around the signal.
Signal Before Symptom™ Means Context Before Conclusion
Earlier information can create an earlier opportunity—but only when the signal is interpreted responsibly.
Do not ask a wearable to know the whole Veteran.
Ask it to do a specific job well, in a defined pathway, with enough context for a human being to make a better decision.
The number moved.
Before you build an alert, a dashboard, or a sales pitch around it, answer the question that matters:
What changed?
Building a wearable or connected-health pathway for VA? Explore JhetVet’s Wearable Health work or start a conversation about mapping the signal, context, workflow, and market path.
Educational note: This article is for general information and is not medical or legal advice.
