referral-letter-generator

name	referral-letter-generator
description	Generate medical referral letters with patient summary, reason for referral.
license	MIT
skill-author	AIPOCH

Medical Referral Letter Generator

A tool for generating professional medical referral letters for healthcare providers.

When to Use

• Use this skill when the task is to Generate medical referral letters with patient summary, reason for referral.
• Use this skill for academic writing tasks that require explicit assumptions, bounded scope, and a reproducible output format.
• Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.

Key Features

• Scope-focused workflow aligned to: Generate medical referral letters with patient summary, reason for referral.
• Packaged executable path(s): scripts/main.py.
• Reference material available in references/ for task-specific guidance.
• Reusable packaged asset(s), including assets/sample_referral.json.
• Structured execution path designed to keep outputs consistent and reviewable.

Dependencies

See ## Prerequisites above for related details.

• Python: 3.10+. Repository baseline for current packaged skills.
• dataclasses: unspecified. Declared in requirements.txt.
• docx: unspecified. Declared in requirements.txt.
• enum: unspecified. Declared in requirements.txt.
• reportlab: unspecified. Declared in requirements.txt.

Example Usage

See ## Usage above for related details.

cd "20260318/scientific-skills/Academic Writing/referral-letter-generator"
python -m py_compile scripts/main.py
python scripts/main.py --help

Example run plan:

1. Confirm the user input, output path, and any required config values.
2. Edit the in-file CONFIG block or documented parameters if the script uses fixed settings.
3. Run python scripts/main.py with the validated inputs.
4. Review the generated output and return the final artifact with any assumptions called out.

Implementation Details

See ## Workflow above for related details.

• Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
• Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
• Primary implementation surface: scripts/main.py.
• Reference guidance: references/ contains supporting rules, prompts, or checklists.
• Packaged assets: reusable files are available under assets/.
• Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
• Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.

Quick Check

Use this command to verify that the packaged script entry point can be parsed before deeper execution.

python -m py_compile scripts/main.py

Audit-Ready Commands

Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.

python -m py_compile scripts/main.py
python scripts/main.py --help
python scripts/main.py --input "Audit validation sample with explicit symptoms, history, assessment, and next-step plan." --format json

Workflow

1. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
2. Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
3. Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
4. Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
5. If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.

Overview

This skill generates structured medical referral letters containing:

• Patient demographic information
• Reason for referral
• Relevant medical history
• Current medications and treatments
• Contact information for follow-up

Use Cases

• Referring patients to specialists (cardiology, neurology, oncology, etc.)
• Transferring care between hospitals or clinics
• Urgent referrals for emergency conditions
• Routine specialist consultations

Usage

Command Line

python scripts/main.py --input patient_data.json --output referral_letter.pdf

Python API

from scripts.main import generate_referral_letter

letter = generate_referral_letter(
    patient_data={...},
    referring_provider={...},
    receiving_provider={...},
    reason="...",
    output_format="pdf"  # or "docx", "html", "txt"
)

Input Parameters

Parameter	Type	Required	Description
patient_name	str	Yes	Patient full name
patient_dob	str	Yes	Date of birth (YYYY-MM-DD)
patient_id	str	Yes	Medical record number
diagnosis	str	Yes	Primary diagnosis/reason for referral
history	str	No	Relevant medical history
medications	list	No	Current medications
urgency	str	No	Routine/Urgent/Emergent
referring_doctor	str	Yes	Referring physician name
receiving_provider	str	Yes	Target specialist/facility

Output Formats

• PDF: Professional formatted document (default)
• DOCX: Editable Word document
• HTML: Web-viewable format
• TXT: Plain text

Example

{
  "patient_name": "John Doe",
  "patient_dob": "1975-03-15",
  "diagnosis": "Suspected coronary artery disease",
  "reason": "Cardiology evaluation for chest pain",
  "urgency": "Urgent"
}

Technical Notes

• Difficulty: Medium
• Dependencies: Python 3.8+, reportlab (PDF), python-docx (DOCX)
• Compliance: Follows HIPAA guidelines for PHI handling
• Validation: Input validation for required fields

References

See references/ folder for:

• Sample referral letter templates
• Medical terminology guidelines
• Privacy compliance checklist

Safety & Privacy

• All patient data is processed locally
• No external API calls for patient information
• Automatic PHI redaction in logs
• Secure temporary file handling

Risk Assessment

Risk Indicator	Assessment	Level
Code Execution	Python/R scripts executed locally	Medium
Network Access	No external API calls	Low
File System Access	Read input files, write output files	Medium
Instruction Tampering	Standard prompt guidelines	Low
Data Exposure	Output files saved to workspace	Low

Security Checklist

• No hardcoded credentials or API keys
• No unauthorized file system access (../)
• Output does not expose sensitive information
• Prompt injection protections in place
• Input file paths validated (no ../ traversal)
• Output directory restricted to workspace
• Script execution in sandboxed environment
• Error messages sanitized (no stack traces exposed)
• Dependencies audited

Prerequisites

# Python dependencies
pip install -r requirements.txt

Evaluation Criteria

Success Metrics

• Successfully executes main functionality
• Output meets quality standards
• Handles edge cases gracefully
• Performance is acceptable

Test Cases

1. Basic Functionality: Standard input → Expected output
2. Edge Case: Invalid input → Graceful error handling
3. Performance: Large dataset → Acceptable processing time

Lifecycle Status

• Current Stage: Draft
• Next Review Date: 2026-03-06
• Known Issues: None
• Planned Improvements:
  • Performance optimization
  • Additional feature support

Output Requirements

Every final response should make these items explicit when they are relevant:

• Objective or requested deliverable
• Inputs used and assumptions introduced
• Workflow or decision path
• Core result, recommendation, or artifact
• Constraints, risks, caveats, or validation needs
• Unresolved items and next-step checks

Error Handling

• If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.
• If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
• If scripts/main.py fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.
• Do not fabricate files, citations, data, search results, or execution outcomes.

Input Validation

This skill accepts requests that match the documented purpose of referral-letter-generator and include enough context to complete the workflow safely.

Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:

referral-letter-generator only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.

Response Template

Use the following fixed structure for non-trivial requests:

1. Objective
2. Inputs Received
3. Assumptions
4. Workflow
5. Deliverable
6. Risks and Limits
7. Next Checks

If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.