Establish a "TEFCA Patient-Developer Credential" for Comprehensive, Direct Data Access

Recommendation: ONC, in coordination with the RCE, must define, oversee, and mandate support for a "TEFCA Patient-Developer Credential." This program will provide individuals with a unique, identity-bound digital credential. This credential will enable applications they develop and directly control to securely access only their own data via all standard TEFCA QHIN APIs, and to facilitate simplified registration and access directly with participant EHR FHIR API endpoints, free of network or prohibitive registration access charges for this specific personal use.

Rationale & Specifics: To fully empower individuals, foster grassroots innovation, and ensure patients can directly participate in managing their health information, a dedicated and comprehensive pathway is needed. This pathway allows individuals, acting as their own developers, to bypass commercial IAS provider intermediaries for TEFCA network access and simplifies direct connection to EHRs for their personal data. It positions the patient as a direct, albeit limited-scope, participant across the ecosystem for their own information.

  1. Issuance and Nature of the Patient-Developer Credential:
  2. TEFCA Network Access using the Credential:
  3. Facilitating Direct EHR FHIR API Access for Patient-Developers:
  4. Clear Distinction from Commercial Pathways: This entire Patient-Developer Credential pathway is explicitly for individual, non-commercial use by patients developing tools for their own data. It does not replace or alter requirements for commercial IAS providers or other applications operating at scale or for multiple users.

Establish a