synthetic-health-data

Name: synthetic-health-data
Availability: InStock
Author: InnerScopeHearing

Generate synthetic health data and de-identify real data to HIPAA standards.

Updated May 30, 2026

Search Tags:#data generation #HIPAA compliance #de-identification #health data #development testing

Ready to run

npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill synthetic-health-data

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: synthetic-health-data
Source: https://github.com/InnerScopeHearing/otchealth-claude-tools/tree/main/skills/synthetic-health-data
Command: npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill synthetic-health-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, crypto, fs, path, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides tools for generating realistic health data for development and testing environments, and de-identifying real health data to comply with HIPAA regulations, ensuring sensitive information is protected and data privacy is maintained.

Core Features & Use Cases

Synthetic Data Generation: Fabricate realistic health data (hearing screenings, patient records, customers, orders) for dev/test/agent work without exposing PHI.
De-identification: Strip personal identifiers from real health data to HIPAA Safe Harbor standards.
Use Case: A healthcare developer working on a new application needs to create a test environment. Using this Skill, they can generate synthetic health data to simulate real-world scenarios without violating privacy laws.

Quick Start

To generate synthetic hearing screening data with 20 records, run:

node gen.mjs hearing-screening --count 20 --seed 42

Frequently Asked Questions about synthetic-health-data

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

FAQPage Schema

How do I generate synthetic health data for development testing without exposing PHI?▼

You can generate synthetic health data for development testing by fabricating realistic hearing screenings, patient records, and customer orders without exposing PHI. This allows you to simulate real-world scenarios securely.

How do I de-identify real health data to comply with HIPAA Safe Harbor standards?▼

To de-identify real health data to HIPAA Safe Harbor standards, you strip personal identifiers from the records. This ensures sensitive information is protected and data privacy is maintained for compliance.

Do I need Node.js to run synthetic health data generation and de-identification scripts?▼

Yes, you need Node.js and specific modules including crypto, fs, and path to process data fabrication, de-identification, and validation. These dependencies are required for the scripts to execute properly.

What is the best way to create a test environment using synthetic patient records?▼

The best way to create a test environment using synthetic patient records is generating fabricated health data that mimics real-world scenarios. This approach ensures development testing proceeds without violating privacy laws.

Can I specify the number of records and a seed value when generating synthetic hearing screening data?▼

Yes, you can specify the number of records and a seed value when generating synthetic hearing screening data. Running the generation script with count and seed parameters produces deterministic, customized datasets.

What types of health data can I fabricate for development and agent work?▼

You can fabricate hearing screenings, patient records, customers, and orders for development, testing, and agent work. This synthetic data generation covers multiple health data categories while maintaining privacy.