eduKateSG · Why Science?
Read a wellness feature through its claim, evidence and risk
Use FDA’s January 2026 general-wellness guidance through intended use, low-risk policy, non-invasive sensing, validated values, trends, notifications, chronic-disease wording and user action.
Fitness trackers and wellness apps can turn movement, sleep or optical signals into colourful scores. The scientific question comes before the dashboard: what does the product claim to do, what does it actually sense, and what could a user reasonably do with the result?
FDA’s final General Wellness: Policy for Low Risk Devices guidance, issued on 6 January 2026, clarifies a compliance policy for low-risk products that promote a healthy lifestyle. It also adds detailed examples for some non-invasive sensing products, values, trends and notifications.
Did you know? Two products can use similar sensors yet sit on different policy paths because their intended uses, displayed interpretations and recommended actions differ. A wellness label does not erase a diagnostic or treatment function.
This guide supports science and digital-health literacy. It does not classify a specific product, replace current labeling or provide medical advice.
Chapter index
Chapters 1–9: intended use, policy categories and sensing
- 1. The January 2026 guidance is the current anchor
- 2. General wellness has two policy categories
- 3. Claims must stay inside intended use
- 4. Software may fall outside the device definition
- 5. Some products are devices under enforcement discretion
- 6. Low risk is a separate test
- 7. Non-invasive sensing received 2026 clarification
- 8. Validation remains necessary
- 9. Values and trends need context
Chapters 10–17: validation, outputs, user response and limits
- 10. Notifications can remain wellness-oriented
- 11. A disease reference needs careful wording
- 12. The same sensor can support different claims
- 13. Product instructions reveal the real pathway
- 14. Risk includes foreseeable user response
- 15. The policy has scope limits
- 16. Guidance is a policy document
- 17. A complete wellness receipt preserves boundaries
CHAPTER 1 OF 17 · Define the claim
1. The January 2026 guidance is the current anchor
A wellness claim becomes clearer when intended use, sensing method, output and user action stay connected. FDA issued the final General Wellness: Policy for Low Risk Devices guidance on 6 January 2026 to explain its compliance policy for low-risk products that promote a healthy lifestyle. This keeps a lifestyle message from turning into an unsupported medical claim.
Try this
Evidence question: Which official guidance passage or product record supports the point about the january 2026 guidance is the current anchor? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for the january 2026 guidance is the current anchor. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the january 2026 guidance is the current anchor, its identifier or version context, and one limit that must remain visible.
The January 2026 FDA guidance gives a current route through low-risk general-wellness policy. The guidance describes products with intended uses related to maintaining or encouraging a general state of health or healthy activity and certain healthy-lifestyle uses related to reducing the risk or impact of chronic disease. It also makes validation and low-risk design visible rather than assumed.
Try this
Evidence question: Which official guidance passage or product record supports the point about general wellness has two policy categories? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for general wellness has two policy categories. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for general wellness has two policy categories, its identifier or version context, and one limit that must remain visible.
A friendly wearable display can still require careful reading of what is measured, estimated or inferred. A product statement should be read for whether it encourages wellness or crosses into diagnosis, cure, mitigation, prevention or treatment of a disease or condition. A value, trend or notification needs context before it guides action.
Try this
Evidence question: Which official guidance passage or product record supports the point about claims must stay inside intended use? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for claims must stay inside intended use. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for claims must stay inside intended use, its identifier or version context, and one limit that must remain visible.
CHAPTER 4 OF 17 · Define the claim
4. Software may fall outside the device definition
The evidence boundary sits between supporting a healthy lifestyle and diagnosing or treating disease. Section 520(o)(1)(B) excludes certain software intended for maintaining or encouraging a healthy lifestyle and unrelated to diagnosis, cure, mitigation, prevention or treatment from the device definition. Product wording and actual function must agree.
Try this
Evidence question: Which official guidance passage or product record supports the point about software may fall outside the device definition? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for software may fall outside the device definition. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for software may fall outside the device definition, its identifier or version context, and one limit that must remain visible.
CHAPTER 5 OF 17 · Inspect sensing
5. Some products are devices under enforcement discretion
A wellness claim becomes clearer when intended use, sensing method, output and user action stay connected. For other low-risk general-wellness products that may meet the device definition, the guidance describes circumstances in which FDA does not intend to examine compliance with applicable device requirements. This keeps a lifestyle message from turning into an unsupported medical claim.
Try this
Evidence question: Which official guidance passage or product record supports the point about some products are devices under enforcement discretion? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for some products are devices under enforcement discretion. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for some products are devices under enforcement discretion, its identifier or version context, and one limit that must remain visible.
The January 2026 FDA guidance gives a current route through low-risk general-wellness policy. The product should not present inherent risks to user safety or risks from other regulated products, such as implants, that would require controls to mitigate. It also makes validation and low-risk design visible rather than assumed.
Try this
Evidence question: Which official guidance passage or product record supports the point about low risk is a separate test? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for low risk is a separate test. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for low risk is a separate test, its identifier or version context, and one limit that must remain visible.
CHAPTER 7 OF 17 · Inspect sensing
7. Non-invasive sensing received 2026 clarification
A friendly wearable display can still require careful reading of what is measured, estimated or inferred. FDA explains that certain products using non-invasive sensing, including optical sensing, may estimate, infer or output physiological parameters within the policy when the stated conditions are met. A value, trend or notification needs context before it guides action.
Try this
Evidence question: Which official guidance passage or product record supports the point about non-invasive sensing received 2026 clarification? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for non-invasive sensing received 2026 clarification. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for non-invasive sensing received 2026 clarification, its identifier or version context, and one limit that must remain visible.
The evidence boundary sits between supporting a healthy lifestyle and diagnosing or treating disease. The 2026 examples condition low-risk treatment of some sensed physiological values on validation, so a plausible sensor output is not enough by itself. Product wording and actual function must agree.
Try this
Evidence question: Which official guidance passage or product record supports the point about validation remains necessary? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for validation remains necessary. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for validation remains necessary, its identifier or version context, and one limit that must remain visible.
A wellness claim becomes clearer when intended use, sensing method, output and user action stay connected. Qualifying products may display values, ranges, trends, baselines or longitudinal summaries and contextualise them for wellness domains such as sleep, activity, stress or recovery. This keeps a lifestyle message from turning into an unsupported medical claim.
Try this
Evidence question: Which official guidance passage or product record supports the point about values and trends need context? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for values and trends need context. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for values and trends need context, its identifier or version context, and one limit that must remain visible.
CHAPTER 10 OF 17 · Test the risk boundary
10. Notifications can remain wellness-oriented
The January 2026 FDA guidance gives a current route through low-risk general-wellness policy. A notification can support a healthy-lifestyle action when it avoids directing diagnosis or treatment and when false or missed notifications do not create safety risks requiring regulatory controls. It also makes validation and low-risk design visible rather than assumed.
Try this
Evidence question: Which official guidance passage or product record supports the point about notifications can remain wellness-oriented? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for notifications can remain wellness-oriented. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for notifications can remain wellness-oriented, its identifier or version context, and one limit that must remain visible.
CHAPTER 11 OF 17 · Test the risk boundary
11. A disease reference needs careful wording
A friendly wearable display can still require careful reading of what is measured, estimated or inferred. A healthy-lifestyle claim related to a chronic disease must align with well-understood associations between healthy choices and reduced risk or better living with that condition. A value, trend or notification needs context before it guides action.
Try this
Evidence question: Which official guidance passage or product record supports the point about a disease reference needs careful wording? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for a disease reference needs careful wording. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for a disease reference needs careful wording, its identifier or version context, and one limit that must remain visible.
CHAPTER 12 OF 17 · Test the risk boundary
12. The same sensor can support different claims
The evidence boundary sits between supporting a healthy lifestyle and diagnosing or treating disease. An optical or electrical measurement does not determine regulatory status alone; the intended use, displayed output, interpretation and recommended action matter. Product wording and actual function must agree.
Try this
Evidence question: Which official guidance passage or product record supports the point about the same sensor can support different claims? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for the same sensor can support different claims. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for the same sensor can support different claims, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Preserve the receipt
13. Product instructions reveal the real pathway
A wellness claim becomes clearer when intended use, sensing method, output and user action stay connected. App text, onboarding, alerts, reports and marketing can show whether users are encouraged toward general wellness or asked to make medical decisions. This keeps a lifestyle message from turning into an unsupported medical claim.
Try this
Evidence question: Which official guidance passage or product record supports the point about product instructions reveal the real pathway? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for product instructions reveal the real pathway. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for product instructions reveal the real pathway, its identifier or version context, and one limit that must remain visible.
The January 2026 FDA guidance gives a current route through low-risk general-wellness policy. Evaluation should consider what users may do after a value or warning, including delaying care, changing treatment or relying on an inaccurate output. It also makes validation and low-risk design visible rather than assumed.
Try this
Evidence question: Which official guidance passage or product record supports the point about risk includes foreseeable user response? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for risk includes foreseeable user response. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for risk includes foreseeable user response, its identifier or version context, and one limit that must remain visible.
A friendly wearable display can still require careful reading of what is measured, estimated or inferred. The guidance does not apply to products regulated by other FDA centers, such as drugs, biologics, foods, dietary supplements or cosmetics, or to combination products. A value, trend or notification needs context before it guides action.
Try this
Evidence question: Which official guidance passage or product record supports the point about the policy has scope limits? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for the policy has scope limits. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for the policy has scope limits, its identifier or version context, and one limit that must remain visible.
The evidence boundary sits between supporting a healthy lifestyle and diagnosing or treating disease. FDA guidance describes current thinking and compliance policy; it does not provide a clearance, approval or product-specific finding. Product wording and actual function must agree.
Try this
Evidence question: Which official guidance passage or product record supports the point about guidance is a policy document? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for guidance is a policy document. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for guidance is a policy document, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Preserve the receipt
17. A complete wellness receipt preserves boundaries
A wellness claim becomes clearer when intended use, sensing method, output and user action stay connected. Record the exact intended use, claim category, sensing method, validation evidence, output, notification, user action, risk analysis, labeling version and source date. This keeps a lifestyle message from turning into an unsupported medical claim.
Try this
Evidence question: Which official guidance passage or product record supports the point about a complete wellness receipt preserves boundaries? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the function, identifier, date and one evidence limit for a complete wellness receipt preserves boundaries. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for a complete wellness receipt preserves boundaries, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A cheerful wellness score becomes useful when its claim and evidence boundary remain visible
The 2026 policy makes room for low-risk wellness innovation while keeping validation and foreseeable user response in view. Read the exact claim, not merely the product category or marketing tone.
Save the product and software version, intended user and use, claim wording, sensor and placement, measured or inferred parameter, validation source, output units and ranges, notification logic, instructions, risk analysis, limitations and access date.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Claim | Defines the wellness purpose | Does it imply diagnosis or treatment? |
| Sensor output | Value, range, trend or notification | Was it measured, estimated or inferred? |
| Validation | Supports performance of the output | Which population and conditions? |
| User action | Connects information to behaviour | Could error create a safety risk? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA General Wellness Final Guidance — accessed 25 October 2026.
- FDA General Wellness Guidance PDF — accessed 25 October 2026.
- FDA General Wellness Town Hall — accessed 25 October 2026.
- FDA Digital Health Policy Navigator — accessed 25 October 2026.
- FDA Digital Health Guidance List — accessed 25 October 2026.