AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Clinical Data Structuring

skill-elisaterumi-ai-clinical-agent-skills-data-structuring · by elisaterumi-ai

Converts unstructured clinical text into structured JSON by extracting key medical information such as symptoms, diagnoses, medications, procedures, and temporal data. Use when transforming clinical notes into machine-readable format.

No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-elisaterumi-ai-clinical-agent-skills-data-structuring

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-elisaterumi-ai-clinical-agent-skills-data-structuring)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Clinical Data Structuring? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

When structuring clinical data, follow these steps:

1. Extract key information

Identify and extract relevant clinical elements:

  • Symptoms and complaints
  • Diagnoses or conditions
  • Medications (include dosage if available)
  • Procedures and treatments
  • Laboratory results
  • Temporal information (dates, durations, sequence of events)

Only extract explicitly mentioned information.

2. Organize into structured fields

Group extracted information into the following categories:

  • symptoms
  • diagnoses
  • medications
  • procedures
  • lab_results
  • timeline

If a category has no data, return an empty list.

3. Preserve original text

  • Keep extracted values as they appear in the input
  • Do not normalize or translate
  • Do not modify wording

4. Avoid duplication

  • Do not repeat the same entity multiple times
  • Keep distinct entries separate

5. Handle temporal data

  • Represent events with associated time when available
  • If time is missing, include "time": "unknown"

6. Output format

Return the result as JSON:

{
  "symptoms": [],
  "diagnoses": [],
  "medications": [],
  "procedures": [],
  "lab_results": [],
  "timeline": [
    {
      "time": "...",
      "event": "..."
    }
  ]
}

7. Constraints

  • Do not hallucinate information
  • Do not infer missing data
  • Only include explicitly stated clinical information
  • Keep output strictly in JSON format
  • Do not include explanations

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.