> For the complete documentation index, see [llms.txt](https://docs.nerovasystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerovasystems.com/guides/verticals/medicine/sensitive-intake.md). # Sensitive intake What the sensitive label does on the wire and in conversation, why the contract defaults closed, and the conformance checks that reject mislabeled clinical fields. ## What the label controls `sensitivity` is a channel policy, enforced by Nerova on your behalf: * **`standard`** fields may be collected conversationally. The concierge asks the question in WhatsApp and relays the answer into the booking. * **`sensitive`** fields are never captured on conversational or otherwise untrusted channels. They are collected only on trusted surfaces and relayed to your platform in the booking request; they do not transit the chat thread. Either way, your platform receives the answers in `intakeResponses` and remains the system of record. The label controls where the data is *collected*, not whether you get it. ## Fail-closed, in your favor An intake field that omits `sensitivity` is treated as `sensitive`. For a clinical platform this default is your safety net: a field someone forgets to label gets maximum protection, not accidental exposure in a chat. The cost is on the salon side of the spectrum, where forgetting the `standard` label silently removes a question from the conversation; see the [beauty guide](/guides/verticals/beauty-and-nails/intake.md) for that failure mode. ## What conformance rejects The `intake.sensitivity_labels` check fails any service that labels a clinically sensitive key as `standard`. Keys such as `medical_history`, `medications`, `allergies`, and `diagnosis` must be `sensitive`. This is not advisory: a practice platform that tries to collect a medication list through chat fails certification. {% hint style="warning" %} Renaming a key does not change its nature. A field keyed `current_meds` holding a medication list is still clinical data; label it `sensitive`. The check catches the well-known keys, but the channel policy is only as honest as your schema. {% endhint %} ## Design guidance for practice schemas * Keep the `standard` set minimal and genuinely conversational: `reason_for_visit`, appointment logistics, preferences. * Put every clinical answer behind `sensitive`, including free-text fields that merely invite clinical detail. * Prefer `longText` for history-style fields and `required: false` unless your practice truly refuses bookings without them; required sensitive fields must still be satisfiable outside the chat. * Follow-up and administrative services should carry lean schemas, as on the [previous page](/guides/verticals/medicine/manifest-and-services.md): asking less is a feature. Next: [Dependents and booking](/guides/verticals/medicine/dependents-and-booking.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nerovasystems.com/guides/verticals/medicine/sensitive-intake.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.