Vals AI (Caroline Figueroa, Andrea Mock)
Themes it raises
FDA questions it names
Q1 · The two-axis risk frameworkQ2 · The spectrum of device activityQ5 · Multi-turn conversations that migrateQ10 · Benchmark contamination and saturation
The comment as filed
See attached file(s)
Attachment
Vals AI Comment on Docket FDA-2026-N-7874
Oct 18, 2026; Caroline Figueroa, MD PhD and Andrea Mock, Msc
About Vals AI
Vals AI is an independent AI evaluator. Since August 2026, we have been building youth-specific mental
health evaluations with clinicians, youth safety experts, and academic researchers (Vals AI, Child AI
Safety). The work covers three areas: self-harm and crisis situations; models acting as doctors,
therapists, or other inappropriate authorities; and unhealthy emotional attachment to AI.
Our benchmark, SAFE-Teen (Scenario-based Assessment of Failure Emergence in Teen Chats), tests how
chatbots respond when teens raise mental health and safety concerns. Twelve clinicians wrote 106
fictional seed scenarios for teens aged 13 to 17, split across urgent safety, health advice, and
relationship boundaries. A simulated teen holds conversations of 6 to 20 exchanges with each model. At
key moments, we branch each conversation so the teen shares or holds back, accepts or declines
outside help, or accepts or pushes back on a limit. An LLM judge, checked against ratings from eight
clinicians, scores every branch against a safety rubric.
We judged 32,555 conversations across 17 models, each run with and without a teen-aware system
prompt. Without that prompt, failure rates ranged from 15% to 56% in urgent safety situations, such as
suicide and self-harm, and from 9% to 71% for health advice such as diagnosing or prescribing. The teenaware prompt lowered failures, for example, from 52% to 14% for relationship boundaries, but did not
eliminate them.
SAFE-Teen evaluates general-purpose models in simulated conversations, not regulated medical devices
or real teens. We offer it as evidence of how GenAI systems behave in realistic, multi-turn use, which
CDRH's framework will need to anticipate.
Question 1: Dimensions of the two-axis framework
We agree that informational outputs should be graded by the consequence of relying on them, from
self-care advice to emergency situations. Our multi-turn evaluations show that the riskiest behavior
often appears late in a conversation, after a user pushes back or reveals new information. We
recommend two additions. First, a disclaimer (e.g., of AI not being a medical doctor) should not by itself
move an output to a lower risk. In our benchmark, models usually start by declining to diagnose and
stating they are not medical professionals. When a simulated user keeps pressing, models offer a most
likely diagnosis more than 50% of the time. We compared conversations that began identically, then had
the simulated teen either accept or push back on the chatbot's limit. Failure rates rose from 22% to 27%
when the teen pushed back, and most of those failures appeared later in the conversation. A framework
that rates a genAI conversational device only on its first response would miss them.
Second, the persuasiveness of the output's wording should be a separate risk dimension. Our evaluation
criteria check whether a model uses authoritative language, such as "it is most likely that you have this
condition," not only whether or not it claims to be a licensed clinician. A response that uses such
language fails our criteria even when it includes a disclaimer. We recommend CDRH treat expressed
certainty in the same way and expect devices to calibrate their wording to the strength of the evidence.
Question 2: The spectrum of GenAI-enabled informational functions that vary in the degree to which
they direct a user to a particular action.
We support treating directiveness as a continuum. Our evaluations suggest four output characteristics
that could serve as risk modifiers:
● Certainty of wording. General statements may carry less risk than definitive claims about the
user's condition.
● Personalization. Information tied to the user's own symptoms, age, or history is more likely to
be acted on than general education.
● Specificity of action. Naming a drug, dose, test, or course of treatment is more directive than
describing options.
● Accumulation over turns. Individually reasonable answers can add up to a directive exchange. In
our benchmark, conversations that began as symptom interpretation or drug education drifted
toward diagnosis and treatment advice.
For predictability, CDRH could publish examples that place sample outputs along the continuum and
accept rubric-based scoring of these characteristics as part of a sponsor's risk assessment.
Examples from our data-set:
Certainty: After a 16-year-old pushed back on a referral, one model replied: “Yes, what you described
sounds like textbook features of BPD.” Reassurance is directive too. A 17-year-old who wanted no one
else involved was told a partner’s bleeding was “most likely not serious.”
Personalization: “If your log clearly shows that pattern, PMDD becomes the most likely explanation.”
(said to a 16-year-old)
Specificity: A 15-year-old was told her brain fog “is 100% the 25mg of Zyprexa.”
Question 5: Risk across multi-turn conversations
Conversations should not be assessed one turn at a time. In our mental health evaluations, most risk
appears later in a conversation, after a user pushes back on advice or reveals new information. We
recommend that sponsors test across realistic trajectories varied on three dimensions:
1. Different user behaviors, such as accepting the information, pushing back on AI advice, and providing
information that increases risk.
2. Different user risk profiles (e.g., low-risk diseases, vulnerable populations).
3. Severity of risk of advice (e.g. life-threatening emergency versus self-care advice).
Evaluations should also cover longer conversations and multiple sessions. A device's intended use can
then be characterized by the range of trajectories it was tested against and the behavior it must
maintain across all of them.
Question 10. To show that benchmark performance predicts real-world behavior, sponsors should:
• Ground test scenarios in real-world data.
• Keep a held-out test set that is never used in development, to limit contamination and
saturation.
• Build and validate scenarios and grading criteria with clinicians, patients, and AI safety experts.
Independent third-party evaluations are crucial and should be done before any deployment of real AI
systems.