The porch light’s on but nobody’s home.
A wearable app can throw a beautiful housewarming party for your data. The upload finishes, the graph appears, and a reassuring check mark tells the Veteran everything arrived. Lovely. Now tell me who was supposed to answer the door.
I am talking about a pathway that accepts information without establishing awareness and review. That is a design problem, not permission to blame a clinician who was never notified. “Available in the system” can sound reassuring while leaving the actual human handoff completely unfinished.
VA's public guidance on patient generated health data makes that distinction explicit. Sharing information does not automatically notify the care team. The Veteran and the team should agree on what to track and how it will be reviewed.
A successful upload proves that the information moved. It does not prove that somebody knows it arrived.
Pick the Lane Before Celebrating Arrival
First decide what kind of pathway you are building. A Veteran may be sharing information from a consumer device for a future conversation, sending a short summary through an agreed nonurgent channel, or participating in a formal monitoring program with assigned review responsibilities. Those are different jobs.
The pathway must say which job it performs. A portal built for later discussion should not look or sound like a monitored service. A formal monitoring program should not rely on the Veteran guessing when the team will review the information. A company cannot cover both situations with an integration slide and a confident nod.
An irregular rhythm alert is a useful test. The source could be an optical pulse pattern notification or an ECG recording, and those features do not have the same intended use or limits. If the receiving team cannot identify which feature produced the information, part of the meaning disappeared before anybody started interpreting it.
Give the Information a Real Address
Start with the question being asked. Is the Veteran reporting symptoms, requesting review of a tracing, or bringing a pattern to the next appointment? Then identify the actual destination. “VA has it” is not an address.
Technical transport, storage, access permission, entry into the official health record, and clinical awareness are separate events. One can happen without the next. A vendor that says the product “integrates” should be able to show the route, name the receiving system, explain who becomes aware, and state what review has actually been agreed.
The sharing authority matters too. The Veteran should understand what information is leaving, who receives it, why it is being shared, and what response should or should not be expected. Consent can open the door. It does not staff the house.
Six Things That Must Travel With the Signal
1. Device and Feature
Name the device, the feature that produced the information, and the software version when it matters. A summary generated from optical pulse patterns is not the same thing as a recorded ECG tracing.
2. Observation Window
Preserve the date, time, duration, and pattern. A single point, a repeated alert, and a sustained change tell different stories. The receiving team needs to know which one it is seeing.
3. Symptoms and Context
Record relevant symptoms, activity, medicine changes, sleep, illness, and other context the Veteran can reasonably provide. A number without context can walk into the room wearing somebody else's name tag.
4. Confirmation Status
State what the device reported and whether the information has been confirmed through an appropriate clinical process. An alert can earn a better question. It does not appoint itself as the diagnosis.
5. Authority and Destination
Document what the Veteran agreed to share, where the information is going, and who can access it. Data movement and permission are related, but they are not interchangeable.
6. Awareness and Review Plan
Identify the person or team who becomes aware that the information exists. Define what creates that awareness, the review cadence, coverage when the usual reviewer is away, and how the Veteran learns whether a response should be expected.
A Porch Light Cannot Carry a Shift
The mistake is installing an attractive intake portal and treating its availability as a staffed service. The glowing welcome sign does not have a clinical license, a work schedule, or a backup when the queue fills up. Somebody has to design and resource that work.
The U.S. Government Accountability Office has identified clinical workflow integration and clearer responsibilities as important challenges for wearable technology. That is a practical invitation for product teams: show the receiving workflow along with the sensor. For clinical leaders, it is a reason to define capacity before inviting another stream of information.
The decision about action belongs with the appropriate clinical team. The pathway should state what needs confirmation, what belongs in routine review, what warrants escalation, and what documentation follows if the information changes care. Those rules need clinical, operational, privacy, and security ownership.
What a Credible Pilot Must Prove
A useful pilot should trace a small number of agreed signals through receipt, awareness, review, confirmation, documentation, and communication back to the Veteran. Measure where the information stalls and how much work each step creates. Fix the route before widening the front door.
The scorecard should answer practical questions. Did the right information arrive? Did the right person know? Could the reviewer understand the source and context? Did the review happen within the agreed window? Was the decision documented? Did the Veteran know what happened next? Could the program keep working when the usual person was out?
If the pilot can only prove that the graph appeared, it tested the porch light. It did not test the handoff.
From Handoff Design to VA Growth
Veterans should know whether they are sharing information for a later conversation or participating in a monitoring arrangement. Clinicians should know what responsibility they have accepted. Companies should be able to show who answers after the data arrives.
That is also a market question. A device may generate a useful signal, but VA still has to understand the Veteran use case, receiving workflow, staffing burden, purchasing path, evidence requirement, support model, and plan for scale. The product cannot carry that whole house on its back.
Industry, which event in your pathway turns arrival into somebody's awareness? VA leaders and clinicians, what information must accompany a wearable signal before it deserves space in the workflow? Product teams, can you show the complete route without using the word “integration” as a moving blanket?
JhetVet® helps medical device and health technology companies assess VA readiness, define the Veteran use case, map the stakeholders and purchasing path, build the implementation model, and stay involved through execution. Bring us the signal and the proposed workflow. We will help map the path forward before the porch light starts doing a job it was never hired to do.
Explore JhetVet® wearable health work, review how we operate, or start the conversation.
