Add FHIR R4 Healthcare Intelligence connector example

README.md

@@ -325,8 +325,8 @@ These examples rely on features that are currently in Private preview. To enable
 - [claude_fda_drug tutorial](https://github.com/fivetran/fivetran_connector_sdk/tree/main/all_things_ai/tutorials/claude/fda_drug_tutorial) - This example demonstrates how to use Claude to create a CSDK connector to get data from the FDA drug API.
 - [cursor_fda_food tutorial](https://github.com/fivetran/fivetran_connector_sdk/tree/main/all_things_ai/tutorials/cursor/fda_food_tutorial/fda_food_connector) - This example demonstrates how to use Cursor to create a CSDK connector to get data from the FDA food API.
 - [vscode_fda_tobacco tutorial](https://github.com/fivetran/fivetran_connector_sdk/tree/main/all_things_ai/tutorials/vscode/fda_tobacco_tutorial/fda_tobacco_connector) - This example demonstrates how to use VSCode to create a CSDK connector to get data from the FDA tobacco API.
-
 - [snowflake-cortex-livestock-weather-intelligence](https://github.com/fivetran/fivetran_connector_sdk/tree/main/all_things_ai/tutorials/snowflake-cortex-livestock-weather-intelligence) - This example demonstrates real-time AI enrichment via Snowflake Cortex Agent REST API during Fivetran data ingestion. It syncs weather forecasts and enriches them with livestock health risk assessments using Snowflake's llama3.3-70b model with Cortex Analyst. It shows how to integrate Snowflake Intelligence into Fivetran pipelines for any industry vertical.
+- [databricks-fm-fhir-healthcare-intelligence](https://github.com/fivetran/fivetran_connector_sdk/tree/main/all_things_ai/tutorials/databricks-fm-fhir-healthcare-intelligence) - This example syncs clinical data from a FHIR R4 server and enriches it with AI-powered hybrid analysis using Databricks `ai_query()`. It implements the Hybrid pattern (Discovery + Debate) to provide population health risk stratification and per-patient intervention recommendations using Databricks Foundation Models.
 > Note: As of Connector SDK version 2.0.0, `yield` is no longer required for Connector SDK operations. This folder contains examples that still use `yield`, but we recommend using the latest version of Connector SDK and avoiding `yield` in your connector code. For more information, refer to our [Connector SDK release notes](https://fivetran.com/docs/connector-sdk/changelog#august2025).
 
 ## Issue

all_things_ai/tutorials/databricks-fm-fhir-healthcare-intelligence/README.md

@@ -0,0 +1,244 @@
+# FHIR R4 Healthcare Intelligence Connector Example
+
+## Connector overview
+
+This connector syncs clinical data from a FHIR R4 server and enriches it with AI-powered hybrid analysis using Databricks' `ai_query()`. It implements the Hybrid pattern (Discovery + Debate) to provide population health risk stratification and per-patient intervention recommendations.
+
+The connector fetches Patient, Condition, Observation, and MedicationRequest resources from any FHIR R4-compliant server, then applies two AI enrichment phases: a Discovery phase that analyzes the patient cohort to identify at-risk populations, and a Debate phase where a Clinical Risk Analyst and a Resource Allocation Analyst debate intervention priorities for each patient, producing a consensus intervention level with a disagreement flag. 
+
+Optionally, the connector can create a [Genie Space in Databricks](https://docs.databricks.com/aws/en/genie/) for natural language clinical analytics.
+
+## Requirements
+
+- [Supported Python versions](https://github.com/fivetran/fivetran_connector_sdk/blob/main/README.md#requirements)
+- Operating system:
+  - Windows: 10 or later (64-bit only)
+  - macOS: 13 (Ventura) or later (Apple Silicon [arm64] or Intel [x86_64])
+  - Linux: Distributions such as Ubuntu 20.04 or later, Debian 10 or later, or Amazon Linux 2 or later (arm64 or x86_64)
+- Databricks workspace with a SQL warehouse and Foundation Model API access (required if AI enrichment is enabled)
+- Access to a FHIR R4 server (default: HAPI FHIR public test server, no credentials required)
+
+## Getting started
+
+Refer to the [Connector SDK Setup Guide](https://fivetran.com/docs/connectors/connector-sdk/setup-guide) to get started.
+
+## Features
+
+- Fetches Patient, Condition, Observation, and MedicationRequest resources from any FHIR R4-compliant server
+- Supports optional ICD-10 code prefix filtering to target a specific patient cohort (e.g., `E11` for diabetes)
+- Supports incremental sync using FHIR `_lastUpdated` filtering based on the previous sync timestamp
+- Discovery phase: calls Databricks' `ai_query()` to identify at-risk populations, dominant conditions, and recommended screenings across the cohort
+- Debate phase: for each patient, a Clinical Risk Analyst and a Resource Allocation Analyst independently assess the patient, then a Consensus Agent synthesizes a final intervention level with a disagreement flag
+- Produces eight destination tables: four FHIR resource tables and four AI enrichment tables
+- Optional Genie Space creation in Databricks for natural language clinical analytics
+
+## Configuration file
+
+The `configuration.json` file holds the connection parameters. Copy the template and fill in your values.
+
+Note: Ensure that the `configuration.json` file is not checked into version control to protect sensitive information.
+
+Note: The `fivetran_connector_sdk` and `requests` packages are pre-installed in the Fivetran environment. To avoid dependency conflicts, do not declare them in your `requirements.txt`.
+
+| Parameter | Description | Required | Default |
+|---|---|---|---|
+| `fhir_base_url` | Base URL of the FHIR R4 server | No | https://hapi.fhir.org/baseR4 |
+| `databricks_workspace_url` | Databricks workspace URL (https://...) | Yes (if enrichment enabled) | None |
+| `databricks_token` | Databricks Personal Access Token | Yes (if enrichment enabled) | None |
+| `databricks_warehouse_id` | Databricks SQL warehouse ID | Yes (if enrichment enabled) | None |
+| `databricks_model` | Databricks Foundation Model name | No | databricks-claude-sonnet-4-6 |
+| `enable_enrichment` | Enable AI enrichment phases (true/false) | No | true |
+| `enable_discovery` | Enable Discovery phase (true/false) | No | true |
+| `enable_genie_space` | Create Databricks Genie Space (true/false) | No | false |
+| `genie_table_identifier` | Genie Space table identifier (catalog.schema.table) | Yes (if Genie enabled) | None |
+| `max_patients` | Maximum patients to sync per run | No | 20 |
+| `max_enrichments` | Maximum patients to enrich per run | No | 5 |
+| `condition_filter` | ICD-10 code prefix to filter patients (e.g., E11) | No | None |
+| `databricks_timeout` | Databricks API timeout in seconds | No | 120 |
+
+## Authentication
+
+The FHIR R4 data source uses no authentication by default. The HAPI FHIR public test server (`https://hapi.fhir.org/baseR4`) is an open server that requires no credentials. If you configure a private FHIR server that requires authentication, add the appropriate authorization header to the session in `connector.py`.
+
+Databricks authentication uses a Personal Access Token (PAT). Generate a PAT from your Databricks workspace under **Settings** > **Developer** > **Access tokens**, then set it as the `databricks_token` configuration value. The token is passed as a `Bearer` token in the `Authorization` header for all Databricks SQL Statement API calls.
+
+## Pagination
+
+FHIR R4 servers return resources as paginated Bundle resources. The connector follows `Bundle.link` entries with `relation=next` to retrieve subsequent pages until no next link is present or the configured `max_patients` limit is reached. The next-page URL is used directly as provided by the server; query parameters are only passed on the initial request.
+
+Databricks SQL Statement API responses can be paginated via `next_chunk_internal_link`, but this tutorial connector reads the immediate `ai_query()` result only and does not follow chunk-pagination links. The included AI queries return a single result value rather than a large multi-row result set.
+
+## Data handling
+
+FHIR resources use deeply nested JSON structures (CodeableConcept, Reference, Quantity, HumanName). The connector normalizes these using dedicated extraction helpers:
+
+- `extract_codeable_concept()` — extracts the first code and display text from a CodeableConcept
+- `extract_reference_id()` — extracts the resource ID from a FHIR Reference string
+- `extract_quantity()` — extracts the numeric value and unit from a Quantity
+
+All remaining nested dictionaries are flattened using `flatten_dict()` before upsert. Arrays and lists are serialized to JSON strings. AI enrichment fields that return JSON arrays (e.g., `dominant_conditions`, `immediate_actions`) are stored as JSON strings in the destination.
+
+## Error handling
+
+FHIR API requests are retried up to 3 times with exponential backoff for status codes 429, 500, 502, 503, and 504. Authentication errors (401, 403) are not retried and raise an immediate error with a credential check message.
+
+Databricks' `ai_query()` calls retry the initial POST up to 3 times with exponential backoff for status codes 429, 500, 502, 503, and 504. If all retry attempts fail, or if the statement returns a final FAILED state, that patient's assessment is skipped and a warning is logged, but the sync continues. Checkpoints are written after each patient debate and after each enrichment phase so that progress is not lost if a sync is interrupted.
+
+## Tables created
+
+The connector creates the following tables in the destination:
+
+### PATIENTS
+
+The `PATIENTS` table consists of the following columns:
+
+| Column | Description |
+|---|---|
+| `patient_id` | Unique FHIR Patient resource ID (primary key) |
+| `mrn` | Medical record number from identifier |
+| `given_name` | Patient first name |
+| `family_name` | Patient last name |
+| `gender` | Administrative gender |
+| `birth_date` | Date of birth (YYYY-MM-DD) |
+| `deceased_boolean` | True if patient is deceased |
+| `deceased_date_time` | Date and time of death if applicable |
+| `marital_status` | Marital status display text |
+| `language` | Preferred communication language |
+| `address_line` | Street address |
+| `city` | City |
+| `state` | State or province |
+| `postal_code` | Postal code |
+| `country` | Country |
+| `active` | Whether the patient record is active |
+| `last_updated` | FHIR resource last updated timestamp |
+
+### CONDITIONS
+
+The `CONDITIONS` table consists of the following columns:
+
+| Column | Description |
+|---|---|
+| `condition_id` | Unique FHIR Condition resource ID (primary key) |
+| `patient_id` | Reference to the patient |
+| `code` | ICD-10 or SNOMED condition code |
+| `display` | Human-readable condition name |
+| `code_system` | Coding system URI |
+| `category` | Condition category code |
+| `clinical_status` | active, resolved, inactive |
+| `verification_status` | confirmed, unconfirmed, refuted |
+| `onset_date` | Date condition began |
+| `abatement_date` | Date condition resolved |
+| `recorded_date` | Date condition was recorded |
+| `last_updated` | FHIR resource last updated timestamp |
+
+### OBSERVATIONS
+
+The `OBSERVATIONS` table consists of the following columns:
+
+| Column | Description |
+|---|---|
+| `observation_id` | Unique FHIR Observation resource ID (primary key) |
+| `patient_id` | Reference to the patient |
+| `code` | LOINC observation code |
+| `display` | Human-readable observation name |
+| `code_system` | Coding system URI |
+| `category` | Observation category (laboratory, vital-signs) |
+| `value` | Observation result value |
+| `value_unit` | Unit of measure |
+| `status` | final, preliminary, amended |
+| `effective_date` | Date observation was made |
+| `issued` | Date result was issued |
+| `interpretation` | Normal, High, Low, Critical |
+| `reference_range_low` | Lower bound of normal range |
+| `reference_range_high` | Upper bound of normal range |
+| `last_updated` | FHIR resource last updated timestamp |
+
+### MEDICATIONS
+
+The `MEDICATIONS` table consists of the following columns:
+
+| Column | Description |
+|---|---|
+| `medication_id` | Unique FHIR MedicationRequest resource ID (primary key) |
+| `patient_id` | Reference to the patient |
+| `medication_code` | RxNorm or NDC medication code |
+| `medication_display` | Human-readable medication name |
+| `medication_system` | Coding system URI |
+| `status` | active, completed, stopped |
+| `intent` | order, plan, proposal |
+| `authored_on` | Date prescription was written |
+| `dosage_text` | Free-text dosage instructions |
+| `dosage_timing` | Dosage timing details (JSON) |
+| `dosage_route` | Route of administration |
+| `last_updated` | FHIR resource last updated timestamp |
+
+### POPULATION_INSIGHTS
+
+The `POPULATION_INSIGHTS` table consists of the following columns:
+
+| Column | Description |
+|---|---|
+| `insight_id` | Unique insight identifier (primary key) |
+| `condition_filter` | ICD-10 prefix used to filter cohort, or "none" |
+| `patient_count` | Number of patients analyzed |
+| `dominant_conditions` | Most prevalent conditions in cohort (JSON array) |
+| `risk_factors` | Key risk factors identified (JSON array) |
+| `high_risk_indicators` | Summary of high-risk indicators |
+| `recommended_screenings` | Preventive screenings recommended (JSON array) |
+| `comorbidities_to_investigate` | Comorbidities flagged for investigation (JSON array) |
+| `population_risk_summary` | Narrative population risk summary |
+
+### CLINICAL_ASSESSMENTS
+
+The `CLINICAL_ASSESSMENTS` table consists of the following columns:
+
+| Column | Description |
+|---|---|
+| `patient_id` | Reference to the patient (primary key) |
+| `assessment_type` | Always "clinical" |
+| `clinical_risk_score` | Risk score 1-10 (urgency-maximizing) |
+| `worst_case_scenario` | Description of worst-case clinical outcome |
+| `intervention_recommendation` | INPATIENT_CARE_MGMT, OUTPATIENT_INTENSIFY, TELEHEALTH, or ROUTINE |
+| `immediate_actions` | Immediate actions recommended (JSON array) |
+| `complication_risks` | Complication risks identified (JSON array) |
+| `reasoning` | Clinical analyst reasoning narrative |
+
+### RESOURCE_ASSESSMENTS
+
+The `RESOURCE_ASSESSMENTS` table consists of the following columns:
+
+| Column | Description |
+|---|---|
+| `patient_id` | Reference to the patient (primary key) |
+| `assessment_type` | Always "resource" |
+| `resource_risk_score` | Risk score 1-10 (proportional) |
+| `expected_risk` | Probability-weighted expected risk description |
+| `intervention_recommendation` | INPATIENT_CARE_MGMT, OUTPATIENT_INTENSIFY, TELEHEALTH, or ROUTINE |
+| `cost_effective_actions` | Cost-effective actions recommended (JSON array) |
+| `mitigating_factors` | Factors that reduce risk (JSON array) |
+| `reasoning` | Resource analyst reasoning narrative |
+
+### DEBATE_CONSENSUS
+
+The `DEBATE_CONSENSUS` table consists of the following columns:
+
+| Column | Description |
+|---|---|
+| `patient_id` | Reference to the patient (primary key) |
+| `assessment_type` | Always "consensus" |
+| `intervention_level` | Final intervention: INPATIENT_CARE_MGMT, OUTPATIENT_INTENSIFY, TELEHEALTH, or ROUTINE |
+| `consensus_risk_score` | Balanced risk score 1-10 |
+| `debate_winner` | CLINICAL, RESOURCE, or DRAW |
+| `winner_rationale` | Why one analyst was more persuasive |
+| `agreement_areas` | Areas of analyst agreement (JSON array) |
+| `disagreement_areas` | Areas of analyst disagreement (JSON array) |
+| `disagreement_flag` | True if analysts significantly disagreed |
+| `disagreement_severity` | NONE, MINOR, SIGNIFICANT, or FUNDAMENTAL |
+| `recommended_next_step` | Recommended immediate next step |
+| `executive_summary` | Narrative summary of the debate consensus |
+
+## Additional considerations
+
+This connector was built by David Millman during a working session with Kelly Kohlleffel. It follows the Hybrid (Discovery + Debate) pattern established by the NOAA Weather Risk Intelligence connector (PR #570) and the FDA FAERS Pharmacovigilance Intelligence connector (PR #571). The HAPI FHIR public test server (`https://hapi.fhir.org/baseR4`) is used as the default data source and contains synthetic clinical data suitable for demonstration purposes.
+
+The examples provided are intended to help you effectively use Fivetran's Connector SDK. While we've tested the code, Fivetran cannot be held responsible for any unexpected or negative consequences that may arise from using these examples. For inquiries, please reach out to our Support team.

all_things_ai/tutorials/databricks-fm-fhir-healthcare-intelligence/configuration.json

@@ -0,0 +1,15 @@
+{
+  "fhir_base_url": "<FHIR_BASE_URL>",
+  "databricks_workspace_url": "<DATABRICKS_WORKSPACE_URL>",
+  "databricks_token": "<DATABRICKS_TOKEN>",
+  "databricks_warehouse_id": "<DATABRICKS_WAREHOUSE_ID>",
+  "databricks_model": "<DATABRICKS_MODEL_NAME>",
+  "enable_enrichment": "<TRUE_OR_FALSE_DEFAULT_TRUE>",
+  "enable_discovery": "<TRUE_OR_FALSE_DEFAULT_TRUE>",
+  "enable_genie_space": "<TRUE_OR_FALSE_DEFAULT_FALSE>",
+  "genie_table_identifier": "<CATALOG.SCHEMA.TABLE>",
+  "max_patients": "<MAX_PATIENTS_PER_SYNC>",
+  "max_enrichments": "<MAX_ENRICHMENTS_PER_SYNC>",
+  "condition_filter": "<ICD10_CODE_PREFIX>",
+  "databricks_timeout": "<DATABRICKS_TIMEOUT_SECONDS>"
+}