{{ currentGuideRow.detail }}
| Rank | Most-endorsed belief | Lens | Score | Review note |
|---|---|---|---|---|
| {{ row.rank }} | {{ row.short }} | {{ row.lensLabel }} | {{ row.scoreLabel }} | {{ row.why }} |
| # | Lower-endorsed anchor | Score | How it can help |
|---|---|---|---|
| {{ row.id }} | {{ row.short }} | {{ row.scoreLabel }} | {{ row.anchorNote }} |
This queue stays focused on the strongest current endorsements first. If nothing crosses the selected review cutoff, the table still ranks the highest-scored items so the result never goes empty.
| # | Item | Lens | Score | Priority | Why it stands out | Reframe prompt | Experiment prompt |
|---|---|---|---|---|---|---|---|
| {{ row.rank }} | {{ row.id }} | {{ row.lensLabel }} | {{ row.scoreLabel }} | {{ row.priority }} | {{ row.why }} | {{ row.reframe }} | {{ row.experiment }} |
| # | Lens | Statement | Score | Priority | Review note | Copy |
|---|---|---|---|---|---|---|
| {{ row.id }} | {{ row.lensLabel }} | {{ row.text }} | {{ row.scoreLabel }} | {{ row.priority }} | {{ row.why }} |
DBAS-16 measures sleep-related beliefs and attitudes. It is useful for structured review, but it is not a diagnosis of insomnia or another sleep disorder.
Sleep beliefs are the rules people carry into the night about how much sleep they need, what a bad night means, and how much control they really have. When those beliefs turn rigid or catastrophic, they can keep insomnia distress going even when the original trigger was short term. This assessment turns that problem into a structured 16-item review so you can see which beliefs are carrying the most weight.
The package is most useful when someone already notices a pattern such as dreading the next day after one poor night, trying harder and harder to force sleep, or assuming imperfect sleep automatically means failure. Instead of leaving those reactions as a vague feeling, it converts 0 to 10 agreement ratings into a mean score, a domain profile, and a ranked set of cognitive targets that can be discussed in a sleep journal or a cognitive behavioral therapy for insomnia (CBT-I) conversation.
A realistic use case is a person who has had several rough nights and wants something more precise than “I am sleeping badly.” Rating all 16 statements can show whether the pressure comes mostly from rigid sleep expectations, helplessness and worry, catastrophic next-day consequences, or control and medication beliefs. That difference matters because the most helpful follow-up question is not always the same as the loudest emotion.
The result needs a careful reading. High agreement with these statements can point to beliefs that maintain insomnia, but it does not identify the cause of sleep trouble and it does not separate insomnia from sleep apnea, circadian disruption, pain, mood symptoms, medication effects, or another medical issue. The package also adds its own interpretation layer, so some labels are best understood as coaching cues rather than formal research scores.
This assessment is informational and not a clinical diagnosis, treatment plan, or substitute for professional sleep evaluation.
The cleanest first pass is to answer every statement before touching the Advanced panel. That gives you the raw belief profile the package calculates from the 16 ratings, and it keeps later queue changes from being mistaken for score changes.
Start Assessment is a good fit when you want a structured check-in before a CBT-I appointment, a coaching session, or a personal review after a run of poor sleep.Percentile ~ value. In this package that number is only a quick estimate from the mean score, so confirm it against Mean, Top domain, and the item table before treating it like a population percentile.Details before changing cutoffs. Many apparent surprises come from one or two statements carrying the profile more than the user expected.When the summary badges and the highest-scored statements tell the same story, open Intervention Queue next and use that as the practical follow-up view.
The published DBAS-16 is a 16-item sleep-belief measure scored from agreement ratings, and this package keeps that basic shape by asking for one 0 to 10 response per statement and averaging the completed set. Higher agreement raises the overall mean, which the tool then maps to four package-defined severity bands: low, mild, moderate, and high maladaptive belief load.
The package does more than report a single mean. It also builds four domain means, ranks the strongest beliefs, counts higher-scored items, and creates a follow-up queue with reframe prompts. Those extra layers make the result easier to act on, but they also matter for comparability. A person can keep the same raw answers and still see the queue change after adjusting High-priority cutoff, Critical belief cutoff, Follow-up cadence, or Intervention track.
One important limit comes from how the package groups items. The published DBAS-16 literature describes four conceptual domains, but the tool's radar and queue use four consecutive four-item blocks: items 1 to 4 for Expectations, 5 to 8 for Worry/Helplessness, 9 to 12 for Consequences, and 13 to 16 for Medication/Control. That makes the radar internally consistent inside this package, yet it should not be read as a claim that the original research instrument is scored in that exact four-by-four pattern.
Privacy is simple here. There is no server-side package for this slug and no network request in the scoring flow, so answers, chart rendering, and JSON output stay in the browser unless the user deliberately copies or downloads an export.
The core score is the arithmetic mean of the 16 item ratings. Everything else builds on that mean or on sorted item scores.
Here ri is the rating for one statement on the 0 to 10 scale. The package shows that value as Mean in the summary badge and rounds the displayed mean to two decimals.
The interpretation layers follow fixed thresholds from the package code rather than published clinical cut points. That is why the output is best treated as a structured review aid.
| Output | Boundary | Meaning inside this package |
|---|---|---|
Mean band |
< 3, < 5, < 7, otherwise | Low, Mild, Moderate, or High maladaptive belief load |
High-priority beliefs |
>= 7 | Fixed count of strongly endorsed items |
Critical beliefs |
>= selected cutoff | Escalation count based on the Advanced threshold |
Percentile ~ |
round(mean x 10), clamped 0 to 100 | Quick position marker, not a norm-referenced percentile |
The queue logic is also deterministic. Beliefs are sorted from highest score to lowest score, rows at or above the selected priority cutoff are preferred, and the package shows at most six queue items. If nothing reaches the cutoff, it still falls back to the top five beliefs so the screen does not go empty. Review dates are then spaced from the chosen cadence, which is why those dates change over time even when the scores do not.
The flow is short once you know which outputs matter.
Start Assessment and confirm the progress bar appears. That tells you the tool has moved from the intro screen into the item-by-item rating flow.Previous, Next, or the question list if you need to revisit an item.DBAS-16 Profile summary, Belief Domain Radar, Intervention Queue, and JSON views appear only after every response is present.Mean, Top domain, High-priority beliefs, Critical beliefs, and Focus.Advanced and adjust High-priority cutoff, Critical belief cutoff, Follow-up cadence, or Intervention track. Those settings reshape prioritization, not the underlying responses.Details to inspect item-level scores, then compare that with Belief Domain Radar and Intervention Queue. If the queue feels wrong, verify the highest-scored items before forcing a different track.When the summary, item table, and queue all point in the same direction, the result is ready to keep as a baseline or discuss with a clinician.
The summary badge is the fastest read, but the item table is the confidence check. A higher band means stronger endorsement of unhelpful sleep beliefs in this package, not proof of insomnia severity, diagnosis, or cause.
Mean < 3 reads as low maladaptive belief load, >= 3 and < 5 as mild, >= 5 and < 7 as moderate, and >= 7 as high.High-priority beliefs always counts items scored >= 7, while Critical beliefs follows the Advanced cutoff you selected.Percentile ~ should not be overread as a published DBAS norm. Verify it against the actual Mean and the highest rows in Details.Top domain and the leading rows in Intervention Queue disagree, check whether Intervention track was locked away from Auto.A useful next check is simple: read the top three scored statements and ask whether they sound like repeating beliefs, not just a bad week.
A user enters mostly 0 to 3 ratings, with responses such as 1, 2, 2, 3 on the first four items and no value above 3 anywhere else. The package reports Mean 1.69 — Low maladaptive belief load, shows Top domain as Consequences, and leaves both High-priority beliefs and Critical beliefs at zero. That pattern fits a person who is bothered by sleep but is not strongly endorsing rigid or catastrophic beliefs across the questionnaire.
Another user scores the first four expectation items at 8, 8, 7, and 8, keeps the worry items around 5 to 6, and leaves medication/control beliefs low. The summary becomes Mean 5.06 — Moderate maladaptive belief load, Top domain becomes Expectations, and the badge row shows four High-priority beliefs with three meeting the default Critical beliefs cutoff. The right reading is not “moderate insomnia”; it is that rigid expectations are now strong enough to deserve direct cognitive work.
If someone has entered 15 ratings and left the final item blank, the progress bar stalls short of full completion and the DBAS-16 Profile card does not appear. The fix is not in Advanced; it is to return to the unanswered statement, enter the last 0 to 10 value, and let the package calculate the summary. This is a common false alarm when users expect the radar or queue to build from a partial run.
No. A high band means stronger endorsement of the sleep-related beliefs presented in this package. It does not diagnose insomnia or explain why sleep is poor.
Percentile ~ number look rough?Because the package estimates it by multiplying the mean score by 10 and clamping the result from 0 to 100. It is a quick orientation marker, not a published DBAS percentile table.
The queue depends on High-priority cutoff, Critical belief cutoff, Follow-up cadence, and Intervention track. Those settings can reorder priorities without changing the raw item scores.
DBAS-16 Profile or Belief Domain Radar yet?The package waits until all 16 responses are complete. Check the progress bar or the question list for the unanswered item, then finish that rating.
No server-side package is present for this tool, and the scoring flow runs in the browser after load. Data leaves the page only if you deliberately copy or download an export.