Monthly Oura Health Report for Doctor Appointments

PromptCreate

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.

Example output

July 2026 summary Across 28 of 31 nights with data, your average sleep score was 74, down 4 points from June. Average resting heart rate was 58 bpm, up 2 bpm on the previous month, and average HRV was 42 ms, down from 46 ms. You averaged 6 h 51 m asleep, roughly 20 minutes less than June. Readiness averaged 71, down 3 points. Body temperature ran above your own baseline on 4 nights, all in the week of 14 July, alongside the lowest readiness scores of the month. Blood oxygen averaged 96 percent. Three nights came in below 94 percent (2, 3 and 17 July), and breathing disturbance was higher than your monthly typical on those same three nights. Things you may want to raise at your appointment: the rise in resting heart rate alongside the fall in HRV, and the cluster of nights with lower blood oxygen.

What does this prompt do?

Runs automatically on the first day of every month and looks back over your last 30 days of Oura ring readings.
Turns six streams of data (sleep, readiness, resilience, stress, blood oxygen, and overnight heart and breathing detail) into trends instead of a wall of numbers.
Shows what changed since the month before and points out individual nights that stood out, so you have specific things to ask about.
Writes it into a Google Doc with a short summary at the top and supporting tables below, then emails you the link.

What do I need to use this?

An Oura account and a ring you have been wearing regularly.
An active Oura membership. Without one, no data comes back through the connection.
A Google account, for creating the document and sending the email.
The email address you want the monthly summary delivered to.
A Gen 3 ring or newer if you want the blood oxygen and breathing section. Older rings still get everything else.

How can I customize it?

Change the timing. Monthly on the 1st is the default, but you can run it quarterly, or a week before a scheduled appointment instead.
Change who receives it. Send it just to yourself, or copy a partner, carer, or family member.
Change what it covers. Add sections like daily activity and steps, or narrow it down to sleep and resting heart rate only.
Adjust what counts as worth flagging, such as how far a reading has to move before it gets called out.

FAQs

Is this medical advice?

No. The summary is written to be factual and descriptive: it says what your numbers did and how they changed, and nothing about what that might mean. It is meant as a conversation starter to bring to an appointment, not a diagnosis or a substitute for talking to a clinician.

Do I need a particular Oura ring?

Any ring works for the sleep, readiness, resilience, and stress sections. Blood oxygen and breathing detail are only recorded on Gen 3 and newer rings, so if you have an older one the report simply notes that the section was unavailable and carries on.

What happens on nights I did not wear my ring?

Gaps are fine. Averages are based on the nights that actually have data, and the report tells you how many nights it used, so you can see when a month was patchy rather than being misled by a thin average.

Will my doctor accept this?

Treat it as background you bring along, not a clinical record. It is consumer wearable data, and the value is that you arrive with specific dates and trends to point at instead of trying to remember how you have been sleeping.

Where does the report end up?

It is created as a document in your own Google Drive and the link is emailed to you. Nothing is shared with anyone else unless you add them as a recipient or share the document yourself.

Related templates

Trace phishing emails to the sending IP and report abuse

Every 15 minutes, forwarded phishing reports get traced back to the server that really sent them, with a verdict in Slack and the worst senders reported.