Fetch My Epic Token CAIHL draft report

Fetch My Epic Token: CAIHL reassessment

September 8, 2026. Published AI-assisted draft.

Fetch My Epic Token enables patient-directed record retrieval. Its 88 describes infrastructure, not clinical AI output. Local scripts and hosted helpers have different data-processing boundaries, and broad no-collection wording does not explain all necessary transient processing.

Scope and agency posture

Patient-directed record retrieval and AI-enabling infrastructure. The core token utility does not itself provide AI clinical judgments.

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

Axis: 88/100, retained provisionally. No numerical recalibration was performed.

Sources and documented findings

• The homepage describes patient login, token/ID access and FHIR exports, and explicitly offers a hosted copy of its download script. https://fetch-my-epic-token.org/

• The policy still says no personal-information collection, retention or distribution. Public script source accepts a POST token or local environment token, creates a temporary directory and sends bearer-authorized record requests. This confirms processing, not the live server's retention or logs. https://fetch-my-epic-token.org/policies.shtml and https://raw.githubusercontent.com/glmck13/Fetch-My-Epic-Token/main/getEHR_async.py

Patient authority

Inference from the documented workflow: Patients gain portable records and can choose downstream analysis. Hosted helper use delegates sensitive processing, while local script use has a different trust boundary.

Critical capacity

Editorial assessment: Access to underlying records can support checking and advocacy. Correcting source records remains a provider process, and downstream AI quality is outside this utility.

Informed control

Editorial assessment: The policy's broad no-collection wording does not explain necessary transient server processing. Source availability enables inspection but is not an audit or evidence of deployment parity.

Assessment and limits

The strong enabling contribution is grounded in data portability, not free licensing alone. A direct comparison with conversational clinical assistants would misstate scope.

Confidence: Moderate for public interface and source design.

Remaining uncertainty: Hosted code parity, logging, temporary-data deletion behavior and practical credential warnings remain unverified

Published documentation is evidence of stated conditions, not proof of actual implementation. Unknowns did not receive automatic negative points. Funding, sponsorship, and public code do not determine agency by themselves.

Review provenance

• Reviewer/model: OpenAI Codex / GPT-6.
• Method: Focused public-source reassessment using CAIHL: patient authority, critical capacity, and informed control. Existing evidence plus one focused primary-source pass and at most one targeted follow-up. No live product testing. Numerical scores remain provisional editorial placements, not a new calculation.
• Human review: Hugo Campos authorized publication of these AI-assisted draft reassessments on September 8, 2026. This does not claim comprehensive human verification of every finding.
• Earlier review: 2026-06-12. Historical assessment. Earlier claims are not automatically reverified by this publication.