Set Up a FHIR Connection
Use FHIR Connections to connect an EHR endpoint, then link Gravity Rail Members to the matching patient records. The EHR administrator supplies the endpoint and client credentials. A connection alone does not link Members or expand access in the EHR.
Create the connection
- Open Connections → FHIR Connections and select New FHIR Connection.
- Choose the EHR vendor shown in the wizard: eClinicalWorks, Epic, Cerner, or Athena.
- Enter a connection name and the FHIR base URL supplied for that environment. Add the Practice ID if the EHR requires it.
- Enter the client ID and any client secret or token endpoint supplied by the EHR administrator.
- Review the rate limit and save the connection. Keep sandbox credentials paired with the sandbox URL and production credentials paired with the production URL.
The App Connections Directory also lists a general FHIR Connection entry. The FHIR setup wizard currently asks you to choose one of the four vendors above; the generic directory entry is not a fifth vendor option. For vendor-specific setup and Member matching, use the relevant section below.
Generic FHIR directory entry
Use the generic directory entry to open the shared FHIR connection setup when your EHR exposes a compatible FHIR endpoint. Select the matching vendor in the wizard and confirm its endpoint, credentials, and access requirements with the EHR administrator. See the FHIR developer guide for connection and data-mapping contracts.
eClinicalWorks
Select eClinicalWorks and use the endpoint, credentials, and client type provided for that practice. The wizard's client type choice is Backend Bulk or Backend Single Patient. Ask the eClinicalWorks implementation contact which profile is enabled before saving. See the eClinicalWorks integration reference.
Epic
Select Epic and enter the FHIR endpoint and app credentials registered for the customer's Epic environment. Epic controls app approval and which resources are available. See the Epic integration reference.
Cerner / Oracle Health
Select Cerner and use the endpoint and credentials provisioned for the customer's Oracle Health environment. Confirm the authorized resource access with the EHR administrator. See the Cerner integration reference.
Link Members to patient records
After the connection is created, open its Members area and link each existing Member to the correct patient record. A connection does not automatically select a patient based on name or email. For Athena, see the Athena connection walkthrough; it covers the additional practice and Member-linking steps.