Report a Bug
Use this page when something is broken, incorrect, or behaving differently from what users or the business expect.
A good bug report helps QA reproduce the issue quickly and helps engineering understand impact, likely scope, and urgency.
Include these essentials
Describe the issue clearly
- What is broken?
- Where is it happening?
- Who is affected?
- How often does it happen?
Write testable steps to reproduce
- List the steps in order.
- Use real URLs, pages, patient links, records, or environments where relevant.
- State the actual result and the expected result separately.
Attach evidence
- Screenshots or screen recordings
- Error messages or logs
- Related emails, tickets, or support conversations
- Time observed, if the issue may be intermittent
Add context that helps triage
- Severity or business impact
- Whether there is a workaround
- Whether this is a regression or longstanding issue
- Any known edge cases, patterns, or affected segments
Suggested bug format
Summary
Short description of the issue.
Environment
Production / staging / specific clinic / specific browser / device if relevant.
Steps to reproduce
1. ...
2. ...
3. ...
Actual result
What happened.
Expected result
What should have happened.
Impact
Who is affected and how urgently this matters.
Evidence
Links, screenshots, logs, emails, or examples.
Before submitting
- Confirm the issue still reproduces
- Check whether the ticket already exists
- Make sure the evidence points to the exact problem being reported
- Add enough detail that someone else can reproduce it without a live walkthrough
Related guidance: Request Readiness