1up Clinical Connect automates clinical data acquisition directly from providers' EHRs, unifying USCDI-v3.1-standard clinical data with claims into a single longitudinal member record.
1upHealth, the payer, and the provider organization collaborate to create a patient roster. These are the provider's patients who have coverage with that payer. 1up will only request data for patients on that roster. See below for more information about the member roster.
Information about 1upHealth's architecture and certifications are available at our 1upHealth Security Trust Center.
1up Clinical Connect works with existing APIs your EHR already supports. The process is designed to be as easy for provider organizations as possible.
1up Clinical Connect runs in the background with no disruption to your providers' clinical workflow and no day-to-day maintenance for your IT team.
Typically, this connection takes at most a few hours of your team's time. 1upHealth will need a project point of contact and a technical or support contact.
The connection process depends on your EHR and how it supports authorizing external organizations to access the required FHIR API endpoints. Consult your EHR's documentation or support team to scope the effort required for approving 1upHealth's connected app. For example, here is the 1up Clinical Connect app on Epic Showroom™.
1upHealth has already connected to providers using Epic® and athenahealth®.
At a high level, regardless of the EHR, this is how connecting your EHR for 1up Clinical Connect works:
- Authorize 1upHealth to query your FHIR API endpoints. This authorization process depends on the EHR.
- You, the payer, and 1upHealth collaborate to create a member roster.
- 1up queries clinical data from individual patients on the member roster.
- 1up presents that clinical data to the payer.
1up searches for each patient's data individually with a standard FHIR search using information from the member roster. The searches use either unique IDs in your EHR, or matching demographic parameters for the Patient resource.
Each of our payer customers leveraging 1up Clinical Connect provide 1up with a member roster so 1up can query data for specific patients. There are two types of rosters:
- ID-based: Payers provide a member roster file with IDs for each member according to the provider's EHR. This type requires payers to coordinate with providers to provide exact matches based on a unique ID like Medical Record Number (MRN), Social Security Number (SSN), etc.
- Demographic-based: Payers provide a member roster file with demographic information like name, date of birth, postal code, etc.