Connect FHIR Data to Claris FileMaker via ESS using an ODBC Driver and the CData SQL Gateway

Claris FileMaker is a low-code platform that enables users to quickly create custom apps to manage and automate data workflows. Using the CData ODBC Driver for FHIR and the CData SQL Gateway, FileMaker connects to FHIR data through its ESS (External SQL Source) feature, allowing you to work with FHIR records as if they were native FileMaker tables.

In this article, we configure and use the CData ODBC Driver for FHIR and the CData SQL Gateway, along with the MySQL ODBC Driver, to connect to FHIR data using the ESS functionality in FileMaker.

Create an ODBC Data Source for FHIR

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

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.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Configuring the CData SQL Gateway

The CData SQL Gateway bridges non-SQL data sources (like SaaS applications, APIs, and NoSQL databases) with SQL-based tools (like FileMaker, MySQL clients, and BI tools).

In simple terms, it exposes any CData driver-supported source - for example, FHIR - as a standard MySQL or SQL Server endpoint.

See the SQL Gateway Overview to set up FHIR data connectivity as a virtual MySQL database. Set up a MySQL remoting service that listens for MySQL requests from clients, and configure the service through the SQL Gateway UI (as shown below). Save the user credentials (Username and Password) for future use.

Once you establish the connection, you can use the CData SQL Gateway to access FHIR data through the MySQL protocol.

Installing the MySQL ODBC Driver

Follow the steps below to install and configure the MySQL ODBC Driver:

1. Download and install the latest 64-bit Windows version of the MySQL ODBC Unicode Driver from this link.
2. Launch ODBC Data Sources (64-bit) from Windows search. Open the System DSN tab, click Add, select MySQL ODBC Unicode Driver from the Create New Data Source window, and click Finish.
👁 Create a new data source using the latest MySQL ODBC Unicode Driver

3. Enter the following connection details in the MySQL Connector/ODBC Data Source Configuration window:
   • Data Source Name: Enter a DSN of your choice
   • TCP/IP Server: localhost
   • Port: Enter the port set in the SQL Gateway (for this procedure, use "3307")
   • User: Enter the username set in the CData SQL Gateway
   • Password: Enter the password set in the CData SQL Gateway
   • Database: CData FHIR Sys
   👁 Configure the MySQL ODBC Driver using CData SQL Gateway credentials
   
4. Click Test to verify that the "Connection Successful" dialog box appears. Then click OK to save the configuration details.

You have now successfully configured the MySQL ODBC Driver.

Use FileMaker ESS function to load FHIR data

In this section, we explore how to use the ESS (External SQL Source) feature to retrieve data in the FileMaker application. Follow the given steps to complete the process:

1. Open FileMaker Pro. Navigate to Create from the left panel and select Blank > Create.
👁 Create a new application in FileMaker Pro

2. Enter a desired filename and click Save.
3. In Manage Database, remove the Tables and Fields from the respective tabs. Select the Relationships tab and click Add Table.
👁 Add a table in the Manage Database window in FileMaker Pro

4. In Specify Table, expand the Data Source dropdown menu and select Add ODBC Data Source. Click OK.
👁 Add an ODBC Data Source in the Specify Table window

5. In Select ODBC Data Source, select the previously configured MySQL ODBC driver and click Continue.
👁 Select the newly configured MySQL ODBC Unicode Driver

6. In the Edit Data Source window, enter the following details:
• Name: This field will be auto-filled. Enter a new name of choice if necessary.
• Type: Select "ODBC".
• Under Authentication, select the Specify username and password radio button and enter the following details:
• User name: Enter the username set in the CData SQL Gateway.
• Password: Enter the password set in the CData SQL Gateway.
• Catalog Name: CData FHIR Sys
7. Click OK.
👁 Configure the data source in FileMaker

8. View the tables from FHIR populated under the Data Source section. Select the table of your choice and click OK.
👁 Add a new table in the Specify Table window

9. The Relationships tab now displays the selected table and its metadata. Click OK.
👁 The new table gets added in the Relationships tab

10. Select the table from the Layout dropdown. The FHIR table data appears on the screen. (As shown)
👁 The FHIR table data is displayed in FileMaker Pro

Get Started Today

Download a free 30-day trial of CData ODBC Driver for FHIR to integrate FHIR data into Claris FileMaker and use FHIR data in your FileMaker applications.

Contact our Support Team if you have any questions.