clinical-reports
# Clinical Reports
What this skill does
# Clinical Reports Professional clinical documentation covering case reports, diagnostic reports, trial reports, and patient documentation. ## Triggers - User needs to write a case report - User is documenting clinical findings - User wants to format trial results - User needs diagnostic report structure - User is preparing clinical documentation ## Report Types ### 1. Case Reports (CARE Guidelines) **Required Sections**: | Section | Content | |---------|---------| | Title | Diagnosis and intervention focus | | Abstract | Structured: background, case, conclusion | | Introduction | Why this case matters | | Patient Information | Demographics, history (de-identified) | | Clinical Findings | Presentation, exam, initial assessment | | Timeline | Chronological events | | Diagnostic Assessment | Workup, reasoning, differentials | | Therapeutic Intervention | Treatment details | | Follow-up and Outcomes | Results, adherence, adverse events | | Discussion | Context, rationale, limitations | **HIPAA De-identification** (Remove 18 identifiers): - Names, geographic data, dates (except year) - Phone, fax, email, SSN, MRN - Health plan numbers, account numbers - License/vehicle numbers, device IDs - URLs, IP addresses, biometrics, photos ### 2. Diagnostic Reports #### Cardiology-Specific **Echocardiography Report Structure**: - Patient demographics - Indication - Technical quality - LV size and function (EF method specified) - RV assessment - Valvular assessment (stenosis/regurgitation grading) - Other findings - Comparison with prior - Impression and recommendations **Cardiac Catheterization Report**: - Procedure indication - Access and technique - Hemodynamics (pressures, gradients) - Coronary anatomy (dominance, lesions) - LV function - Intervention performed (if any) - Complications - Recommendations **Electrophysiology Report**: - Indication - Baseline intervals - Findings (inducibility, mechanism) - Ablation details (if performed) - Outcomes and endpoints - Recommendations ### 3. Clinical Trial Reports #### Serious Adverse Event (SAE) Reports **Timeline Requirements**: - Fatal/life-threatening: 7 days - Other serious: 15 days **Required Elements**: - Event description and onset date - Seriousness criteria met - Causality assessment - Action taken with study drug - Outcome - Relevant medical history - Concomitant medications #### Clinical Study Report (ICH-E3 Structure) 1. Title page 2. Synopsis 3. Table of contents 4. List of abbreviations 5. Ethics 6. Investigators and study sites 7. Introduction 8. Study objectives 9. Investigational plan 10. Study patients 11. Efficacy evaluation 12. Safety evaluation 13. Discussion and conclusions 14. Tables, figures, graphs 15. Reference list 16. Appendices ### 4. Patient Documentation #### SOAP Note Format ``` S (Subjective): Patient's reported symptoms, history O (Objective): Vital signs, exam findings, test results A (Assessment): Diagnosis, clinical reasoning P (Plan): Treatment, follow-up, patient education ``` #### History & Physical Structure - Chief complaint - History of present illness - Past medical/surgical history - Medications and allergies - Family history - Social history - Review of systems - Physical examination - Assessment and plan #### Discharge Summary Elements - Admission diagnosis - Hospital course - Procedures performed - Discharge diagnosis - Discharge medications (with changes noted) - Follow-up appointments - Patient education provided - Contingency instructions ## Compliance Requirements ### Regulatory Standards | Regulation | Applies To | Key Requirements | |------------|------------|------------------| | HIPAA | All US healthcare | Privacy, minimum necessary | | 21 CFR Part 11 | Electronic records | Audit trails, signatures | | ICH-GCP | Clinical trials | Protocol adherence, consent | | FDA 21 CFR 312 | INDs | Safety reporting | ### Standardized Terminology - **SNOMED CT**: Clinical terms - **LOINC**: Laboratory tests - **ICD-10-CM**: Diagnoses - **CPT**: Procedures - **RxNorm**: Medications ### Prohibited Abbreviations (Joint Commission) | Don't Use | Problem | Use Instead | |-----------|---------|-------------| | U | Mistaken for 0 | "unit" | | IU | Mistaken for IV | "international unit" | | QD, QOD | Confused | "daily," "every other day" | | Trailing zero (1.0) | Decimal missed | 1 mg | | No leading zero (.5) | Decimal missed | 0.5 mg | | MS, MSO4, MgSO4 | Confused | "morphine" or "magnesium" | ## Quality Standards ### Documentation Must Be - **Complete**: All relevant information included - **Accurate**: Facts verified, no assumptions - **Timely**: Documented promptly - **Clear**: Understandable to readers - **Compliant**: Meets regulatory requirements ### Common Deficiencies to Avoid - Missing dates/times - Illegible entries (if handwritten) - Use of prohibited abbreviations - Incomplete medication reconciliation - Missing informed consent documentation - Inadequate follow-up instructions ## Cardiology Case Report Considerations ### What Makes a Publishable Case - Novel presentation of known disease - Unexpected treatment response - Diagnostic challenge with learning points - Rare condition with management insights - Adverse event with safety implications ### Key Cardiovascular Data to Include - ECG findings (with images if relevant) - Imaging results (echo, angiography, CT/MRI) - Biomarkers (troponin, BNP trends) - Hemodynamic data - Procedural details and outcomes - Long-term follow-up
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.