Apple Health's Medications feature contains more than a list of names. A person may have a tracked medication, a schedule, a reminder, and one or more events logged as Taken or Skipped. Those layers answer different questions and should not be collapsed into one medication fact.

This guide maps the data model for an AI analysis. It uses synthetic examples only and keeps a recorded status separate from what happened clinically, so a summary can say what was logged without pretending to verify ingestion, absorption, or treatment effectiveness.

At a glance

What to keep in view

  • A medication in the list is a tracking definition, not proof that a dose was taken.
  • A schedule describes an expected time; a dose event describes what was recorded about a dose.
  • Taken, Skipped, Not Interacted, Not Logged, Snoozed, and Notification Not Sent have different meanings.
  • MCP is an optional third-party interface for a minimized, user-approved summary—not an Apple protocol or a HealthKit permission mechanism.

Four layers of medication data

The tracked medication is the item a person adds to Apple Health, including details such as name, type, strength, and optional schedule settings. It answers: what did the person choose to track? It does not prove a dose was taken on a particular day.

A schedule is an expected timing configured in Health. It can drive reminders and follow-up notifications, but it is not an observation. A dose event is a HealthKit record of a specific medication log. Interpretation is the later human or AI explanation of how those records relate, with uncertainty kept visible.

  • Medication definition: configured for tracking.
  • Schedule: expected timing according to the user's settings.
  • Dose event: a recorded status and quantity at a time.
  • Interpretation: a bounded explanation, not a clinical conclusion.

Dose status is not a binary adherence fact

HealthKit documents more states than Taken and Skipped. Taken means the person logged that they took the dose; Skipped means the person logged that they skipped it. Not Interacted means a scheduled reminder received no interaction, Not Logged means a previously logged status was undone, Snoozed means the reminder was postponed, and Notification Not Sent means the system could not deliver the scheduled notification.

Those states should remain attached to the original event timestamp. Notification Not Sent is a delivery problem, not evidence of a missed dose. Not Interacted is not the same as Skipped, and Not Logged does not prove that a dose never happened.

Scheduled and as-needed events need separate logic

HealthKit distinguishes scheduled and as-needed dose events. Apple's API documentation says scheduled events can carry a scheduled date, while an as-needed event does not have an expected schedule date to score as late or missed.

For a scheduled item, an analysis may compare the logged time with the configured schedule while preserving time-zone and schedule details. For an as-needed item, the record supports a narrower statement: an as-needed dose was logged at a particular time. It does not establish that taking it was clinically indicated.

Dose quantity remains a reported value

The dose quantity is the amount reported in the dose event. Apple documents that a scheduled event can default to the scheduled quantity when logged from a reminder; in the medication-tracking experience, an as-needed event defaults to one and can be edited.

That provenance is useful, but it is not pharmacy-dispensing data, laboratory evidence, or proof of absorption. Keep the quantity, unit, schedule type, and whether the value was edited visible in an export or model payload.

A synthetic timeline

The following values are invented and contain no real medication information. They show the narrow wording an AI should preserve.

  • Jan 1 — a person configured an example medicine with a daily schedule.
  • Jan 3, 08:00 — a dose was scheduled; at 08:07 it was recorded as Taken.
  • Jan 4 — the notification was not sent; dose-taking status is unknown.
  • Jan 5 — the person recorded the scheduled dose as Skipped.
  • Jan 6, 14:00 — an as-needed dose was recorded with a reported quantity of two.

What an AI analysis should preserve

Before summarizing medication activity, preserve the medication concept, strength and unit when present, schedule type and dates, dose-event status and timestamp, dose quantity, source app or device, object identifier, archive or undo state, time zone, extraction time, selected date range, and known gaps.

Useful outputs include a transparent timeline, counts by original status, and unresolved records. Avoid turning no event found into missed medication, reducing every non-Taken state to nonadherence, or generating a dosage recommendation from logs alone.

MCP may carry a minimized, user-approved summary to a compatible AI client. It does not grant HealthKit permission, increase measurement validity, or replace the person's control over which medication fields leave the device.

Privacy and medical boundaries

Medication names, strengths, schedules, and dose history are sensitive health data. Request only the fields and time window needed for the question. Prefer a selected medication or aggregate timeline when a complete history is unnecessary, and disclose external model processing, retention, deletion, and revocation behavior.

Apple's support documentation states that the Medications feature is not a substitute for professional medical judgment. This article does not diagnose, change a dose, recommend stopping a medication, or assess treatment effectiveness. Medication decisions belong with an appropriate clinician or pharmacist.

Use boundary

Information, not medical advice

This article explains data and research methods. It does not diagnose a condition, prescribe treatment, establish a universal normal range, or replace qualified professional care. If symptoms or a medical decision concern you, use an appropriate clinical service.