Agent skill
Epic Consulting
Epic EMR consulting workflows for ClinDoc, Bridges, interfaces, and clinical builds. USE WHEN user mentions Epic, orderset, ClinDoc, Bridges, interface, HL7, provider matching, VersaCare, ScottCare, OR any client name (Memphis, Raleigh, Orlando, Nova, Baptist).
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/Epic
SKILL.md
Epic Consulting Skill
Expertise Areas
- ClinDoc configuration and optimization
- Bridges interface setup and troubleshooting
- HL7 message parsing and routing
- Provider matching algorithms
- Orderset builds and clinical workflows
- Cardiac rehabilitation system integration (VersaCare, ScottCare)
Workflow Routing
- Orderset builds → Workflows/OrdersetBuild.md
- Interface configuration → Workflows/InterfaceConfig.md
- Provider matching issues → Workflows/ProviderMatching.md
- Client status updates → Workflows/StatusReport.md
- New client onboarding → Workflows/ClientOnboard.md
Client Quick Reference
- Memphis: [Key contacts, current projects, quirks]
- Raleigh: [Key contacts, current projects, quirks]
- Orlando: [Key contacts, current projects, quirks]
- Nova: [Key contacts, current projects, quirks]
- Baptist Rehab: Optimization project, ScottCare integration
Common Patterns
- Provider matching usually fails due to mismatched identifiers or missing mappings
- HL7 interfaces need careful attention to segment ordering and field mapping
- ClinDoc optimization typically involves SmartText tuning and workflow streamlining
Billable Hour Tracking
- Log all client work to Finance/BillableHours
- Target: 15-20 hours/week
- Track by client for invoicing
Tools Available
- Context: Context/Clients/*.md for client-specific info
Quality Standards
- Always document decisions in History/Decisions/Client/
- Update client context files after significant interactions
- Track commitments in State/Commitments.md
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?