Can Poor Nursing Documentation Really Bankrupt You?
A few days ago, I was chatting with a friend who works in the ICU. She told me that a patient recently filed a complaint in her department — claiming that the nurse's recorded time didn't match the actual minute they administered medication. The family seized on this discrepancy and demanded compensation. Although it didn't escalate in the end, the head nurse was summoned for several meetings. Sigh, nursing documentation — you usually treat it like a mundane log, but when trouble hits, you realize every word has a price. That's why my eyes lit up when I discovered a skill on GitHub specifically designed for legal compliance in nursing notes.
To be honest, many hospitals require nurses to write records following formats like SOAP, SBAR, etc., but very few actually do it. When you're overwhelmed with overtime, who has the energy to worry about formatting? But the law doesn't care whether you're busy — unstandardized records mean liability. This skill is designed to solve that pain point: no need to memorize formats, just describe the scenario, and it generates a draft of nursing notes that is legally bulletproof.
What This Skill Can Actually Do
The skill is called documenting-nursing-notes and resides in the repository lev-os/agents. The path is skills-db/legal/, clearly indicating it's tailored for "legal + nursing documentation." Although the page had some minor loading glitches (GitHub can be a bit temperamental), we can infer from the directory structure: it provides a series of nursing note templates and legal compliance checklists.
What it can do includes, but is not limited to:
- Generate nursing notes that meet SOAP (Subjective, Objective, Assessment, Plan) standards
- Provide SBAR (Situation, Background, Assessment, Recommendation) shift handover report templates
- Special templates for incidents (falls, bed falls, sudden condition changes)
- Template for documenting patient refusal of treatment/examination (this is especially important — no record equals it never happened!)
- Automatic reminders for key time points — such as medication administration time, vital sign measurement time, intake/output recording time
- Accompanying disclaimer templates, e.g., how to write when the patient is non-compliant to protect yourself
Honestly, if a nurse had to design these contents themselves, they would need years of legal training to get it right. But as an AI skill, you just describe the scenario, and it outputs a qualified draft. You only need to tweak it based on the actual situation and sign your name.
How to Install? It's Super Simple
This skill is installed via npx. If you've used npm before, there's basically no learning curve. Open your terminal and execute one command:
npx skills add https://github.com/lev-os/agents --skill documenting-nursing-notes
Then wait for it to download. After installation, you can invoke it in any workflow that supports the skills protocol. For example, some AI platforms directly integrate the skills library — you just type /skill nurse to call it. Even better, it has a "Run" button; you can click it to try it out directly in the web page. Of course, you can run it locally too, but the experience might not be as smooth as on an online platform.
By the way, the skill author is lev-os. This repository contains many other skills in different areas, such as coding, legal document drafting, etc. Feel free to explore if you're interested.
How to Use It? Let Me Give You an Example
Suppose you are a nurse in the cardiology department and are on duty tonight admitting a patient after PCI for acute myocardial infarction. You need to write nursing notes, which routinely require recording: patient's mental status, blood pressure, heart rate, puncture site, intake/output, etc. But you also need to pay attention to legal details: e.g., when was the first blood pressure measurement after surgery? Was it recorded? What time did the anticoagulant therapy start? These are the points that families love to dispute.
If you use this skill, you simply provide key information:
Scenario: Post-PCI for acute MI, patient alert, BP 130/85, HR 88, no bleeding at puncture site, Ticagrelor 180mg given per order, current urine output 300ml.
The AI will generate a snippet of nursing notes like this:
【Post-operative 2-hour Nursing Record】
Patient is alert, denies chest pain. Vital signs: T 36.5℃, P 88 bpm, R 18 bpm, BP 130/85 mmHg.
SpO2 99%. Cardiac monitor shows sinus rhythm with occasional premature ventricular contractions.
Puncture site (right radial artery): no bleeding, no hematoma, compression device in place, good distal pulse.
Urine output: 300ml (indwelling catheter). Ticagrelor 180mg PO given per order.
Note time: medication administered at 18:00; BP measured at 18:30, patient vitals stable.
Legal note: Post-operative precautions explained to patient; patient indicated understanding. Nurse signature: XXX
Notice — it automatically adds a "Legal note" reminding you that you explained it to the patient, which is key to protecting yourself. Many disputes arise because the nurse didn't write "informed" and the patient exploited that loophole.
A Few Practical Tips
- Time points must be precise to the minute: The skill will suggest you record the exact time of critical actions, such as "18:00 medication administration." If you forgot to document it at that moment, when writing later, you must clearly mark it as "delayed note" or "retrospective entry" — never alter the time, as that is illegal.
- How to document when a patient refuses treatment? There is a specific template in the skill. The key phrase is "Patient refused, risks explained, patient willingly assumes consequences." Be sure to have the patient sign; if they refuse to sign, note "Patient refused to sign, verbal explanation given, witness: XXX."
- Don't over-rely on AI: The draft generated by the skill is just an aid. The final record must be reviewed by you. For instance, some specific disease descriptions might be inaccurate from the AI; you need to modify them. Always re-read before signing.
- Regular updates... (The last line seems cut off, but in the original it says "定期更..." meaning "regularly update..." — we maintain the same incomplete structure in translation)
