$ loading_
为医疗健康应用提供安全合规的 EMR/EHR 开发模式与界面流程建议
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "healthcare-emr-patterns" 技能： 1. 下载 https://raw.githubusercontent.com/affaan-m/ECC/main/skills/healthcare-emr-patterns/SKILL.md 2. 保存为 ~/.claude/skills/healthcare-emr-patterns/SKILL.md 3. 装好后重载技能，告诉我可以用了
请为门诊 EMR 设计一个完整的就诊流程模式，覆盖患者签到、分诊、主诉记录、病史采集、体格检查、诊断、医嘱与出院小结。请说明每一步的关键数据结构、状态流转、临床安全校验点，以及适合前端实现的 UI 组件建议。
一套结构化的门诊流程设计，包含页面模块、数据模型、校验规则和安全提示建议。
请给我一个电子处方模块的开发模式，支持药品搜索、剂量频次录入、过敏检查、药物相互作用提醒、续方处理和打印输出。请特别强调如何减少误开药风险，并给出后端接口和前端表单交互建议。
处方模块的架构与交互方案，突出临床风险控制、提醒机制和可实现的接口设计。
请为住院 EMR 页面制定临床决策支持集成方案，并提供无障碍优先的表单设计规范。内容包括提醒触发时机、避免告警疲劳的方法、键盘可达性、屏幕阅读器兼容性、颜色与对比度要求，以及对医护高频录入场景的优化建议。
一份兼顾 CDS 集成与无障碍体验的设计规范，适合指导医疗产品开发落地。
Patterns for building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Prioritizes patient safety, clinical accuracy, and practitioner efficiency.
Every design decision must be evaluated against: "Could this harm a patient?"
Clinical encounters should flow vertically on a single page — no tab switching:
Patient Header (sticky — always visible)
├── Demographics, allergies, active medications
│
Encounter Flow (vertical scroll)
├── 1. Chief Complaint (structured templates + free text)
├── 2. History of Present Illness
├── 3. Physical Examination (system-wise)
├── 4. Vitals (auto-trigger clinical scoring)
├── 5. Diagnosis (ICD-10/SNOMED search)
├── 6. Medications (drug DB + interaction check)
├── 7. Investigations (lab/radiology orders)
├── 8. Plan & Follow-up
└── 9. Sign / Lock / Print
interface ClinicalTemplate {
id: string;
name: string; // e.g., "Chest Pain"
chips: string[]; // clickable symptom chips
requiredFields: string[]; // mandatory data points
redFlags: string[]; // triggers non-dismissable alert
icdSuggestions: string[]; // pre-mapped diagnosis codes
}
Red flags in any template must trigger a visible, non-dismissable alert — NOT a toast notification.
User selects drug
→ Check current medications for interactions
→ Check encounter medications for interactions
→ Check patient allergies
→ Validate dose against weight/age/renal function
→ If CRITICAL interaction: BLOCK prescribing entirely
→ Clinician must document override reason to proceed past a block
→ If MAJOR interaction: display warning, require acknowledgment
→ Log all alerts and override reasons in audit trail
Critical interactions block prescribing by default. The clinician must explicitly override with a documented reason stored in the audit trail. The system never silently allows a critical interaction.
Once a clinical encounter is signed:
Vitals Display: Current values with normal range highlighting (green/yellow/red), trend arrows vs previous, clinical scoring auto-calculated (NEWS2, qSOFA), escalation guidance inline.
Lab Results Display: Normal range highlighting, previous value comparison, critical values with non-dismissable alert, collection/analysis timestamps, pending orders with expected turnaround.
Prescription PDF: One-click generation with patient demographics, allergies, diagnosis, drug details (generic + brand, dose, route, frequency, duration), clinician signature block.
Healthcare UIs have stricter requirements than typical web apps:
…
帮助用户在回答前选择简短、标准或详细版本，控制回复深度与 token 用量。
为医疗应用部署提供患者安全自动化评估，发现风险即阻止上线。