Overview

The driver dynamically models resources from your FHIR instance as tables.

This documentation describes a "best-case" where the FHIR provider's implementation has been developed in strict accordance with the FHIR standard.

FHIR does not enforce that every table, column, search parameter, or implementation of server-side processing is present in any given FHIR implementation. As a result, some of the information documented here may differ from your FHIR implementation.

Key Features

• The driver models FHIR resources like patients, tasks, and appointments as relational views, allowing you to write SQL to query FHIR data.
• Stored procedures allow you to execute operations to FHIR.
• Live connectivity to these objects means any changes to your FHIR account are immediately reflected when using the driver.

Views

Views describes the available views. Views are dynamically discovered from the FHIR instance specified in the Url connection property.