Short answer: Epic (MyChart), Oracle Health, athenahealth (for its athenaPractice, athenaFlow and athenaFlex systems) and NextGen Healthcare each publish patient-access connection points for apps (their own pages, checked 20 October 2026). A Cures Act rule requires developers of health record software certified to the federal standardized-API criterion to offer a patient-access API and publish, at no charge, the web addresses apps use. Whether you can connect depends on your provider's setup and your app's support for that vendor. PatientPower connects to Epic MyChart today.
The 21st Century Cures Act led the federal health IT office, the Office of the National Coordinator for Health Information Technology (ONC), to issue its Cures Act Final Rule in 2020. ONC says the rule calls on the healthcare industry to adopt standardized application programming interfaces (APIs), which will help allow individuals to securely and easily access structured electronic health information using smartphone applications.
In practice, the API part of the rule is a condition on certified electronic health record software: it binds the software developer, while each hospital or practice deploys that software for its own patients. Health IT certified to the standardized API criterion in 45 CFR 170.315(g)(10) must offer a patient-access API built on the HL7 FHIR standard. Under 45 CFR 170.404, the developer of that software must let health information be accessed, exchanged and used without special effort through APIs, and must publish, at no charge and in a standard format, the service base URLs and related organization details that patients can use to access their electronic health information, for all of its customers. A service base URL is the web address an app connects to for one health system or practice.
A second part of the rule covers information blocking (45 CFR Part 171). It applies to health care providers, certified health IT developers, and health information networks and exchanges, and it includes exceptions, such as for privacy and preventing harm, under which some information may lawfully be withheld. The rule does not mean every app can reach every record: the app has to support your provider's system, your provider's connection has to be active, and you approve what is shared.
The table summarizes what each vendor's own patient or developer page says, as checked on 20 October 2026. These pages describe what the vendor offers; they do not show whether your particular hospital or practice has switched it on, and vendor pages change, so check the linked page for the current wording.
| Vendor (patient portal) | What the vendor's own page says | Where to look | Checked on |
|---|---|---|---|
| Epic (MyChart) | MyChart help says you approve sharing, usually by logging in to your MyChart account, and that apps can only request a standard set of information called USCDI. It says one reason you may not find your organization in an app is that the organization might not have turned on support for the app. Epic's endpoint list says apps can use it to connect to health systems that use Epic software. | mychart.org help: Can I share my health information with another app?; open.epic.com Endpoints list | 20 October 2026 |
| Oracle Health (Millennium Platform and Soarian Clinicals) | Oracle's developer page says that after a consumer app is registered, it will be provisioned for all active Oracle Health Millennium Platform and Soarian Clinicals FHIR API consumer access endpoints, which can be accessed in a machine-readable format. | oracle.com: API Access and Fees and Registering an App | 20 October 2026 |
| athenahealth (athenaPractice, athenaFlow and athenaFlex) | athenahealth's developer portal for athenaPractice and athenaFlow has a FHIR URLs page that lists base URLs of API servers that can be used by apps for patients to access their electronic health information, and says the same base URL serves athenaFlex FHIR R4 APIs. This portal is labelled for athenaPractice and athenaFlow and does not mention athenaOne; if your practice uses athenaOne, ask the practice whether patients can connect a third-party app. | mydata.athenahealth.com: FHIR URLs | 20 October 2026 |
| NextGen Healthcare | NextGen's Patient Access API page describes its Enterprise Patient Access API as being for developers creating apps that give patients access to their own health data, and offers a Practice Search where developers can see whether a practice has installed and configured the Patient Access API. The same page also documents a FHIR API for NextGen Office. | nextgen.com: Patient Access API | 20 October 2026 |
Step 1. Search for your provider inside the app you want to use. Many apps build their provider search from vendor endpoint lists like those above; PatientPower's Epic search, for example, is built from Epic's public directory. If your provider appears, start the connection; you will usually be sent to your provider's own sign-in page to approve the request.
Step 2. If you cannot find your provider, try the exact name shown on your portal's sign-in page, or the hospital or clinic name. For Epic MyChart, Epic's help gives two reasons an organization may not appear: it might not have turned on support for the app, or the name you are searching for might not match exactly.
Step 3. Ask your provider which electronic health record system it uses and whether patients can connect a third-party app to it. The medical records or health information management office is usually the right place to ask. Being on a vendor's list does not guarantee that a provider has turned on support for every app, and a provider may be missing from a vendor's list; NextGen's page, for example, lets developers check practice by practice whether the Patient Access API has been installed and configured.
Step 4. Check your portal's settings for connected apps. In MyChart, Epic's help describes Linked Apps and Devices, where you can see apps you have shared with and stop sharing.
If your provider is covered by HIPAA, you still have a legal right to your records. Under the HIPAA right of access (45 CFR 164.524) you can ask for a copy of your medical records, including an electronic copy where the provider holds them electronically; the provider generally must act within 30 days and may charge a reasonable, cost-based fee. A written request to the provider's medical records office is the usual route. Our guide to getting records from a provider that is not on MyChart includes a request letter you can use.
Once you have the copy, you can keep it alongside your other records. PatientPower lets you add records from a provider that does not use Epic by typing information in, with an AI that can read a PDF or a photo of a document to help. Our guide to organizing MyChart records from multiple providers walks through putting records from several sources in one place.
If you believe a provider is unreasonably refusing or delaying electronic access, ONC's information-blocking page explains the rules and their exceptions.
PatientPower is a personal health record app. Today it connects to Epic MyChart: its Epic MyChart connection is live and was approved for use on 16 September 2026. That approval does not mean Epic endorses PatientPower; PatientPower is an independent app and is not affiliated with or endorsed by Epic. You sign in on your health system's own MyChart page, so PatientPower never sees your MyChart password.
PatientPower does not connect directly to Oracle Health, athenahealth, NextGen or other non-Epic portals today. For those providers, use the PDF, photo or manual entry options described above.
Records you connect or add may be incomplete, delayed or contain errors, so verify important details with your care team. PatientPower is for education and organization; it does not diagnose conditions and is not medical advice.
Related: How to organize MyChart records from multiple providers · Connect your Epic MyChart records to PatientPower · Is it safe to connect third-party apps to MyChart?.
Not directly. The rule requires the developer of electronic health record software certified to the federal standardized-API criterion to offer a standard patient-access API and to publish, at no charge, the web addresses apps use to connect. Separately, the Cures Act information-blocking rule applies to health care providers, with exceptions such as privacy and preventing harm. Whether you can connect a given app still depends on your provider's setup and on the app supporting that system.
Both vendors publish patient-access connection points. Oracle says registered consumer apps are provisioned for all active Oracle Health Millennium Platform and Soarian Clinicals FHIR API consumer access endpoints. athenahealth's developer portal for its athenaPractice and athenaFlow systems lists FHIR base URLs that patients' apps can use to connect, and says the same base URL serves athenaFlex (both checked 20 October 2026). You need an app that supports that vendor. PatientPower connects only to Epic MyChart today.
For Epic MyChart, Epic's help gives two reasons: the organization might not have turned on support for the app, or the name might not match exactly. Try the name on your portal's sign-in page, or ask the provider whether it supports third-party app connections.
Epic MyChart. PatientPower's Epic MyChart connection is live and was approved for use on 16 September 2026; this is not an Epic endorsement. For other portals you can type information in, and PatientPower's AI can read a PDF or a photo of a document to help.
Request a copy of your records from a HIPAA-covered provider under the HIPAA right of access (45 CFR 164.524), including an electronic copy if the provider keeps your records electronically, then keep the copy and enter what you need into your personal health record.
It is a standard way for an app you choose to read parts of your health record after you sign in to your provider's portal and approve the request. Health IT certified to 45 CFR 170.315(g)(10) must support it using the HL7 FHIR standard.