Public OfRoot connection
A read-only MCP endpoint can explain OfRoot, its integration status, and its privacy boundaries. It accepts no health details and cannot access an OfRoot account.
Interoperability
A careful bridge between OfRoot and ChatGPT Health.
The public foundation is live. Patient data remains private while OfRoot pursues the review required for a direct ChatGPT Health connection.
OfRoot keeps the longitudinal record. ChatGPT Health may eventually become another place a person can explore that record, with explicit permission and narrow access.
Release path
Three distinct states, stated plainly.
A deployed endpoint, a private account connection, and a dedicated Health source are separate milestones.
Private account connection
The authorization and data-minimization contract is defined, but patient data stays disabled until the required OpenAI Health review and production identity controls are complete.
Dedicated ChatGPT Health source
OfRoot must be accepted for the dedicated Health environment before ChatGPT can read a person’s OfRoot timeline directly.
Data boundaries
Useful groundwork without a hidden data path.
These limits stay in place until the direct connection is reviewed, authorized, tested, and released.
No patient data on the public endpoint
It does not accept symptoms, notes, reports, account identifiers, or medical records.
No implied Health approval
A working public endpoint is technical groundwork. It does not mean OfRoot is an approved ChatGPT Health source.
No medical conclusions
OfRoot remains a preparation and timeline product. It does not diagnose or replace professional medical care.
OfRoot today
Build the health story before choosing where to use it.
OfRoot already helps people keep symptoms, quiet days, timing, and lived context together before care. The direct ChatGPT Health connection will remain optional when it becomes available.