clinical-case-schema

Structure synthetic clinical cases for the AI Patient Simulator API in Chilean contexts.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/danycapo8/labs-skills --skill clinical-case-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clinical-case-schema
Source: https://github.com/danycapo8/labs-skills/tree/main/clinical-case-schema
Command: npx skills add https://github.com/danycapo8/labs-skills --skill clinical-case-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilita la creación y validación de estructuras de casos clínicos sintéticos para el AI Patient Simulator siguiendo la API oficial, asegurando consistencia y trazabilidad para sprint de validación y decisiones de severidad.

Core Features & Use Cases

  • Definición y validación de estructuras de casos según el esquema de la API.
  • Conversión de propuestas del scout en casos ejecutables para simulación.
  • Decisión de stop_reason y severidad clínica (P1/P2/P3) respetando contexto Chile/MINSAL.
  • Guía para casos en cardiology-ambulatory y chronic care.

Quick Start

Crea un golden case mínimo siguiendo el esquema, especificando id, title, patient, turnos y acceptance.

Frequently Asked Questions about clinical-case-schema

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure synthetic clinical cases for a patient simulator API?

To structure synthetic clinical cases for a patient simulator API, define required YAML fields including id, title, patient demographics, turns, and acceptance criteria, ensuring alignment with the official API schema.

How do I convert scout proposals into executable simulator cases?

Converting scout proposals into executable simulator cases requires mapping the proposal data into the validated YAML clinical case schema, specifying patient interactions and acceptance tests for the simulation environment.

How do I assign clinical severity and stop_reason for Chilean MINSAL contexts?

Assigning clinical severity (P1/P2/P3) and stop_reason for Chilean MINSAL contexts involves evaluating patient acuity against local triage guidelines to determine the simulation's termination conditions and priority level.

What are the required fields for a golden case in cardiology ambulatory simulations?

Required fields for a golden case in cardiology ambulatory simulations include a unique id, title, patient profile, structured conversational turns, and acceptance criteria, all validated against the YAML schema.

Does this clinical case schema support chronic care patient simulations?

Yes, the clinical case schema supports chronic care patient simulations by enforcing structured YAML fields for patient history and turn interactions, specifically aligning with chronic care and ambulatory cardiology guidelines.