About Patient Connect
You can use 1upHealth’s Patient Connect mobile responsive web app to get access to 1upHealth’s FHIR® APIs from more than 7,600 supported health plans and health systems. App developers can use Patient Connect to help patients instantly connect to health plans and health systems, using an automated login process to authorize access to their electronic medical records.
Patient Authorization Workflow
To connect to supported health plans and health systems, and enable access to their data, patients complete the following process to allow access to their data.
Patient access steps
-
In the 1up System Search interface, patients search for the hospital name where their medical records are stored.
An app developer can embed the search interface as an iframe in existing workflows, or create a custom search tool that uses our 1up API endpoints to get the search results.
-
After patients locate their providers or hospitals, they can enter their patient portal credentials.
App developers can include instructions for patients to create their patient portal credentials, if they don't already have their credentials.
-
After patients enter their portal credentials, they can authorize a third-party app to get access to their electronic medical records.
This patient authorization is enabled by ONC’s 21st Century Cures Act.
Patients who have medical records in multiple hospitals must authorize access from each hospital.
About HIPAA & Patient Consent
This patient authorization workflow is allowed by ONC’s 21st Century Cures Act. The ONC 21st Century Cures Act Final Rule is focused on empowering patients by making it easier for them to get access to their electronic healthcare information.
Patients can allow third-party apps to access their health data through the secure, OAuth 2.0 process, which enables patients to choose a safe, reputable, third-party health data app to share their electronic medical records with.
About EHR Data
After patients authorize a third-party app to get access to their electronic medical records, the authorized data can be retrieved as read-only data using our 1up FHIR APIs. The FHIR resources include patient demographics, prescriptions, doctor notes, allergens, and more.
Test Credentials
For testing purposes, you can use the following test user names and passwords for each of the specified EHR (electronic health record) vendors. In the 1upHealth application, the demo connection health systems include the (demo) label.
Test accounts in the EHR Sandboxes are provided and maintained by the major EHR vendors. The availability of these accounts is not guaranteed by the vendors. We monitor the status of the accounts and if there are issues with the accounts, we work with the EHR vendors to restore the accounts at the earliest possible time.
|
EHR |
Environment |
FHIR Version |
Account user names |
Account passwords |
|---|---|---|---|---|
|
Veradigm |
Test Allscripts Professional 20.1 FMH EHR ID: 32 |
DSTU2 |
donna.dobson_prounityfhir |
Allscripts#1 |
|
Cerner |
Test Cerner EHR ID: 4707 |
DSTU2 |
wilmasmart joesmart1 nancysmart valeriesmart1 fredricksmart timmysmart haileysmart timApeters |
Cerner01 |
|
Epic® |
Test Epic EHR ID: 4706 |
DSTU2 |
fhirjason fhirdaisy fhircamila fhirderrick fhirdesiree fhirelijah
|
epicepic1
|
|
Test Epic EHR ID: 8364847 |
R4 |
|||
|
Medicare |
Test Medicare EHR ID: 4748 |
STU3 |
BBUser29999 |
PW29999! |
|
eClinicalWorks |
Test eCW EHR ID: 11035 This test environment is unavailable. |
STU3 |
AdultFemaleFHIR AdultMaleFHIR ChildFemaleFHIR ChildMaleFHIR |
e@CWFHIR1 |
