Skip to content
Skills Library
Medicine & health · Writing

epic-note

/epic-note

Drafts a concise patient-portal message the user can copy-paste to a clinician via Epic MyChart, Oracle Health HealtheLife, or similar. Personal data is referenced from an external profile file, never embedded. USE FOR: symptom reports, refill requests, lab/result follow-ups, visit follow-ups, asking a single clear question. DO NOT USE FOR: clinical notes, SOAP/discharge documentation, insurance or billing letters, or answering the patient's medical question.

Repository
tula ↗
Licence
Apache-2.0
Last repository change
17.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Drafts a concise patient-portal message the user can copy-paste to a clinician via Epic MyChart, Oracle Health HealtheLife, or similar. Personal data is referenced from an external profile file, never embedded. USE FOR: symptom reports, refill requests, lab/result follow-ups, visit follow-ups, asking a single clear question. DO NOT USE FOR: clinical notes, SOAP/discharge documentation, insurance or billing letters, or answering the patient's medical question.

Original author description

Drafts a concise patient-portal message the user can copy-paste to a clinician via Epic MyChart, Oracle Health HealtheLife, or similar. Personal data is referenced from an external profile file, never embedded. USE FOR: symptom reports, refill requests, lab/result follow-ups, visit follow-ups, asking a single clear question. DO NOT USE FOR: clinical notes, SOAP/discharge documentation, insurance or billing letters, or answering the patient's medical question.

How it works

  1. When to Use
  2. When NOT to Use
  3. Setup
  4. Workflow
  5. Examples
  6. Privacy
  7. Troubleshooting
Original SKILL.md headings · 80 lines, 399 words
SKILL.md preview
---
name: epic-note
description: "Drafts a concise patient-portal message the user can copy-paste to a clinician via Epic MyChart, Oracle Health HealtheLife, or similar. Personal data is referenced from an external profile file, never embedded. USE FOR: symptom reports, refill requests, lab/result follow-ups, visit follow-ups, asking a single clear question. DO NOT USE FOR: clinical notes, SOAP/discharge documentation, insurance or billing letters, or answering the patient's medical question."
metadata:
  {
    "openclaw":
      {
        "emoji": "✉️"
      }
  }
---

# epic-note

## When to Use

✅ Use when:

- The user asks for help drafting a message to their PCP or specialist
- Reporting a new or worsening symptom
- Asking about a recent test or lab result
- Requesting a medication refill
- Following up after a visit, procedure, or referral

## When NOT to Use

❌ Don't use when:

- Symptoms suggest an emergency - return the 911 redirect from
  [`references/triage-rules.md`](references/triage-rules.md), don't draft
- Generating a clinician-facing note (SOAP, discharge, dictation)
- Drafting non-clinical letters (insurance, billing)
- The user is asking a medical question for advice - that's answered directly,
  not in a portal message

## Setup

**Profile.** Resolve from the precedence in
[`references/profile-schema.md`](references/profile-schema.md#where-the-profile-lives)
(skill config -> env var -> `~/.openclaw/workspace/memory/profile.yaml`).
Use `care_team.pcp.display_name` as the default greeting recipient when
the user doesn't name a clinician. The skill never contains the profile.

## Workflow

1. **Triage first.** Scan input for red-flag symptoms. If present, do NOT
   draft - return the 911 redirect text from
   [`references/triage-rules.md`](references/triage-rules.md).

2. **Identify the single ask.** If multiple unrelated topics exist, propose
   separate messages and ask the user which to send first.

3. **Draft** using the canonical format in
   [`references/portal-message-format.md`](references/portal-message-format.md):
   `Subject:` line with urgency, greeting, one-sentence ask, 2-4 sentences
   of context, optional bullet data, sign-off.

4. **Word budget.** Aim for ≤150 words; hard cap 220. Front-load the ask.
   Plain language. No self-diagnosis, no filler praise, no PHI of others.

5. **Output is copy-paste ready.** No explanations or meta-commentary
   wrapped around the message - just the message itself.

## Examples

See [`references/examples.md`](references/examples.md) for worked
input/output pairs (medication side effect, lab follow-up, refill request,
multi-topic split).

## Privacy

Portal messages travel through health-system networks under HIPAA. Tula
generates drafts locally - no PHI leaves the workspace.

- Don't include PHI of family members or third parties.
- The draft stays in the conversation. Never auto-send.
- Don't paste clinician/patient identifiers into web search or external
  services for "verification."

## Troubleshooting

- **No clinician name given** -> use `care_team.pcp.display_name` from the
  profile, or `Hello [Care Team],` if none resolves.
- **Vague input** -> ask one clarifying question (onset, severity, which
  clinician), then draft.
- **User asks for medical advice** -> decline politely; this skill drafts
  messages *to* clinicians, not answers from them.
- **Multi-topic input** -> propose separate messages, don't bundle.
- **Emergency-flavored prompt** -> return triage redirect; never wrap a
  drafted message around it.
Files in this package (6)
  • README.md 4 KB
  • SKILL.md 3 KB
  • references/examples.md 2 KB
  • references/portal-message-format.md 1 KB
  • references/profile-schema.md 1 KB
  • references/triage-rules.md 2 KB

Versions

The database has no other skills named epic-note.

Database snapshot: 13.11.2026 · package version 635b29095e7c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100health-records
    Pulls the user's medical records from patient portals (Epic MyChart, Oracle/Cerner) via end-to-end-encrypted SMART on FHIR, into per-provider JSON files Tula can reason over. Personal data is referenced from an external profile file, never embedded. USE FOR: connecting or…
  • 100med-pdf
    Reads medical PDFs (labs, radiology, MyChart/Epic exports, discharge summaries, pathology) and turns them into structured JSON Tula can reason over. Personal data is referenced from an external profile file, never embedded. USE FOR: the user sharing a health-related PDF, image,…
  • 100patient-results-letter
    Generate patient-friendly radiology result communications in plain language. Also use when the user needs to explain findings to patients without medical jargon, write result letters, or create follow-up reminders.
  • 100soap-notes
    Structures clinical encounter information into a SOAP note (Subjective, Objective, Assessment, Plan) for a clinician to review and sign. Use when a health professional wants help organizing visit notes, dictation or a transcript into SOAP format.
  • 90alterlab-clinical-reports
    Writes comprehensive clinical reports — case reports (CARE guidelines), diagnostic reports (radiology, pathology, lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP notes, H&P, discharge summaries) — with templates, regulatory compliance (HIPAA,…
  • 100patient-demographics-summary
    Retrieves and formats a complete patient demographic summary from FHIR Patient, RelatedPerson, and Coverage resources. Use when user asks to "pull demographics", "get patient info", "show patient details", "who is this patient", "patient summary", "emergency contacts",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.