Connect to Providers
You can use EHR Connectivity to connect to the provider sites for these EHR (Electronic Health Record) vendors: Epic®, Cerner (Beta), and Athena (Beta). The integration process is managed by 1upHealth and can vary for each EHR.
The 1upHealth Implementation team works with each of your providers to establish a connection within your 1upHealth network. We then validate that the data ingestion process is working properly and that the supported resource types are imported correctly to the 1upHealth FHIR Server.
Supported Resources
EHR Connectivity supports the data elements specified in United States Core Data for Interoperability v1 (USCDI v1). The USCDI resources that are available vary depending on the capabilities of each EHR vendor: Epic, Cerner, and Athena.
Epic Integrations
To import resources, Epic integrations use Epic’s FHIR® R4 APIs. For each patient, the following primary resources are imported to the 1up FHIR Server.
-
AllergyIntolerance
-
CarePlan
-
Condition
-
Device
-
DiagnosticReport
-
DocumentReference
-
Encounter
-
Goal
-
Immunization
-
MedicationRequest
-
Observation
-
Procedure
-
ServiceRequest
The following secondary resources are also imported, if they are referenced by any of the primary resources.
-
Binary
-
Location
-
Medication
-
Organization
-
Practitioner
We also generate the following resources.
-
ClinicalImpressions
-
Provenance
Cerner Integrations
Cerner connections are in Beta.
To import resources, Cerner integrations use Cerner’s FHIR R4 APIs. For each patient, the following primary resources are imported to the 1up FHIR Server.
-
AllergyIntolerance
-
CarePlan
-
CareTeam
-
Condition
-
Device
-
DiagnosticReport
-
DocumentReference
-
Encounter
-
Goal
-
Immunization
-
MedicationRequest
-
Observation
-
Procedure
-
RelatedPerson
-
ServiceRequest
The following secondary resources are also imported, if they are referenced by any of the primary resources.
-
Binary
-
Location
-
Organization
-
Practitioner
We also generate the following resources.
Provenance
Athena Integrations
Athena connections are in Beta.
To import resources, Athena integrations use Athena’s DSTU2 APIs and convert them to R4. For each patient, the following primary resources are imported to the 1up FHIR Server.
-
AllergyIntolerance
-
CarePlan
-
Condition
-
Device
-
DiagnosticReport
-
DocumentReference
-
Encounter
-
Goal
-
Immunization
-
MedicationStatement
-
Observation
-
ServiceRequest
The following secondary resources are also imported, if they are referenced by any of the primary resources.
-
Medication
-
Organization
-
Practitioner
We also generate the following resources.
-
CareTeam
-
MedicationRequest
-
Provenance