“A day late and a dollar short.”
Your Fitbit can congratulate you for getting off the couch while its VA sharing connection needs attention. The wrist is celebrating. The handoff may have stopped. Before we throw another little parade for the step count, somebody ought to check whether anything new made it out of the damn driveway.
This is a specific notice for Veterans who share Fitbit data through VA’s Share My Health Data service. VA says they needed to reconnect through Google Health by October 30, 2026 to continue sharing. Without reconnection, Fitbit sharing with VA stops after that date. Previously shared data remains displayed. That last detail deserves a second look: seeing yesterday’s information does not prove today’s connection works.
A working watch is not a working route
That is the distinction I want Veterans, companies and care teams to keep straight. A device collecting information, an account holding it, and VA receiving new information are separate jobs. A lovely graph can sit there looking employed long after the job you need has stopped getting done. Historical data can be useful. It should not get mistaken for proof of a current handoff.
I am not declaring every Fitbit connection broken. If you already completed the change, this may be settled for you. If you have not, or cannot remember, start with the official instructions instead of assuming the watch would tell you. A cheerful screen on your wrist is a remarkably poor witness to what happened farther down the route.
Nor is this a reason to blame the Veteran. People have appointments, families and actual lives. A notice asking them to reconnect an account is competing with pharmacy reminders, password warnings and somebody’s urgent offer of twenty percent off patio furniture. The person wearing the device should not need a second career in integration maintenance to keep a useful sharing arrangement working.
Here is the route VA publishes now
For the web route, VA directs you to sign in to My HealtheVet on VA.gov, choose Medical records, then Share your personal health data. In Connect my Health Accounts, choose Google Health, select Connect and follow the prompts to choose what you share. A Google account is required.
Use the current official Share My Health Data instructions linked with this Article. Do not hand your password or health information to a stranger offering to “fix the connection.” Read the permission prompts yourself. If the instructions and the screen in front of you do not agree, use the app’s Help resources rather than improvising your way through somebody else’s tutorial.
Then look for evidence of recent information, not just the comfort of a familiar chart. Check the dates you can see and the information you intended to share. If something is missing, describe the problem without inventing its cause: which connection, which information and the latest date visible. “Everything disappeared” and “my old data is visible but I cannot find anything recent” send troubleshooting in very different directions.
Reconnecting also does not appoint a clinician to watch your wrist. VA says sharing does not automatically notify your care team. Agree on what information matters and how it will be reviewed; let the team know at an appointment or through a message in My HealtheVet if you want review sooner. Do not use this route for an emergency. Call 911 for a medical emergency.
When you ask for help, make the question answerable: “I reconnected this account, but the latest information I can see is dated Friday. Is that expected, and what should I check next?” Give the support team the dates and route without posting your medical history in a public comment. If your care team expected information during that period, tell them what you know about the interruption. Do not quietly turn missing data into a story about how well or poorly you were doing.
Companies: the ribbon cutting was not the finish line
If you sell a connected health service, put this next to the launch photograph. Somebody will eventually change a connection, an account requirement or a permission flow. Your wonderful first demonstration will not walk the Veteran through that change. The balloons will have come down. The support problem will still have a pulse.
For this particular change, the official VA instructions are the place to start. For the wider design question, I want companies to show how they distinguish a current connection from an old chart. Where does the Veteran see that new information has arrived? What happens when it has not? What help is offered, and who owns explaining whether anything needs to be done?
VA’s published Google Health privacy information describes access based on the permissions a user grants, with access limited to reading designated data. Those permissions are part of the route, not a nuisance to click past. Explain the requested information and purpose in ordinary language. “Just authorize everything” is a hell of a substitute for doing the explanatory work.
My proposed test: break the handoff on purpose
In a controlled test with authorized participants and test data, have the implementation team simulate an interrupted connection. Keep old information visible. Then ask a participant to determine whether sharing is current without a sales representative standing behind them narrating the correct answer. That is my proposed usability test, not a claim about a defect in VA’s system.
Next, ask the participant to find the recovery instructions, understand the permissions and reconnect. Confirm whether expected new test information reaches the intended destination. Record what failed, what the person misunderstood and what support was needed. Do not score success because somebody reached the last setup screen. We are testing the handoff, not awarding a participation trophy to the Connect button.
For the test, count successful recovery, misunderstood instructions and requests for help. Ask the participant to explain what is now connected. That answer may tell you more than another screenshot of your cheerful completion message. Recovery is not complete until the person understands what the connection now does.
Bring the receiving VA clinical or program team into planning any real pilot. Agree on the information they need, where they can find it, what review is actually supported and how a collection interruption should be handled. The company’s technical team, support staff, privacy reviewers and clinical partners each have work here. A connection diagram cannot volunteer those people for duties they have never accepted.
Test with people who differ in technical confidence, eyesight, dexterity and access to help, including women and men Veterans. If the fix only works when your best engineer is sitting beside the participant, you have demonstrated the value of your best engineer. You have not yet demonstrated that the person at home can recover the connection.
Veterans using this Fitbit route: check the official reconnection guidance and whether your intended recent information is present. Care teams and companies: what evidence would help you distinguish a quiet week from a quiet connection? Keep private health details out of public replies. The watch can keep counting. The handoff still has to earn its keep.
Put recovery into the VA plan before the launch
For companies pursuing VA, this is work to scope before the demonstration: what has to keep working, who explains an account change, how the Veteran gets help, and how the receiving team knows what information it can rely on. JhetVet® helps companies examine the Veteran use case, evidence, stakeholder responsibilities, support model and purchasing path, then connect those decisions to actual channel execution. Bring the recovery plan alongside the product. If the plan ends at “the account connected,” we still have work to do.
Explore JhetVet® Wearable Health, see how we operate, or discuss your VA pathway.
Sources
VA Share My Health Data: Fitbit reconnection FAQ and current instructions
VA Telehealth: patient generated health data and care team review
This Article explains an official connection change and questions for a care team or implementation team. It does not establish your individual connection status, automatic monitoring, a local VA service commitment or a product recommendation.
