Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Analyze FHIR Data in Infragistics Reveal
Use the CData API Server to create an OData API on top of FHIR data and visualize live FHIR data in Ingragistics Reveal.
Reveal is a data visualization solution provided by Infragistics and can be paired with the CData API Server and FHIR ADO.NET Provider to build dynamic dashboards from live FHIR data. The CData API Server generates an OData API for FHIR, which is natively consumable in Reveal. In this article, we walk through connecting to FHIR in API Server and connecting to the API Server from Infragistics Reveal to create a simple dashboard.
Connect to FHIR from API Server
CData API Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.
- Open API Server and click Settings -> Connection -> Add Connection
- Select "FHIR"
- Enter the necessary authentication properties to connect to FHIR.
Set URL to the Service Base URL of the FHIR server. This is the address where the resources are defined in the FHIR server you would like to connect to. Set ConnectionType to a supported connection type. Set ContentType to the format of your documents. Set AuthScheme based on the authentication requirements for your FHIR server.
Generic, Azure-based, AWS-based, and Google-based FHIR server implementations are supported.
Sample Service Base URLs
- Generic: http://my_fhir_server/r4b/
- Azure: https://MY_AZURE_FHIR.azurehealthcareapis.com/
- AWS: https://healthlake.REGION.amazonaws.com/datastore/DATASTORE_ID/r4/
- Google: https://healthcare.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/datasets/DATASET_ID/fhirStores/FHIR_STORE_ID/fhir/
Generic FHIR Instances
The product supports connections to custom instances of FHIR. Authentication to custom FHIR servers is handled via OAuth (read more about OAuth in the Help documentation. Before you can connect to custom FHIR instances, you must set ConnectionType to Generic.
Add FHIR Resource Definitions in API Server
After connecting to FHIR, create Resources, which represent API endpoints for FHIR data.
- Click Settings -> Resources -> Add Resource
- Select the FHIR connection
- Select the table you wish to retrieve and click Next
- (Optional) Edit the resource to select specific fields and more
- Save the settings
Add an API Server User
Create a User to connect to FHIR from Reveal through API Server.
- Click Settings -> Users
- Click Add
- Configure a User with access to the FHIR Connection and Resource(s)

(Optional) Configure Cross-Origin Resource Sharing (CORS)
When accessing and connecting to multiple different domains from an application such as Ajax, there is a possibility of violating the limitations of cross-site scripting. In that case, configure the CORS settings in Settings -> Server.
- Enable cross-origin resource sharing (CORS): ON
- Allow all domains without '*': ON
- Access-Control-Allow-Methods: GET, PUT, POST, OPTIONS
- Access-Control-Allow-Headers: Authorization
Save the changes to the settings.

Create a Dashboard in Reveal
With the API Server configured, we can visualize FHIR data in Reveal.
- Log into Reveal and click Dashboards -> New
- Click Data Source -> OData Feed
- Specify the API Server API endpoint URL, for example: https://serverurl/api.rsc
- Select Generic Credentials and specify the API Server username and authentication token
- Select the entity you wish to visualize
- Select fields and choose a chart type
More Information & Free Trial
At this point, you have created a simple dashboard from live FHIR data. For more information on creating OData feeds from FHIR (and more than 150 other sources), visit the API Server page. Download a free, 30-day trial and start working live FHIR data in tools that consume OData APIs.