FHIR
FHIR server operations including resource CRUD, search, and batch operations.
/fhir-providerCreates a new FHIR provider configuration with authentication credentials.
Note: The "sandbox" provider type cannot be created via this API - it is managed internally.
successmessageFHIR provider created successfullydataid1716d214-de93-43a4-aa6b-a878d864e2adnameEpic SandboxdescriptionEpic sandbox environment for testingproviderepicbase_urlhttps://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4client_idyour-client-idauth_configs{}last_updated2024-01-15T10:30:00Z/fhir-provider/{fhir_provider_id}Retrieves a specific FHIR provider configuration by its ID.
Sandbox providers return FhirProviderSandboxInfo. On shared instances, only sandbox providers can be accessed.
successmessageFHIR provider retrieved successfullydataid1716d214-de93-43a4-aa6b-a878d864e2adnameEpic SandboxdescriptionEpic sandbox environment for testingproviderepicbase_urlhttps://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4client_idyour-client-idauth_configs{}last_updated2024-01-15T10:30:00Z/fhir-provider/{fhir_provider_id}Deletes a FHIR provider.
Note: Sandbox providers cannot be deleted.
successmessageFhir provider deleted successfully/fhir-provider/{fhir_provider_id}/fhirExecutes a FHIR Bundle transaction or batch operation on the specified provider. This allows multiple FHIR resources to be processed in a single request.
The request body should contain a valid FHIR Bundle resource with transaction or batch type.
The request is proxied to the configured FHIR server with appropriate authentication headers.
/fhir-provider/{fhir_provider_id}/fhir/{fhir_path}Retrieves FHIR resources from the specified provider. Supports both individual resource retrieval (e.g. Patient/123 via the path) and search operations.
FHIR search parameters are passed through to the upstream server verbatim as native query-string parameters; this proxy does not model, validate, or transform them. Append standard FHIR search parameters directly to the request URL. Supported parameters include:
- Resource-specific search parameters (e.g.
namefor Patient,statusfor Observation) - Common search parameters (
_id,_lastUpdated,_tag,_profile,_security,_text,_content,_filter) - Result parameters (
_count,_offset,_sort,_include,_revinclude,_summary,_elements) - Search prefixes for dates, numbers, and quantities (
eq,ne,gt,ge,lt,le,sa,eb,ap)
Examples:
Patient?name=John%20Doe&_count=10&_sort=familyObservation?patient=Patient/123&date=ge2023-01-01&category=vital-signs&_sort=-date
When using a generated SDK, supply these via the client's request-level query-parameter option (the SDK escape hatch) rather than a typed argument.
The request is proxied to the configured FHIR server with appropriate authentication headers.
/fhir-provider/{fhir_provider_id}/fhir/{fhir_path}Creates or updates a FHIR resource on the specified provider. If the resource exists, it will be updated; otherwise, it will be created.
The request is proxied to the configured FHIR server with appropriate authentication headers.
/fhir-provider/{fhir_provider_id}/fhir/{fhir_path}Creates a new FHIR resource on the specified provider. The request body should contain a valid FHIR resource in JSON format.
The request is proxied to the configured FHIR server with appropriate authentication headers.
/fhir-provider/{fhir_provider_id}/fhir/{fhir_path}Deletes a FHIR resource from the specified provider.
The request is proxied to the configured FHIR server with appropriate authentication headers.
/fhir-provider/{fhir_provider_id}/fhir/{fhir_path}Partially updates a FHIR resource on the specified provider.
Two body formats are supported, selected by request content type:
application/json-patch+json— an array of JSON Patch operations as defined in RFC 6902. Each operation specifies:op: The operation type (add, remove, replace, move, copy, test)path: JSON Pointer to the target location in the resourcevalue: The value to use (required for add, replace, and test operations)
application/fhir+json— a partial FHIR resource for merge-patch semantics.
Note: This proxy currently forwards the request body to the upstream FHIR server with Content-Type: application/fhir+json regardless of the declared request content type. JSON Patch (RFC 6902) therefore only succeeds against upstream servers that accept patch arrays under application/fhir+json; servers that strictly enforce patch media types may reject or misinterpret it. Support for either format ultimately depends on the upstream FHIR server.
The request is proxied to the configured FHIR server with appropriate authentication headers.
[
{
"op": "replace",
"path": "/name/0/family",
"value": "NewFamilyName"
}
]/fhir-provider/{fhir_provider_id}/add-auth-configAdds a new authentication configuration to an existing FHIR provider. This enables key rotation and multiple auth configurations per provider.
Note: Sandbox providers cannot be modified.
successmessageAuth configuration added successfullydataid1716d214-de93-43a4-aa6b-a878d864e2adnameEpic SandboxdescriptionEpic sandbox environment for testingproviderepicbase_urlhttps://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4client_idyour-client-idauth_configs{}last_updated2024-01-15T10:30:00Z/fhir-provider/{fhir_provider_id}/remove-auth-configRemoves an authentication configuration from a FHIR provider. Cannot remove the currently active auth configuration.
Note: Sandbox providers cannot be modified.
successmessageAuth configuration removed successfullydataid1716d214-de93-43a4-aa6b-a878d864e2adnameEpic SandboxdescriptionEpic sandbox environment for testingproviderepicbase_urlhttps://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4client_idyour-client-idauth_configs{}last_updated2024-01-15T10:30:00Z/fhir-provider/{fhir_provider_id}/set-active-auth-configSets which authentication configuration should be active for a FHIR provider. Only one auth config can be active at a time.
If the specified auth config is already active, the request succeeds without making any changes and returns a message indicating the config is already active.
Note: Sandbox providers cannot be modified.
successmessageActive auth configuration set successfully, or the config was already active. Check the message field to determine which case occurred.
dataid1716d214-de93-43a4-aa6b-a878d864e2adnameEpic SandboxdescriptionEpic sandbox environment for testingproviderepicbase_urlhttps://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4client_idyour-client-idauth_configs{}last_updated2024-01-15T10:30:00Z