Dataset Viewer
The dataset viewer is not available for this subset.
Cannot get the split names for the config 'default' of the dataset.
Exception:    SplitsNotFoundError
Message:      The split names could not be parsed from the dataset config.
Traceback:    Traceback (most recent call last):
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 290, in _generate_tables
                  pa_table = paj.read_json(
                      io.BytesIO(batch), read_options=paj.ReadOptions(block_size=block_size)
                  )
                File "pyarrow/_json.pyx", line 364, in pyarrow._json.read_json
                File "pyarrow/error.pxi", line 155, in pyarrow.lib.pyarrow_internal_check_status
                File "pyarrow/error.pxi", line 92, in pyarrow.lib.check_status
                  raise convert_status(status)
              pyarrow.lib.ArrowInvalid: JSON parse error: Column() changed from object to string in row 0
              
              During handling of the above exception, another exception occurred:
              
              Traceback (most recent call last):
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
                  for split_generator in builder._split_generators(
                                         ~~~~~~~~~~~~~~~~~~~~~~~~~^
                      StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 101, in _split_generators
                  pa_table = next(iter(self._generate_tables(**splits[0].gen_kwargs, allow_full_read=False)))[1]
                             ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 304, in _generate_tables
                  batch = json_encode_fields_in_json_lines(original_batch, json_field_paths)
                File "/usr/local/lib/python3.14/site-packages/datasets/utils/json.py", line 111, in json_encode_fields_in_json_lines
                  examples = [ujson_loads(line) for line in original_batch.splitlines()]
                              ~~~~~~~~~~~^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/utils/json.py", line 20, in ujson_loads
                  return pd.io.json.ujson_loads(*args, **kwargs)
                         ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
              ValueError: Expected object or value
              
              The above exception was the direct cause of the following exception:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 68, in compute_split_names_from_streaming_response
                  for split in get_dataset_split_names(
                               ~~~~~~~~~~~~~~~~~~~~~~~^
                      path=dataset,
                      ^^^^^^^^^^^^^
                      config_name=config,
                      ^^^^^^^^^^^^^^^^^^^
                      token=hf_token,
                      ^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
                  info = get_dataset_config_info(
                      path,
                  ...<6 lines>...
                      **config_kwargs,
                  )
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
                  raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
              datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

Clinical Panel Corpus

A corpus of independent, round-one (pre-discussion) multi-role clinical panel responses: clinical questions in paired closed/open form, answered by a five-role panel of LLM agents, sampled 30x per case across multiple models.

v0.1 preview. This release contains the round-one (independent, pre-discussion) panel responses only. The panel design is being revised; a later version will add deliberation rounds and abstention labels and will supersede this one. The generation and analysis code is not yet public. Expect the layout to stay stable, but treat v0.1 as a preview rather than the version of record.

⚠️ AI-generated outputs β€” not clinical advice. Every response was produced by a language model for research on panel behaviour. None of it is validated for, or intended for, clinical use.

At a glance

Cases 300 closed (MedXpertQA-R, MedXpertQA-U MCQ); 268 also in open (de-optioned) form
Roles Diagnostician, Investigator, Therapeutist, Safety and Pharmacology specialist, Mechanism specialist (5)
Sampling 30 independent realisations per case; temperature 0.7; root seed 20260428
Models claude-haiku-4-5-20251001, gemini-2.5-flash, gemini-2.5-flash-lite, gemini-3.5-flash
Total 340,800 panel responses (4 models Γ— 2 arms Γ— 5 roles Γ— 30 runs)
Per response primary_recommendation, key_finding, contraindication_flag, reasoning
Files 2,312 (embeddings: 37, loaded: 3, responses: 2272) + RELEASE_MANIFEST.json

Layout

Three top-level folders + RELEASE_MANIFEST.json (sha256 of every file):

  • responses/ β€” one JSONL trace per case at responses/<model_tag>/panel_runs/headline__<case_id>__<spec-hash>.jsonl; <model_tag> fuses model and arm (closed vs -open). Because <case_id> contains a / (e.g. MedXpertQA-R/Text-702), each trace nests one directory deeper. Each trace is a header row followed by one response row per (role Γ— realisation). A validity flag is computed at load time, not stored.
  • embeddings/ β€” optional float32 .npz grids over the question and the response fields (text-embedding-005).
  • loaded/ β€” rehydrated case content (the closed + de-optioned open questions), as cases.parquet and cases_open_ended.parquet.

Loading

Each trace mixes a header row with response rows, so the generic datasets auto-loader is not the intended entry point. Download the repo and read the traces directly:

import json
from pathlib import Path
from huggingface_hub import snapshot_download

root = Path(snapshot_download("bowyerlab/clinical-panel-corpus", repo_type="dataset",
                              allow_patterns=["responses/gemini-2_5-flash-range/**"]))

for trace in root.glob("responses/*/panel_runs/**/*.jsonl"):
    rows = [json.loads(line) for line in trace.open()]
    header, responses = rows[0], rows[1:]
    for r in responses:
        # r["agent_id"], r["run_idx"], r["seed"], r["model_version"], token counts, timestamp
        try:
            fields = json.loads(r["text"])   # the four structured fields
        except json.JSONDecodeError:
            fields = None                    # refusal / malformed output: kept as observed

Header rows carry case_id, agent_ids, n_runs, panel_spec_name and panel_spec_hash. Response rows carry agent_id, agent_idx, run_idx, seed, model_version, resolved_model_version, input_tokens, output_tokens, thinking_tokens, timestamp and text (the model's raw output, normally a JSON object with the four fields above). Join to the question content on case_id via loaded/cases.parquet (closed arm) or loaded/cases_open_ended.parquet (open arm).

Scope β€” not a correctness benchmark

Each role gives its own domain assessment (a diagnosis, the next investigation, a management step, a safety flag, a mechanism), not the source MCQ's answer option β€” so the gold answer is not a correctness label for these responses, by construction. Pair with an external reference standard if you need correctness. What is validated is the data's integrity and behaviour (coverage, schema validity, refusal/degeneracy rates, role fidelity, diversity, stochastic variation).

Licensing

  • Responses, corpus structure, de-optioned rewrites: CC-BY-4.0.
  • Source questions: MedXpertQA-R, MedXpertQA-U via MedAgentsBench (dataset commit 87e99bf4), MIT-licensed and redistributed under MIT.

Citation

No DOI or paper yet. Until there is one, please cite the dataset directly:

Bowyer, S. (2026). Clinical Panel Corpus (v0.1, preview) [Dataset]. Imperial College London. https://huggingface.co/datasets/bowyerlab/clinical-panel-corpus

@misc{bowyer2026clinicalpanelcorpus,
  author       = {Bowyer, Stuart},
  title        = {Clinical Panel Corpus},
  year         = {2026},
  version      = {0.1},
  publisher    = {Hugging Face},
  howpublished = {\url{https://huggingface.co/datasets/bowyerlab/clinical-panel-corpus}},
  note         = {Preview release}
}

Ethics

Source items are exam/benchmark questions β€” no real patient data, no PII. All responses are model-generated and labelled as not clinical advice.

Downloads last month
28