tdg-personal/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.
71
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
67%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 does well at specifying concrete healthcare development capabilities and occupies a clear niche that minimizes conflict with other skills. However, it lacks an explicit 'Use when...' clause, which weakens its completeness, and could benefit from additional natural trigger terms that users might actually say when requesting this type of help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when building healthcare applications, electronic medical/health record systems, or clinical software.'
Include common user-facing trigger term variations such as 'electronic medical records', 'patient records', 'FHIR', 'HL7', 'medical software', 'health app', or 'clinical documentation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. These are distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain context, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes relevant domain terms like 'EMR', 'EHR', 'healthcare', 'clinical', 'prescription', 'encounter workflows', but misses common user variations like 'electronic medical records', 'patient records', 'FHIR', 'HL7', 'medical software', or 'health app'. | 2 / 3 |
Distinctiveness Conflict Risk | The healthcare/EMR/EHR domain is a clear niche with distinct triggers. Terms like 'prescription generation', 'clinical decision support', and 'encounter workflows' are highly specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid domain-specific guidance for healthcare EMR development with strong workflow clarity and safety-first patterns. Its main weaknesses are the lack of fully executable code examples (relying on flowcharts and narrative walkthroughs instead) and the monolithic structure that could benefit from splitting detailed topics into referenced files. The clinical safety patterns and anti-patterns are genuinely valuable additions that Claude wouldn't inherently know.
Suggestions
Add executable code examples for key patterns — e.g., a concrete React component for the drug interaction modal, or a working function that checks interactions against a medication list and returns blocking/warning results.
Split detailed subsections (accessibility guidelines, prescription PDF generation, lab results display) into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Replace narrative example walkthroughs (Example 1-3) with more compact input/output pairs or code-driven examples that demonstrate the actual implementation rather than describing user flows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes some explanatory text that Claude already knows (e.g., explaining what WCAG AA is, what an audit trail is). The examples section is somewhat verbose with narrative walkthroughs that could be tightened. However, the domain-specific clinical safety patterns and anti-patterns are genuinely useful additions. | 2 / 3 |
Actionability | The skill provides good structural guidance (TypeScript interface, workflow diagrams, encounter flow) but lacks fully executable code. The medication safety pattern is described as a flowchart rather than implementable code. The ClinicalTemplate interface is a good start but there's no concrete implementation showing how to wire up interaction checking, alert display, or audit logging. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit validation checkpoints. The medication safety pattern has a clear decision tree with blocking/override/audit steps. The encounter flow is well-sequenced (1-9 steps). The locked encounter pattern includes explicit feedback loops (no edit → addendum only → audit trail). Critical safety validations are explicitly called out as blocking steps. | 3 / 3 |
Progressive Disclosure | The content is entirely self-contained in a single file with no references to external files for deeper topics. Given the breadth of topics covered (encounter workflows, medication safety, CDSS integration, accessibility, UI patterns, audit trails), some content like the accessibility guidelines or prescription PDF generation could be split into referenced files. The internal organization with headers is decent but the file is quite long. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents