athenahealth

Embedded UI Component

• Launch the Embedded ZAP from the Apps tab in the patient chart (SMART on FHIR app launcher)
• Write conditions, labs and vitals to the patient chart directly from the ZAP
• Resizable and movable

Data Synchronization

Zus syncs data from athena to Zus via two main mechanisms:

• CCDAs (Consolidated Clinical Document Architecture documents, the standard clinical summaries athenahealth produces)
• athena APIs

CCDA data sync

• Frequency: Zus pulls a patient's full CCDA when any of the following conditions are met:
  • Patients are added to Zus or enrolled in a package
  • On app launch (at most once per 7 days)
  • 3 days after any appointment within athena
  • Every 30 days (if none of the above events triggers a sync)
• Data elements: The following data is pulled from CCDAs during the single patient sync:
  • Allergies
  • Care Plans
  • Care Teams
  • Conditions
  • Coverage
  • Demographics
  • Devices
  • Diagnostic Reports
  • Encounters
  • Family Member History
  • Goals
  • Immunizations
  • Medications
  • Observations
  • Procedures
  • Related Persons

Note: Medications arrive as MedicationStatement resources, which record a medication a patient is taking. Some encounters arrive without a class (for example, ambulatory), so they show an unknown class.

API data sync

• Frequency: Every 15 minutes based on Athena
• Data elements:
  • Appointments
  • Demographics

Custom Fields

Zus is able to consume Athena custom fields into the FHIR Patient.extension. This can be useful if there are custom fields that would be helpful when querying Zus data in Snowflake or to drive auto-enrollment (eg. enrolling in a specific Zus subscription package based on a custom field value).

Setup Requirements

• Go to our listing on the Athena Marketplace and fill out the authorization and consent form
• An Athena admin must enable the app for your practice

Related pages

• EHR Integrations General Concepts
• Automatic Patient Enrollment via EHR Integrations