# Supporting FHIR Subscriptions

<u>**FHIR Subscriptions**</u> are a service that allow you to receive event notifications from another organization based on a triggered event (e.g., a patient arrived for an appointment or lab reults were posted). Once a <u>Subscription</u> has been established, you can receive <u>FHIR notification</u> with the relevant event data. [Learn more about FHIR subscriptions](https://build.fhir.org/subscriptions.html).

Redox supports <u>FHIR Subscriptions</u> on your behalf. Generally, this works like this: 

1. An EHR system pushes events to Redox.
2. Redox translates and enriches like we do for any other data standard (e.g., HL7v2).
3. Redox pushes the data to you through a Redox FHIR notification. [View our supported FHIR notifications](https://docs.redoxengine.com/permalink/fhir-notification-landing-page).

While HL7 FHIR defines standards for Subscriptions, EHR adoption of this standard is still emerging. Each EHR system also handles and authenticates their outbound events differently, meaning Redox must do implementation work to support Subscriptions for them. As more EHR systems adopt FHIR Subscriptions, we will add connectivity for them. 

Currently, we support FHIR Subscriptions with this EHR system: 

- [athenahealth](https://www.athenahealth.com/)