Sample report
What's inside a Clinical Read.
Every report follows the same structure so your team can find what matters fast. Length depends on the product; most run 4 to 8 pages.
Fictional example. Not from a real product or client.
Break point: Sepsis alert acknowledgment (High)
The alert asks the nurse to open a separate tab to acknowledge it. During a busy admission, the nurse is likely to dismiss it from the banner and not open the tab. Recommendation: allow acknowledgment and a one-line reason from the banner, and show the values that triggered the alert next to it.
- 1.
Summary
The bottom line in a few sentences: would nurses use this, and what stands in the way.
- 2.
What we reviewed
The product, version, access type (demo, screenshots, video), the users and setting assumed, and anything out of scope.
- 3.
The shift, step by step
Where the product shows up in a nurse's day, what else is happening at that moment, and how long the nurse has.
- 4.
Where the workflow breaks
Each break point with the screen or step, what happens, and why it matters on the unit.
- 5.
Safety risks
Issues that could lead to missed findings, delayed care, wrong values or poor handoffs. Each rated High, Medium or Low.
- 6.
Usability risks
Readability, clicks, logins, alert load, shared devices and interruptions. Each rated High, Medium or Low.
- 7.
What nurses need to trust it
What the product must show, explain or prove before a nurse relies on it, and what would make them stop.
- 8.
Prioritized recommendations
What to fix first, second and later.
- 9.
Questions to test with your users
Specific questions to take into pilots, interviews or usability sessions.
- 10.
Limits of this review
What a written review by a practicing nurse can and can't tell you.