clinical-case-report

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Clinical Case Report Skill

临床病例报告Skill

Generate a structured medical case presentation for clinical rounds, conferences, or documentation. The output follows standard medical formatting conventions used in hospital settings worldwide.
生成用于临床查房、会议或文档记录的结构化病例展示内容。输出遵循全球医院通用的标准医疗格式规范。

What you will produce

生成内容

A single-page HTML case report (
index.html
). Content varies by format (see
references/case-formats.md
— selected in Step 0):
SOAP / Conference format:
  • Patient identification — age, sex, chief complaint
  • History of Present Illness (HPI) — chronological narrative with pertinent positives and negatives
  • Past Medical History, Medications, Allergies
  • Review of Systems
  • Physical Examination — systematic findings by system
  • Vital Signs — formatted table with reference ranges and flags
  • Investigations — laboratory results and imaging findings
  • Assessment — primary diagnosis and differential (3–5 items) with clinical reasoning for each
  • Management Plan — evidence-based, organised by problem
Brief Rounds format (daily review, ward round, handover, ICU, post-call):
  • ID line — age, sex, day of admission, primary problem
  • Interval events / current status — what has changed since last review
  • Active problems — numbered list
  • Plan-by-problem — concise actions for each active problem
  • Full HPI and systematic physical examination are not included

一份单页HTML病例报告(
index.html
)。内容格式取决于所选类型(详见
references/case-formats.md
,需在步骤0中选择):
SOAP/会议格式:
  • 患者身份信息——年龄、性别、主诉
  • 现病史(HPI)——按时间顺序叙述,包含相关阳性及阴性症状
  • 既往病史、用药史、过敏史
  • 系统回顾
  • 体格检查——按系统分类的检查结果
  • 生命体征——带参考范围及异常标记的格式化表格
  • 辅助检查——检验结果及影像学表现
  • 评估——主要诊断及鉴别诊断(3-5项),每项附临床推理依据
  • 诊疗计划——循证方案,按问题分类
简要查房格式(日常查房、病房交班、ICU查房、术后查房):
  • 身份栏——年龄、性别、入院天数、主要诊断
  • 病情变化/当前状态——自上次评估以来的病情变化
  • 现存问题——编号列表
  • 按问题制定的计划——针对每个现存问题的简洁处理措施
  • 不包含完整现病史及系统体格检查

Step-by-step workflow

分步工作流程

Step 0 — Load reference files

步骤0 — 加载参考文件

Before starting, read both reference files:
  1. references/case-formats.md
    — use this to choose the correct output format (SOAP, Conference, or Brief Rounds) based on the user's context
  2. references/checklist.md
    — keep P0 gates in mind throughout; you must pass all P0 items before emitting the final artifact
开始前,请阅读两份参考文件:
  1. references/case-formats.md
    ——根据用户场景选择正确的输出格式(SOAP、会议或简要查房)
  2. references/checklist.md
    ——全程牢记P0检查项,在生成最终成果前必须通过所有P0项

Step 1 — Parse the brief

步骤1 — 解析需求

Read the user's prompt and extract:
  • Patient age and sex
  • Chief complaint or presenting problem
  • Any vitals, labs, or imaging the user has provided
  • Clinical context: ED, ward rounds, conference case, outpatient, etc.
  • Specialty context: cardiology, emergency, internal medicine, etc.
If the chief complaint or presenting problem is missing:
  • SOAP / Conference: ask one clarifying question before proceeding. Do not proceed without it.
  • Brief Rounds: if the admission problem or ID line is already available (e.g. "day-3 ICU review for septic shock"), proceed directly — a separate chief complaint is not required.
阅读用户提示并提取以下信息:
  • 患者年龄及性别
  • 主诉或就诊问题
  • 用户提供的任何生命体征、检验或影像学结果
  • 临床场景:急诊、病房查房、会议病例、门诊等
  • 专科场景:心内科、急诊科、内科等
若缺失主诉或就诊问题:
  • SOAP/会议格式:在继续前询问一个明确的问题,不得在缺失该信息的情况下继续。
  • 简要查房格式:若已有入院诊断或身份栏信息(如“ICU住院第3天,感染性休克复查”),可直接继续——无需单独询问主诉。

Step 2 — Build the clinical narrative

步骤2 — 构建临床叙事

For SOAP / Conference outputs: write the HPI as a continuous prose narrative in standard clinical style:
"This is a [age]-year-old [sex] with a history of [relevant PMH] who presents with [chief complaint]. Symptoms began [timeline] and are characterised by [quality, severity, radiation]. Associated symptoms include [list]. Pertinent negatives include [list]."
The HPI must be chronological. Include timeline markers ("2 hours prior to presentation", "onset yesterday morning").
For Brief Rounds outputs (daily review, ward round, handover, ICU, post-call): skip the full HPI and examination. Instead produce:
  • ID line: "[Age][sex], Day [N] of admission, [primary problem]"
  • Interval events / current status: what has changed since last review
  • Active problems: numbered list
  • Plan-by-problem: concise action for each active problem
针对SOAP/会议格式输出: 以标准临床风格撰写连续 prose 叙述形式的现病史:
“这是一位[年龄]岁[性别]患者,有[相关既往病史],因[主诉]就诊。症状始于[时间线],表现为[性质、严重程度、放射部位]。伴随症状包括[列表]。相关阴性症状包括[列表]。”
现病史必须按时间顺序撰写,包含时间标记(如“就诊前2小时”“昨日清晨起病”)。
针对简要查房格式输出(日常查房、病房交班、ICU查房、术后查房):跳过完整现病史及体格检查,生成以下内容:
  • 身份栏:“[年龄][性别],入院第[N]天,[主要诊断]”
  • 病情变化/当前状态:自上次评估以来的病情变化
  • 现存问题:编号列表
  • 按问题制定的计划:针对每个现存问题的简洁处理措施

Step 3 — Generate physiologically consistent clinical data

步骤3 — 生成生理指标一致的临床数据

If the user has not provided specific values, generate values that are internally consistent with the diagnosis:
Consistency checks (typical patterns):
  • A patient in shock typically has: HR >100, SBP <90, raised lactate, impaired capillary refill — but medications (beta-blockers), age, or shock type (neurogenic, spinal) can alter this pattern
  • Pneumonia typically presents with raised WBC, raised CRP, temperature >38°C — but afebrile pneumonia exists, especially in the elderly or immunocompromised
  • A STEMI typically shows ST elevation in contiguous leads and raised high-sensitivity troponin — but early presentations may have initially normal troponin; CK-MB is not universally required
  • Sepsis typically shows raised or low WBC, raised lactate >2, temperature abnormality — but compensated early sepsis may present with normal vitals
  • Lab units must match convention: creatinine in µmol/L or mg/dL (state which), glucose in mmol/L, haemoglobin in g/dL
Critical rule — preserve user-provided data:
  • Never overwrite a value the user has explicitly stated
  • If a user-provided value is atypical for the diagnosis, keep it and note the atypical presentation in the assessment rather than forcing canonical numbers
  • Never generate a value that contradicts the stated diagnosis
若用户未提供具体数值,生成与诊断内部一致的数值:
一致性检查(典型模式):
  • 休克患者通常表现为:心率>100次/分,收缩压<90mmHg,乳酸升高,毛细血管再充盈时间延长——但药物(如β受体阻滞剂)、年龄或休克类型(神经源性、脊髓源性)可能改变此模式
  • 肺炎通常表现为:白细胞升高、CRP升高、体温>38℃——但存在无热肺炎,尤其在老年或免疫功能低下患者中
  • ST段抬高型心肌梗死(STEMI)通常表现为:相邻导联ST段抬高、高敏肌钙蛋白升高——但早期就诊时肌钙蛋白可能正常;CK-MB并非普遍必需
  • 脓毒症通常表现为:白细胞升高或降低、乳酸>2mmol/L、体温异常——但代偿期早期脓毒症可能表现为生命体征正常
  • 检验单位必须符合惯例:肌酐单位为µmol/L或mg/dL(需注明),血糖单位为mmol/L,血红蛋白单位为g/dL
关键规则——保留用户提供的数据:
  • 不得覆盖用户明确给出的数值
  • 若用户提供的数值与诊断不符,保留该数值并在评估部分注明非典型表现,而非强制使用标准数值
  • 不得生成与所述诊断矛盾的数值

Step 4 — Write the assessment

步骤4 — 撰写评估部分

The assessment section must contain:
  1. Primary diagnosis stated clearly on the first line
  2. Clinical reasoning — one sentence explaining why this is the most likely diagnosis
  3. Differential diagnosis — exactly 3 to 5 items, each with one sentence of supporting or refuting evidence
  4. Risk stratification — include a validated clinical score where applicable (TIMI for ACS, GRACE for ACS, Killip class + Shock Index for STEMI/cardiogenic shock, CURB-65 for pneumonia, qSOFA for sepsis, Wells for PE, etc.). Killip class and Shock Index together are accepted as sufficient risk stratification for STEMI/cardiogenic shock cases.
评估部分必须包含:
  1. 主要诊断:在第一行明确陈述
  2. 临床推理:用一句话解释为何该诊断最可能
  3. 鉴别诊断:恰好3-5项,每项附一句支持或排除的依据
  4. 风险分层:适用时纳入验证过的临床评分(如ACS用TIMI评分、ACS用GRACE评分、STEMI/心源性休克用Killip分级+休克指数、肺炎用CURB-65评分、脓毒症用qSOFA评分、肺栓塞用Wells评分等)。对于STEMI/心源性休克病例,Killip分级联合休克指数可作为充分的风险分层依据。

Step 5 — Write the management plan

步骤5 — 撰写诊疗计划

The plan must be:
  • Specific: write drug names, doses, routes, and frequencies. Do not write "start antibiotics" — write "Piperacillin-Tazobactam 4.5g IV q8h for 5 days"
  • Organised by problem using numbered headers
  • Evidence-based: management must reflect current standard of care for the diagnosis
  • Complete: include investigations to order, monitoring parameters, consults to request, and disposition
If you are uncertain about a specific dose, write "[drug name] — dose per local formulary/protocol" rather than inventing a dose.
诊疗计划必须:
  • 具体:写出药物名称、剂量、给药途径及频次。不得写“启动抗生素治疗”,而应写“哌拉西林-他唑巴坦 4.5g 静脉滴注 q8h,疗程5天”
  • 按问题分类:使用编号标题
  • 循证:诊疗方案必须符合当前该诊断的标准治疗规范
  • 完整:包含需开具的辅助检查、监测指标、需会诊的科室及去向安排
若不确定具体剂量,应写“[药物名称]——剂量参照当地处方集/诊疗规范”,而非自行编造剂量。

Important — Prescribing Safety

重要提示——处方安全

Generated plans must:
  • Be marked as educational/simulated, not a substitute for clinician judgment
  • Use "per local formulary/protocol" language when required patient variables (weight, renal function, allergies) are missing from the brief
  • List key contraindications and unknowns before medication recommendations when relevant patient data has not been provided
  • Never claim a plan is "definitive" or "standard of care" without full patient context (allergy status, renal/hepatic function, pregnancy status, weight, anticoagulation/bleeding risk)
  • Include a disclaimer footer in the HTML output stating the case is for educational and documentation purposes only
生成的诊疗计划必须:
  • 标注为教育/模拟用途,不可替代临床医师判断
  • 当缺失所需患者变量(体重、肾功能、过敏史)时,使用“参照当地处方集/诊疗规范”的表述
  • 当相关患者数据缺失时,在推荐药物前列出关键禁忌症及未知信息
  • 在无完整患者背景(过敏状态、肾/肝功能、妊娠状态、体重、抗凝/出血风险)的情况下,不得声称计划为“确定性”或“标准治疗方案”
  • 在HTML输出中添加免责声明页脚,说明本病例仅用于教育及文档记录目的

Step 6 — Write
index.html

步骤6 — 撰写
index.html

Requirements for the HTML output:
  • Professional medical document typography (Georgia or system serif font preferred)
  • White background, dark text — suitable for printing
  • Vital signs and lab results in HTML
    <table>
    elements
  • Critical findings (ST elevation, raised troponin, low BP, etc.) highlighted in a visually distinct callout box with red left border
  • @media print CSS rules so the document prints cleanly on A4/Letter
  • Tag every major section with
    data-od-id
    for comment-mode targeting:
html
<section data-od-id="hpi">...</section>
<section data-od-id="vitals">...</section>
<section data-od-id="pmh">...</section>
<section data-od-id="examination">...</section>
<section data-od-id="investigations">...</section>
<section data-od-id="assessment">...</section>
<section data-od-id="plan">...</section>
HTML输出要求:
  • 专业医疗文档排版(优先使用Georgia或系统衬线字体)
  • 白底黑字——适合打印
  • 生命体征及检验结果使用HTML
    <table>
    元素展示
  • 关键异常结果(ST段抬高、肌钙蛋白升高、低血压等)用左侧红色边框的醒目标注框突出显示
  • 添加@media print CSS规则,确保文档可在A4/Letter纸型上清晰打印
  • 为每个主要章节添加
    data-od-id
    标签,用于评论模式定位:
html
<section data-od-id="hpi">...</section>
<section data-od-id="vitals">...</section>
<section data-od-id="pmh">...</section>
<section data-od-id="examination">...</section>
<section data-od-id="investigations">...</section>
<section data-od-id="assessment">...</section>
<section data-od-id="plan">...</section>

Step 7 — Self-check against
references/checklist.md

步骤7 — 根据
references/checklist.md
进行自我检查

Before emitting
<artifact>
, run every P0 item in
references/checklist.md
. All P0 items must pass. Fix any failures before emitting.
在生成
<artifact>
前,运行
references/checklist.md
中的所有P0检查项。所有P0项必须通过,修复所有问题后再生成最终成果。