Ask a question or bring in the context.
YOUR REVIEW
YOUR NEXT STEPS
Follow-ups, with the review that gave them context.
Private to your account. Follow-ups do not send notifications or perform actions in an EHR. How briefs and follow-ups work ↗
Monitor reliability, adoption, model usage, and account access. Operational metadata only.
Fixed aggregate counts of cases and shared work. Ownership confirmations are recorded events; case content and per-person activity are excluded.
Extension editor checks and clinician-reported saves. These counts do not verify EHR persistence.
Daily aggregate counts. No user or patient-session drilldown.
Current application and model readiness.
Request counts, response times, server errors, and rejected requests. History polling is excluded.
| Operation | Requests | Server errors | Rejected | Average | Maximum |
|---|
Grouped status codes only. Raw error messages, request paths, and request bodies are not available.
| Operation | HTTP status | Count |
|---|
Counts of records and request states. No titles, text, attachments, or captured context.
Provider-reported token counts. Add your contracted USD rates per million tokens to estimate model costs.
| Model | Calls | Input tokens | Output tokens | Estimated cost | Pricing |
|---|
Approve or suspend workspace and extension access. Email verification is still required. The configured owner is the only super admin.
| Account email | Access | Updated | Action |
|---|
Recent console views, reports, pricing edits, and approval changes. User conversation audits are not exposed here.
| Time | Action | Account affected |
|---|
Connecting to your account.
One account for your workspace and Chrome extension.
Account help