AgentStack
SKILL verified Apache-2.0 Self-run

Clinical Timeline Extraction

skill-elisaterumi-ai-clinical-agent-skills-timeline-extraction · by elisaterumi-ai

Extracts and organizes clinical events into a chronological timeline based on patient records or medical notes. Use when reconstructing the sequence of symptoms, diagnoses, treatments, or hospital events.

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

Install

$ agentstack add skill-elisaterumi-ai-clinical-agent-skills-timeline-extraction

✓ 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.

Are you the author of Clinical Timeline Extraction? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

When extracting a clinical timeline, follow these steps:

1. Identify temporal information

Detect all time-related expressions, including:

  • Dates (e.g., 12/03/2023)
  • Relative time (e.g., "2 days ago", "last week")
  • Event order (e.g., "after admission", "prior to surgery")

2. Extract clinical events

Identify relevant events such as:

  • Symptom onset
  • Medical visits or admissions
  • Diagnoses
  • Treatments or procedures
  • Medication changes
  • Test results

Only include explicitly mentioned events.

3. Link events to time

  • Associate each event with its corresponding time reference
  • If no explicit time is given, mark as "time": "unknown"

Do not infer missing temporal information.


4. Normalize order

  • Arrange events in chronological order
  • Use relative ordering if exact dates are not available

5. Preserve original meaning

  • Keep event descriptions close to the original text
  • Do not rewrite or interpret beyond what is stated

6. Output format

Return the result as JSON:

{
  "timeline": [
    {
      "time": "...",
      "event": "..."
    }
  ]
}

7. Constraints

  • Only include events present in the text
  • Do not hallucinate dates or events
  • Do not infer temporal relationships not explicitly stated
  • Do not modify clinical meaning

Keep event descriptions concise and factual

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.