You've worn your Apple Watch faithfully, collected weeks of heart-rate readings, and opened Cardiogram before a cardiology appointment. Then your clinician asks the simple question, “What has been happening?” The screen fills with spikes, episode rows, trend lines, and notes. Everything may be accurate, but the story is hard to see.
That's the gap report customization is meant to close. A patient reviewing patterns at home needs context and detail. A clinician reviewing a PDF needs a concise timeline, clear measurements, and relevant symptoms. A caregiver may need a simpler summary. The underlying data stays the same, but the presentation should change according to the decision each person needs to make.
This guide shows how to shape a Cardiogram report around an appointment, a symptom pattern, or a follow-up question. It also covers filtering, symptom context, PDF readability, privacy, and the small routine that keeps your reports useful over time.
Why Your Raw Heart-Rate Data Needs a Fresh Look
Raw heart-rate data answers one question, what did the watch record? A clinical report must answer several more: when did the episode occur, how high did the rate rise, how long did it remain high, what symptoms appeared, and what context might explain it?
That difference becomes obvious on appointment day. A patient may bring an unfiltered history containing ordinary fluctuations, activity-related changes, recovery periods, and episodes that felt completely different from one another. The clinician then has to separate meaningful patterns from background information while also listening to the patient's account.
A focused report doesn't replace your experience or your clinician's judgment. It gives both of you a shared reference point. Cardiogram analyzes Apple Health heart-rate data to identify tachycardic episodes and organize them into episode details, trends, and exportable summaries. You can learn more about the broader role of a digital health solution when you're deciding how much of your tracking routine belongs in an appointment workflow.
The same data serves different readers
At home, you may want to inspect every episode and compare symptoms across days. During a clinical visit, that level of detail can distract from the central question. Your clinician may need to determine whether episodes follow a consistent pattern, whether symptoms accompany them, and whether the available record supports further evaluation.
Think of report customization as editing, not hiding. You're selecting the evidence that best answers a defined question while keeping the underlying history available for deeper review if your clinician asks for it.
Practical rule: Build the report around the appointment question, not around everything your watch has ever recorded.
For example, a report for an initial discussion about possible orthostatic tachycardia may emphasize episode timing, baseline rate, peak rate, sustained duration, and linked symptoms. A follow-up report may place more attention on trends and changes surrounding a treatment or routine adjustment. Neither version is universally correct. The useful version is the one that helps your clinician understand what happened and decide what to ask next.
Selecting Time Ranges and Core Metrics
Start with the time range. A report covering your entire history may contain valuable information, but it can also make the current concern harder to locate. Choose a window that matches the appointment's purpose, such as the period since your last visit, the days surrounding a change in symptoms, or a recent stretch when standing-related episodes became more noticeable.
Before exporting, write down the question you want the report to answer. This prevents a common mistake, selecting every available metric because each one looks useful in isolation.
Match the window to the clinical question
Use a recent window when the appointment focuses on what's happening now. Use a broader window when your clinician needs to understand whether a pattern is recurring or changing. If you're unsure, prepare a focused version first and keep the larger history available rather than placing every row in the main document.
A practical selection sequence looks like this:
- Choose the relevant dates. Check that the start and end points cover the symptoms or treatment period you want to discuss.
- Review the episode feed. Confirm that the listed events belong to the selected window and that the timestamps make sense.
- Add the metrics that answer the question. Don't treat the export as a storage bin for every chart.
- Create a second version only when it has a distinct purpose. A symptom-focused report and a trend-focused report should each be easy to explain.
Put core measurements first
For a report about suspected orthostatic tachycardia, prioritize the episode-level measurements that show what changed and how long the change lasted. Cardiogram's detection feature records the baseline heart rate, peak heart rate, sustained duration, and time of occurrence, along with its stated detection rule. Those fields give your clinician a more useful starting point than a long collection of disconnected graph points.
Resting-heart-rate trends, weekly summaries, and heatmaps can provide context. They're supporting material, though, unless the appointment specifically concerns longer-term changes or patterns across days.
Ask yourself what your clinician is likely to do with each page. If the question is whether episodes repeatedly follow standing or occur alongside dizziness, the episode feed and symptom context deserve priority. If the question is whether your overall pattern has changed, a trend view may deserve more space.
You can also export a leaner version for a short appointment. Removing a chart that doesn't answer the current question isn't losing evidence. It's making the relevant evidence easier to find.
Applying Filters and Linking Symptoms
A heart-rate rise during a workout has a different meaning from a similar rise while you're standing in the kitchen. Your report needs enough context to keep those situations from appearing identical.
Cardiogram can exclude workouts and recovery periods from episode counts when those activities are recorded in Apple Health. Before preparing the report, check that activities such as running, swimming, yoga, or other exercise sessions have accurate start and end times. If an activity wasn't logged, the app may not have the context needed to distinguish exercise-related elevation from an episode that deserves discussion.
Clean the activity context first
Open your activity history and look for gaps around the dates you selected. You don't need to record every movement manually, but you should correct obvious omissions before exporting. A missing workout can create an apparent gap or leave your clinician wondering why a cluster of high readings appears during exercise.
Use this quick review:
- Check the activity record. Confirm that major workouts are present and timed correctly.
- Separate recovery from symptoms. Note whether the period after exercise feels like ordinary recovery or resembles your usual dysautonomia symptoms.
- Review suspicious clusters. If several episodes occur during a recorded workout, confirm how the report handles them before treating them as clinically comparable to resting or standing events.
- Keep your explanation ready. If a context is uncertain, label it as uncertain rather than presenting an assumption as fact.
Filtering isn't about making the episode count look smaller. It's about making each remaining event easier to interpret. For more background on reducing misleading readings, review Cardiogram's guidance on false-positive reduction.
Attach symptoms to the event
A timestamped symptom note changes the clinical value of an episode. “Elevated heart rate” is a measurement. “Elevated heart rate with dizziness and palpitations while standing” is a starting point for a conversation about circumstances, severity, and next steps.
Use the symptom and trigger logger to connect details such as:
- dizziness
- palpitations
- fatigue
- brain fog
- hydration
- salt intake
- sleep quality
- medication timing
Write notes in language you'll recognize later. Instead of recording only “bad,” try describing what you felt, what you were doing, and whether the symptom lasted beyond the heart-rate event. You don't have to create a perfect diary. A few specific entries can be more useful than vague notes attached to every episode.
For a new-diagnosis appointment, a symptom-focused report may help your clinician locate the events that affected your daily life most. For a routine follow-up, you may prefer a broader episode view with selected symptom examples. In either case, preserve the distinction between what the app measured and what you personally experienced.
Formatting Clinician-Ready PDF Summaries
The export is where your choices become a document someone else must read quickly. A clinician-ready PDF should make the main pattern visible without requiring the reader to decode crowded tables, inconsistent labels, or unexplained units.
Cardiogram's PDF report can state the detection criterion used and summarize episodes, trends, and logged context for clinical review. Treat the default export as a starting point. Review every page before sharing it, because a technically complete report can still be difficult to scan.
Build the page around the story
Public-health reporting guidance from the Agency for Healthcare Research and Quality recommends reducing cognitive burden by summarizing, interpreting, highlighting meaning, and narrowing options instead of exposing every raw data point. That principle applies well to a personal heart-rate report.
Arrange information in the order that helps the reader understand the issue:
- Begin with orientation. State the selected date range and identify the kind of information included.
- Show the central evidence. Place the relevant episode measurements where they're easy to locate.
- Add context afterward. Use trends, heatmaps, and symptom notes to explain the pattern rather than burying the episode details.
- Keep interpretation separate from measurement. Your note about dizziness is not the same thing as the recorded heart-rate value.
The same guidance recommends white space or light highlighting to separate rows and columns, removing gridlines when possible, using graphs instead of color-coded cells, and applying bold or italics sparingly. Right-justified numbers are easier to compare because the values align. Plain-language labels, explicit units, and minimal decimals also reduce the mental work required to understand the page.
Perform a final scan
Look for labels that assume too much. A reader shouldn't have to guess whether a value represents beats per minute, a duration, or a percentage. If a section feels cramped, narrow the date range or remove a metric that doesn't support the appointment question.
A useful test is to hand the PDF to someone who hasn't seen your tracking history. Can they identify the period covered, the relevant episodes, the symptoms attached to them, and the question you want answered? If not, revise the export before sending it.
You can also review Cardiogram's information about its Apple Watch heart-rate app as you decide which parts of your watch history belong in a clinician-facing summary. The aim isn't visual polish for its own sake. It's a document that lets your clinician spend the appointment discussing your health rather than reconstructing your spreadsheet.
Managing Privacy and Export Settings
Privacy should shape report customization from the first selection, not only at the moment you tap share. A report may contain heart-rate history, symptoms, medication notes, and details about daily routines. Decide what each recipient needs before you export.
Cardiogram describes its analysis as on-device, with syncing through iCloud and read-only Apple Health access. That approach keeps the analysis within your Apple ecosystem, but it doesn't remove your responsibility for the exported file. Once you save or send a PDF, its privacy depends on where you store it and who can access it.
Create different sharing layers
A clinician may need detailed episode measurements and medication context. A family member helping you prepare for an appointment may only need dates, symptoms, and a concise timeline. Sharing the same full report with everyone increases disclosure without necessarily improving support.
Before exporting, review:
- The date range. Remove unrelated periods.
- The metric list. Include only measurements that serve the recipient's purpose.
- Symptom and medication notes. Decide whether each category belongs in that specific copy.
- The destination. Save the file locally first if you want to inspect it before forwarding.
- The final recipient list. Check email addresses or message recipients carefully.
Twilio's 2025 customer engagement findings describe a perception gap in personalization, with 84% of businesses reporting good or excellent personalized engagement compared with 54% of consumers who agree. Although that research concerns engagement rather than clinical reports, the broader lesson is relevant: personalization should reflect the recipient's actual needs, not the sender's confidence that more information is better.
Privacy habit: Export a local draft, read it as the recipient would, and share only the finalized version.
Troubleshooting Common Issues and Best Practices
A report can look incomplete for several different reasons, and each one calls for a different fix. Don't immediately assume that a missing episode means your watch failed or that the app lost your data.
Start with the activity record. Cardiogram's filtering depends on workout and recovery context from Apple Health, so an unlogged activity can create an apparent gap or change how an elevated period is classified. Check the dates around the missing information and confirm that the relevant activity was recorded with a sensible start and end time.
Diagnose the problem before re-exporting
Sync timing can also create temporary differences between what you expect to see and what appears in the report. After a period of heavy watch use, allow the Apple Health and Cardiogram records time to update before creating the final PDF. If the report still looks wrong, compare a specific timestamp rather than reviewing the entire history at once.
A sparse symptom log often has a simpler explanation. Check whether the entry was saved on the correct date and close enough in time to the episode you intended to annotate. A note placed at the wrong time may fail to connect with the event even though the note itself still exists.
Use this troubleshooting order:
- Verify the date window. The event may fall outside the selected range.
- Check synchronization. Compare recent readings after allowing the records to update.
- Inspect activity context. Look for workouts or recovery periods that explain the apparent omission.
- Review symptom timestamps. Correct entries that don't align with the episode.
- Export again and compare. Change one setting at a time so you know which adjustment affected the result.
Keep a clinical note beside the report
A monthly review can reveal details that a single PDF won't. Record what you noticed, such as whether symptoms appeared after poor sleep, whether medication timing seemed relevant, or whether better hydration coincided with a different experience. Treat these as observations to discuss, not conclusions that the report has proven.
Over several export cycles, your notes and reports can form a longitudinal record. That record gives your clinician more context than one stressful appointment-day recollection, while still leaving room for medical interpretation.
Building a Sustainable Report Customization Routine
Report customization works best as a repeatable habit rather than an emergency task before an appointment. A consistent routine lets you catch missing context while the dates are still familiar and gives your care team a clearer record to review.
Choose a recurring day for a brief check. Select a relevant recent window, inspect the activity and symptom context, and export a version that matches your current purpose. You don't need to create every possible variation each time.
Start with one dependable format
A simple monthly routine can include:
- Review the recent period. Confirm that the dates match what you remember.
- Check the episode feed. Look for unexplained gaps or events that need context.
- Add meaningful notes. Link symptoms and triggers while the experience is still clear.
- Prepare the appropriate version. Use a focused clinical report for an upcoming visit and a simpler personal view for home review.
- Store it deliberately. Keep finalized reports in a place you can find without sending multiple drafts to your clinic.
As your appointments become more specific, your configurations can become more specific too. A symptom-focused version may help during a difficult flare. A trend-focused version may suit a routine follow-up. A minimal summary may be easier to discuss during a short check-in.
The important shift is from collecting data to curating evidence. Your Apple Watch history is a record of measurements. Thoughtful customization turns selected measurements, symptoms, and context into a story your clinician can question and use.
Return to your settings each month, especially after your care goals change. A report designed for an initial evaluation may not be the right report for treatment follow-up. Keep asking one practical question: What does my clinician need to see to understand this period accurately?
Cardiogram turns Apple Watch heart-rate data into structured episodes, trends, symptom context, and exportable PDF summaries that you can tailor for a clinical appointment. Visit Cardiogram to explore the app and start building reports that are focused, shareable, and aligned with the questions you want to discuss with your care team.
