[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C1AY42JB2B449HVN0QSWW":3,"skill-same:01M73C1AY42JB2B449HVN0QSWW":50},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M73C1AY42JB2B449HVN0QSWW","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.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhealthcare-emr-patterns\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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.\norigin: Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel\nversion: \"1.0.0\"\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,"origin":24,"version":25,"description":7},"Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel","1.0.0","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fhealthcare-emr-patterns",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill healthcare-emr-patterns",{"tool":42,"command":43},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill healthcare-emr-patterns",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill healthcare-emr-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhealthcare-emr-patterns\u002FSKILL.md",true,[],[51,59,66,74,82,90],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\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},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\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":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]