Implementation Guidelines

XUND is a certified medical device. These rules aren't stylistic preferences — they're conditions of using the API, and XUND runs an acceptance test after integration to verify them before production launch.

Content integrity

Content returned by the API (questions, answer options, illness descriptions, disclaimers, report results) must not be modified, rephrased, summarized, or filtered before being shown to the user — no LLM/AI post-processing, no custom rewriting. Questions and answer options must be presented exactly as the API returns them; you can restyle them (text vs. graphical widgets) but not reinterpret them. Report results must keep the API's sort order — don't hide entries or highlight specific conditions.

When in doubt about how something should look or behave, XUND's own Symptom & Illness Check App is the reference implementation partners are measured against.

Consent and imprint

• The end user must explicitly consent to XUND's Terms of Use and Privacy Policy before using any check feature — either folded into your own consent flow or shown as a standalone prompt.
• Your app's imprint/legal notice must name XUND Solutions GmbH as the manufacturer, with a visible "Powered by XUND" mark. Render the imprint data from GET /v1/imprintResources dynamically (it changes across releases) rather than hardcoding it, and link the impressum.userManual resource.

Checkflow rules you can't skip

• Overview: GET /v1/chatbot/overview must be shown before confirming it — all added and suggested symptoms must be visible, and the user must be able to add/edit/remove symptoms from that screen.
• Disclaimers: any legal data the API returns must be displayed and explicitly acknowledged — don't auto-skip it.
• Warning signs: if a check response includes a warning sign, show it immediately in the flow, and again in the final report — these flag potentially life-threatening conditions.
• Back navigation: users must be able to step back through the flow to review or change earlier answers — see Changing earlier answers.

Age-gating (your responsibility, not the API's)

The symptom/illness checker is intended for ages 10+, with 10–15 year olds requiring supervision by someone 16 or older. The API does not enforce this — your app must collect age and gate access itself (e.g. a confirmation modal before continuing) below age 16.