A connection is an organization that you can exchange data with via Redox. A single connection may include one or more technical integrations that allow for connectivity between your system and those of the organization you're connected with.
We help you establish connections with your preferred healthcare organization(s). Then, you can view all of your connections on the Connections page of the Redox dashboard.
When you first set up your organization on Redox, you have two default connections to Redox Engine and Redox Health System. These connections are available so that you can configure your system with Redox using any of the available data models.
Learn how to request a new connection.
The first step to complete before viewing your connections though, is to create and manage the API keys and endpoints used to exchange data—whether via SEND, RECEIVE, REQUEST, or RESPOND—on the Developer page of the Redox dashboard.
The beauty of configuring an API key or endpoint with Redox is that you can typically use that same configuration to integrate with multiple connections. There are cases for having more than one configuration with Redox; for example, you may want a unique configuration for each communication method you establish. But most often, you can use the same configuration for a given API action to exchange data with all of your connections.
Learn more about data exchange.
After you configure your system, we help establish the business agreement with your connection and configure the nitty gritty details of the data models you want to exchange, the notifications you want to receive, and any filters you want to apply. Then, you get to see the visual picture of your configuration and connections back on the Connections page.
On the Connections page, you now find a list of your connections. When you click on one of the connection tiles, the Data Flow tab opens, which displays the respective data flow for that connection.
Data flows are a visualization of the data exchange between you and your connection, including the type of data exchanged, the direction of the data, and your connection's endpoints—in other words, all the nitty gritty details that we helped you configure.
The left side of a data flow represents your system. Since you must have at least one endpoint to receive data, the endpoint GUID of your system displays on the left. You can copy this GUID by clicking the copy icon next to it. You can also view and manage the endpoint by clicking on the URL for the endpoint, which opens the endpoint's Settings page. Or, you can navigate to the Developer page to view all your endpoints. If you have a VPN endpoint, you can also see a status icon with a color code to display the current VPN status. Learn more about VPN statuses.
The right side of a data flow displays a list of your connection’s endpoints, but some may have duplicate IDs. This happens if your connection has one endpoint to handle multiple event types (e.g., a connection may use one endpoint for both RECEIVE and RESPOND transactions). For the sake of simplicity, we show the endpoint for those transactions separately in the dashboard. Just keep in mind that the list on the right might seem like it has extra endpoints, when in actuality, some endpoints simply display twice. You can copy your connection endpoint's GUID or view the endpoint's Settings by clicking the URL, just like you can with yours. The difference is that your connection's endpoint details aren't editable.
In between your system and your connection's system, an arrow indicates the direction of the data being exchanged, as well as the data model or FHIR® resource being used. The number of arrows on the page is determined by the number of data models or FHIR® resources you plan to exchange (SEND, RECEIVE, REQUEST, or RESPOND) with your connection.