healthex-export

Export health data from a HealthClaw FHIR store into a FHIR R4 transaction bundle.

27|9|Updated Mar 31, 2025

Search Tags:#healthcare #export #fhir #data-migration #de-identification #curatr #healthex

Ready to run

npx skills add https://github.com/aks129/HealthClawGuardrails --skill healthex-export

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: healthex-export
Source: https://github.com/aks129/HealthClawGuardrails/tree/main/skills/healthex-export
Command: npx skills add https://github.com/aks129/HealthClawGuardrails --skill healthex-export

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) components.

What problem does it solve?

HealthClaw HealthEx Export automates exporting all health data from the local HealthClaw FHIR store into a portable FHIR bundle. It enables migration to a new tenant, archiving records, creating de-identified snapshots for provider sharing, pre-screening records for Curatr quality issues, and streamlining the HealthEx → local FHIR store ingestion pipeline.

Core Features & Use Cases

Automated export of a tenant's complete clinical data as a FHIR transaction bundle.
Optional de-identification and Curatr pre-tagging to support auditing and safe sharing.
Easy import path to another tenant or archival repository through /Bundle/$ingest-context.
Real-world use: migrate to a new tenant, archive records, or prepare data for provider review.

Quick Start

Export all resources for a tenant and optionally import the bundle into another tenant.

Frequently Asked Questions about healthex-export

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

FAQPage Schema

How do I export clinical data from a FHIR store into a portable bundle?▼

Exporting FHIR data into a portable bundle allows you to migrate tenant records or archive health data. The process outputs a FHIR R4 transaction bundle ready for ingestion via /Bundle/$ingest-context.

Can I de-identify health records during a FHIR data migration?▼

Yes, de-identifying health records during a FHIR data export is supported. The process applies optional de-identification to produce safe, shareable snapshots for provider review and auditing.

What is the best way to migrate health data to a new FHIR tenant?▼

Migrating health data to a new FHIR tenant involves exporting all records into a FHIR R4 transaction bundle. You then import this bundle into the target tenant through the /Bundle/$ingest-context endpoint.

Do I need Python to export a FHIR transaction bundle?▼

Yes, you need Python 3 and the requests library to generate a FHIR transaction bundle. These dependencies execute the scripts that extract health data and package it for migration.

Does the FHIR export process support Curatr pre-tagging for quality screening?▼

Yes, the FHIR export process supports optional Curatr pre-tagging. This pre-screens records for quality issues during the export, streamlining the data preparation workflow before ingestion.