HealthEx Export (MCP, Redacted)

scripts/export_healthex_mcp.py is the current HealthEx pull path. It:

1. Opens a Streamable HTTP MCP session to https://api.healthex.io/mcp
2. Optionally calls update_records + check_records_status to refresh
3. Invokes each clinical tool (get_health_summary, get_conditions, get_medications, get_allergies, get_immunizations, get_vitals, get_labs, get_procedures, get_visits, search_clinical_notes)
4. Redacts PHI in-process before anything touches disk — via scripts/healthclaw_redact.py, which mirrors the HealthClaw guardrail proxy's redaction rules
5. Writes the result as JSON (default) or NDJSON (one resource per line)

The raw MCP response is never written. Only the redacted payload goes to disk.

Quick Start

# Set the HealthEx token (use macOS Keychain on the Mac mini)
export HEALTHEX_AUTH_TOKEN="$(security find-generic-password -s healthex -w)"

# Default — all tools, local redaction, single JSON file
python scripts/export_healthex_mcp.py \
    --tenant-id my-tenant \
    --output exports/healthex-$(date +%Y-%m-%d).json

# NDJSON (one line per FHIR resource — easier to diff / grep)
python scripts/export_healthex_mcp.py \
    --tenant-id my-tenant \
    --output exports/healthex-$(date +%Y-%m-%d).ndjson

# Only the tools you need
python scripts/export_healthex_mcp.py \
    --tenant-id my-tenant \
    --output exports/labs-only.json \
    --tools get_labs get_conditions

# Proxy mode — redact via a running HealthClaw guardrail server instead
python scripts/export_healthex_mcp.py \
    --tenant-id my-tenant \
    --output exports/snap.json \
    --redact-mode proxy \
    --healthclaw-url https://healthclaw.io

# Synthetic-only escape hatch (keeps PHI in output — NEVER use on real data)
python scripts/export_healthex_mcp.py \
    --tenant-id desktop-demo \
    --output exports/demo-raw.json \
    --no-redact

Redaction Rules (identical to the HealthClaw proxy)

_meta.redaction_stats in the output counts every redaction performed.

Telegram / OpenClaw Integration

Bots call this via the /export slash command registered in scripts/bot_commands.py → cmd_export(). The bot resolves HEALTHEX_AUTH_TOKEN from (1) environment, (2) macOS Keychain service healthex. Output lands in ~/.healthclaw/exports/healthex-<date>.json.

Typical end-to-end flow over Telegram:

1. /export — pulls HealthEx, redacts, writes bundle
2. /import <path printed by /export> — ingests into local HealthClaw
3. /conditions / /labs / /summary — agent reads from local store

Smoke Test

tests/test_healthclaw_redact.py exercises both the redaction rules and the end-to-end export flow against a mocked MCP session. Part of the CI suite:

uv run python -m pytest tests/test_healthclaw_redact.py -v

For a one-off CLI check without pytest, scripts/smoke_test.py runs the same assertions and prints a redaction summary.

Relationship to healthex-export (legacy)

The older healthex-export skill and scripts/export_healthex_legacy.py pull from the local HealthClaw FHIR store via direct REST. Keep for tenant-to-tenant copies. Use this skill when the source of truth is HealthEx itself and you want the MCP SDK + in-process redaction.