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.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/healthcare-emr-patterns/SKILL.md

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

Quality

Content

62%

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

The body is well-structured with strong, safety-aware workflow sequencing and a genuinely useful TypeScript interface, but it is monolithic with no progressive disclosure to bundle files and mixes executable structures with ASCII-pseudocode flows and prose UI descriptions. Tightening redundant restatement and splitting detailed examples would improve it.

Suggestions

Move the three worked Examples (or the Accessibility for Healthcare section) into a separate references file linked from the body, so SKILL.md stays a lean overview.

Tighten redundancy: the 'critical interactions block prescribing by default / clinician must override with documented reason / system never silently allows' idea is stated three times in the Medication Safety Pattern — state the rule once.

Trim or collapse accessibility basics Claude already knows (contrast ratios, 44x44px touch targets, color-only indicators) down to the healthcare-specific deviations, keeping only what is non-obvious.

Dimension	Reasoning	Score
Conciseness	Most of the content is domain-specific and earns its place (encounter flow, medication safety logic, locked-encounter rules), but the Accessibility section restates standard concepts Claude already knows (4.5:1 contrast, 44x44px targets, no color-only indicators) and the critical-interaction block/override rule is stated three times.	2 / 3
Actionability	There is one concrete, complete TypeScript interface and several specific rules (block critical interactions, NEWS2/qSOFA scoring, ICD-10/SNOMED), but the core encounter and medication workflows are ASCII pseudocode/diagrams and the UI patterns are descriptive prose rather than executable guidance.	2 / 3
Workflow Clarity	The encounter flow is an explicit numbered 1-9 sequence and the medication safety pattern includes explicit validation checkpoints (interaction, allergy, and dose checks) with decision branches, escalation, and audit logging, so validation is present and no cap applies.	3 / 3
Progressive Disclosure	Sections are clearly organized with headers, but the skill is a single monolithic file well over 50 lines with no external references, and the three detailed examples plus the accessibility section are inline content that could plausibly be split into separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

57%

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

The description is specific to a distinct healthcare-EMR niche and lists relevant capability areas, but it lacks an explicit 'Use when' trigger clause and relies on nominalized topic phrases rather than concrete action verbs. Adding trigger guidance would lift completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger situations, e.g. 'Use when building patient encounter workflows, prescribing modules with drug-interaction checks, or CDSS integration for healthcare apps.'

Reframe the capability list around concrete verbs (e.g. 'Generate prescriptions, check drug interactions, flag abnormal labs, build single-page encounter workflows') instead of nominalized noun-phrases.

Include common colloquial trigger terms users would actually say (e.g. 'electronic health records, medical records, prescribing, medication interactions') alongside the technical acronyms.

Dimension	Reasoning	Score
Specificity	Names the domain and several capability areas ('prescription generation, clinical decision support integration, accessibility-first UI for medical data entry'), but these are nominalized noun-phrases rather than crisp concrete action verbs, and 'Clinical safety' is abstract rather than a concrete action.	2 / 3
Completeness	It clearly states what the skill covers, but there is no explicit 'Use when...' clause or equivalent trigger guidance, so the 'when' is only implied and completeness is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Relevant domain keywords a healthcare developer would say are present (EMR/EHR, prescription, clinical decision support), but there is no 'Use when' trigger phrasing and the keyword set lacks common colloquial variations, so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	'EMR/EHR development patterns for healthcare applications' identifies a clear, narrow niche with domain-specific triggers that are very unlikely to fire for or conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/healthcare-emr-patterns/SKILL.md
Commit: 754b8dd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.