PATIENT GUIDE
How to Organize Wearable Health Data for a Doctor Visit
How to Organize Wearable Health Data for a Doctor Visit
How to Organize Wearable Health Data for a Doctor Visit
Organize wearable health data by source, metric, unit, date range, gaps, and context so your clinician can review the information without inferred conclusions.
Organize wearable health data by source, metric, unit, date range, gaps, and context so your clinician can review the information without inferred conclusions.
Organize wearable health data by source, metric, unit, date range, gaps, and context so your clinician can review the information without inferred conclusions.
Glass Health
For a routine doctor visit, organize your wearable data into a short, source-labeled view instead of bringing a pile of screenshots. Keep the original source, device, metric label, unit, date range, and any missing periods together, and keep the original source view nearby.
A review of wearable technologies for health research describes how measurements can vary across devices, algorithms, and collection conditions. That is why the source context matters when you prepare data for a clinician.
A wearable chart can help start a conversation, but it is not a diagnosis or a direct substitute for a clinical measurement.
Capture the basics before you connect or import anything
Before you connect data to another app or import it into an organizer, write down exactly what you are looking at.
| Capture this | What to write |
|---|---|
| Source | The app, export, or portal where the data came from |
| Device or wearable | The device used in that time window |
| Metric label | Copy the exact label from the source |
| Unit | Copy the exact unit shown |
| Time window | Start date and end date |
| Coverage | Missing wear time, missing dates, or partial data |
| Collection notes | Travel, schedule changes, manual entries, or other context that may affect collection |
| Visit question | One plain-language question for your clinician |
Use these sorting rules:
- New source, new line.
- New device, split the timeline.
- New label or unit, do not merge it with the old one.
- Unknown source, keep it separate and mark it as unknown.
If data passed through another app before you saved it, note both the original source and the app that passed it through.
Label gaps and changes directly
Missing data should stay labeled as missing. If part of the record synced late, disappeared, or came from a different device, say that plainly in the summary.
Useful labels include:
- not worn
- sync gap
- permissions changed
- source disconnected
- new device started on a specific date
- manual entries mixed with automatically collected data
Do not:
- fill in missing periods from memory
- treat missing data as zero
- smooth over a gap by averaging it away
- combine pre-change and post-change data without a note
If a period cannot be verified from the source, leave it marked as missing.
Keep the original source available
Your short summary is easier to trust when you can trace it back to the original source.
Save the original export, screenshot, or source view that shows:
- where the data came from
- the dates covered
- the label and unit
- any filters you used
- when you pulled the data
Bring the short view for discussion, and keep the original view available if your clinician wants to see what sits behind it.
Build a short visit snapshot
The first page only needs enough information to answer four questions quickly:
- What data is this?
- What dates does it cover?
- What limits should be kept in mind?
- What do I want to ask about it?
A compact snapshot can include:
- source, device, metric label, and unit
- the time window tied to the visit question
- missing wear time, source gaps, or device changes
- collection context you can verify
- one question for the visit
On the front page, include only the dates and context needed for the visit question, and keep the fuller source available in case it is needed.
Generic example
| Field | Example |
|---|---|
| Metric label | Exact metric label from your source |
| Source | Original source export or source view |
| Unit | Exact unit shown |
| Time window | Dates tied to the visit question |
| Coverage note | Missing wear time listed directly |
| Device note | Device changed on a specific date |
| Visit question | Is this source useful for this visit, and what context should I label next time? |
The useful interval depends on why the visit is happening and on what your clinician wants to review. If you are not sure which period matters most, keep the front page short and bring the longer original history so the fuller timeline is still available.
Compare like with like
Before you place two charts side by side, check:
- Are they from the same source?
- Do they use the same label?
- Do they use the same unit?
- Was the same device used?
- Was collection similar enough for the comparison to be understandable?
If any answer is no, keep both charts labeled and separate instead of blending them into one trend.
Questions that help at the visit
Questions are most useful when they stay focused on relevance and context.
You can ask:
- Is this data source relevant to the reason for today’s visit?
- Is this summary enough for discussion, or do you want the original source view?
- Do the gaps or device changes limit how useful this chart is?
- If I keep tracking this, what context should I label next time?
- Is there a time range you would want me to bring to future visits?
For more visit-planning prompts, see questions to ask your doctor.
Quick review before you go
Before the visit, check that your packet answers these at a glance:
- Which source am I looking at?
- Which device collected it?
- What is the exact metric label and unit?
- What dates does it cover?
- Are any days or nights missing?
- Did the device or source change during this period?
- Do I still have the original export or source view?
- Do I have one clear question for the visit?
If you are also organizing records, uploads, or lab information, pair this with how to organize medical records.
Use Glass for Patients
On a paid patient plan, Glass can connect wearable data from a source that appears in the current connection flow. Check that flow for current source and metric availability before relying on the connection.
To keep building your visit packet, start with the Patients hub, read how to use Glass for Patients, or Explore supported wearable connections.
Patient Service eligibility and limits
Glass for Patients is available to adults age 18 or older who live in the United States or its territories and have, and intend to consult, their own physician or other licensed health care provider before acting on information received through the Patient Service.
Glass for Patients provides general health information and educational support. It does not provide medical advice, diagnosis, treatment, clinical recommendations, urgent triage, or a substitute for a licensed clinician. Review the current Terms of Service.
Glass for Patients provides general health information and educational support. It does not provide medical advice, diagnosis, treatment, urgent triage, or a substitute for a licensed clinician.
Try Glass for Patients