Part of Connect Data & Intelligence
Shared context. More connected care.
Relay's community information exchange connects the organizations that serve the same members: a shared partner network, consent recorded and checked before information is shared, and access limited by role and organization.
Community Information Exchange
- Keep member identity clear within your organization
- Check consent before information is shared
- Give each team access appropriate to its role
What your team can accomplish
Make information useful across your care network.
Who it serves
- Network leads bringing partner organizations into a shared network
- Care teams that need consent-aware access to member information
- Community partners that accept referrals and report capacity
- Integration teams connecting Relay to other systems
How the exchange works
Record consent before sharing
Versioned, revocable, expiring consents—including 42 CFR Part 2 and consent for AI use—are checked on the server when a referral is bound to a recipient, when a partner receives it, and before AI actions.
Limit access by role and organization
Fail-closed route policies and per-organization row-level security decide what each user can read and change.
Share referrals with community partners
Partners receive the referrals sent to them in the partner portal, accept or decline them, and report services and outcomes back—without access to your organization's full member records.
Run the shared partner network
Partner organizations, programs, capacity and credentialing are reference data for everyone in the network.
Keep one record per person
Possible duplicate members are matched within each organization and reviewed by a person before any merge, with an audit trail.
Connect through standards
FHIR R4 interfaces, an ADT event ingest API and eligibility checks bring outside information into the member record.
Who sees what
Sharing in Relay follows the role, the organization and the member's consent.
| Information | Who can see it | What controls it |
|---|---|---|
| Member record | Staff in your organization, by role | Route policies and organization-level row security |
| Referral | The partner it was sent to | Consent checked when the recipient is chosen; the partner portal shows only its own referrals |
| Consent | Your organization's staff, by role | A versioned ledger of who consented to what, and until when |
| Reporting data | Holders of read-only BI credentials (optional add-on) | Separate credentials that never grant access to records in Relay |
Partners see the referrals sent to them, and your member records stay with your organization.
How it connects to the rest of Relay
- Integrations
FHIR R4, ADT ingest and eligibility checks that bring outside data in.
- Closed-loop referrals
Consent is checked when referrals are bound to a recipient.
- Operate Your Network
The partner network the exchange is built on.
- Security & privacy
Access controls, audit history and data protection.
Plan your community information exchange
Tell us which organizations need to share what, and we'll show how Relay governs it.
Request a demo