# What are Redox connections?
A **connection** is a set of subscriptions (i.e., integrations) you have with a connected organization that agrees to exchange healthcare data with you via Redox.
Connections are important because they:
- Represent a business relationship between you and a connected organization.
- Enable data flow between different systems.
- Simplify integration since you can build multiple subscriptions for one connected organization.
## Who can you connect to via Redox?
In the digital health world, "integration" is a loaded word that includes conversations about EHRs, HL7v2, FHIR, VPNs, APIs, and more. Review the ecosystem options you have with Redox below.
Connected solutions: Current Redox customers
When we talk about **connected solutions**, we’re talking about Redox customers. This is an incredible library of digital health companies—from scrappy startups to industry unicorns—using Redox to power their interoperability.
[Review the organizations](https://redoxengine.com/connected-solutions/) that have "graduated" Redox onboarding. They aren't just _thinking_ about integration; they are proven and ready to connect to health systems and other partners right away.
Connected organizations: Healthcare entities
Whether it’s an EHR system, a Health Information Exchange (HIE), an Enterprise Resource Planner (ERP), or a Cloud Hosted Provider (CHP), we’ve likely seen it.
To date, Redox connects to over 100 different EHR systems and 80+ additional platforms. If your customer is using it, there’s a high probability we already speak its language. [Use Redox explore](https://redoxengine.com/explore/) to see which healthcare entities we've already reached.
When we say a hospital or a payer is a **connected organization**, it means we’ve integrated there before and are _actively exchanging live data_ with them for other Redox customers. This is a massive shortcut for your implementation team. When we have an active connection, we move at lightning speed because:
- **We skip the security line**: If we’ve already cleared their security review, we don’t have to start from scratch.
- **The integration pipes are already laid**: Reusing existing VPNs or cloud integrations can shave weeks off a timeline.
- **We have the "cheat codes"**: We apply our existing configuration library tailored to that specific site. Instead of sweating over custom specs, we use what we know works, while still maintaining the flexibility to customize for your specific needs.
Redox partners: Cloud connectivity and enrichment
Interoperability isn’t just about moving data from point A to point B; it’s about what you do with it once it’s moving. [Review our partner ecosystem](https://redoxengine.com/company/partners/) helps you do more:
- **Cloud partners**: We know how to get your data to the cloud in real-time using standardized formats that minimize the "data cleaning" you have to do downstream. We have deep expertise with AWS**,** GCP**,** Databricks**,** Azure**, and** Snowflake**.** Learn more about cloud connectivity.
- **Enrichment partners**: Want to enhance your data in flight? Partners like IMO and Verato help you normalize code sets and manage patient IDs while the data passes through Redox. Keep an eye on this space—we’re constantly adding partners to help you enrich your data.
Interoperability shouldn’t be the thing that slows your growth. Whether you’re looking to join our family of **connected solutions** or need to tap into our healthcare network of healthcare organizations and payers, Redox handles the "niche lingo" so you can focus on building great software.
[Review all our supported methods and specifications](/implementation-guide/supported-methods-and-specifications). Don’t see a connection you want to work with? [Learn about how to add a new system adapter](/implementation-guide/add-a-new-system-adapter-to-redox) to the Redox ecosystem. Then, [learn how to request a new connection](/how-to-use-redox/manage-your-redox-setup/request-a-connection-or-subscription).
## View your Redox connections
We help you establish connections with your preferred partner organization(s). You can view them on the Connections page of the Redox dashboard.
> **Connections must have subscriptions **
>
> For a connection to appear in the dashboard, it must have at least one subscription. If you don’t see the connection you expect, talk to a Redoxer to make sure a subscription has been created for it.
*Your Redox connections*
When you set up your Redox organization, there are two default connections to Redox Engine and Redox Health System. These connections are available so that you can configure and test your system with Redox. [Learn how to request a new connection](/how-to-use-redox/manage-your-redox-setup/request-a-connection-or-subscription).
*Default connections*
## What are subscriptions?
A connection must have at least one subscription, but likely has multiple. A **subscription** is the bridge of data exchange between two systems. It links a source, destination, and data model to define how and what data is exchanged between two organizations.
### One-party subscriptions
> **Closed beta feature**
>
> This is a closed beta feature for a limited pilot group by invitation only. We’re not currently accepting additional participants, but we’ll let you know when it’s available to everyone.
Typically, a **subscription** is the bridge of data exchange between _two_ parties (or two systems). However, you can choose to have a subscription with yourself, meaning your organization owns both the source and destination.
A one-party subscription is useful for populating **cloud repositories**. [Learn more about Redox cloud connectivity](/basics/connecting-to-the-cloud-with-redox).
To populate a cloud repository, you can create a cloud destination within your Redox organization, then set up a subscription from a source you own. [Learn how to create a destination](/how-to-use-redox/manage-your-redox-setup/set-up-destinations).
## View your Redox subscriptions
On the Connections page of the Redox dashboard, you can view either:
- One connection’s subscriptions at a time in a visual flow on the Connected orgs tab.
- All your subscriptions at once in a table on the All subscriptions tab.
Connected orgs tab
By default, the Connected orgs tab opens with tiles for each of your connections. To view subscriptions for one connection at a time, click the **connection** **tile** you want to review. The Subscriptions tab opens with a visual of the sources and destinations used, the type of data exchanged, and the direction of traffic.
*Connected orgs tab: View one connection’s subscriptions*
Subscriptions show the “what” and “how” of each implementation (i.e., integration) with your Redox connections.
*Your subscriptions*
| | **Description** |
| --- | --- |
| **1** | Your Redox organization. This list shows the source or destination in each subscription that you own. |
| **2** | The name and ID of the source or destination. Click the **name** to open the settings or the **copy** icon to copy the ID. You can also navigate to the Developer page to view all your sources and destinations independent of their subscriptions. |
| **3** | Your connection’s organization. This list shows the source or destination in each subscription that your connection owns. |
| **4** | The name and ID of your connection’s source or destination. Click the **name** to open the settings in a read-only view. Or click the **copy** icon to copy the ID. There might be duplicate IDs if your connection has one source or destination for asynchronous and synchronous traffic. It might look like your connection has extra sources or destinations, but it’s only splitting them out by traffic type. |
| **5** | The type and direction of traffic. The type is the Redox data model or FHIR resource that’s being exchanged. The direction of the arrow for asynchronous traffic goes from the source to the destination. This represents one-way traffic that’s delivered without waiting for a response. The direction of the arrow for synchronous traffic shows traffic going from the destination to the source. This represents two-way traffic: The source sends a query and the destination responds with results. The number of arrows matches the number of subscriptions you have. To see another view of how data travels from source to destination, [learn about logs](/basics/data-exchange-with-redox/logs-for-data-exchange). |
| **6** | The VPN status of an MLLP source or destination. [Learn more about checking a VPN status](/how-to-use-redox/check-a-vpn-status). |
All subscriptions tab
To view all existing subscriptions at once, click the **All subscriptions** tab. A table opens with an active subscription in each row. _For beta one-party users_, [learn how to create a subscription](/how-to-use-redox/manage-your-redox-setup/create-a-subscription).
*All subscriptions tab*
To narrow down the list of subscriptions, enter any **keyword** into the Search field. For example, to search for active subscriptions, enter “Active”. The table filters to only subscriptions with an Active queue status.
*All subscriptions table*
Review the details in the columns of each subscription:
- **Connected org**: The organization name of the connection. Click the **sort icon** to sort the subscriptions by connection alphabetically in ascending or descending order.
- **Subscription**: The name of the subscription.
- Click the **subscription name** to open the Details page with the source, destination, data model, go-live (i.e., activation) date, and queue information.
- If a user in your organization created the subscription and is assigned to an engineer role, click the **pencil icon** to edit the subscription name.
- If you own the destination in the subscription, you can view and manage filters from the Details page. [Learn how to define filters](/how-to-use-redox/define-and-manage-filters).
- _For beta users_, you can delete the subscription from the Details page, too.
- **Data model**: The Redox FHIR or Redox data model that determines the shape of the data being exchanged.
- Click the **View logs** link to see the subscription’s related logs. The Logs page automatically opens with the source, destination, and data model filters already populated.
- **Queue**: The current status of the subscription queue. Subscriptions with async traffic could have any of these three statuses:
- Ready: The queue is ready for traffic, but nothing is flowing. Once traffic starts to flow after go-live, this changes to Active.
- Active: The queue is running and traffic is flowing through the subscription queue. The queue depth (i.e., the number of async messages waiting to be processed in the subscription queue) appears beneath the status. [Learn more about queues and handling async notifications](/basics/data-exchange-with-redox/handling-notifications-and-responses).
- Paused: A Redoxer has manually paused the queue. The queue depth still appears beneath the status. Talk to your Technical Account Manager for more details.
> **Queue depth**
>
> Most active, healthy async subscriptions have a queue depth close to 0. Queue depth might be higher if:
>
> - Queue is retrying a failed transaction or has been manually paused. [Learn more about when Redox pauses a queue](https://docs.redoxengine.com/permalink/1vFPDeTOMENuIP4mzkONZ9/#when-redox-pauses-the-queue).
> - Transaction volume is higher than usual (e.g., backfilling historical data).
> - Traffic includes SFTP file transfers.
>
> If the queue depth doesn’t drain and is continuously increasing over a 24-hour period, [submit a request to our Help Center](https://redoxengine.zendesk.com/hc/en-us).
- **Source**: The name, owner, VPN status (if applicable), and directionality of the source associated with the subscription.
- Hover over the **copy icon** to view or copy the source ID. Or, click the **source name** to open the Details page to view its configured settings and VPN details.
- If your organization owns the source, users assigned to an engineer role can click the **Edit** button to open the source wizard or click the **Delete** button to delete the source from the Details page. [Learn more about roles](/basics/managing-access-for-your-redox-organization/what-are-user-roles).
- If your organization doesn’t own the source, you can view the name and basic details, including VPN ports (if applicable).
- **Destination**: The name, owner, VPN status (if applicable), and directionality of the destination associated with the subscription.
- Hover over the **copy icon** to view or copy the destination ID.
- Users assigned to an engineer role can click the **destination name** to open the destination wizard and edit any destination settings. [Learn more about roles](/basics/managing-access-for-your-redox-organization/what-are-user-roles).
## What are sources and destinations?
A subscription must have one source and one destination. Sources and destinations are the building blocks of data exchange:
- A **source** represents where a messages starts (i.e., `SEND`, `REQUEST`). Think of a source like the address in the “From” line of an email header, which specifies where the message originates.
- A **destination** represents where a message is delivered (i.e., `RECEIVE`, `RESPOND`). Think of a destination like the address in the “To” line of an email header, which specifies where the message should go.
You can view and manage sources and destinations on the Developer page of the Redox dashboard.
*Your sources and destinations*
One of the main benefits of Redox is that you can typically use the same API source and destination to exchange data with all of your connections. However, you might want to use unique sources and destinations for each communication method. [Learn more about data exchange](/basics/data-exchange-with-redox).