GALE - Athena Integration
This page contains resources and frequently asked questions regarding the GALE-Athena integration
Introduction
We recognize that implementing a system like GALE involves many logistical details, especially when paired with an extensive system like Athena. While we can’t speak to specific Athena policies, procedures, or workflows, we can address several common questions about our integration and how it may affect the everyday operations at your Health Centers.
If you have additional questions or concerns about your deployment that aren’t covered below, please don’t hesitate to contact us. We’re happy to help however we can!
Frequent Questions
Workflow Questions
Why do I have to log in?
In order to “send” data (vitals, notes) to a Patient Profile on Athena from GALE, we need to know who that patient is. To access patient details from Athena, a login is required, as this information is sensitive.
If a patient doesn't have an account, can I create one on GALE?
No. Patients must be created prior to a GALE encounter. GALE operators are not able to create patient profiles.
Is the department the location of the provider or the patient?
This is up to you, depending on how you bill your visits.
What details about the patient can the operator see?
-
Basic patient details (Name, DOB, Gender)
-
Insurance details
-
Contact details
-
Previous Measurements
What details about the patient can the operator not see?
Images from the patient's profile are not downloaded onto GALE.
Can the GALE operator edit patient details?
No. Patient details are view-only on GALE.
What if there is an appointment made on Athena before the GALE encounter?
Do not create an appointment through Athena for GALE consultations. The encounter is treated like a walk-in. If an appointment has been created on Athena, it will be ignored, and a new encounter will be created.
What visit details get uploaded from GALE to Athena?
-
Observations (measurements, vital signs)
-
Images (otoscope, exam camera, GALE camera)
-
Visit reason
-
Clinical notes, if written by the Provider through Insights
What visit details do not get uploaded to Athena
-
GALE Intake questions
-
Forms
-
Mp3 files (stethoscope recordings)
Technical Questions
What information does 19Labs need about our Athena instance?
-
practiceId - The practice's Athena practice ID
-
departmentId - The department ID for patient searches and document uploads
-
appointmentTypeId - The appointment type to use for walk-in appointments
Why do I have to give 19Labs details about our Athena instance?
We need the above details to be able to “talk” to your Athena instance and to “do the right thing” when we load patients, create encounters, and upload data.
Do 19Labs employees have access to our Athena instance?
No. Only the GALE operator has access to patient data at the time of the encounter, and that is only temporary access to a single patient during an encounter. We do not have access to your Athena instance or any patient data.
Further Scope
We understand that no single solution fits every deployment. That's why we're committed to ongoing collaboration and open communication, ensuring our solution continues to evolve to meet your needs as completely as possible.
Below are a few examples of additional support and capabilities we are exploring. As always, we welcome your feedback! If some features or enhancements would make your workflow even more seamless, please don't hesitate to contact us. We're always looking for ways to support your success.
School-based use case
Explore additional workflows and users that allow uploading patient data to Athena
Additional data uploads
-
Intake questions
-
Forms
-
Visit summary PDF
-
Mp3 (Stethoscope recordings)
Additional downloads
-
Images
-
Documents
Documents
Test Cases
We recommend that all deployments validate their integration in a test environment before rolling it out across all locations. This collaborative testing process helps ensure the integration is configured correctly and that our systems are communicating as expected before full deployment.
While we thoroughly test all features and functionality prior to release, we do not have direct access to individual customer environments. As a result, we rely on each Health Center to partner with us during validation to confirm the integration performs as expected within their unique environment.