Health

Search Health's medical-record provider directory using a concise provider name. Each query word must match the provider's name or description. Returns up to 25 providers with IDs, names, available descriptive and regional details, availability, and connectionState. hasMore indicates additional matches. Results are not ranked by match confidence. connectionState is connected, expired, not-connected, or unknown; unknown means connection status could not be verified. An unavailable field means the provider cannot currently be connected. A missing result does not establish that a provider is unsupported.

search_providers

Search RxNorm ingredient concepts for current-medication reconciliation.

search_medications

Subscribe to generation updates from the Health insights API.

subscribe_insights

Show options for connecting or reconnecting medical records or Apple Health. For an expired connection, reuse its organizationId from list_account_connections without searching. If recent tool results show the requested provider is already connected, answer in text instead. Otherwise, use search_providers once for a named provider; pass at most one returned ID whose name and available regional details clearly match. Omit organization_ids for no named provider, ambiguity, or search failure; "Add more" is always available for the user to search for and select a provider. For ambiguous matches, show generic options now and let the user choose in the picker. Call once; lookup failure already provides the fallback. Showing options does not connect records or confirm success. organizationSuggestions contains one result per requested medical provider, including failures: organizationId matches the input ID, status describes the outcome, and name is optional. An empty list means no provider was requested. Only status suggested offers a provider to connect; these results exclude Apple Health. For requested Apple Health data, set suggest_apple_health=true; otherwise leave it false. Do not search for an Apple Health provider. appleHealthSuggestionStatus is suggested (not connected), already-connected (no setup needed), or lookup-failed (unknown). isNativeIosClient describes this invocation, not Connect availability. For suggested Apple Health, when isNativeIosClient is false, tell the user to open this conversation in the ChatGPT iOS app to continue setup. Only when true, direct them to Apple Health above. Reply in 1–2 plain-language sentences focused on the user's next step. Ground any explanation in the conversation and tool results. - Suggested provider: direct the user to select its name above to sign in and give permission to share records with Health. Explain why you are suggesting this particular provider only if it helps the user; skip rationale for obvious matches. - Already-connected provider: say so; no setup is needed. - Otherwise, with no medical-provider suggestion and no Apple Health request: explain any uncertainty about which provider to use only if relevant, and direct the user to "Add more" above to search for their provider and choose the option matching their account. - Expired connection: explain that access has expired, then direct the user to "Reconnect" above to sign in again and restore access. Do not narrate your actions, use terms like "widget" or "card," or expose technical or implementation details. Avoid directing users to Health settings or the Accounts tab when the controls shown above support their next step.

show_connection_suggestions

Sync an active Health provider connection to fetch updated records, such as when a question concerns results newer than lastSyncTime. Get the connection ID and current status from list_account_connections. Only call this tool when connectionState is connected and operationStatus is idle. Expired connections require the user to reconnect first (call show_connection_suggestions with organization_ids=[organizationId] when available; otherwise direct the user to Health's Accounts tab). After syncing, check status and retrieve relevant records before answering. Success does not guarantee new or complete records. A timeout may mean syncing is still underway; avoid repeated retries. Does not support Apple Health.

sync_account_connection

Save only the specified changes to the user's Health profile. A clear explicit request to update the profile authorizes that change. For information merely shared in conversation, explain the proposed profile changes and get agreement before calling this tool. Clarify tentative statements, ambiguous items, or who the information concerns; do not save another person's conditions as the user's own. Read/resolve the section first and reuse the returned selections. Skip changes whose requested state is already user-confirmed: reply briefly in plain text without calling this tool. A matching candidate is already confirmed only when lastConfirmedAt is non-null and newSinceLastConfirmation is false. Also skip removals when the item is absent and there is no matching unresolved source suggestion. An imported candidate's selected default is not user confirmation; an explicit request can still confirm that candidate. The profile stores membership or currentness, not structured dose/frequency or family relationships. Pass only discussed items, once each. Unrelated confirmed decisions are carried forward. Call once per changed section. Valid requested changes save immediately and display a tappable receipt; unrelated imported records remain unreviewed. Briefly confirm what was saved; never claim failed or unchanged operations were saved. If has_unreviewed_imports is true, tell the user in your reply that they can open the profile update above to review the remaining items and save their choices. For example: 'Other medications from your health records haven't been reviewed yet. You can open the profile update above to confirm which ones you currently take.' The requested changes are already saved; reviewing the other items is optional.

update_health_profile

Replace one user-reported Health profile section after explicit user review. Selections are positive assertions; reviewed source references are reconciliation metadata, not negative clinical statements.

update_user_reported_health_section

Apple Health only: return the user's most recent synced static characteristics. This does not search provider medical records, clinical diagnoses, or user-reported reconciliation data. Use for static Apple Health characteristics, not metric discovery or historical analysis.

fetch_characteristics

Apple Health only: list which synced metrics actually have data, including each metric's available date range. This does not search provider medical records or user-reported reconciliation data. Use after `health_summary` when exact wearable metric availability or historical coverage is needed, then retrieve the relevant values with an Apple Health query action. Use the returned first and last dates to select separate recent and older windows for longitudinal questions; a day count, first/last date, latest value, or coverage metadata alone is not trend evidence. Use `view_all_metrics` only for the supported catalog and `fetch_characteristics` for static Apple Health characteristics.

view_synced_metrics

List the user's Health providers with their connection id, organizationId, connectionState (connected or expired), lastSyncTime, and operationStatus (idle, syncing, or deleting). Does not include Apple Health.

list_account_connections

Get one user-reported Health profile section with saved selections and current synced candidates.

get_user_reported_health_section

Get a summary of the authenticated user's Health resources grouped by organization and resource type.

resources_summary

General starting point for most questions about the authenticated user's connected health data. Returns a condensed cross-source snapshot that can include Apple Health or other wellness tracking data, connected provider medical records, and user-reported or reconciled conditions and medications when present. Start here before choosing a provider-record link or an Apple-Health-only action, unless the request is already limited to an exact Apple Health metric and date window. Do not treat a sparse summary as proof that detailed data are absent. If the question needs all values, exact counts, trends, correlations, or a period not represented in the summary, continue to the relevant detailed source before answering. Do not substitute a web search for connected Health data.

health_summary

Get a single health organization by organization ID.

get_organization

Open a Health link returned by a prior Health response for detailed analysis. Use this for connected provider or clinical records and other linked Health resources when the answer needs detail beyond the summary, including visits, labs, medications, imaging, notes, linked historical views, and ECG waveform links. A waveform link attaches the complete recording as JSON for Python inspection or plotting. Pass only a link returned by Health, except for the observation-detail template in the link parameter; do not invent a path. This is not the raw or custom-window Apple Health time-series interface. For all-results, count, range, average, older record, or longitudinal questions, open the returned full-history or collection link rather than stopping at latest/previous summary fields. Continue through additional relevant returned links in the same turn when one resource is insufficient. For charts, open a /records/detail view with response_format=genui. Observation detail includes the selected observation and bounded related history for its metric and coding system. Collection views (/observations, allResults, categories) have no chart series; use an observation's detail view instead of changing the collection's scope.

open_medical_resource