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.
- Issuance and Nature of the Patient-Developer Credential:
- Identity Verification: The credential must be issued to an individual only after high-assurance identity verification through a federally recognized or TEFCA-approved Identity Provider (IdP) (as per
req_tefca_trustworthy_ias_architecture).
- Cryptographic Binding & Purpose Designation: The issued credential (e.g., a specific type of client certificate or token) must be cryptographically and uniquely bound to the verified individual’s identity and explicitly designated for "self-access/patient-developer" use only.
- Cost-Free to the Individual: Obtaining this Patient-Developer Credential must be free of charge.
- TEFCA Network Access using the Credential:
- Full TEFCA QHIN API Access (for Own Data): When presented by an application, this credential must grant access to the full suite of TEFCA QHIN APIs (e.g., query, retrieve) that a commercial IAS provider or other network participant would use.
- Strictly Scoped to Own Data (Network Level): Access granted via this credential at the QHIN level must be technically restricted to only the data pertaining to the credentialed individual.
- Mandatory QHIN Recognition & Fee Exemption: All TEFCA QHINs must recognize valid Patient-Developer Credentials and not charge individuals or their apps network access fees for this personal use.
- Facilitating Direct EHR FHIR API Access for Patient-Developers:
- EHR Recognition of Patient-Developer Context: The TEFCA framework (or related ONC certification criteria for TEFCA participants) should ensure that EHR systems of TEFCA participants are capable of recognizing a context or assertion associated with the Patient-Developer Credential (or a derivative token) to streamline app registration for direct EHR FHIR API access for that specific patient's data.
- Simplified EHR Dynamic Registration Pathway: For applications presenting evidence of being operated by a patient for their own data (potentially signaled via the Patient-Developer Credential context), EHRs supporting dynamic registration must offer a simplified pathway. This could involve accepting specific assertions or self-attestations for app identity in lieu of more complex commercial registration requirements, enabling individual/hobbyist app development for personal data access directly from an EHR's FHIR API is achieved through this mechanism).
- No Prohibitive EHR Registration Fees for Personal Use: This simplified pathway for patient-developers accessing their own data directly from an EHR should not involve prohibitive registration or certification fees from the EHR vendor.
- 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.
