Start in MedLocker
The user opens Connect Records, chooses the correct MedLocker patient record, and selects Epic / MyChart.
Epic / MyChart connection
Connect MyChart records into your MedLocker timeline.
MedLocker lets a patient or authorized caregiver start a MyChart connection, approve sharing through Epic, and bring supported records into the same private timeline used for visits, labs, medications, documents, and care history.
Consent first
User authorizes in MyChart before MedLocker imports records.
Patient record
Imported data appears in MedLocker timeline and summary views.
Control remains
Disconnect stops future syncs; sharing stays user-directed.
How it works
A user-directed connection from MyChart into MedLocker.
The connection starts inside MedLocker, continues through the MyChart authorization flow, and returns data to the selected MedLocker record after authorization succeeds.
Authorize in MyChart
The user signs in through the Epic authorization experience and approves sharing supported records.
Review the updated record
MedLocker imports supported data into the patient timeline, summaries, and source-aware record views.
Consent summary
Connecting MyChart is user-initiated. Disconnecting the portal stops future syncs; it does not silently erase records already brought into MedLocker.
What imports
Patient-readable categories first, reviewer detail below.
MedLocker imports the categories it can already organize into useful product views. Unsupported categories are not presented as if the record were complete.
Supported FHIR resources for reviewers
Encounter
Condition
AllergyIntolerance
MedicationRequest
MedicationAdministration
Observation
DiagnosticReport
Procedure
Immunization
DocumentReference
CarePlan
CareTeam
For patients and caregivers
Imported records stay inside the normal MedLocker experience.
Epic data is shown in the same longitudinal record, timeline, summaries, and linked patient views that MedLocker uses for other sources. Users can see connection state, refresh status, and whether MyChart needs attention.
User-visible status
Connected, syncing, needs reconnect, disconnected, or failed states are visible in product surfaces.
Backend-owned credentials
The mobile app starts the flow, but the MedLocker backend handles token exchange and encrypted token storage.
Support contacts
Product support: hello@alpinelabs.ai
Privacy questions: privacy@alpinelabs.ai
MedLocker trust docs