Generate Emergency Medical Information Cards
Emergency Medical Card Generator turns a user's health records into a prioritized, printable emergency card - allergies, meds, implants.
Why it matters
Create comprehensive, prioritized medical information cards for emergency situations. Supports multiple output formats including HTML, JSON, and text for easy access and sharing.
Outcomes
What it gets done
Extract critical health data including allergies, medications, and conditions.
Prioritize medical information based on emergency severity.
Generate printable HTML, JSON, or text-based medical information cards.
Output cards in various formats optimized for different use cases (e.g., A4, wallet-sized).
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-emergency-card | bash Overview
Emergency Medical Information Card Generator
Generates a prioritized emergency medical information card - severe allergies, active medications, chronic conditions, implants, and emergency contacts - from a user's personal health records, in HTML, JSON, text, or PDF. Use to prepare emergency medical information for travel, first aid, or a medical visit - not as a diagnostic tool or substitute for professional medical advice.
What it does
Emergency Medical Information Card Generator produces a quick-access medical information summary for emergencies or medical visits, built from a user's existing personal health records. It extracts the most critical information: severe allergies (prioritizing grade 3-4 reactions including anaphylaxis), current active medications with name/dosage/frequency, urgent medical conditions, implants such as pacemakers or stents (relevant to imaging and treatment decisions), and emergency contacts.
Information is ranked by medical urgency into three tiers: P0 critical (anaphylaxis, severe drug allergy, life-threatening conditions), P1 important (current medications, chronic disease, implants), and P2 general (blood type, age, weight, recent exams). Output supports four formats: a printable HTML card (recommended) using Tailwind CSS and Lucide icons via CDN with responsive/print-optimized layout, multiple size variants (A4, wallet card, large-print), and automatic card-type detection (standard, child, elderly, severe-allergy); structured JSON for system integration; a plain-text card formatted for printing and carrying; and PDF for long-term, professional-quality printing. The HTML generator is invoked as:
python scripts/generate_emergency_card.py standard wallet
selecting card type (standard/child/elderly/severe) and print size (a4/wallet/large), writing to emergency-cards/emergency-card-{variant}-{YYYY-MM-DD}.html. Generated cards are designed for offline use - saved to phone photos/files, printed and carried in a wallet or bag, or optionally backed up to the cloud.
The generation workflow reads from a defined set of local data sources - data/profile.json (basic info, blood type, emergency contacts), data/allergies.json (allergy history and severity grading), data/medications/medications.json (active medication plan and dosage), chronic-disease trackers (hypertension-tracker.json, diabetes-tracker.json, copd-tracker.json with diagnosis dates, classification/GOLD grade, and control status), data/radiation-records.json, and glob-scanned surgery and discharge-summary records for implants and diagnoses - then filters, prioritizes, and assembles the card, always including a disclaimer that the card is for reference only and does not replace professional medical diagnosis.
The skill enforces explicit safety principles: it never adds medication recommendations (only lists currently active medications as recorded), never provides diagnostic conclusions (only lists already-known diagnoses), never gives treatment advice, and always includes the reference-only disclaimer. It only extracts information that is already recorded - never inferred or guessed - and recommends periodic updates. Privacy protections include optional hiding of sensitive fields, partial masking of phone numbers (e.g. 138****1234), and keeping all data local. Missing data degrades gracefully: missing allergy data outputs "no allergy history recorded", missing medication data outputs "no current medications recorded", missing implant data outputs "no implants", a failed profile.json read falls back to defaults, and a single failed source (e.g. allergies) is skipped without interrupting generation of the rest of the card. A failed QR code generation degrades to text-format output instead.
When to use - and when NOT to
Use this skill when a user asks to generate an emergency medical information card, prepare medical information for travel, organize allergy information into a card, prepare an emergency first-aid information summary, or prepare materials for a medical visit. Do not treat the output as a substitute for environment-specific validation, testing, or expert review - the card is explicitly for reference only, not a diagnostic or treatment tool - and stop to ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Who it's for
Individuals maintaining a personal health record system who want a fast, prioritized, offline-usable medical summary for emergencies, travel, or medical visits, especially those with severe allergies, chronic conditions, or implants that first responders need to know about immediately.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.