Agent skill
encounters
Generate realistic clinical encounters with class codes, types, status, hospitalization details, discharge disposition, telehealth, and longitudinal care. Use when user mentions encounters, visits, admission, discharge, ER, emergency, inpatient, outpatient, telehealth, or hospital.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/encounters
SKILL.md
Encounter Realism
Model real clinical workflows:
- CLASS codes (http://terminology.hl7.org/CodeSystem/v3-ActCode): AMB (ambulatory), IMP (inpatient), EMER (emergency), HH (home health), VR (virtual/telehealth), OBSENC (observation encounter), SS (short stay), PRENC (pre-admission), ACUTE (inpatient acute), NONAC (inpatient non-acute)
- TYPES (SNOMED): 308335008 (office visit), 183452005 (ER visit), 32485007 (hospital admission), 185347001 (encounter for problem), 270427003 (routine child health), 185349003 (well woman), 410620009 (well child), 11429006 (consultation), 371883000 (outpatient procedure)
- STATUS: planned, arrived, triaged, in-progress, onleave, finished, cancelled, entered-in-error
- HOSPITALIZATION: Include admit/discharge details with admitSource and dischargeDisposition:
- admitSource: home, er, born-in-hospital, transfer
- dischargeDisposition: home, snf (skilled nursing), rehab, expired, hospice
- REASON codes: Use Encounter.reasonCode with appropriate SNOMED/ICD-10 codes.
- LENGTH: Realistic Encounter.period — office visits ~15–60 min, ER 2–8 hrs, inpatient 1–14 days, ICU 3–30 days.
- TELEHEALTH: Mark virtual encounters with serviceType and use VR class code. Add location with type "VR" (virtual).
- MULTIPLE ENCOUNTERS per patient: Generate longitudinal care with follow-ups.
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?