Use Personalized Summaries in ChatGPT Health: Connect Records, Select Charts, Verify Trends, Manage Memory, and Disconnect Data

What changed on September 28: Health can explain a selected chart, metric, or record

OpenAI’s September 28, 2026 release notes say ChatGPT added personalized explanations and insights in the Health tab when an eligible user selects a chart, metric, or record. In practical terms, the update changes the workflow from “type a broad health prompt and paste context” to “choose a specific connected item and ask ChatGPT Health to explain what it is looking at.” That distinction matters because health records are full of dates, units, reference ranges, duplicate labels, and missing intervals; a useful summary begins with the exact item selected, not with a generalized medical question.

This tutorial treats the new personalized-summary feature as a record-organization and question-preparation tool. You can use it to summarize a lab panel, explain what a metric represents, compare a visible trend against the dates and units shown in your connected source, and prepare a concise question list for a licensed professional. You should not use it to diagnose yourself, decide whether to start or stop treatment, change medication doses, forecast your medical risk, triage an emergency, or replace care from a qualified clinician. OpenAI states that Health is designed to support, not replace, medical care and is not intended for diagnosis or treatment.

Availability is narrower than “everyone with ChatGPT.” According to OpenAI’s Health help article, Health is rolling out to eligible logged-in Free, Go, Plus, and Pro users in the United States who are 18 or older, on web and iOS. Connecting Apple Health requires an iPhone. Current behavior can vary by account, app, region, rollout state, and workspace policy, so a missing Health tab or unavailable connector does not necessarily mean your account is misconfigured.

The supported connected sources identified by OpenAI are user-authorized Apple Health data, supported U.S. provider records, One Medical, and Function Health. The feature can use these connected records when you authorize access and select a chart, metric, or synced record. OpenAI also notes that users may invoke Health with @Health when they want connected data applied in a conversation. The key operational rule is simple: connect only sources you intentionally want ChatGPT Health to read, and do not assume the system has context from a provider portal, wearable, PDF, image, or app unless that source is actually connected or you have provided the relevant information in a safe, minimal way.

OpenAI’s Health article also sets an important data-direction boundary: ChatGPT can read connected records, but it cannot write back to Apple Health or provider records. That means a summary cannot modify your chart, correct a lab value, update a medication list, add a diagnosis, or send a message to your clinician. If you discover a mismatch, the corrective path is to verify the original source and then contact the provider, lab, health system, or device source through its official process.

This guide covers ChatGPT Health permissions and privacy across Apple Health, medical records, memories, disconnects, and workspace boundaries. The ChatGPT Health Permissions and Privacy Guide: Apple Health, Medical Records, Memories, Disconnects, and Workspace Boundaries article is a focused companion for ChatGPT Health Data Controls because it is the strongest match for a marker about Health data controls because it directly addresses permissions, privacy, memory handling, and disconnect behavior for ChatGPT Health.

Who this tutorial is for, and what it deliberately does not do

This tutorial is for eligible adults who want a privacy-first way to organize their own connected health information before an appointment, annual physical, specialist visit, caregiver discussion, benefits conversation, or personal record review. It is also useful for knowledge workers, parents helping an adult family member with consent, educators building health-literacy examples, legal-technology professionals thinking about sensitive-data workflows, and enterprise administrators who need to understand why consumer Health is not the same as a clinical deployment.

The tutorial does not provide medical advice. It does not interpret your symptoms, choose a diagnosis, recommend a treatment plan, calculate personalized risk, advise dosage changes, or determine whether a situation is an emergency. If you may be experiencing an emergency or a time-sensitive health issue, seek immediate professional help through local emergency services, urgent care, your clinician’s instructions, or another qualified real-world medical resource. A chatbot explanation of a record is not a safe substitute for emergency triage.

The safest use pattern is to turn raw records into a structured preparation packet: what was selected, what the original source says, which dates and units are involved, what changed over time, what data appears to be missing, what the explanation says with uncertainty labels, and which questions you want to ask a professional. That workflow is especially helpful when a portal contains multiple documents with similar names, a wearable chart has gaps, a lab report uses a reference range you do not recognize, or a provider record contains abbreviations you want explained before a visit.

Every workflow in this article uses four verification habits. First, check the original record, chart, or metric rather than relying only on the generated explanation. Second, preserve dates, units, and reference ranges because a number without its measurement context can be misleading. Third, note missing data, device gaps, duplicate records, and uncertain source provenance. Fourth, separate observation from interpretation: “the selected chart shows fewer recorded sleep hours last week” is an observation; “therefore I have a sleep disorder” is a medical interpretation that requires professional evaluation.

Supported versus not supported: use the right boundary before you connect data

The table below summarizes what OpenAI’s sources support for this tutorial and what remains outside the safe or stated scope. Use it as a pre-flight checklist before connecting a source or asking for an explanation. If your intended use lands in the “not supported” column, reframe it as record organization, ask a licensed professional, or use the official healthcare or provider process instead.

The privacy-first mental model: select less, verify more, share nothing unnecessary

A good Health workflow starts with data minimization. Connect the source you need for the task at hand, select the smallest relevant chart, metric, or record, and ask for an explanation that preserves source context. Do not connect every possible source just because a connector is available. A focused lab report, one metric trend, or one provider record is easier to verify than a broad cross-source request that blends data with different collection methods, date ranges, and reliability levels.

OpenAI’s Health Privacy Policy and Health help article state that connected medical records, Apple Health information, and conversations that use them are not used to train foundation models or target ads. That is an important first-party commitment, but it should not be read as permission to be careless with sensitive health information. Your own operational risk still includes who can access your device, whether you save screenshots, whether you export conversations, whether you paste content into unrelated tools, and whether you allow third-party apps or integrations to access conversation context.

For this tutorial, do not post screenshots of your charts, lab reports, provider notes, medication lists, or wearable data in public forums or workplace channels. If you need help from a clinician, use the clinician’s preferred secure communication method. If you need help from a caregiver or family member, share the minimum necessary information with consent and avoid forwarding full records when a short question or appointment agenda would suffice.

The safest output from ChatGPT Health is not “the answer.” It is a structured note that helps you ask better questions: “The selected record appears to be a lipid panel from March 12, with values shown in mg/dL and a reference range printed by the lab. ChatGPT’s explanation says the report includes total cholesterol, HDL, LDL, and triglycerides. I need to ask my clinician how to interpret this in light of my history and whether any follow-up is needed.” This framing preserves context without turning an AI summary into medical decision-making.

Example opening workflow: from connected record to appointment question

The following example is a safe workflow pattern, not medical advice. It shows how to use the September 28 personalized-summary behavior for organization and verification. Replace the record type with your selected item, and stop before any step that would ask ChatGPT to diagnose, prescribe, predict risk, or decide urgency.

1. Choose one source intentionally. Connect only the Apple Health, supported provider, One Medical, or Function Health source you need for the review. If the source is unavailable in your account, use the official portal directly instead of trying to bypass the limitation.
2. Select one chart, metric, or synced record. Choose a bounded item such as a visible metric trend, a lab report, a visit summary, or another synced record. Avoid starting with an open-ended request across your entire medical history.
3. Read the original context first. Note the record title, source, date, measurement unit, reference range if shown, and any obvious missing interval. If a metric comes from a wearable or device, check whether there are days with no data.
4. Request a plain-language explanation. Ask ChatGPT Health to explain what the selected item contains and to keep observations separate from interpretations. If the contextual explanation appears automatically, still ask it to identify the source date and units it is using.
5. Compare the explanation with the original. Confirm that numbers, dates, labels, and ranges match the source. If anything differs, treat the original record as the authority and mark the explanation as uncertain.
6. Draft questions for a professional. Ask for neutral questions you can bring to your clinician, such as “What does this result mean in my overall context?” or “Do I need any follow-up testing?” Do not ask for a diagnosis or treatment decision.
7. Control what remains in ChatGPT. Decide whether to keep the conversation, delete it, use Temporary Chat for future sensitive reviews, adjust memory settings, or disconnect the source after the task is complete.

This article explains ChatGPT Health’s medical records integration, including its launch context, mechanics, implications, and privacy landscape. The ChatGPT Health Launches: How OpenAI’s Medical Records Integration Changes Personal Healthcare in 2026 article is a focused companion for Medical Record Verification because it fits medical record verification because the current tutorial discusses connecting and checking medical records, and this target specifically focuses on ChatGPT Health medical-record integration.

Safe starter prompts for personalized summaries

The September 28 update can provide contextual explanations without a typed prompt when you select a chart, metric, or record, but careful prompts still help enforce boundaries. The safest prompts ask for organization, source checking, uncertainty, and professional follow-up questions. They do not ask ChatGPT to decide what condition you have, what treatment to take, whether a medicine is safe for you, or whether symptoms are urgent.

Prompt: explain a selected record without diagnosing

I selected this Health record for organization before a medical appointment. Please explain what type of record it appears to be, identify the source date, units, and reference ranges shown, and summarize only what the record says. Separate observations from possible interpretations, label uncertainty, note any missing data, and suggest neutral questions I can ask a licensed professional. Do not diagnose, recommend treatment, recommend dosage changes, predict my risk, or decide urgency.

This prompt works because it makes the output auditable. It asks ChatGPT Health to anchor the summary to visible record details, preserve units and dates, flag missing data, and produce appointment questions rather than medical conclusions. If the answer omits the original date, unit, or reference range, ask it to revise the summary using only those source details that are actually present.

Prompt: review a selected metric trend conservatively

I selected this Health metric trend. Please describe the visible trend over the selected date range using the chart's dates and units. Identify gaps, unusually sparse periods, or possible device/source limitations if they are visible. Do not infer a diagnosis or medical cause. End with a short list of questions I could ask a clinician if I am concerned about the trend.

This trend prompt is intentionally conservative. Wearable and health-app metrics can be affected by device usage, sync gaps, manual edits, sensor limitations, and changes in behavior or environment. A safe summary says what the chart shows and what is unknown; it does not convert a consumer metric into a clinical conclusion.

Prompt: prepare a visit agenda from one selected item

Using only the selected Health record, help me prepare a brief visit agenda. Include: 1) the record name and date, 2) the key values or sections with units and reference ranges where shown, 3) items I should verify in the original portal, 4) missing context that may matter, and 5) five neutral questions for my licensed professional. Do not provide diagnosis, treatment, dosage, or emergency guidance.

This prompt is useful when you are trying to make a short appointment more productive. It helps convert a record into a checklist while preserving the clinician’s role. If you need to send questions to a provider, review and edit the text yourself, remove unnecessary personal details, and use the provider’s official communication channel.

Why original-record verification is mandatory

Health records often contain repeated names, overlapping panels, amended results, multiple time zones, different units, and reference ranges that depend on the lab, age, sex, method, or clinical context. A generated explanation can help you understand labels and organize questions, but it should never become the source of truth. The source of truth is the original provider record, lab report, device chart, or connected source display, plus the judgment of qualified professionals who understand your context.

Before acting on any summary, perform a five-point verification. Confirm the record date; confirm the source organization or device; confirm the units; confirm the reference range or note that none is shown; and confirm whether all expected data is present. If any of those checks fail, write “unverified” beside the summary and avoid using it for decisions. If the record appears wrong, contact the original source rather than asking ChatGPT to “fix” the record.

Be especially cautious with trends. A metric that appears to rise or fall can reflect changed measurement frequency, a new device, a gap in syncing, a different lab method, travel, time-zone differences, or missing days. A safe trend summary says, “The selected chart shows a change during this date range,” then asks what additional context is needed. It should not say, “This means you have a condition,” or “You should change treatment.”

The same caution applies to reference ranges. A number can be marked high or low by one lab and not by another, and reference ranges are not the same as personalized clinical targets. Ask ChatGPT Health to report the reference range shown, not to invent one. If no reference range is visible, the summary should say that the range is not shown in the selected record.

Memory, Temporary Chat, and apps: privacy controls you must plan before sensitive reviews

OpenAI’s memory FAQ states that ChatGPT can remember information when memory is on, and OpenAI’s Health help article clarifies the Health-specific boundary: memories are not created directly from synced data, but Health conversations can create memories when memory is on. The practical takeaway is that connected source data is not supposed to become a memory by itself, but statements you make during a Health conversation may still be eligible for memory behavior if memory is enabled.

If you are discussing sensitive health context that you do not want carried into future chats, consider using Temporary Chat where available. OpenAI’s Temporary Chat FAQ describes Temporary Chat as a way to have a conversation that will not appear in chat history and will not use or create memories, subject to OpenAI’s stated retention and safety practices. Use this for sensitive record-review preparation when you do not need the conversation saved for later.

Projects and workspace settings can add another layer of behavior, including project-specific memory where available. Do not assume a family member’s account, a workplace account, a school account, or a managed workspace behaves like your personal account. Administrators and policy owners may configure access differently, and Health availability itself may vary. When in doubt, do not put health information into an account you do not personally control or into a workspace governed by someone else’s policy.

OpenAI’s apps-in-ChatGPT documentation is also relevant because apps can involve permissions and data sharing with third-party services. Health data is sensitive, so review app permissions before using any app in the same conversation context as health information. Do not ask an app to process medical records unless you understand what data it receives, why it needs that data, and whether you have authority to share it. Human approval is mandatory before sending external messages, uploading sensitive records to third parties, booking appointments, making purchases, submitting forms, or taking any consequential action.

Disconnecting is not the same as deleting every conversation

OpenAI states that disconnecting a Health source causes synced source data to be deleted from OpenAI systems within 30 days. That is a source-level control: it addresses the synced data from the connected source. OpenAI also states that information already present in conversation history remains until those conversations are deleted. Therefore, a safe cleanup process has two parts: disconnect the source you no longer want synced, and separately review conversations that contain health information.

Use a clear decision rule. If you connected a source for a one-time appointment-preparation task, consider disconnecting it after you finish and save only the notes you truly need in a secure place you control. If you expect to review trends over time, leave the source connected only if the convenience outweighs the privacy and account-access considerations. If you used Health in a conversation that includes sensitive details, decide whether to delete that conversation, keep it for continuity, or use Temporary Chat next time.

Do not treat disconnection as an emergency privacy eraser. The deletion window OpenAI states for synced source data is within 30 days, and conversation history is separate. If you accidentally included sensitive information in a chat, review the relevant ChatGPT data controls and delete the conversation if appropriate. If the information was also sent to a third-party app, exported, screenshotted, emailed, or copied elsewhere, you must handle that location separately because disconnecting the Health source does not control downstream copies you created.

Opening checklist: the safe way to begin

Before moving into the step-by-step connection and summary workflow, use this opening checklist. It keeps the task inside the intended Health boundary and reduces the chance that a useful explanation becomes an unsafe medical decision.

• Eligibility check: Confirm you are an eligible logged-in adult user in the United States on a supported surface, recognizing that rollout and account behavior can vary.
• Source check: Use only supported connected sources identified by OpenAI: Apple Health with an iPhone, supported U.S. provider records, One Medical, or Function Health.
• Minimum data check: Connect only the source needed for the immediate record-review task.
• Selection check: Select a specific chart, metric, or synced record rather than asking broad questions across your entire history.
• Verification check: Record the original source, date, unit, reference range if shown, and missing-data notes before relying on any explanation.
• Boundary check: Ask for plain-language explanation, trend organization, and professional questions; do not ask for diagnosis, treatment, dosage, risk prediction, or emergency triage.
• Memory check: Decide whether memory should be on, whether Temporary Chat is more appropriate, and whether the conversation should be saved.
• Permission check: Review app and third-party permissions before using any app around health data.
• Cleanup check: If the task is complete, decide whether to disconnect the source and delete conversations containing health information.

Operational warning: A personalized Health summary can make a record easier to understand, but it does not validate that the record is complete, clinically interpreted, or safe to act on. Treat every summary as a preparation aid until the original record and a qualified professional’s guidance support the next step.

CE113 medical-use boundary: Health is designed to support, not replace, medical care and is not intended for diagnosis or treatment. For urgent symptoms or emergencies, seek immediate professional help rather than relying on a generated summary.

Connect the minimum necessary health source

Start this workflow only if you are an eligible logged-in adult user in a supported rollout context, because OpenAI says Health is rolling out to eligible Free, Go, Plus, and Pro users in the United States who are age 18 or older on web and iOS, and that Apple Health connection requires an iPhone. If Health is not visible in your account, do not attempt to bypass age, region, app, workspace, provider, or account controls; availability can vary by plan, rollout, device, and policy.

Recommendation: before connecting anything, decide the single question you want the summary to help you understand. A narrow question such as “What does this lab result show compared with the reference range printed on the report?” requires less data than a broad request such as “Analyze my health,” and it is easier to verify against the original record. Health is designed to support, not replace, medical care, and OpenAI states it is not intended for diagnosis or treatment.

1. Open ChatGPT in a supported context. Use the web or iOS app where Health is available to your account. If you are using a work, school, or managed device, check whether workspace policy restricts apps, connectors, memory, or health-related data use before proceeding.
2. Open Health. Use the Health tab or the Health entry point that appears in your ChatGPT interface. Product labels and placement may change during rollout, so rely on the official in-product flow rather than a third-party screenshot.
3. Choose one source category at a time. OpenAI says Health can use user-authorized Apple Health data, supported U.S. provider records, One Medical, and Function Health. Select only the account or source needed for your current task, rather than connecting every available record source at once.
4. Confirm that the account is yours or that you are authorized to use it. Do not connect another adult’s provider portal, Apple Health data, or lab account unless you have clear authorization and the account flow permits it. Do not connect a child’s records for experimentation or convenience; this tutorial is written for eligible adults using their own selected records.
5. Review the authorization screen slowly. Check the source name, account identity, categories of data requested, and whether you are granting access to provider records, Apple Health information, lab records, metrics, or other categories shown by the source. If the authorization page presents broader categories than your question requires, stop and reconsider whether you need that source.
6. Approve only the selected account. If the source shows multiple profiles, organizations, portals, family members, or accounts, choose only the one that matches your intended review. A common operational mistake is authorizing a household account, old provider portal, or secondary profile because it appears first in a list.
7. Wait for sync to complete. Health summaries depend on synced data being available inside the Health experience. Do not assume a chart is complete immediately after connection; newly connected sources may need time before records, dates, and metrics are visible.
8. Look for obvious sync boundaries. Before asking for an explanation, identify what appears to be present and absent: old records, recent visits, lab reports, device metrics, medication lists, vitals, activity data, or provider documents. Missing intervals are not medical trends; they may simply be sync gaps.

Operational warning: ChatGPT cannot write back to connected Apple Health or provider records according to OpenAI’s Health documentation. Treat Health as a reading and explanation surface, not as a record-correction, chart-editing, prescription, appointment, claim, or patient-portal submission tool. If a record is wrong, the correction path remains the original provider, device, lab, or health-data source.

This article explains multi-account plugin governance in ChatGPT, including source attribution, account selection, action approvals, and auditability. The Multi-Account Plugin Governance in ChatGPT: Source Attribution, Account Selection, Action Approvals, and Auditability article is a focused companion for Plugin Permission Review because it is semantically appropriate for reviewing plugin permissions because it focuses on how ChatGPT plugins should be governed, attributed, approved, and audited across accounts.

Permission review table before you authorize a source

Use this table as a conservative review checklist. It is not a legal or clinical consent form; it is a practical way to avoid over-connecting data when a narrower source would answer the question.

Select one chart, metric, or record before asking for an explanation

OpenAI’s September 28 release-note entry says ChatGPT added personalized explanations and insights when an eligible user selects a chart, metric, or record in the Health tab. The safest way to use that capability is to select a single item, ask a bounded explanation question, and verify every claim against the original source before relying on it for a conversation with a clinician.

Procedure: after sync, choose one item that directly relates to your question. For example, select one lab panel, one blood pressure chart, one sleep metric, one activity metric, one visit record, or one provider result. Avoid selecting a bundle of unrelated records and asking for a broad interpretation, because broad prompts make it harder to separate data extraction from interpretation.

1. Open the Health view that contains the item. Navigate to the chart, metric, or synced record you want to review. The exact layout may differ by device, account, rollout, and source.
2. Select the chart, metric, or record. Use the in-product selection behavior available to your account. OpenAI says users can select an item and receive a contextual explanation without typing a prompt, when the feature is available.
3. Read the generated explanation as a draft aid. Treat the response as a plain-language summary that must be checked, not as a diagnosis, treatment recommendation, risk prediction, or replacement for professional care.
4. Optionally invoke Health explicitly with @Health. If you are in a conversation and want connected data applied, OpenAI says Health may be invoked with @Health. Use this only when you intend the response to use connected Health data.
5. Ask for citations to the selected item’s details. Request that ChatGPT distinguish what it read from the record from what it is explaining in general terms. Do not ask it to infer missing facts, fill gaps, or decide treatment.

Example request after selecting a record:

Explain the selected Health record in plain language without diagnosing me.
Separate:
1. Facts visible in the selected record.
2. General background that may help me understand those facts.
3. Items I should verify in the original source.
4. Neutral questions I can ask a licensed clinician.

Do not recommend treatment, dosage changes, emergency triage, or risk predictions.

Example request after selecting a metric chart:

@Health Please summarize the selected metric chart conservatively.
Identify the date range, unit, apparent high and low points, and any missing intervals you can see.
Do not call this a medical trend unless the underlying record is complete enough to support that wording.
List what I should check in the original app, device, provider portal, or lab report.

Example request for a provider record:

Using only the selected synced record, help me prepare for a clinician conversation.
Create a non-diagnostic summary with:
- record source and date to verify
- values and units to verify
- reference range shown in the original record, if present
- what is unclear or missing
- five neutral appointment questions

Do not infer a diagnosis or treatment plan.

Choose the right item type for the question

Different Health items carry different verification burdens. A lab result usually has a collection date, result date, value, unit, and reference range. A device metric may have sampling gaps, device changes, algorithm updates, manual entries, or app-specific scores that may not transfer into Health. A provider note may include context that is difficult to summarize safely without the full original document.

Verify the original source before you trust a summary

Verification is mandatory because a personalized summary can only be as reliable as the synced item, the visible context, and the user’s understanding of what transferred. The goal is not to prove ChatGPT wrong; it is to avoid turning a partial sync, unit mismatch, missing interval, or app-specific score omission into a medical conclusion.

Verification rule: every Health explanation should be checked against the original record, date, unit, reference range, source, missing intervals, device changes, and whether app-specific scores transferred. If any of those cannot be verified, the summary should remain an observation draft, not a conclusion.

Original-record verification workflow

1. Open the original source. Use the provider portal, Apple Health source, device app, lab portal, One Medical, Function Health, or other source shown in the Health connection flow. Do not rely on screenshots shared by someone else.
2. Confirm the record title. Match the selected item to the original record name, panel name, metric name, note type, visit type, or source label.
3. Confirm the date. Record the collection date, result date, encounter date, measurement date range, or chart period. For labs, collection date and result date may differ. For wearable metrics, a chart may aggregate multiple days or weeks.
4. Confirm the unit. Units can change the meaning of a value. Do not compare two values unless the unit is the same or a qualified professional has confirmed how to convert them.
5. Confirm the reference range if present. Reference ranges can vary by lab, method, age, sex, pregnancy status, and other context. Use the range printed on the original report rather than a generic internet range.
6. Confirm the source. Identify whether the item came from a provider, a lab, Apple Health, a device, a manually entered value, One Medical, Function Health, or another connected source shown in your account.
7. Mark missing intervals. For charts and metrics, note days, weeks, or months with no data. Missing data should be labeled as missing, not normal, abnormal, improved, or worsened.
8. Check device or app changes. If you changed phones, watches, apps, scales, cuffs, sleep trackers, or data sources, mark the date of the change. A device transition can look like a trend even when physiology did not change.
9. Check whether app-specific scores transferred. Some apps calculate proprietary scores or composite ratings. If the original app shows a score that is not visible in Health, do not ask ChatGPT to reconstruct it from partial fields.
10. Separate observation from interpretation. “The chart has no sleep entries from March 4 to March 12” is an observation. “My sleep got worse that week” is an interpretation that may be false if the device was not worn.

Operational warning: do not upload, publish, or share health screenshots or records to get outside opinions from public forums or untrusted tools. If you need medical interpretation, bring verified details to a licensed professional. If symptoms are severe, sudden, or concerning, use appropriate real-world medical support rather than an AI summary.

Non-diagnostic verification worksheet

Copy this worksheet into a private note, a local document, or a secure place you control. Do not include unnecessary identifiers such as full account numbers, insurance IDs, full birth date, home address, or unrelated medical history. The worksheet is designed to capture verification facts and appointment questions, not to diagnose a condition.

Copy-paste worksheet template

Non-diagnostic Health summary verification worksheet

Selected Health item:
Original source checked:
Source type:
Date or date range verified:
Collection date, result date, or encounter date if applicable:
Value and unit verified:
Reference range shown in original source:
Missing intervals or sync gaps:
Device, app, sensor, or source changes:
Manual entries or imported entries:
App-specific scores visible in original app:
App-specific scores visible in Health:
Facts visible in the selected record:
General explanation from ChatGPT that I still need to verify:
Uncertainties:
Questions for a licensed professional:
Decisions I will not make from this AI summary alone:

Ask for an explanation that preserves uncertainty

A useful Health prompt should constrain ChatGPT to the selected item, require uncertainty labels, and prohibit diagnosis or treatment decisions. This matters because a polished explanation can sound more complete than the underlying record. The prompt should force a distinction between verified facts, general educational context, and questions for a professional.

Recommended prompt pattern:

@Health Use the selected Health item only.
Create a non-diagnostic explanation with these headings:
1. What the selected item appears to show.
2. Date, unit, source, and reference range I must verify in the original record.
3. Missing intervals, device changes, or sync gaps that could affect interpretation.
4. General background, clearly labeled as general information.
5. Questions to ask a licensed professional.

Do not diagnose me, predict my risk, recommend treatment, change medication or dosage, or tell me to ignore symptoms.

If you are reviewing a chart rather than a single record, add a completeness instruction. For example, ask ChatGPT to identify whether the chart appears continuous, whether data points cluster around certain dates, and whether any visible gap prevents a confident description. Do not ask it to infer a trend across periods with missing data.

@Health Review the selected chart only.
Before summarizing any pattern, list:
- visible date range
- unit
- number or density of visible data points if apparent
- gaps or missing intervals
- possible device/source changes I should check
- whether app-specific scores appear to be included

Then provide a cautious, non-diagnostic summary and appointment questions.

If you are reviewing a lab record, add a reference-range instruction. A value without its original unit and reference range is not enough for reliable interpretation, and generic ranges found elsewhere may not match the lab method used for your report.

@Health Explain the selected lab record conservatively.
Use the reference range printed in the selected record only if visible.
If the unit, collection date, result date, or reference range is not visible, mark it as "not verified."
Do not compare this result with other labs unless the date, unit, and source are verified for each item.

Red-flag wording that should make you pause

Pause and re-check the original source if an AI explanation uses words that exceed the evidence in the selected item. Examples include “diagnostic,” “definitive,” “requires,” “safe to ignore,” “change your dose,” “you should stop,” “risk is low,” or “risk is high.” Health may help explain records, but OpenAI states it is not intended for diagnosis or treatment, and consequential medical decisions require qualified real-world care.

Turn the verified summary into appointment questions

The safest output from a personalized Health explanation is often a better appointment conversation, not a self-directed conclusion. Your goal is to bring concise, verified facts and neutral questions to a licensed professional. Avoid asking ChatGPT to decide whether you need testing, medication, imaging, procedures, emergency evaluation, or a treatment change.

Appointment-question template:

I reviewed one selected Health item and verified the following against the original source:

Record or metric:
Original source:
Date or date range:
Value and unit, if applicable:
Reference range shown, if applicable:
Missing intervals or sync gaps:
Device/app/source changes:
App-specific scores that did or did not transfer:
What I understand as a neutral observation:
What remains unclear:

Questions for my appointment:
1. Does this record need follow-up in my situation?
2. Are the date, unit, and reference range the right ones to use?
3. Could missing data, device changes, or source differences affect the apparent pattern?
4. Should this be compared with prior records, and if so which ones?
5. What symptoms, context, or history should I make sure you know?
6. What should I do if I notice new or concerning symptoms before the visit?

Prompt to generate appointment questions from your worksheet:

Using the verification worksheet below, draft neutral questions for a licensed clinician.
Do not diagnose, recommend treatment, predict risk, or suggest medication changes.
Focus on what to ask, what context to bring, and what record details need confirmation.

Worksheet:
[Paste only the minimum necessary worksheet details, without account numbers, full identifiers, or unrelated private information.]

Operational warning: if your situation involves urgent symptoms, severe pain, sudden changes, breathing difficulty, signs of stroke or heart attack, self-harm concerns, overdose concerns, or any condition that feels emergent, do not use an AI summary as a gatekeeper. Seek immediate professional or emergency support through appropriate local services.

Separate “bring to appointment” from “send to portal”

Do not automatically send AI-generated summaries through a patient portal, employer system, insurer, school, or public channel. External messages can become part of a record, trigger administrative workflows, or omit context a clinician needs. Human review is mandatory before external messages, submissions, permission changes, publication, legal commitments, or other consequential actions.

Keep the final appointment packet short. A clinician can usually work more efficiently with one verified item, the original date and unit, the printed reference range, and a few direct questions than with a long AI-generated narrative. If the Health explanation helped you understand terminology, bring the terminology questions rather than presenting the AI explanation as a medical finding.

Memory, privacy, and limits you should decide before a sensitive Health review

OpenAI says ChatGPT Health can read the connected records you authorize, including supported provider records and other supported health sources, but it cannot write back to Apple Health or provider records. Treat that as a one-way review model: ChatGPT may help explain a selected chart, metric, or record, but it should not be used as the system of record, the place where you “correct” a medical chart, or the tool that sends instructions to a clinician, insurer, pharmacy, school, employer, or caregiver.

The practical consequence is simple: if you notice a possible error, outdated medication entry, missing lab, duplicate diagnosis, or confusing timestamp, your next step is to verify the original record and contact the relevant professional or portal using the ordinary process for that provider. Do not assume that a clarification typed into ChatGPT updates your Apple Health data, provider chart, One Medical record, Function Health record, or any other source. Keep the correction workflow inside the official health system or with a licensed professional who can act on it.

OpenAI’s Health privacy policy and Health help article draw a specific boundary around model training and advertising: connected medical records, Apple Health information, and conversations that use them are not used to train OpenAI’s foundation models or to target ads. That statement is important, but it is not a reason to become careless with sensitive records. A privacy-first Health workflow still minimizes what you connect, limits what you paste, avoids screenshots, verifies against the source, and deletes or disconnects data you no longer need.

Before you select a chart or ask for an explanation, decide which privacy mode fits the task. If you want Health to apply connected data in a normal conversation, understand that the conversation may remain in your chat history until you delete it. If you want a more ephemeral review, consider Temporary Chat where available and appropriate. If you are working inside a project, review whether project-specific memory is enabled and whether that is suitable for sensitive health context.

This article explains Temporary Chat personalization, including how memory, plugins, custom instructions, saving, and privacy behave in temporary conversations. The ChatGPT Temporary Chat Personalization Explained: Memory, Plugins, Custom Instructions, Saving, and Privacy article is a focused companion for Temporary Chat Privacy because it is the exact match for a marker about Temporary Chat privacy because it directly covers privacy-related behavior and personalization controls in Temporary Chat.

Use a one-way-read model: Health can explain, not update records

A safe Health workflow starts by separating three different places where information may appear: the source record, the ChatGPT conversation, and any memory or project context that ChatGPT may later use. The source record is the original health system or Apple Health data. The conversation is the chat where you asked for an explanation. Memory, when enabled, is a separate personalization feature that can let ChatGPT remember useful details across chats, subject to OpenAI’s memory controls and account settings.

Because ChatGPT cannot write back to connected records, you should avoid language such as “update my record,” “fix my chart,” “send this to my doctor,” or “mark this medication as discontinued.” A better instruction is: “Help me draft questions to ask my licensed clinician after I verify this item in the original portal.” That phrasing keeps ChatGPT in a support role and prevents you from confusing an explanatory summary with an actual medical-record action.

Use the following decision rule when a Health summary identifies something that looks important: if the next step would affect diagnosis, treatment, medication, insurance, school accommodations, work accommodations, caregiving duties, payment, legal status, or emergency response, stop and use a qualified real-world process. ChatGPT can help you organize observations and questions, but a human professional must review consequential medical, legal, financial, or administrative actions before anything is submitted or changed.

Training and ads boundary: important protection, not a reason to over-share

OpenAI states that connected medical records, Apple Health information, and conversations that use them are not used to train foundation models or target ads. For users, administrators, and privacy reviewers, that statement answers two common questions: whether these Health-connected materials are used for foundation-model training, and whether they are used for ad targeting. The documented answer in the Health sources is no.

That boundary does not eliminate all privacy concerns because data may still exist in your account history, synced source storage before deletion completes, app permissions, browser environment, device backups, exported notes, downloaded files, screenshots, or messages you send outside ChatGPT. A safe procedure avoids copying sensitive details into places that are not necessary for the task. Do not upload public screenshots, paste full medical histories, or share a Health explanation in a group chat just to get a second opinion.

For enterprise administrators and security teams, the correct review question is not only “Is this used to train foundation models?” It is also “Who can access the account, device, browser profile, workspace, project, chat history, exported file, or shared screen where this appears?” A user can create privacy risk even when training and ad targeting are restricted if they paste sensitive health information into ordinary notes, ticketing systems, documents, or collaboration tools that are not approved for health data.

For educators, parents, and caregivers, the conservative rule is stricter: do not require students, minors, patients, family members, employees, or dependents to connect or disclose health records to complete a lesson, workplace task, wellness challenge, or administrative process. The Health feature described by OpenAI is rolling out to eligible logged-in users in the United States who are 18 or older, and the tutorial workflow should not be repurposed into a public assignment or a disclosure requirement.

Memory behavior: Health source data is not directly turned into memories, but Health conversations can still matter

OpenAI’s Health source notes distinguish synced source data from conversation content. Memories are not created directly from synced Health data, but Health conversations can create memories when memory is on. That means the connected record itself is not the direct source of a saved memory; however, if you discuss sensitive health context in a normal conversation and memory is enabled, a relevant detail from that conversation may be remembered according to the memory feature’s behavior and controls.

The operational rule is to decide memory posture before you start a sensitive Health session, not after a long conversation. If you do not want health-related context to influence future chats, use the applicable memory controls, consider Temporary Chat, or use a project configuration that fits the task. Do not test this by entering more sensitive detail than necessary. Instead, plan the privacy mode first, then select only the chart, metric, or record required for the immediate question.

This guide covers how to configure, manage, and optimize ChatGPT memory and personalization while safeguarding long-term context and privacy. The ChatGPT Memory and Personalization in 2026: How to Configure, Manage, and Optimize Your AI’s Long-Term Context article is a focused companion for ChatGPT Memory Controls because it best supports a practical marker about ChatGPT Memory Controls because it focuses on configuring and managing memory rather than only describing memory architecture conceptually.

A safe prompt can explicitly state your preference, but account settings and product controls remain the authoritative mechanism. For example, you may write: “Do not save or rely on any health-related details from this conversation as memory. Explain only the selected item and help me prepare questions for my clinician.” This prompt is useful as an instruction, but you should still verify memory settings, Temporary Chat availability, and any workspace or project controls because behavior can vary by account, plan, region, rollout, and policy.

If a memory is created from a Health conversation and you later decide it is not appropriate, use the memory-management controls described by OpenAI rather than assuming that disconnecting a health source removes memories or prior chat text. Disconnecting a source is about synced source data; memories and conversation history have their own controls and deletion pathways.

Project-specific memory: useful for continuity, risky for sensitive context

OpenAI’s memory documentation describes a project-specific memory option. In a Health workflow, that option should be treated as a deliberate scoping choice, not a convenience toggle. Project-specific memory may help keep context within a defined project, but sensitive health discussions still require careful naming, access control, and deletion planning. Do not create a broadly shared project for personal medical review, family caregiving, employee wellness, student support, or client health analysis unless your organization has explicitly approved that use and has appropriate safeguards.

A practical use case for project-specific memory is a private, narrowly scoped personal project where you want continuity for appointment preparation while avoiding spillover into unrelated chats. Even then, avoid adding full record dumps. Use verified summaries, dates, units, and questions rather than complete charts. If a professional later needs details, retrieve them from the original provider portal or Apple Health source instead of relying on an AI-generated recap as the authoritative record.

Legal-technology professionals and enterprise administrators should be especially cautious about project structures that mix health facts with legal claims, workplace disputes, benefits decisions, immigration matters, disability accommodations, insurance coverage, or litigation strategy. ChatGPT Health is not intended for HIPAA covered-entity use according to the source notes, and OpenAI points to separate healthcare products for eligible clinical settings. Do not route regulated clinical workflows or privileged legal-health material into consumer Health features without qualified compliance review.

Use this conservative project rule: if more than one person can access the project, or if the project relates to employment, education, legal rights, benefits, insurance, or clinical operations, do not put personal health records there unless your organization has a documented lawful basis, approved platform configuration, and human governance process. The safer pattern is to keep sensitive Health sessions private, minimal, and separated from collaborative workspaces.

Temporary Chat: when you want less carryover from a sensitive review

Temporary Chat can be useful when you want a health-related question to have less carryover into future conversations, subject to the behavior described in OpenAI’s Temporary Chat FAQ and the availability of the feature in your account. Use it for narrow, one-time tasks such as understanding the meaning of labels on a selected chart, creating a short verification checklist, or drafting appointment questions from a single record.

Temporary Chat should not be treated as permission to paste complete medical histories or unnecessary identifiers. The same minimization rule applies: select one chart, metric, or record; ask for an explanation that preserves uncertainty; verify date, unit, reference range, and source; then copy only the appointment questions you actually need. If you do not need the person’s name, address, member ID, claim number, or full portal screenshot, do not include it.

Temporary Chat also does not turn ChatGPT into an emergency service. If the selected record or metric relates to urgent symptoms, a medical emergency, self-harm risk, poisoning, severe allergic reaction, chest pain, stroke-like symptoms, or any other immediate danger, use local emergency services or qualified crisis and medical support rather than trying to resolve the issue through a summary. ChatGPT can support preparation and understanding; it should not delay urgent real-world care.

Apps and plugin permissions: review connected capabilities before using Health context

OpenAI’s apps documentation describes apps in ChatGPT and permission settings. For Health workflows, the conservative rule is to avoid combining sensitive health context with unrelated apps, plugins, external tools, calendars, documents, email systems, task managers, or publishing workflows unless you have a clear reason and understand the permission implications. A health explanation should not automatically become an email, appointment request, public document, school note, insurance submission, legal filing, or employer message.

Before invoking an app or tool in a conversation that contains Health information, pause and ask what data the tool can access and what action it might take. If the tool can send messages, create documents, schedule events, update records, share files, or call external services, human approval is mandatory before anything leaves ChatGPT or changes another system. This is especially important when a Health summary contains names, dates of service, lab values, medication names, symptoms, diagnoses, or provider details.

Use this permission review checklist before combining Health with any app capability:

• Purpose: Identify the exact reason the app is needed. If the task is only to understand a record, do not use an external app.
• Data minimization: Remove unnecessary identifiers, portal screenshots, insurance details, and unrelated medical history before drafting anything.
• Action boundary: Confirm whether the app can merely draft content or can also send, publish, schedule, submit, purchase, or update something.
• Human approval: Require explicit review before any external message, appointment request, portal submission, payment, publication, permission change, or legal commitment.
• Recipient check: Verify the exact recipient, organization, account, and purpose before sharing health-related content outside ChatGPT.
• Record check: Compare the draft against the original source date, unit, reference range, and missing-data notes before relying on it.
• Deletion plan: Decide whether the conversation, draft, exported file, or app-created artifact should be deleted after use.

A safe example is asking ChatGPT to draft a private appointment agenda that you manually copy into a provider portal after verifying every line. An unsafe example is allowing a connected app to send a message containing unverified lab interpretations, full screenshots, or unnecessary family history to a recipient you have not checked. Drafting is not the same as authorized submission.

Disconnecting source data versus deleting copied conversation information

OpenAI’s Health help article states that disconnecting a source causes synced source data to be deleted from OpenAI systems within 30 days. It also states that information already present in conversation history remains until those conversations are deleted. This distinction is central to safe Health use because disconnecting a source is not a universal eraser for everything you discussed, copied, summarized, exported, or shared.

Think of Health data as having at least two tracks. The first track is synced source data from the connected health source. Disconnecting addresses that synced source data under the documented deletion timeline. The second track is conversation history: text generated or entered in chats, including explanations, copied values, appointment questions, and summaries. That conversation track follows conversation deletion rules, not source-disconnection rules.

This matters when you paste or ask ChatGPT to repeat sensitive information from a connected record. If the chat now contains “Lab X was 123 on June 1 with reference range Y,” that text may remain in the conversation history even after the original source is disconnected, unless you delete the conversation according to the applicable controls. If you exported, copied, screenshotted, emailed, or saved that text elsewhere, those copies are outside the simple disconnect workflow and must be managed separately.

A practical shutdown workflow after a sensitive review is: save only the minimum appointment questions you need, delete unnecessary drafts, remove screenshots, delete the Health conversation if you do not want it in history, review memory controls, then disconnect the source if you no longer need synchronized access. Perform these steps before handing a device to another person, presenting on a shared screen, or using the same browser profile for unrelated work.

No screenshots, no public sharing, and no crowdsourced interpretation

This tutorial does not require screenshots, public posts, or shared images of health records. Do not publish a chart, lab result, portal page, wearable dashboard, prescription list, insurance explanation, appointment note, or AI-generated Health summary to ask strangers for interpretation. Public sharing can expose identifiers, dates, provider names, rare conditions, family information, location clues, and metadata that you may not notice when focusing on the medical value.

If you need help from a clinician, use the provider’s secure channel or bring a verified, minimal question list to the appointment. If you need help from a caregiver, share only the information they need for that role and only with the person’s consent or other valid authority. If you are supporting a child, dependent adult, employee, student, client, or patient, follow applicable law, organizational policy, consent requirements, and professional duties rather than relying on ChatGPT to determine who may receive the information.

A safer alternative to screenshot sharing is a de-identified personal worksheet kept offline or in an approved private location. Even then, avoid pretending that de-identification is perfect. Dates, rare tests, unusual diagnoses, provider names, locations, and combinations of events can re-identify a person. Use the worksheet to prepare questions, not to create a public case file.

Recommended private worksheet format

Selected source:
Original record date:
Metric or record name:
Unit shown in original source:
Reference range or label shown in original source:
What the selected item appears to show:
What data may be missing:
What I do not understand:
Neutral questions for a licensed professional:
What I should not assume:
Whether I need to delete this chat after use:

Recommended privacy workflow for one sensitive Health session

The following workflow is a recommendation, not a statement that every account has identical settings or user-interface labels. Use it to structure a sensitive review while respecting OpenAI’s documented boundaries and the limits of non-diagnostic assistance.

1. Define the task before connecting anything. Write one sentence such as: “I want to understand the labels and trend in one cholesterol chart before my appointment.” If the task is diagnosis, treatment, dosage, emergency triage, or legal decision-making, do not use ChatGPT as the deciding authority.
2. Choose the least persistent mode that fits. Review whether normal chat, Temporary Chat, or a project with project-specific memory is appropriate. If you do not want future carryover, do not begin in a memory-enabled ordinary conversation by default.
3. Review app and plugin permissions. Disable or avoid unnecessary external actions for the session. Do not connect health context to tools that can send, publish, submit, schedule, purchase, or update without a separate approval step.
4. Select only one chart, metric, or record. Ask for a contextual explanation without adding full medical history unless it is genuinely necessary and appropriate.
5. Require source verification. Ask ChatGPT to list the original date, unit, reference range, source name, missing data, and uncertainty, then compare those items yourself against the original record.
6. Separate observation from interpretation. Keep “what the record shows” separate from “what it might mean,” and treat interpretations as questions for a licensed professional.
7. Do not authorize external actions. If ChatGPT drafts a message, review it manually. Do not let an app send it, submit it, or publish it without explicit human approval.
8. Close the data loop. Delete unnecessary conversations, review memories, remove exported drafts, and disconnect the source if ongoing access is not needed.

This workflow is intentionally slower than asking a broad health question and accepting the first answer. The extra steps reduce the chance that you rely on a misread unit, overlook a missing date, preserve sensitive information longer than intended, or let a draft leave ChatGPT before a human has checked it.

Sample prompts for memory-safe, privacy-minimized Health reviews

The following sample prompts are operational examples. They are not medical advice, do not request diagnosis or treatment, and should be adapted only with information you are comfortable processing in ChatGPT under your account settings.

Prompt: explain without saving health context as memory

I selected one Health chart or record. Explain what the selected item appears to show in plain language without diagnosing, predicting risk, recommending treatment, or suggesting medication changes.

Please structure the answer as:
1. Original source details I should verify: date, unit, reference range or label, and source.
2. Plain-language observation.
3. Important missing context or uncertainty.
4. Questions I can bring to a licensed professional.

Do not treat this as an emergency assessment. Do not send, save, publish, or share anything externally. Do not rely on this conversation as memory for future chats.

Prompt: check what should be deleted after the session

Help me make a privacy cleanup checklist for this Health conversation.

List separately:
- Information that came from the connected source.
- Information now present in this conversation.
- Any health-related details that might be inappropriate to keep as memory.
- Drafts or notes I may have copied elsewhere.
- Steps I should consider, such as deleting the conversation, reviewing memory controls, removing external copies, or disconnecting the source if I no longer need it.

Do not include diagnosis, treatment advice, or emergency triage.

Prompt: turn a verified observation into questions only

I have verified the selected record against the original source. Turn the observation below into neutral questions for a licensed professional.

Verified observation:
[Insert only the minimum necessary observation, date, unit, and reference range.]

Requirements:
- Do not diagnose.
- Do not recommend medication, dosage, supplements, or treatment.
- Do not imply urgency unless the original source explicitly says urgent or I describe an emergency.
- Include uncertainty and missing-data notes.
- Produce a short appointment agenda I can review before sharing.

What to do when privacy and medical safety conflict

Sometimes the safest privacy choice and the safest medical choice point in different directions. For example, you may not want to preserve a sensitive Health conversation, but you may need a reliable list of questions for an appointment. In that case, keep a minimal, verified question list and delete broader chat content that is not needed. Do not delete the original provider record or rely on an AI summary as the only copy of clinically relevant information.

If a summary makes you worried, avoid escalating the worry by repeatedly asking for speculative interpretations. Instead, return to the original record, confirm whether the value, date, unit, and reference range were read correctly, and contact a qualified professional through the appropriate channel. If there is an emergency or immediate risk, seek real-world emergency help rather than continuing the ChatGPT session.

If you are assisting someone else, privacy and authority come first. Do not connect another person’s records, paste their results, or ask for a summary unless you have appropriate consent or legal authority and the use is necessary for their care or support. When in doubt, use the least revealing path: help them prepare their own questions, encourage them to contact their provider, or support them in using the official portal themselves.

CE113 training-and-ads boundary: OpenAI states that connected medical records, Apple Health information, and conversations that use that connected information are not used to train foundation models or target ads. This statement does not remove the need to review permissions, memory, chat history, sharing, and deletion controls.

Disconnect sources safely and confirm what remains

Disconnecting a Health source should be treated as a privacy operation, not as a casual cleanup step. OpenAI’s Health documentation states that disconnecting a source causes synced source data to be deleted from OpenAI systems within 30 days, while information already present in conversation history remains until those conversations are deleted. That distinction matters because a lab value, medication name, diagnosis label, provider note excerpt, or trend summary may have been copied into a chat message even after the original connected source is no longer available to Health.

Use the workflow below when you are finished with a review, when you connected a source only for a single task, when you are no longer comfortable with ongoing access, when an enterprise or family device policy changes, or when a clinician, attorney, administrator, parent, or privacy officer asks you to reduce retained context. This workflow is a recommendation, not a statement that every account exposes the same controls in the same location; ChatGPT behavior can vary by plan, app, region, rollout, and workspace policy.

Safe disconnect workflow

1. Stop new Health analysis first. Finish or abandon the current conversation before disconnecting the source. Do not ask for additional interpretations, predictions, triage, diagnosis, treatment options, medication changes, or risk scores while you are in the middle of removing access.
2. Record what you need outside ChatGPT, if appropriate. If you need a non-sensitive reminder for an appointment, write it in your own notes using minimal wording such as “Ask clinician about the lab result dated [date] and units [unit].” Do not export full records, screenshots, or unnecessary identifiers into shared documents.
3. Open the Health data-source controls available in your account. Locate the connected Apple Health, supported provider, One Medical, or Function Health connection that you want to remove. If your app, plan, or rollout does not show the same interface, use OpenAI’s current Help Center instructions or contact support rather than guessing.
4. Disconnect only the source you intend to remove. Confirm the source name, account, and data category before approving the disconnect action. A family member’s phone, a shared browser profile, or an old provider portal connection can make source identity easy to misread.
5. Assume synced source data deletion is not instantaneous. OpenAI’s documented boundary is deletion from OpenAI systems within 30 days after disconnecting the source. Do not reconnect merely to check whether deletion has completed unless you actually need the source again.
6. Review conversation history separately. Search or inspect relevant Health conversations where sensitive information may have been discussed. Delete conversations you no longer want retained, because disconnecting the source does not delete information already present in conversation history.
7. Review Memory settings separately. OpenAI states that memories are not created directly from synced Health data, but Health conversations can create memories when memory is on. If a memory was created from what you discussed, manage it using ChatGPT’s memory controls rather than assuming source disconnection removed it.
8. Review apps and connected capabilities separately. If you used any app-like capability around the same session, check its permissions and remove access that is no longer needed. Do not paste health summaries into external apps unless you understand the destination’s policies and have a necessary, authorized purpose.
9. Close shared sessions and devices. Sign out of browsers or devices you do not control, especially on shared family computers, school devices, workplace machines, or clinical workstations. A disconnected source does not protect old visible chat content from someone with access to the same account or screen.
10. Escalate if the disconnect path fails. If the source cannot be disconnected, the wrong source appears, deletion behavior is unclear, or a workplace account policy blocks the control you need, contact OpenAI support or the relevant workspace administrator. Do not attempt to bypass account, provider, or device restrictions.

This ChatGPT Privacy Center guide explains how memory, Temporary Chat, connected apps, model-improvement controls, export, and account-security settings differ, providing the broader control map users need when disconnecting Health data and separately deleting retained conversations. The ChatGPT Privacy Center Guide: Memory, Personalized Ads, Temporary Chat, Connected Apps, Model Improvement, Data Export, and Account Security article is a focused companion for Health Data Deletion because the target directly covers ChatGPT privacy controls and deletion-adjacent settings, whereas the draft target described connecting Health sources without explaining the separate cleanup surfaces.

Disconnect-versus-delete decision table

Example end-of-session cleanup checklist

Health session cleanup checklist

[ ] I stopped asking Health for new analysis before changing permissions.
[ ] I saved only the minimum appointment question I need, without screenshots or unnecessary identifiers.
[ ] I disconnected any source I no longer want ChatGPT Health to use.
[ ] I understand synced source data is deleted from OpenAI systems within 30 days after disconnection.
[ ] I reviewed Health conversations that may contain copied record information.
[ ] I deleted conversations I do not want retained in history.
[ ] I reviewed ChatGPT memory controls for any sensitive memory created from discussion.
[ ] I used Temporary Chat for future sensitive one-off reviews where continuity is not needed.
[ ] I reviewed apps or connected capabilities before sharing any Health-derived text.
[ ] I will ask a licensed professional about medical meaning, urgency, diagnosis, treatment, or medication decisions.

This checklist intentionally separates privacy cleanup from medical follow-up. Deleting a conversation may reduce retained text, but it does not answer whether a symptom, lab result, device trend, medication list, or clinician note is clinically important. If the issue could affect care, prepare concise questions for a licensed professional and include the original record date, unit, reference range, missing data, and source system rather than relying on a summary alone.

Troubleshooting access, missing records, and incomplete explanations

When Health does not behave as expected, start by checking eligibility and source availability before assuming a bug or a medical-data problem. OpenAI’s Help Center states that Health is rolling out to eligible logged-in Free, Go, Plus, and Pro users in the United States who are age 18 or older on web and iOS. Apple Health connection requires an iPhone. If your account, location, age status, device, app version, organization policy, or rollout status does not meet the documented boundary, the Health tab or a particular connection option may not appear.

Feature availability can also differ between personal and managed environments. Health is not supported in Codex, and the Health documentation says it is not intended for HIPAA covered-entity use. Developers and legal-technology teams should not design workflows that route covered-entity clinical operations through consumer Health features unless they have a separate eligible healthcare product, appropriate agreements, and counsel-approved controls. This tutorial is for individual, privacy-conscious use of documented Health capabilities, not for deploying a regulated clinical record system.

Problem: the Health feature is missing

If Health is absent after these checks, contact OpenAI support when you believe your account meets the documented criteria but the feature still does not appear. For workplace, school, legal, or clinical environments, contact the workspace administrator or compliance owner first because account-level policy may be intentional. Do not ask ChatGPT to diagnose access problems from screenshots containing health information, identifiers, insurance details, or portal names.

Problem: your provider is unavailable

OpenAI’s Health documentation says Health can use supported U.S. provider records, One Medical, Function Health, and user-authorized Apple Health data. It does not say that every provider, payer, lab, hospital, pharmacy, wearable, or patient portal is available. If your provider is missing, use the provider’s official portal or request records through the provider’s normal process rather than copying large amounts of protected or sensitive material into ChatGPT.

A provider connection can also fail because of account mismatch, portal authentication changes, institutional restrictions, network issues, or provider-side data formatting. The safest troubleshooting path is to verify the record directly in the provider’s own portal, confirm that the data exists there, and then decide whether you can wait for supported integration. If the matter is medically important, do not wait for a ChatGPT connection; contact the provider, pharmacist, clinic, emergency service, or other qualified professional through normal channels.

Problem: Apple Health sharing is incomplete

Apple Health connection requires an iPhone, and the user authorizes what is shared. If a chart, metric, or record seems incomplete, check whether the relevant Apple Health category was shared, whether the device actually recorded the data, whether the date range includes the period you are reviewing, and whether the data came from one device or multiple devices. Fitness wearables, manual entries, imported records, and device settings can create gaps or duplicate-looking segments.

Do not treat an incomplete Apple Health trend as evidence that a health event did or did not happen. Device-derived metrics can be affected by wear time, sensor placement, battery status, app permissions, manual edits, and syncing delays. When the question is clinically meaningful, compare the Health summary with the original Apple Health entry, any provider record, and a licensed professional’s guidance.

Problem: a proprietary metric is missing or explained only generally

Some health systems, labs, devices, and wellness services use proprietary metrics, derived scores, or context-specific labels. OpenAI’s source notes do not establish that ChatGPT Health can interpret every proprietary scoring system, vendor algorithm, or provider-specific flag. If a metric is missing, appears without full context, or receives a general explanation, check the original source’s definition, date, unit, reference interval, device manual, lab methodology, or clinician note before drawing conclusions.

A conservative prompt can reduce overinterpretation: “Explain what information is visible about this selected metric, identify what is missing, and list questions I should ask the source provider. Do not diagnose, estimate risk, or recommend treatment.” This is a sample prompt, not medical advice, and it should be used only with data you are authorized to review.

Problem: the explanation conflicts with the original record

If a Health explanation appears inconsistent with the original record, trust the original source over the generated summary until a qualified professional clarifies the issue. Re-check the date, unit, reference range, abnormal flag, specimen type, device category, patient identity, time zone, and whether the selected item represents a single result or a trend. A common failure mode in any summarization workflow is mixing a visible value with a nearby date, note, or reference interval from another item.

Use a correction-oriented prompt only after you have verified the source: “The selected explanation appears to conflict with the original record. The original record shows [minimal non-identifying description], dated [date], with unit [unit] and reference range [range if visible]. Please identify the discrepancy and provide a non-diagnostic list of questions for my licensed professional.” Do not include names, account numbers, full screenshots, addresses, or unrelated record content.

Problem: the conversation becomes too medical, urgent, or personal

Health is designed to support, not replace, medical care and is not intended for diagnosis or treatment. If the conversation shifts toward emergency symptoms, self-harm, medication changes, pregnancy complications, severe pain, neurological symptoms, chest pain, breathing difficulty, allergic reactions, overdose concerns, or any other urgent situation, stop using ChatGPT as the decision-maker and seek immediate qualified help through local emergency services or an appropriate licensed professional. ChatGPT should not be used for emergency triage.

If the issue is not an emergency but could affect care, convert the output into questions rather than actions. A safe format is: “What does this result usually measure?”, “What missing context should I bring?”, “Should I ask whether this trend needs follow-up?”, and “Which original records should I verify before the appointment?” Do not ask for a medication dosage decision, a diagnosis, or a prediction of personal risk.

When to contact support, an administrator, or a licensed professional

Different problems require different escalation paths. Contact OpenAI support for product-access issues, source-disconnection problems, unclear account behavior, or documented controls that do not work as expected. Contact a workspace administrator when a managed account, school account, employer device, or enterprise policy may control feature availability. Contact the provider, lab, device maker, or medical records department when the underlying source record is missing, delayed, inaccurate, or not available through a supported connection.

Contact a licensed professional when the question involves symptoms, diagnosis, treatment, medication, test interpretation, care urgency, procedure decisions, pregnancy, mental health, chronic-condition management, pediatric issues, or any result that worries you. A ChatGPT summary can help prepare your questions, but it cannot examine you, confirm identity, order tests, reconcile medication interactions in a clinical context, or assume legal responsibility for care.

Enterprise, legal, education, and family-use cautions

Enterprise administrators should treat ChatGPT Health as an individual user feature unless their organization has reviewed separate eligible healthcare offerings and appropriate agreements. The Health source notes specify that Health is not intended for HIPAA covered-entity use, and Health does not work in Codex. That means developer teams should not build Codex workflows that expect Health context, and administrators should not direct employees to process patient records through consumer Health features as a substitute for governed clinical systems.

Legal-technology professionals should avoid using Health summaries as evidence, legal advice, disability determinations, benefit decisions, employment decisions, insurance assessments, or litigation analysis without proper authorization, record provenance, expert review, and jurisdiction-specific legal guidance. A generated explanation is not a certified medical record, expert report, or admissibility analysis. If health information is relevant to a legal matter, preserve the official record through authorized channels and consult qualified counsel.

Educators and parents should pay close attention to the age boundary. OpenAI documents Health rollout for eligible users age 18 or older. Do not ask students, children, or minors to connect medical data through an adult account, and do not paste a child’s health information into ChatGPT for convenience. When a child’s health is at issue, use the pediatrician, school nurse, emergency service, or authorized care pathway rather than an AI summary workflow.

Knowledge workers should avoid turning Health into a workplace productivity tool. Do not paste health summaries into project-management systems, shared documents, customer relationship tools, issue trackers, or email threads unless there is a necessary, authorized, and policy-approved reason. Human approval is mandatory before any external message, submission, publication, legal commitment, insurance communication, workplace accommodation request, or other consequential action based on Health-derived text.

Final operating rules for privacy-first Health summaries

The safest way to use personalized Health summaries is to keep the loop small: connect only the source you need, select one chart, metric, or record, ask for a conservative explanation, verify the original date and unit, identify missing context, convert the output into questions, and disconnect sources you no longer need. That process uses the September 28 personalized-summary capability while preserving the core boundary that ChatGPT supports understanding but does not replace medical care.

Remember the three deletion boundaries that matter most. First, disconnecting a source causes synced source data to be deleted from OpenAI systems within 30 days, according to OpenAI’s Health documentation. Second, conversation history remains until deleted, so copied record details in chats require separate cleanup. Third, memories are not created directly from synced data, but Health conversations can create memories when memory is on, so memory review remains part of a complete privacy workflow.

Use Temporary Chat when you want less carryover for a sensitive one-off review, but do not treat any mode as permission to overshare. Connected medical records, Apple Health information, and conversations that use them are not used to train foundation models or target ads, according to OpenAI’s Health privacy materials, but minimization is still the best operational practice. Less connected data means fewer items to verify, fewer places to clean up, and fewer opportunities to misread a generated explanation as a clinical conclusion.

The final decision rule is simple: if the output would change what you take, stop, send, sign, pay, publish, book, cancel, disclose, or do medically, legally, financially, educationally, or professionally, pause and involve the appropriate human authority. For health questions, that authority is a licensed professional or emergency service when urgent. For privacy, legal, and workplace questions, use the relevant administrator, privacy officer, counsel, or official support channel.

Useful Links

• OpenAI Help Center: Health in ChatGPT
• OpenAI Help Center: ChatGPT release notes
• OpenAI Health Privacy Policy
• OpenAI Help Center: Memory FAQ
• OpenAI Help Center: Temporary Chat FAQ
• OpenAI Help Center: Apps in ChatGPT