Repository navigation
Clinical trust: unsigned DSM specifiers read as pending, Clozapine overview reword, faster consumer refusals - #3552
Conversation
The approved line read as if the adverse effects themselves require registration. Reworded so treatment requires registration and blood monitoring because of those effects. Clinical text, pending Josh's sign-off. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016H8cG4UfVRH56goC9AVmL2
The 2026-09-26 reconcile stamped 71 specifier items and 18 universals "clinician-reviewed" by "PsychSift". Those pages read "Definition reviewed by PsychSift" and showed the generated definition as reviewed. The sign-off test now requires a named person, the same rule the site-wide sign-off line uses, so those 89 read as pending and their definitions are withheld until a named clinician signs them. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016H8cG4UfVRH56goC9AVmL2
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
There was a problem hiding this comment.
BigSimmo has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Claude encountered an error after 2s —— View job I'll analyze this and get back to you. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
PR Summary by QodoRequire named clinician sign-off for specifiers and clarify Clozapine overview
AI Description
Diagram
High-Level Assessment
Files changed (5)
|
A question the consumer pattern guard already refuses ("best coffee machine
for my kitchen") still went to the LLM query classifier before the
short-circuit refused it. On the 13 Oct canary that wait made four refusals
take 1.6 to 6.4 s, putting the unsupported route p95 at 6,360 ms against its
4,000 ms gate. The classifier is now skipped for these, as it already is for
adversarial and outside-corpus medical queries. Queries with psychiatric or
clinical context, a medication, a threshold or a document title still reach
the model.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016H8cG4UfVRH56goC9AVmL2
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4751f967b9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Code Review by Qodo
No findings for this group No findings for this group No findings for this group Resolved findings 1.
|
CodeAnt Nitpicks1 code suggestion1. This now marks 71
|
|
Status of the red checks on this PR.
Generated by Claude Code |
- Align specifier sign-off eligibility - Reconcile pending specifier counts
Qodo Fixer✅ Committed (4) · ☑ Fixed (4) Commits pushed directly to this PR — no separate fix PR opened. Process — 4 fixed
|
The review contract's specifier reviewer check accepted role names such as "Clinical Team" that the site's isNamedPerson rejects. It now mirrors the same rule and role-word list, pinned by a parity test. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016H8cG4UfVRH56goC9AVmL2
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016H8cG4UfVRH56goC9AVmL2
|
Code review by qodo was updated up to the latest commit f67d43e |
A list of clinical words to watch for can never be complete, so a query such as "holiday leave for akathisia" could still be refused unchecked. The bypass now requires every word to come from a closed list of everyday shopping and household words; anything else keeps the classifier. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016H8cG4UfVRH56goC9AVmL2
|
Auto-fix: 2 checks fixed. View session →
|
The committed data/repo-awareness-snapshot.json did not list docs/decisions/2026-10-15-specifiers-need-a-named-sign-off.md, so `check:repo-awareness-snapshot` reported documentation differing from the repository. Regenerated with `npm run snapshot:repo-awareness`; the only change is that one catalogued decisions entry.
…77' into claude/clinical-trust-fixes-tjkl77
|
Code review by qodo was updated up to the latest commit 7057a28 |
Code Review ✅ Approved 4 closed / 4 findings🟡 Medium risk · Changing specifier sign-off gating and bypassing classification for consumer queries could hide definitions awaiting review or prematurely refuse ambiguous questions. Requires a named clinician sign-off before DSM specifier definitions show as reviewed, and rewords the Clozapine overview to state that treatment requires registration and blood monitoring because of serious adverse effects. Resolved this session: the clinical review tool now rejects the same reviewer names the display treats as pending, the specifier family note reports the full pending count, a syntax issue after applyClinicalReview is fixed, and the classifier bypass no longer skips clinical queries that contain consumer words. No issues found. ✅ 4 closed✅ Bug: clinical:review still accepts reviewers the display now treats as pending
✅ Quality: Specifier family note still reports only the export's pending count
✅ Bug: Leftover text after applyClinicalReview breaks the review contract
✅ Bug: Skipping classifier removes its rescue of clinical queries with consumer words
VerificationRules No rules evaluated Functional validation Not enabledAuto-approval Approved For more verification details, comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Important Your trial ends in 6 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
CodeAnt PR Risk: Low Risk
Assessed commit: |
User description
Requested by Josh · project thread
Summary
Before: 71 DSM-5-TR specifier pages and 18 universal specifiers read "Definition reviewed by PsychSift" and showed their generated definition as clinician reviewed, although no named clinician signed them. The Clozapine overview read as if the adverse effects themselves require registration.
After: those 89 entries read "Pending qualified review" and their definitions are withheld until a named clinician signs them, the same rule the site-wide "Not signed off yet" line already uses. The Clozapine overview reads: "Antipsychotic for treatment-resistant schizophrenia. Treatment requires registration and blood monitoring through the clozapine monitoring service because of serious, potentially fatal adverse effects."
How:
isSpecifierClinicianReviewednow requiresisNamedPerson(reviewedBy)instead of any non-empty string. One sentence changed indata/medications-snapshot.json. The sign-off queue grows from 514 to 603 specifier rows. Each change is its own commit so either can be dropped.Areas touched: Clinical reference content, Prototypes
Verification
npm run test:focusedfor the specifier change: 412 of 413 passed, the one failure was an outdated assertion, now fixed; the three specifier test files then passed 21 and 15 of 15.npm run test:focused -- --files data/medications-snapshot.json: "Tests 825 passed (825)".typecheck:internalpass.Risk and rollout
catalogue-evidence.tsreads the same helper).Notes
🤖 Generated with Claude Code
https://claude.ai/code/session_016H8cG4UfVRH56goC9AVmL2
Generated by Claude Code
Summary by cubic
DSM specifiers stamped with the product name "PsychSift" instead of a named clinician now read as "Pending qualified review", and their definitions are withheld until a named clinician signs them, so the 71 DSM-5-TR specifier pages and 18 universal specifiers stamped by the 2026-09-26 reconcile no longer count as signed evidence. The review tool and sign-off queue apply the same named-clinician rule the site uses, and unsigned definition wording is no longer sent to Clinical Ask synthesis. The Clozapine overview now says treatment requires registration and blood monitoring because of serious adverse effects, and the medication import script preserves this wording on refreshes. Consumer questions the pattern guard already refuses skip the LLM classifier, keeping unsupported-route refusals under the 4 s latency gate.
unverified(ineligible) rather thanlocally_reviewed, and the decision record is catalogued in the repo-awareness snapshot.Written for commit 46cefa0. Summary will update on new commits.
Summary by Gitar
analyzeQueryWithClassifierFallbackscripts/import-medications-export.tskeeps the signed-off Clozapine overview wording on export refreshvalidation_unverifiedand ineligible, withcontentHashand digests refreshedThis will update automatically on new commits.
Summary by CodeRabbit
Clinical Information
Review Status
Search and Responses
CodeAnt-AI Description
Make clinical review status and medication guidance clearer, and speed up unsupported consumer-query refusals
What Changed
Impact
✅ Unsigned specifier definitions stay hidden✅ Clearer clozapine monitoring guidance✅ Faster consumer-query refusals💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.