healthex-export-redacted

Export PHI-redacted clinical data from HealthEx as JSON or NDJSON.

27|9|Updated Mar 31, 2025
One-click install
npx skills add https://github.com/aks129/HealthClawGuardrails --skill healthex-export-redacted
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: healthex-export-redacted
Source: https://github.com/aks129/HealthClawGuardrails/tree/main/skills/healthex-export-redacted
Command: npx skills add https://github.com/aks129/HealthClawGuardrails --skill healthex-export-redacted

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp>=1.2, httpx, and includes scripts (resource) components.

What problem does it solve?

HealthEx → HealthClaw-redacted export via the official MCP Python SDK enables safe, PHI-redacted data sharing by pulling clinical data directly from HealthEx, producing a redacted bundle for ingestion without exposing sensitive information.

Core Features & Use Cases

  • PHI-redacted export: fetches clinical data via HealthEx MCP SDK and redacts PHI in-process before disk write.
  • Single-file or NDJSON export: outputs a portable JSON or NDJSON bundle for downstream import via /import.
  • Headless and automation-ready: suitable for cron, Telegram bot workflows, or pipelines on mac mini.

Quick Start

Run the HealthEx redacted export to generate a PHI-redacted MCP bundle for downstream ingestion.

Frequently Asked Questions about healthex-export-redacted

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export redacted clinical data from HealthEx using the MCP Python SDK?

To export redacted clinical data from HealthEx, use the MCP Python SDK to fetch records and redact PHI in-process before writing to disk. This produces a safe JSON or NDJSON bundle for downstream ingestion without exposing sensitive patient information.

What is PHI redaction in FHIR clinical data exports?

PHI redaction in FHIR clinical data exports is the process of removing protected health information from clinical records before disk write. The MCP SDK fetches data from HealthEx and strips sensitive fields in-process to ensure safe sharing and downstream ingestion.

Can I run HealthEx redacted exports headlessly for automated Telegram bot workflows?

Yes, you can run HealthEx redacted exports headlessly for automated Telegram bot workflows or cron jobs. The process requires Python 3, the MCP SDK version 1.2 or higher, and the httpx library for HTTP communication and data transfer.

Does the HealthEx MCP export support NDJSON output for HealthClaw import?

Yes, the HealthEx MCP export supports both single-file JSON and NDJSON output formats. These portable bundles are specifically designed for downstream ingestion via the HealthClaw import path after PHI redaction is applied in-process.

What Python dependencies are required to pull and redact HealthEx clinical data?

Pulling and redacting HealthEx clinical data requires Python 3, the MCP SDK at version 1.2 or higher, and the httpx library. These dependencies handle the SDK communication and HTTP data transfer needed for the redacted export workflow.

Why should I redact PHI in-process before writing clinical data exports to disk?

Redacting PHI in-process before writing clinical data exports to disk prevents sensitive patient information from ever touching the file system. This ensures the resulting JSON or NDJSON bundle is safe for downstream ingestion and compliant with health data sharing requirements.