CtrlK
BlogDocsLog inGet started
Tessl Logo

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. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is tdg-personal/healthcare-emr-patterns

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable clinical-safety pattern skill with concrete interfaces, specific thresholds, and clear sequenced workflows. Minor gains are available in tightening redundancy and externalizing the examples.

Suggestions

Trim the overlap between the 'When to Use' bullet list and the description's 'Use when' clause to recover tokens.

Move the three detailed Example walkthroughs into a referenced EXAMPLES.md so SKILL.md stays a tighter overview.

Add an explicit validate→fix→retry feedback loop for the medication-interaction block (e.g., re-check after override) to push workflow clarity higher.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding over concepts Claude already knows; brief rationale clauses earn their place, though the 'When to Use' list lightly duplicates the description's triggers.

4 / 5

Actionability

Provides a concrete TypeScript interface and specific thresholds (NEWS2/qSOFA, 4.5:1 contrast, 44x44px targets) plus concrete example walkthroughs; some core flows are presented as pseudocode rather than executable code.

4 / 5

Workflow Clarity

The 9-step encounter flow and medication-safety flow are clearly sequenced with embedded validation (red-flag alerts, interaction checks, NEWS2 escalation), but classic validate→fix→retry feedback loops are not spelled out.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references in a self-contained skill; at ~150 lines the detailed Examples section could plausibly be split into a referenced file.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities and provides an explicit 'Use when' trigger clause tied to concrete EMR/EHR features. Only minor room to broaden trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry' — giving comprehensive coverage of the EMR domain.

5 / 5

Completeness

Explicitly answers both 'what' (the listed development patterns) and 'when' via 'Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.'

5 / 5

Trigger Term Quality

Good natural keyword coverage including the EMR/EHR synonym pair plus 'encounter workflows', 'prescription generation', and 'clinical data entry UI'; a few common variants like 'medical records' or 'patient records' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear EMR/EHR healthcare niche with distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.