baseline-extraction-for-clinical-trials
Extracts clinical trial baseline data (study, region, participants, etc.) from article text or PMID. Checks PubMed for metadata; always falls back to LLM extraction for full details.
Best use case
baseline-extraction-for-clinical-trials is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Extracts clinical trial baseline data (study, region, participants, etc.) from article text or PMID. Checks PubMed for metadata; always falls back to LLM extraction for full details.
Teams using baseline-extraction-for-clinical-trials should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/baseline-extraction-for-clinical-trials/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How baseline-extraction-for-clinical-trials Compares
| Feature / Agent | baseline-extraction-for-clinical-trials | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Extracts clinical trial baseline data (study, region, participants, etc.) from article text or PMID. Checks PubMed for metadata; always falls back to LLM extraction for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)
# Baseline Extraction (RCT)
This skill extracts 10 key baseline characteristics from clinical trial articles. It implements a hybrid workflow:
1. **PubMed Lookup**: Checks PubMed API using the PMID to verify existence and get basic metadata.
2. **LLM Extraction**: Analyzes the article text to extract detailed baseline data (since PubMed metadata is limited).
## When to Use
- Use this skill when you need extracts clinical trial baseline data (study, region, participants, etc.) from article text or pmid. checks pubmed for metadata; always falls back to llm extraction for full details in a reproducible workflow.
- Use this skill when a data analytics task needs a packaged method instead of ad-hoc freeform output.
- Use this skill when the user expects a concrete deliverable, validation step, or file-based result.
- Use this skill when `scripts/extract_pdf.py` is the most direct path to complete the request.
- Use this skill when you need the `baseline-extraction for clinical trials` package behavior rather than a generic answer.
## Key Features
- Scope-focused workflow aligned to: Extracts clinical trial baseline data (study, region, participants, etc.) from article text or PMID. Checks PubMed for metadata; always falls back to LLM extraction for full details.
- Packaged executable path(s): `scripts/extract_pdf.py`.
- Reference material available in `references/` for task-specific guidance.
- Structured execution path designed to keep outputs consistent and reviewable.
## Dependencies
- `Python`: `3.10+`. Repository baseline for current packaged skills.
- `Third-party packages`: `not explicitly version-pinned in this skill package`. Add pinned versions if this skill needs stricter environment control.
## Example Usage
```bash
cd "20260316/scientific-skills/Data Analytics/baseline-extraction-for-clinical-trials"
python -m py_compile scripts/extract_pdf.py
python scripts/extract_pdf.py --help
```
Example run plan:
1. Confirm the user input, output path, and any required config values.
2. Edit the in-file `CONFIG` block or documented parameters if the script uses fixed settings.
3. Run `python scripts/extract_pdf.py` with the validated inputs.
4. Review the generated output and return the final artifact with any assumptions called out.
## Implementation Details
See `## Workflow` above for related details.
- Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
- Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
- Primary implementation surface: `scripts/extract_pdf.py`.
- Reference guidance: `references/` contains supporting rules, prompts, or checklists.
- Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
- Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.
## Workflow
### Step 1: Check PubMed (Deterministic)
If the user provides a PMID, use the `baseline_extractor.py` script to check PubMed.
```python
import subprocess
import json
# Replace <PMID> with actual PMID
result = subprocess.run(["python", "scripts/baseline_extractor.py", "<PMID>"], capture_output=True, text=True)
print(result.stdout)
```
**Analyze the Script Output:**
* If `status` is `"success"`: **Stop here.** Return the `data` JSON to the user.
* If `status` is `"not_found"`, `"incomplete"`, or `"error"` (or if no PMID was provided): Proceed to Step 2.
### Step 2: LLM Extraction (Fallback)
If Step 1 did not yield a complete result, use the LLM to extract the information from the **full article text**.
**Input:**
* Full article text provided by the user.
**Instructions:**
1. Read the [Extraction Schema](references/extraction_schema.md) carefully.
2. Analyze the text to identify all 10 required fields.
3. Ensure the output is strictly in the JSON format defined in the schema.
4. **Constraint**: Do not hallucinate. If a field is not mentioned in the text, set it to `null` or an empty string.
## Output
Return the final result as a Markdown code block containing the JSON object.
```json
{
"study": "...",
"region": "...",
...
}
```
## Helper Scripts
### PDF Text Extraction
When the user provides a PDF file path, use `extract_pdf.py` to extract the text content before assessment:Related Skills
clinical-reports
Write comprehensive clinical reports (case reports, diagnostic reports, clinical trial reports, and patient documentation) when accuracy, regulatory compliance (HIPAA/FDA/ICH-GCP), and template-driven validation are required.
clinicaltrials-gov-parser
Monitor and summarize competitor clinical trial status changes from ClinicalTrials.gov.
clinicaltrials-db
Query the ClinicalTrials.gov API v2 to search for clinical trials, retrieve detailed study protocols, and analyze recruitment status; use when you need to find trials by condition/drug, export results, or verify study details by NCT ID.
clinical-study-info-extractor
Batch extracts and verifies structured information (PMID, title, abstract, methodology, results, etc.) from clinical research literature using PMIDs. Use when the user wants to extract details from specific PMIDs.
preclinical-pkpd-analyst
Use preclinical pkpd analyst for data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries.
outcome-extraction-for-clinical-trials
Clinical research outcome extraction for meta-analysis. Use when users need to extract outcome measures (binary, continuous, or survival data) from clinical research papers for systematic review and meta-analysis. Handles both database lookup by PMID and real-time LLM extraction.
clinical-data-cleaner
Use when cleaning clinical trial data, preparing data for FDA/EMA submission, standardizing SDTM datasets, handling missing values in clinical studies, detecting outliers in lab results, or converting raw CRF data to CDISC format. Cleans and standardizes clinical trial data for regulatory compliance with audit trails.
meta-baseline-generator
Generates a meta-analysis baseline characteristics section (text + table) from raw data. Supports Chinese and English. Use when the user provides baseline data and wants a formatted results section.
nhanes-clinical-retrospective-biomarker
Generates complete NHANES-style cross-sectional epidemiology + retrospective clinical validation research designs from a user-provided disease and biomarker direction. Always use this skill whenever a user wants to design, plan, or build a population-level biomarker association study using NHANES or similar survey datasets, especially when the article logic includes disease definition, biomarker formula derivation, multivariable logistic regression, restricted cubic spline analysis, subgroup stability testing, and a secondary hospital-based retrospective validation cohort. Covers five study patterns (cross-sectional association, dose-response / RCS, subgroup-stability, NHANES + retrospective validation, preliminary screening-performance) and always outputs four workload configs (Lite / Standard / Advanced / Publication+) with recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path...
clinical-cohort-protocol-designer
Designs retrospective or prospective clinical cohort study protocols for biomedical and clinical research. Always use this skill when the user needs a cohort-based study plan rather than a general study idea, evidence summary, or mechanistic experiment design. Focus on cohort appropriateness, enrollment logic, baseline time-zero definition, follow-up structure, endpoint definition, variable collection, confounding control, and a coherent primary statistical analysis line. Do not invent data availability, follow-up completeness, outcome ascertainment quality, sample size adequacy, or causal interpretability.
unmet-clinical-need-extractor
Extracts concrete unmet clinical needs from guidelines, reviews, real-world studies, and clinical-practice evidence. Use this skill when a user wants to turn broad medical research value into specific clinical pain points such as weak early detection, poor risk stratification, treatment-response heterogeneity, monitoring gaps, diagnostic delay, undertreatment, overtreatment, or implementation failure. Always ground unmet-need claims in retrieved evidence and distinguish true care gaps from generic statements of importance.
clinical-question-clarifier
Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question. Always use this skill whenever a user has an early-stage clinical or research thought, an over-broad topic, an ill-defined evidence question, or an unclear problem statement that must be translated into a question framing suitable for literature retrieval, evidence synthesis, gap analysis, study design, or downstream protocol planning. Never jump straight to answering the substantive medical question unless the user explicitly asks for that. Focus first on question framing, boundary setting, and downstream-ready formulation.