healthcare-emr-patterns
OfficialEMR/EHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry.
What this skill does
When applied, it prepends a system prompt before your request is sent — no extra calls and no change to how you are billed beyond the added tokens.
--- name: healthcare-emr-patterns description: 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. origin: Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel version: "1.0.0" --- # Healthcare EMR Development Patterns Patterns for building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Prioritizes patient safety, clinical accuracy, and practitioner efficiency. ## When to Use - Building patient encounter workflows (complaint, exam, diagnosis, prescription) - Implementing clinical note-taking (structured + free text + voice-to-text) - Designing prescription/medication modules with drug interaction checking - Integrating Clinical Decision Support Systems (CDSS) - Building lab result displays with reference range highlighting - Implementing audit trails for clinical data - Designing healthcare-accessible UIs for clinical data entry ## How It Works ### Patient Safety First Every design decision must be evaluated against: "Could this harm a patient?" - Drug interactions MUST alert, not silently pass - Abnormal lab values MUST be visually flagged - Critical vitals MUST trigger escalation workflows - No clinical data modification without audit trail ### Single-Page Encounter Flow Clinical encounters should flow vertically on a single page — no tab switching: ``` Patient Header (sticky — always visible) ├── Demographics, allergies, active medications │ Encounter Flow (vertical scroll) ├── 1. Chief Complaint (structured templates + free text) ├── 2. History of Present Illness ├── 3. Physical Examination (system-wise) ├── 4. Vitals (auto-trigger clinical scoring) ├── 5. Diagnosis (ICD-10/SNOMED search) ├── 6. Medications (drug DB + interaction check) ├── 7. Investigations (lab/radiology orders) ├── 8. Plan & Follow-up └── 9. Sign / Lock / Print ``` ### Smart Templa
Use this skill
Add a "skill" field with the skill’s ID to your chat completion request. It is applied server-side before your prompt is sent — no extra calls.
{
"model": "gpt-4o-mini",
"skill": "imp-06ba2767-ff1f-4e9a-8714-d5189292f124",
"messages": [{ "role": "user", "content": "…" }]
}Install the skill, enable it in your dashboard and (optionally) limit it to specific models. It then applies automatically to every matching request — with no "skill" field to send each time.
Set it up in your dashboardMore skills
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
Run, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.
Search and analyze your own session logs (older/parent conversations) using jq.
Start voice calls via the OpenClaw voice-call plugin.
Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.
Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.