[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2G987WCHZZEGPR511SW8A":3,"skill-same:01M7B2G987WCHZZEGPR511SW8A":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7B2G987WCHZZEGPR511SW8A","healthcare-emr-patterns",null,"EMR\u002FEHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fhealthcare-emr-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: healthcare-emr-patterns\ndescription: EMR\u002FEHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.\nmetadata:\n  version: \"1.0.0\"\n  origin: Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel\n---\n\n# Healthcare EMR Development Patterns\n\nPatterns for building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Prioritizes patient safety, clinical accuracy, and practitioner efficiency.\n\n## When to Use\n\n- Building patient encounter workflows (complaint, exam, diagnosis, prescription)\n- Implementing clinical note-taking (structured + free text + voice-to-text)\n- Designing prescription\u002Fmedication modules with drug interaction checking\n- Integrating Clinical Decision Support Systems (CDSS)\n- Building lab result displays with reference range highlighting\n- Implementing audit trails for clinical data\n- Designing healthcare-accessible UIs for clinical data entry\n\n## How It Works\n\n### Patient Safety First\n\nEvery design decision must be evaluated against: \"Could this harm a patient?\"\n\n- Drug interactions MUST alert, not silently pass\n- Abnormal lab values MUST be visually flagged\n- Critical vitals MUST trigger escalation workflows\n- No clinical data modification without audit trail\n\n### Single-Page Encounter Flow\n\nClinical encounters should flow vertically on a single page — no tab switching:\n\n```\nPatient Header (sticky — always visible)\n├── Demographics, allergies, active medications\n│\nEncounter Flow (vertical scroll)\n├── 1. Chief Complaint (structured templates + free text)\n├── 2. History of Present Illness\n├── 3. Physical Examination (system-wise)\n├── 4. Vitals (auto-trigger clinical scoring)\n├── 5. Diagnosis (ICD-10\u002FSNOMED search)\n├── 6. Medications (drug DB + interaction check)\n├── 7. Investigations (lab\u002Fradiology orders)\n├── 8. Plan & Follow-up\n└── 9. Sign \u002F Lock \u002F Print\n```\n\n### Smart Template System\n\n```typescript\ninterface ClinicalTemplate {\n  id: string;\n  name: string;             \u002F\u002F e.g., \"Chest Pain\"\n  chips: string[];          \u002F\u002F clickable symptom chips\n  requiredFields: string[]; \u002F\u002F mandatory data points\n  redFlags: string[];       \u002F\u002F triggers non-dismissable alert\n  icdSuggestions: string[]; \u002F\u002F pre-mapped diagnosis codes\n}\n```\n\nRed flags in any template must trigger a visible, non-dismissable alert — NOT a toast notification.\n\n### Medication Safety Pattern\n\n```\nUser selects drug\n  → Check current medications for interactions\n  → Check encounter medications for interactions\n  → Check patient allergies\n  → Validate dose against weight\u002Fage\u002Frenal function\n  → If CRITICAL interaction: BLOCK prescribing entirely\n  → Clinician must document override reason to proceed past a block\n  → If MAJOR interaction: display warning, require acknowledgment\n  → Log all alerts and override reasons in audit trail\n```\n\nCritical interactions **block prescribing by default**. The clinician must explicitly override with a documented reason stored in the audit trail. The system never silently allows a critical interaction.\n\n### Locked Encounter Pattern\n\nOnce a clinical encounter is signed:\n- No edits allowed — only an addendum (a separate linked record)\n- Both original and addendum appear in the patient timeline\n- Audit trail captures who signed, when, and any addendum records\n\n### UI Patterns for Clinical Data\n\n**Vitals Display:** Current values with normal range highlighting (green\u002Fyellow\u002Fred), trend arrows vs previous, clinical scoring auto-calculated (NEWS2, qSOFA), escalation guidance inline.\n\n**Lab Results Display:** Normal range highlighting, previous value comparison, critical values with non-dismissable alert, collection\u002Fanalysis timestamps, pending orders with expected turnaround.\n\n**Prescription PDF:** One-click generation with patient demographics, allergies, diagnosis, drug details (generic + brand, dose, route, frequency, duration), clinician signature block.\n\n### Accessibility for Healthcare\n\nHealthcare UIs have stricter requirements than typical web apps:\n- 4.5:1 minimum contrast (WCAG AA) — clinicians work in varied lighting\n- Large touch targets (44x44px minimum) — for gloved\u002Frushed interaction\n- Keyboard navigation — for power users entering data rapidly\n- No color-only indicators — always pair color with text\u002Ficon (colorblind clinicians)\n- Screen reader labels on all form fields\n- No auto-dismissing toasts for clinical alerts — clinician must actively acknowledge\n\n### Anti-Patterns\n\n- Storing clinical data in browser localStorage\n- Silent failures in drug interaction checking\n- Dismissable toasts for critical clinical alerts\n- Tab-based encounter UIs that fragment the clinical workflow\n- Allowing edits to signed\u002Flocked encounters\n- Displaying clinical data without audit trail\n- Using `any` type for clinical data structures\n\n## Examples\n\n### Example 1: Patient Encounter Flow\n\n```\nDoctor opens encounter for Patient #4521\n  → Sticky header shows: \"Rajesh M, 58M, Allergies: Penicillin, Active Meds: Metformin 500mg\"\n  → Chief Complaint: selects \"Chest Pain\" template\n    → Clicks chips: \"substernal\", \"radiating to left arm\", \"crushing\"\n    → Red flag \"crushing substernal chest pain\" triggers non-dismissable alert\n  → Examination: CVS system — \"S1 S2 normal, no murmur\"\n  → Vitals: HR 110, BP 90\u002F60, SpO2 94%\n    → NEWS2 auto-calculates: score 8, risk HIGH, escalation alert shown\n  → Diagnosis: searches \"ACS\" → selects ICD-10 I21.9\n  → Medications: selects Aspirin 300mg\n    → CDSS checks against Metformin: no interaction\n  → Signs encounter → locked, addendum-only from this point\n```\n\n### Example 2: Medication Safety Workflow\n\n```\nDoctor prescribes Warfarin for Patient #4521\n  → CDSS detects: Warfarin + Aspirin = CRITICAL interaction\n  → UI: red non-dismissable modal blocks prescribing\n  → Doctor clicks \"Override with reason\"\n  → Types: \"Benefits outweigh risks — monitored INR protocol\"\n  → Override reason + alert stored in audit trail\n  → Prescription proceeds with documented override\n```\n\n### Example 3: Locked Encounter + Addendum\n\n```\nEncounter #E-2024-0891 signed by Dr. Shah at 14:30\n  → All fields locked — no edit buttons visible\n  → \"Add Addendum\" button available\n  → Dr. Shah clicks addendum, adds: \"Lab results received — Troponin elevated\"\n  → New record E-2024-0891-A1 linked to original\n  → Timeline shows both: original encounter + addendum with timestamps\n```\n","# Healthcare EMR Development Patterns\n\nPatterns for building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Prioritizes patient safety, clinical accuracy, and practitioner efficiency.\n\n## When to Use\n\n- Building patient encounter workflows (complaint, exam, diagnosis, prescription)\n- Implementing clinical note-taking (structured + free text + voice-to-text)\n- Designing prescription\u002Fmedication modules with drug interaction checking\n- Integrating Clinical Decision Support Systems (CDSS)\n- Building lab result displays with reference range highlighting\n- Implementing audit trails for clinical data\n- Designing healthcare-accessible UIs for clinical data entry\n\n## How It Works\n\n### Patient Safety First\n\nEvery design decision must be evaluated against: \"Could this harm a patient?\"\n\n- Drug interactions MUST alert, not silently pass\n- Abnormal lab values MUST be visually flagged\n- Critical vitals MUST trigger escalation workflows\n- No clinical data modification without audit trail\n\n### Single-Page Encounter Flow\n\nClinical encounters should flow vertically on a single page — no tab switching:\n\n```\nPatient Header (sticky — always visible)\n├── Demographics, allergies, active medications\n│\nEncounter Flow (vertical scroll)\n├── 1. Chief Complaint (structured templates + free text)\n├── 2. History of Present Illness\n├── 3. Physical Examination (system-wise)\n├── 4. Vitals (auto-trigger clinical scoring)\n├── 5. Diagnosis (ICD-10\u002FSNOMED search)\n├── 6. Medications (drug DB + interaction check)\n├── 7. Investigations (lab\u002Fradiology orders)\n├── 8. Plan & Follow-up\n└── 9. Sign \u002F Lock \u002F Print\n```\n\n### Smart Template System\n\n```typescript\ninterface ClinicalTemplate {\n  id: string;\n  name: string;             \u002F\u002F e.g., \"Chest Pain\"\n  chips: string[];          \u002F\u002F clickable symptom chips\n  requiredFields: string[]; \u002F\u002F mandatory data points\n  redFlags: string[];       \u002F\u002F triggers non-dismissable alert\n  icdSuggestions: string[]; \u002F\u002F pre-mapped diagnosis codes\n}\n```\n\nRed flags in any template must trigger a visible, non-dismissable alert — NOT a toast notification.\n\n### Medication Safety Pattern\n\n```\nUser selects drug\n  → Check current medications for interactions\n  → Check encounter medications for interactions\n  → Check patient allergies\n  → Validate dose against weight\u002Fage\u002Frenal function\n  → If CRITICAL interaction: BLOCK prescribing entirely\n  → Clinician must document override reason to proceed past a block\n  → If MAJOR interaction: display warning, require acknowledgment\n  → Log all alerts and override reasons in audit trail\n```\n\nCritical interactions **block prescribing by default**. The clinician must explicitly override with a documented reason stored in the audit trail. The system never silently allows a critical interaction.\n\n### Locked Encounter Pattern\n\nOnce a clinical encounter is signed:\n- No edits allowed — only an addendum (a separate linked record)\n- Both original and addendum appear in the patient timeline\n- Audit trail captures who signed, when, and any addendum records\n\n### UI Patterns for Clinical Data\n\n**Vitals Display:** Current values with normal range highlighting (green\u002Fyellow\u002Fred), trend arrows vs previous, clinical scoring auto-calculated (NEWS2, qSOFA), escalation guidance inline.\n\n**Lab Results Display:** Normal range highlighting, previous value comparison, critical values with non-dismissable alert, collection\u002Fanalysis timestamps, pending orders with expected turnaround.\n\n**Prescription PDF:** One-click generation with patient demographics, allergies, diagnosis, drug details (generic + brand, dose, route, frequency, duration), clinician signature block.\n\n### Accessibility for Healthcare\n\nHealthcare UIs have stricter requirements than typical web apps:\n- 4.5:1 minimum contrast (WCAG AA) — clinicians work in varied lighting\n- Large touch targets (44x44px minimum) — for gloved\u002Frushed interaction\n- Keyboard navigation — for power users entering data rapidly\n- No color-only indicators — always pair color with text\u002Ficon (colorblind clinicians)\n- Screen reader labels on all form fields\n- No auto-dismissing toasts for clinical alerts — clinician must actively acknowledge\n\n### Anti-Patterns\n\n- Storing clinical data in browser localStorage\n- Silent failures in drug interaction checking\n- Dismissable toasts for critical clinical alerts\n- Tab-based encounter UIs that fragment the clinical workflow\n- Allowing edits to signed\u002Flocked encounters\n- Displaying clinical data without audit trail\n- Using `any` type for clinical data structures\n\n## Examples\n\n### Example 1: Patient Encounter Flow\n\n```\nDoctor opens encounter for Patient #4521\n  → Sticky header shows: \"Rajesh M, 58M, Allergies: Penicillin, Active Meds: Metformin 500mg\"\n  → Chief Complaint: selects \"Chest Pain\" template\n    → Clicks chips: \"substernal\", \"radiating to left arm\", \"crushing\"\n    → Red flag \"crushing substernal chest pain\" triggers non-dismissable alert\n  → Examination: CVS system — \"S1 S2 normal, no murmur\"\n  → Vitals: HR 110, BP 90\u002F60, SpO2 94%\n    → NEWS2 auto-calculates: score 8, risk HIGH, escalation alert shown\n  → Diagnosis: searches \"ACS\" → selects ICD-10 I21.9\n  → Medications: selects Aspirin 300mg\n    → CDSS checks against Metformin: no interaction\n  → Signs encounter → locked, addendum-only from this point\n```\n\n### Example 2: Medication Safety Workflow\n\n```\nDoctor prescribes Warfarin for Patient #4521\n  → CDSS detects: Warfarin + Aspirin = CRITICAL interaction\n  → UI: red non-dismissable modal blocks prescribing\n  → Doctor clicks \"Override with reason\"\n  → Types: \"Benefits outweigh risks — monitored INR protocol\"\n  → Override reason + alert stored in audit trail\n  → Prescription proceeds with documented override\n```\n\n### Example 3: Locked Encounter + Addendum\n\n```\nEncounter #E-2024-0891 signed by Dr. Shah at 14:30\n  → All fields locked — no edit buttons visible\n  → \"Add Addendum\" button available\n  → Dr. Shah clicks addendum, adds: \"Lab results received — Troponin elevated\"\n  → New record E-2024-0891-A1 linked to original\n  → Timeline shows both: original encounter + addendum with timestamps\n```\n",{"name":5,"metadata":24,"description":7},{"origin":25,"version":26},"Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel","1.0.0","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fhealthcare-emr-patterns",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill healthcare-emr-patterns",{"tool":43,"command":44},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill healthcare-emr-patterns",{"tool":46,"command":47},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill healthcare-emr-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fhealthcare-emr-patterns\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]