Patient-controlled health records AI

Fetch My Epic Token

Fetch My Epic Token is a free, MIT-licensed, source-available utility that helps patients log in to Epic/MyChart systems, obtain an OAuth access token and patient ID, and use those credentials to call Epic FHIR APIs directly. It is not a conventional clinical AI assistant. Its HugoScore relevance is that it makes patient data programmable and AI-ready through patient-controlled scripts, generated code, and export workflows. The agency upside is strong, but so are the credential-handling, privacy, and technical-burden caveats.

Draft profile Read full report Open directory

Public-source research has been drafted; final human publication review and change-log detail are still required.

88 /100 toward patient-directed

Agency posture Strongly agency-expanding, with credential-handling and technical-burden caveats

The question we ask Who does Fetch My Epic Token serve in this deployment?

Control Patient-chosen use, but vendor-controlled infrastructure

Agency read Likely to expand agency if it supports reflection, action, privacy, and safe boundaries.

Vendor: glmck13 / independent open-source project
Who it serves: Patient-directed, AI-enabling interoperability utility
Primary User: Patients, caregivers, and patient-developers with Epic/MyChart accounts
Control Model: Public web-hosted OAuth helper with source-available code; patients control downstream scripts and AI tools, but optional hosted download helpers process access tokens, patient IDs, API base URLs, PHI, and copied MyChart session credentials during downloads
Patient Impact: Epic/MyChart login, OAuth token and patient ID retrieval, FHIR API calls for USCDI-style records, ZIP export of visits, labs, reports, immunizations, and clinical notes, DIY message transcript export, and downstream patient-controlled scripts or AI-generated applications
Profile Status: Draft profile
Last Reviewed: Jun 12, 2026
Review Confidence: Medium draft, source-available, no independent audit

Summary judgment · 88% toward patient-directed

Strongly agency-expanding, with credential-handling and technical-burden caveats

The tool shifts Epic portal data into patient-controlled scripts, files, and downstream AI workflows, but the strongest workflows require technical skill and high-trust handling of tokens, PHI, and MyChart session cookies.

Patient agency

How this tool changes agency

Expands agency when

It helps patients pull visits, labs, reports, clinical notes, immunizations, and messages into reusable files or scripts for review, preparation, advocacy, archiving, or downstream analysis.

Limits agency when

Use is voluntary and patient-initiated, but practical use requires comfort with OAuth tokens, scripts, shell variables, browser developer tools, FHIR JSON, and PHI handling.

Patient-facing signals

Who does this AI serve?

Patient-directed and AI-enabling

The project serves patients, caregivers, and patient-developers who want direct access to their Epic/MyChart data. It is not an institutional workflow product, and the core utility is not itself an AI clinical assistant.

Can patients tell AI is involved?

Partial

AI appears in the HowTo page's AI code-generation prompt and in the DIY message app's origin story, but the main token and FHIR retrieval flow is conventional OAuth/API tooling.

Can patients meaningfully choose?

Yes, for technically capable users

Use is voluntary and patient-initiated, but practical use requires comfort with OAuth tokens, scripts, shell variables, browser developer tools, FHIR JSON, and PHI handling.

Can patients correct or challenge what the AI produces?

Not applicable to the core retrieval tool, partial downstream

Fetch My Epic Token retrieves records and exposes data. Correction of source records still depends on the institution, and any AI output depends on external tools the patient chooses.

Does it help patients understand or act?

Yes

It helps patients pull visits, labs, reports, clinical notes, immunizations, and messages into reusable files or scripts for review, preparation, advocacy, archiving, or downstream analysis.

Text findings

Who is left out or burdened?

Technical and Epic-access burden

Patients without Epic/MyChart accounts, reliable internet, a desktop browser, scripting comfort, English literacy, privacy/security confidence, or caregiver technical support may be excluded. The message app requires browser developer tools and copied cURL credentials.

What happens to patient data?

Privacy-forward claim, high-trust server-side workflows

The policy says the site does not collect, retain, or distribute personal information and uses no cookies. The EHR ZIP workflow posts access token, patient ID, API base URL, and organization to a server-side script that fetches PHI and deletes temporary files after streaming a ZIP. The message workflow posts copied session credentials, stores a temporary JSON transcript under /tmp, then deletes it. No independent audit was found.

Are the clinical boundaries clear?

Clear that it is a data-access tool, not clinical advice

The service retrieves and packages records. It does not appear to diagnose, triage, recommend treatment, or make clinical claims. The risk is downstream misuse of raw records or AI-generated analysis, not a built-in clinical model.

Who defined what good looks like?

Maintainer-defined, source-auditable, not independently evaluated

The code is public and MIT-licensed, making external review possible. Public evidence did not show independent security review, privacy audit, usability testing, accessibility review, or patient-partnered evaluation.

Review method

Deep public-source review of the official site, HowTo page, policy page, DIY message app page, GitHub repository, OAuth/token-flow source, EHR ZIP downloader source, MyChart message downloader source, MIT license, ONC Cures Act Final Rule page, and Epic on FHIR documentation; no hands-on login with a real MyChart account, security audit, real-PHI code execution, maintainer interview, or legal review.

Draft profile · Medium draft, source-available, no independent audit