openai / openai/codex

Unify Connected Health and Health Projects into a Single Health Workspace

Open
#39,559 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.814.41407

What subscription do you have?

Go

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

OpenAI currently has two separate Health experiences:

  • Connected Health (MyChart, medications, diagnoses, labs)
  • Health Projects (uploaded medical documents)
    These operate as separate knowledge stores, preventing ChatGPT from using uploaded health documents alongside connected health records. Users must repeatedly upload the same files and lose continuity across conversations.
What steps can reproduce the bug?

Feedback ID: no-active-thread-01a01c8c-298f-7d12-a4ad-e86c8d127130

What is the expected behavior?

What steps can reproduce the bug?*

  1. Upload medical documents (e.g., genetic reports) to a Health Project.
  2. Open a conversation in Connected Health.
  3. Ask ChatGPT a question that depends on the uploaded report.
    Expected: ChatGPT can reference both connected health records and uploaded documents.
    Actual: ChatGPT cannot access the uploaded report and asks for it to be uploaded again.
Additional information

This appears to be a product architecture issue rather than a model issue. OpenAI introduced Health previously, then announced Health again this year without clearly deprecating or merging the original project-based experience. The result is two separate Health systems with different capabilities, creating unnecessary confusion, duplicate uploads, and fragmented medical context. A unified Health workspace with user-controlled permissions would provide a much better longitudinal health experience.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no Codex files, tests, or entry points. Start by confirming whether Connected Health and Health Projects are implemented in this repository; done would mean a unified workspace can reference both connected records and uploaded documents without repeated uploads, with user-controlled permissions.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.