Monthly Oura health summary you can take to your doctor

By General Input

On the first of every month, turn 30 days of Oura ring data into a plain language summary in Google Docs and email you the link before your next appointment.

Integrations

  • Oura
  • Google Docs
  • Gmail

Type

Agentic Task

Categories

  • Personal Productivity

On the first day of every month at 8am, build a doctor ready health summary from my Oura data and email it to me so I have it in hand before my next appointment.

Gather my data from Oura. Pull the last 30 days using List Daily Sleep, List Daily Readiness, List Daily Resilience, List Daily Stress and List Daily SpO2, and use List Sleep Periods for the overnight detail on heart rate variability, resting heart rate and breathing. So that the report can show direction of travel, also pull the 30 days before that as a baseline, and compare the most recent 30 days against the preceding 30.

Do not dump raw numbers into the report. Summarise trends instead: monthly averages for each metric, the direction of travel versus the prior month including the size of the change, nights with unusually low blood oxygen or elevated breathing disturbance, and any resting heart rate or body temperature deviations that a clinician would want flagged. State how many nights of data each average is based on, so it is obvious when coverage was patchy and an average should be read with caution.

Create the report with Google Docs Create Document, titled with the month and year, then fill it in using Batch Update Document. Lay it out as a short plain language summary at the top that can be read in under a minute, followed by supporting sections and tables: a section per data stream, each with a table of monthly averages and the month over month change, plus a table of the individual nights worth mentioning with the date and what stood out about them.

Then email me the link to the document with Gmail Send a Message. Put the month in the subject line and include the plain language summary in the body, so I can read the headline version without opening the document.

Keep the tone factual and descriptive, and never diagnostic. Describe what the numbers did, not what they might mean medically, and do not suggest causes, conditions or treatments. This is a conversation starter for an appointment rather than medical advice, so where something is notable, frame it as a question worth raising with the doctor.

Blood oxygen and breathing disturbance are only recorded on Gen 3 and newer rings. If List Daily SpO2 comes back empty, degrade gracefully: skip that section with a short note that the data was not available, rather than failing the run or leaving an empty table. Handle missing nights in the other data streams the same way.

Related prompts

Explore more prompts
Win back LiveChat visitors whose chats went unansweredA searchable RFP answer library your bid team drafts fromRun your weekly Lever pipeline review and decide in the appChase the paperwork every new client and vendor still owesLinkedIn creator sourcing and vetting workbench for B2BFile Gmail attachments into storage with names you can findCandidate rediscovery desk for your archived Lever applicantsLaytime and demurrage claim workspace for chartering opsTurn outbound replies into objection themes you can fixVessel due diligence desk for pre-fixture screening