Eider uses the SMART on FHIR standard (HL7 FHIR R4) to let you optionally import your health records from participating health systems, including Epic MyChart. This connection is always optional, always user-initiated, and always read-only.
01Overview
Eider uses the SMART on FHIR standard (HL7 FHIR R4) to allow users to optionally import their health records from participating health systems, including Epic MyChart. This page explains exactly what data we request, why, how it flows, and how it is protected.
This connection is always optional, always user-initiated, and always read-only.
02How the connection works
- The user taps "Connect Health Records" in Eider Self settings.
- Eider initiates a SMART App Launch using OAuth 2.0 with PKCE.
- The user is redirected to their health system's login page (Epic MyChart, etc.) in a secure browser.
- The user authenticates and reviews the scopes Eider is requesting before approving.
- The health system returns an authorization code; Eider exchanges it for an access token.
- Eider queries the FHIR R4 API for the specific resources listed below.
- Returned records are stored in the user's private Eider account.
- The user can revoke access at any time — from both Eider settings and their MyChart account.
03FHIR scopes requested
| FHIR Resource | SMART Scope | Why Eider Requests It |
|---|---|---|
| Patient | patient/Patient.read | Match imported records to the correct user profile; populate basic demographics |
| Condition | patient/Condition.read | Pre-populate the user's conditions and diagnosis history in Eider Self, eliminating manual entry |
| MedicationRequest | patient/MedicationRequest.read | Pre-populate prescribed medications in the Eider Self medications list |
| AllergyIntolerance | patient/AllergyIntolerance.read | Pre-populate allergy records for the user and their children, critical for emergency situations |
| Immunization | patient/Immunization.read | Pre-populate vaccine history, which is frequently needed for school enrollment, travel, and new provider intake |
We do not request write scopes. We do not request access to clinical notes, imaging, billing records, or any resource type beyond those listed above.
04Data storage and protection
Imported FHIR records are stored in the user's private Firestore document on Google Cloud, encrypted at rest (AES-256) and in transit (TLS 1.3). Per-user Firebase Security Rules ensure that only the authenticated account holder can access their records. Records imported via FHIR are treated identically to records entered manually — they belong to the user, not to Eider.
05Access tokens
OAuth access tokens are stored securely on-device and are never logged or transmitted to Eider's servers in plaintext. Refresh tokens follow the same handling. Revoking access in Eider settings invalidates the token immediately.
06No write access
Eider requests read-only access exclusively. We do not write back to, modify, or delete any data in the connected health system. Your health system records are never altered by Eider.
07User controls
- Users can revoke Eider's access to their health system at any time in Eider Settings.
- Users can also revoke access directly through their MyChart account.
- Revoking access does not delete records already imported into Eider — those can be deleted separately or via full account deletion.
- Users can delete all FHIR-imported data from their Eider account at any time.
08Minimum necessary principle
We request the minimum scopes necessary to provide the connected health records feature. As we add features, any additional scope requirements will be disclosed to users before activation and will require re-authorization.
09Standards compliance
- HL7 FHIR R4
- SMART App Launch Framework (SMART on FHIR)
- OAuth 2.0 with PKCE
- Patient-mediated exchange (user-initiated, not bulk or provider-initiated)
10Questions about FHIR data use
support@eiderhealth.com · Eider Health LLC · Texas