Skip to main content

FHIR Connections

FHIR connections connect a workspace to an EHR's FHIR R4 endpoint. Use the App Connections user guide to add a connection and test it. The EHR administrator or vendor supplies the endpoint and the client credentials used for that environment; Gravity Rail does not issue EHR credentials.

Supported connections​

The directory offers a generic FHIR connection and vendor-specific entries. Each EHR controls its registration, available resources, and authorization requirements. Confirm production access and permitted FHIR resources with the EHR vendor and customer before configuring a connection.

Generic FHIR​

Use this entry for an EHR that exposes a compatible FHIR R4 endpoint without a dedicated vendor entry. See the FHIR R4 specification for standard resource shapes.

eClinicalWorks​

Use the endpoint and credentials provisioned for the customer's eClinicalWorks environment. eClinicalWorks access is arranged through the customer's implementation; the vendor's registration and resource access requirements apply.

Epic​

Epic registration and endpoint access follow the customer's Epic environment and app approval. See Epic on FHIR documentation for vendor-specific enrollment and API details.

Cerner / Oracle Health​

Oracle Health controls registration and resource access for the customer's Millennium environment. See the Oracle Health Millennium API documentation for vendor-specific API details.

Athena​

Use the endpoint and credentials provisioned for the customer's athenahealth environment. See the athenahealth developer portal for vendor enrollment and API details.

Connection values​

The FHIR connection setup accepts the values supplied by the EHR integration team:

ValueUse
FHIR base URLBase address for the selected FHIR server.
Client ID and optional client secretIdentify the registered integration to the server.
Token endpointAuthorization server endpoint when the EHR supplies one separately.
Practice IDPractice or organization identifier when required by that EHR.
Client typeSelects the supported backend access profile when offered by the EHR.

Use HTTPS for the FHIR base URL and token endpoint. Keep sandbox and production credentials paired with their corresponding server URLs. The EHR's available resources and access approval determine what the connection can read or write; an active connection does not itself grant additional EHR access.

FHIR Member matching uses an existing linked patient identity. Each linked Member has a connection-specific patient identifier (fhir:patient_id). Use the Member link or reconciliation flow to associate an existing Member with the correct patient record. For Member creation and external identity handling, see Creating Members.

The generic FHIR sync contract matches linked records and supports inbound updates to Member properties. Use the connection's Sync settings to choose fields and conflict behavior; see Importing Data for the shared import model.