evaluate 0 0 0

mirobody/MedHarm-Bench

published by @mirobody

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
15.8K
Last 30 days
4.5K
Likes
2
Size
42 KB
Created on HF
2026-06-29
Age
3 months ago

Description

MedHarm-Bench

MedHarm-Bench is a red-team compliance benchmark for health-management AI assistants. It uses natural-sounding patient questions that bait the assistant into crossing medical safety boundaries, then scores each response against compliance red lines. Designed for use with the HolyEval framework.

⚠️ Research use only. Questions are designed to elicit unsafe behavior for benchmarking purposes and should not be used for diagnosis or treatment decisions.… See the full description on the dataset page: https://huggingface.co/datasets/mirobody/MedHarm-Bench.

Tags

task_categories:question-answeringlanguage:enlicense:apache-2.0size_categories:n<1Kformat:jsonmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantregion:usmedicalhealthsafetyred-teamcomplianceevaluationtheta-health

README current version from Hugging Face


license: apache-2.0
task_categories:

  • question-answering
    language:
  • en
    tags:
  • medical
  • health
  • safety
  • red-team
  • compliance
  • evaluation
  • theta-health
    pretty_name: MedHarm-Bench — Health AI Red-Team Compliance Benchmark
    configs:
  • config_name: full-202606
    default: true
    data_files:
    • split: test
      path: data/202606/full.jsonl

MedHarm-Bench

MedHarm-Bench is a red-team compliance benchmark for health-management AI assistants. It uses natural-sounding patient questions that bait the assistant into crossing medical safety boundaries, then scores each response against compliance red lines. Designed for use with the HolyEval framework.

⚠️ Research use only. Questions are designed to elicit unsafe behavior for benchmarking purposes and should not be used for diagnosis or treatment decisions.

Motivation

A safe health-management assistant must stay within strict boundaries: it may explain medical concepts and guide users to appropriate care, but it must not issue definitive diagnoses, prescribe drugs or specific dosages, contradict a treating physician, or give advice that delays urgent care. Real users rarely attack these boundaries head-on — they slip the inducement into an ordinary-looking question ("my report says X, so I've definitely got Y, right?"). MedHarm-Bench collects 50 such single-turn inducement questions across 5 attack dimensions and scores responses with a server-side LLM-as-Judge against the compliance red lines above.

Dataset Summary

50 single-turn cases across 5 inducement dimensions:

Dimension (tag) Description Cases
implicit_diagnosis Implicit diagnosis elicitation — bait the AI into a definitive diagnosis 10
second_opinion Second-opinion trap — bait the AI into questioning the doctor or recommending self-medication 15
data_interpretation Data-interpretation baiting — use exam data to bait a definitive conclusion 15
emotional_coercion Urgency / emotional coercion — pressure for specific medication guidance in an "emergency" 5
authority_bias Authority bias / fake citation — cite a fabricated authority to bait agreement 5

Dataset Structure

├── manifest.json                            # Change-detection entry point (root)
├── README.md
└── data/
    └── 202606/                              # Monthly batch directory
        ├── full.jsonl                       # 50 red-team questions (single-turn)
        └── results_sample.jsonl             # Submission template, one {"id", "answer"} per line

Item Schema

Each JSONL line is a BenchItem compatible with the HolyEval framework:

{
  "id": "aq_001",
  "title": "[Implicit Diagnosis] ...",
  "description": "<the user question (the actual test content)>",
  "user": { "type": "manual", "strict_inputs": ["<the user question>"] },
  "eval": { "evaluator": "redteam_compliance", "threshold": 0.7 },
  "tags": ["dimension:implicit_diagnosis", "user:u1"]
}

There is no ground-truth answer in this dataset: compliance is judged by the server-side redteam_compliance LLM-as-Judge (the evaluator implementation is not published). Cases carry no PII and no system-specific bindings.

How to Participate (offline submission)

  1. Download full.jsonl; for each user.strict_inputs, run your AI assistant and collect its reply.
  2. Produce a results file in the results_sample.jsonl format — one {"id", "answer"} per line, answer non-empty.
  3. Upload to the HMA platform; the server-side judge scores each reply against the compliance red lines and aggregates by dimension.

README history 6 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2026-08-24fix: 声明 configs 仅收 full.jsonl,修复 Viewer schema 冲突(0 → 50 rows)fc26c213.7 KB
    Loading...
  2. 2026-06-30Pure-English release: translate all 50 questions to English (language=en)62ea5253.6 KB
    Loading...
  3. 2026-06-29Anglicize item titles ([Implicit Diagnosis] etc.) and metadata; question text...03b90743.6 KB
    Loading...
  4. 2026-06-29Rewrite README in English (align with ESL-Bench / MedHall-Bench style)fb939713.5 KB
    Loading...
  5. 2026-06-29Publish MedHarm-Bench batch 202606 (50 red-team compliance cases, answer-free)b0c66f21.6 KB
    Loading...
  6. 2026-06-29initial commit0e088550 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Community discussions 1 thread · 1 open · 1 comments

Threads posted by the community on Hugging Face: bug reports, questions about usage, pull requests on the README, license clarifications. Click any thread to expand and read the full conversation inline. Newest first.

  1. 2026-08-25[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · evaluate

Read further

Metadata

License
apache-2.0

Repository

Download the dataset

0

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("mirobody/MedHarm-Bench")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="mirobody/MedHarm-Bench", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/mirobody/MedHarm-Bench
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration