affaan-m/ECC

healthcare-emr-patterns

医疗应用中EMR/EHR的开发模式。临床安全、就诊工作流程、处方生成、临床决策支持集成以及以可访问性为先的医疗数据录入用户界面。

64Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/healthcare-emr-patterns"
Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn healthcare-emr-patterns's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: 构建电子病历(EMR)和电子健康档案(EHR)系统的模式。优先考虑患者安全、临床准确性和医生工作效率。

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/healthcare-emr-patterns"
Check the pinned source

Best fit

  • 医疗应用中EMR/EHR的开发模式。临床安全、就诊工作流程、处方生成、临床决策支持集成以及以可访问性为先的医疗数据录入用户界面。

Bring this context

  • A concrete task that matches the documented purpose of healthcare-emr-patterns.
  • The files, examples, or context the task depends on.
  • Your constraints, target environment, and definition of done.

Expected outputs

  • A result that follows the pinned healthcare-emr-patterns instructions.
  • A concise record of assumptions, inputs used, and unresolved questions.
  • A final check against the source workflow and relevant permission signals.

Key source sections

Read healthcare-emr-patterns through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

使用场景

构建患者就诊工作流(主诉、检查、诊断、处方) 实现临床记录(结构化文本 + 自由文本 + 语音转文字) 设计含药物相互作用检查的处方/用药模块 集成临床决策支持系统(CDSS) 构建带参考范围高亮显示的检验结果展示 实现临床数据审计追踪 设计医疗场景下易用的临床数据录入界面

SKILL.md · 使用场景
构建患者就诊工作流(主诉、检查、诊断、处方)实现临床记录(结构化文本 + 自由文本 + 语音转文字)设计含药物相互作用检查的处方/用药模块
02

工作原理

每个设计决策必须通过以下问题评估:"这会对患者造成伤害吗?"

SKILL.md · 工作原理
药物相互作用必须发出警报,不能静默通过异常检验值必须以视觉方式标记关键生命体征必须触发升级工作流
03

患者安全优先

每个设计决策必须通过以下问题评估:"这会对患者造成伤害吗?"

SKILL.md · 患者安全优先
药物相互作用必须发出警报,不能静默通过异常检验值必须以视觉方式标记关键生命体征必须触发升级工作流
04

单页就诊流程

Review the “单页就诊流程” section in the pinned source before continuing.

SKILL.md · 单页就诊流程
Review and apply the “单页就诊流程” source section.
05

智能模板系统

任何模板中的危险信号必须触发可见且不可关闭的警报——而非通知提示。

SKILL.md · 智能模板系统
任何模板中的危险信号必须触发可见且不可关闭的警报——而非通知提示。

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use healthcare-emr-patterns to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned healthcare-emr-patterns source to [task]. Pay particular attention to these source sections: “使用场景”, “工作原理”, “患者安全优先”, “单页就诊流程”, “智能模板系统”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current healthcare-emr-patterns result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “使用场景” has been checked.

The source section “工作原理” has been checked.

The source section “患者安全优先” has been checked.

The source section “单页就诊流程” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

healthcare-emr-patterns

EMR/EHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry.

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does healthcare-emr-patterns do?

构建电子病历(EMR)和电子健康档案(EHR)系统的模式。优先考虑患者安全、临床准确性和医生工作效率。

How do I start using healthcare-emr-patterns?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/healthcare-emr-patterns". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars
234,327
Repository forks
35,711
Quality
64/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

64/100
Documentation20/30
Specificity12/25
Maintenance20/20
Trust signals12/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

healthcare-emr-patterns by affaan-m

EMR/EHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry.

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

design-system-capture by event4u-app

Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

医疗电子病历开发模式

构建电子病历(EMR)和电子健康档案(EHR)系统的模式。优先考虑患者安全、临床准确性和医生工作效率。

使用场景

  • 构建患者就诊工作流(主诉、检查、诊断、处方)
  • 实现临床记录(结构化文本 + 自由文本 + 语音转文字)
  • 设计含药物相互作用检查的处方/用药模块
  • 集成临床决策支持系统(CDSS)
  • 构建带参考范围高亮显示的检验结果展示
  • 实现临床数据审计追踪
  • 设计医疗场景下易用的临床数据录入界面

工作原理

患者安全优先

每个设计决策必须通过以下问题评估:"这会对患者造成伤害吗?"

  • 药物相互作用必须发出警报,不能静默通过
  • 异常检验值必须以视觉方式标记
  • 关键生命体征必须触发升级工作流
  • 无审计追踪不得修改临床数据

单页就诊流程

临床就诊应在单页上垂直流动——无需切换标签页:

患者头部信息(固定显示 — 始终可见)
├── 人口学信息、过敏史、当前用药
│
就诊流程(垂直滚动)
├── 1. 主诉(结构化模板 + 自由文本)
├── 2. 现病史
├── 3. 体格检查(按系统分类)
├── 4. 生命体征(自动触发临床评分)
├── 5. 诊断(ICD-10/SNOMED 搜索)
├── 6. 用药(药品数据库 + 相互作用检查)
├── 7. 检查(实验室/影像学医嘱)
├── 8. 计划与随访
└── 9. 签名 / 锁定 / 打印

智能模板系统

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
}

任何模板中的危险信号必须触发可见且不可关闭的警报——而非通知提示。

用药安全模式

用户选择药物
  → 检查当前用药是否存在相互作用
  → 检查就诊用药是否存在相互作用
  → 检查患者过敏史
  → 根据体重/年龄/肾功能验证剂量
  → 若为严重相互作用:完全阻止开药
  → 临床医生必须记录覆盖理由才能继续操作
  → 若为重大相互作用:显示警告,要求确认
  → 将所有警报和覆盖理由记录在审计追踪中

关键相互作用默认阻止开药。临床医生必须明确覆盖,并在审计追踪中记录原因。系统绝不允许静默通过关键相互作用。

锁定就诊模式

临床就诊一旦签署:

  • 不允许编辑——仅可添加附录(独立的关联记录)
  • 原始记录和附录均显示在患者时间线中
  • 审计追踪记录签署人、签署时间及所有附录记录

临床数据界面模式

生命体征显示: 当前值带正常范围高亮(绿/黄/红),与上次对比的趋势箭头,自动计算的临床评分(NEWS2、qSOFA),内联升级指导。

检验结果展示: 正常范围高亮,与上次值对比,关键值带不可关闭警报,采集/分析时间戳,待处理医嘱及预期周转时间。

处方PDF: 一键生成,包含患者基本信息、过敏史、诊断、药物详情(通用名+商品名、剂量、给药途径、频率、疗程)、临床医生签名栏。

医疗场景无障碍设计

医疗界面的要求比典型网页应用更严格:

  • 最小对比度4.5:1(WCAG AA)——临床医生在不同光照条件下工作
  • 大触摸目标(最小44x44px)——适用于戴手套或快速操作
  • 键盘导航——供快速录入数据的熟练用户使用
  • 不使用纯颜色指示——始终将颜色与文字/图标配对(色盲临床医生)
  • 所有表单字段带屏幕阅读器标签
  • 临床警报不使用自动消失的提示——临床医生必须主动确认

反模式

  • 在浏览器localStorage中存储临床数据
  • 药物相互作用检查静默失败
  • 关键临床警报使用可关闭提示
  • 基于标签页的就诊界面导致临床工作流碎片化
  • 允许编辑已签署/锁定的就诊记录
  • 无审计追踪显示临床数据
  • 使用any类型处理临床数据结构

示例

示例1:患者就诊流程

医生为患者 #4521 开启接诊
  → 固定头部显示:"Rajesh M, 58岁, 男性, 过敏史: 青霉素, 当前用药: 二甲双胍 500mg"
  → 主诉:选择"胸痛"模板
    → 点击标签:"胸骨后", "向左臂放射", "压榨性"
    → 红色预警"压榨性胸骨后胸痛"触发不可关闭的警报
  → 检查:心血管系统 — "S1 S2 正常,无杂音"
  → 生命体征:心率 110, 血压 90/60, 血氧饱和度 94%
    → NEWS2 自动计算:评分 8, 风险 高, 显示升级警报
  → 诊断:搜索"ACS" → 选择 ICD-10 I21.9
  → 用药:选择阿司匹林 300mg
    → CDSS 检查与二甲双胍的相互作用:无相互作用
  → 签署接诊 → 锁定,此后仅可添加补充说明

示例2:用药安全工作流

医生为患者 #4521 开具华法林处方
  → CDSS 检测到:华法林 + 阿司匹林 = 严重相互作用
  → 用户界面:红色不可关闭的模态框阻止开药
  → 医生点击“输入理由并覆盖”
  → 输入:“获益大于风险 — 已监测 INR 方案”
  → 覆盖理由及警报记录在审计追踪中
  → 处方在记录覆盖后继续执行

示例3:锁定就诊 + 附录

Encounter #E-2024-0891 signed by Dr. Shah at 14:30
  → All fields locked — no edit buttons visible
  → "Add Addendum" button available
  → Dr. Shah clicks addendum, adds: "Lab results received — Troponin elevated"
  → New record E-2024-0891-A1 linked to original
  → Timeline shows both: original encounter + addendum with timestamps
Source repo
affaan-m/ECC
Skill path
docs/zh-CN/skills/healthcare-emr-patterns/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected