Provider Notification Nursing Note Example
A provider notification note documents that a nurse communicated information to a provider, what was communicated, and the response.
Educational use & privacy
Educational documentation practice only. Use fictional or instructor-provided information. Do not enter real patient information or protected health information (PHI). Documentation requirements vary by organization, setting, role, policy, and applicable law.
Nursing Notes Privacy & SafetyContent status: Draft — not yet professionally reviewed.
Why it is structured this way
A notification entry protects continuity of care: it shows the team that information reached the provider and what the plan became. The note records what occurred; it never invents orders or conversations.
When this may be used
- After a notification that actually occurred.
- This page does not determine when notification is clinically required. That depends on the patient, orders, protocols and facility policy.
- Documentation requirements, frequency and screens vary by organization, setting and EHR. Follow your program's and facility's policy.
This page teaches documentation of a notification that occurred
It does not decide whether a provider should be called. Never document an order or conversation that did not happen.
Components
Time and method
When and how.
What belongs here
- Time, phone/in person/secure message per policy
What does not belong
- Approximate times you did not note
Who
Recipient.
What belongs here
- Provider's role/name as policy requires
What does not belong
- "MD aware" with no detail
Information communicated
Content.
What belongs here
- Findings reported
What does not belong
- Findings not shared
Response / orders
Result.
What belongs here
- Orders received and read back, or no new orders
What does not belong
- Orders you assumed
Follow-up
Next steps.
What belongs here
- Actions taken and reassessment
What does not belong
- Untaken actions
Short fictional example
- Narrative
- 0730: Provider notified by phone of fingerstick blood glucose 312 mg/dL. No new orders received. Will recheck glucose before lunch per existing order.
More detailed fictional example
- Narrative
- 2210: Temperature 38.6 °C oral, heart rate 104, blood pressure 118/72. Patient states "I feel shaky." 2215: Provider notified by phone of temperature, heart rate, blood pressure and patient statement. Orders received for blood cultures ×2 and acetaminophen 650 mg by mouth once; orders read back and confirmed. 2230: Blood cultures drawn by laboratory staff. 2235: Acetaminophen 650 mg given by mouth. 2335: Temperature 37.9 °C oral.
Annotated example
Notes on the detailed example above:
Provider notified by phone of temperature, heart rate…
— States what was communicated, not just that a call happened.orders read back and confirmed
— Documents the read-back of verbal/telephone orders.Blood cultures drawn by laboratory staff.
— Care by another person is attributed to them.
Common mistakes
- "MD aware" with no content or time.
- Writing orders that were not given.
- Leaving out the follow-up.
Good vs poor documentation
Weaker (fictional)
Dr. notified.
Stronger (fictional)
2215: Provider notified by phone of temperature 38.6 °C, HR 104, BP 118/72. Orders received and read back.
Why: Time, content and response.
Blank educational template
Provider notification: Document a notification that actually occurred. Prompts only; nothing is prefilled.
- Time and method
- [Time and how the provider was contacted]
- Who was notified
- [Role/name per policy]
- Information communicated
- [Findings reported]
- Response / orders received
- [Response and any orders, read back]
- Follow-up
- [Actions taken and reassessment]
Practice this format
- Practice Note Builder — write a practice note from a fictional scenario.
- Documentation practice questions
Related documentation guides
Sources
- ANA's Principles for Nursing Documentation (2010) — American Nurses Association.
- Nursing Fundamentals 2e — 2.5 Documentation — Open RN (Chippewa Valley Technical College).
- Fundamentals of Nursing — 14.5 Guidelines for Effective Documentation — OpenStax.
- TeamSTEPPS — SBAR (Situation-Background-Assessment-Recommendation) — Agency for Healthcare Research and Quality (AHRQ).
All examples on this page are original and fictional. Sources are used to check principles; they do not endorse Dosage Calcs. See Privacy & Safety.