Doctor share.

The flow

1. Generate a code, pick a date range, optionally label the share.
2. The plaintext code is shown once. Hand it to your doctor — paper, message, in person, whatever you trust.
3. Your doctor opens app.mapigo.health/share in any browser and types the code.
4. The server checks the code, issues a short-lived session that only works under /share, and shows the summary.
5. You see the visit on the share’s access log.

What the doctor sees

Only readings inside the date range you chose. The summary includes mean systolic and diastolic, the at-or-under-target percentage, the AM/PM split, variability, and the chronological list. Notes are visible. If your notes mention “pre-dose” or “post-dose,” the means split a second way to show the difference.

The doctor can’t navigate out of /share. No link to your account, no way to see readings outside the range, no way to change anything.

What we guarantee

• The plaintext code is never written to the database.
• Wrong-code attempts are rate-limited. Repeated failures are recorded on your access log.
• The share pages are excluded from the service worker cache, so the doctor’s device retains nothing after the session.
• When you review who used your share, IP addresses are masked and devices are summarised to “Browser on OS.”

The access log

Every event on a share — created, redeemed, viewed, failed attempt, revoked, expired — is written to the access log with the masked IP and a summary of the device. The Shares screen shows the log so you can audit who used your code.

Common questions