Connecting Medical Records Through Epic-Compatible Healthcare Organizations
An accessible explanation of Sift’s intended, patient-authorized connection to participating healthcare organizations.
How connection is intended to work
- 1
Open Sift and choose to connect a healthcare organization.
- 2
Locate the relevant healthcare provider.
- 3
Continue to the provider’s authorization experience.
- 4
Sign in through the provider’s own authentication process.
- 5
Review the permissions requested by Sift.
- 6
Explicitly authorize access.
- 7
Return to Sift to review imported information.
What happens during authorization
Sift should not ask you to give your MyChart password directly to Sift. Authentication occurs through the healthcare organization’s supported authorization experience. You review requested permissions and decide whether to grant them.
Access is limited by the permissions you grant, the organization’s available APIs, and the capabilities Sift has actually implemented. You should be able to revoke access through supported controls once that behavior is verified.
Technical explanation
SMART on FHIR, FHIR R4, OAuth 2.0, and USCDI v3
FHIR R4 is a version of the HL7 standard used to exchange healthcare information in structured resources such as Patient, Observation, and MedicationRequest.
SMART App Launch defines OAuth 2.0-based patterns that let an app request authorization to access a FHIR server. Scopes describe the types of access requested; they do not guarantee that data exists or that every organization exposes it.
OAuth 2.0 lets the healthcare organization authenticate the patient and issue limited access without sharing the patient’s password with Sift.
USCDI v3 automatic client distribution describes Sift’s registration setting. It does not establish access to every Epic API, every MyChart feature, or every item in USCDI v3.
What this connection does not include
The intended registration is for patient-authorized, read-only retrieval of available health information. Messaging clinicians, scheduling appointments, modifying records, prescribing, and other workflows require separate functionality and authorization. This page does not claim those capabilities.
Availability and completeness
Sift is not affiliated with, sponsored by, or endorsed by Epic. Registration does not mean the application is approved, certified, deployed, or used by an Epic customer.