explaingit

charliehzm/medharness

13PythonAudience · ops devopsComplexity · 4/5LicenseSetup · hard

TLDR

A Python framework that adds HIPAA and PIPL compliance controls to AI coding assistants used by medical software teams, with patient data de-identification, a 12-step audit workflow, and tamper-evident archive generation for six-year regulatory retention.

Mindmap

mindmap
  root((MedHarness))
    What It Does
      HIPAA compliance
      AI coding governance
      Audit trail generation
    Workflow
      12-step full track
      5-step micro track
    Tech Stack
      Python
      MCP servers
    Use Cases
      Healthcare dev teams
      Compliance automation
      PHI de-identification
    Audience
      DevOps engineers
      Healthcare developers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Set up a HIPAA-compliant AI coding workflow for a healthcare software team that automatically de-identifies patient data before any AI prompt is sent.

USE CASE 2

Generate a tamper-evident audit archive with a hash chain after each sensitive code change to meet six-year regulatory retention requirements.

USE CASE 3

Integrate MedHarness's 8 MCP servers into a developer's AI editor to enforce compliant data handling automatically without manual review steps.

Tech stack

PythonMCP servers

Getting it running

Difficulty · hard Time to first run · 1day+

Enterprise rollout target is six months, requires connecting 8 MCP servers and configuring an approved AI model list for your team's environment.

The community edition is free to use and modify under Apache 2.0, the commercial edition with advanced features requires a paid license.

In plain English

MedHarness is a Python framework that helps teams at medical software companies use AI coding assistants without violating health data privacy laws. It is built for companies in healthcare data that need to comply with HIPAA (the US health privacy standard) and PIPL (China's personal information protection law). The stated goal is to take a team from informal individual AI editor use to an auditable, enterprise-grade system in six months. The core of MedHarness is a multi-step workflow that governs every piece of code a developer writes with AI assistance. There are two tracks: a 12-step full track for complex or sensitive changes, and a shorter 5-step micro track for small edits like documentation changes or test additions. The first step in the full track is a compliance check that classifies the data involved and confirms the AI model being used is on an approved list. The final step generates a tamper-evident audit archive with a hash chain, intended to be stored for six years to meet regulatory retention requirements. The framework bundles 23 specialized skills and 8 MCP servers, which are modular tools that connect the AI coding environment to specific compliance capabilities such as patient data de-identification, audit logging, and test data generation. Raw patient identifiers are never allowed to enter a prompt directly, the system enforces a de-identification step before any AI interaction involving sensitive data. There is a community edition under Apache 2.0 that includes the core architecture, skills, and MCP servers. A commercial edition adds a trained Chinese medical data detector, a managed cluster for audit storage, a dashboard, and 24/7 compliance support. The README is primarily in Chinese, with code examples and architecture diagrams that are readable even without knowledge of the language. The project is at v0.1.0 alpha stage.

Copy-paste prompts

Prompt 1
I want to integrate MedHarness into my team's Cursor setup for a HIPAA-compliant Python healthcare project. Walk me through connecting the 8 MCP servers and configuring the approved AI model list.
Prompt 2
Show me what the de-identification step looks like in the MedHarness 12-step full track. How does it detect and remove patient identifiers before they reach an AI prompt?
Prompt 3
I need to generate a six-year audit archive for a code change that touched PHI fields using MedHarness. Walk me through running the final audit step and verifying the hash chain output.
Prompt 4
Explain the difference between the 12-step full track and the 5-step micro track in MedHarness and give me examples of changes that belong in each.
Open on GitHub → Explain another repo

← charliehzm on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.