> 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.md).

# Medicine

Build a medical practice platform on Nerova: dependents as subjects, clinical intake behind the sensitive label, and the conformance checks that hold it all closed.

This guide shapes the Provider API contract for a medical practice platform. It is the demanding end of the vertical spectrum, and it exercises the two contract mechanisms the salon build barely touches: subjects and sensitivity.

What you declare here:

* `ReadSubjects` and `CreateSubjects` with a patient vocabulary, so a parent (the client) can book for a child (the subject). This is the dependents pattern.
* `IntakeForms` with clinical schemas where the sensitive fields carry `"sensitivity": "sensitive"` and only the genuinely conversational ones are opted into `standard`.
* The core nine booking capabilities, as every certified platform does.

The pages in order:

1. [Declare the practice](/guides/verticals/medicine/manifest-and-services.md): manifest with a patient vocabulary, and services with clinical intake.
2. [Sensitive intake](/guides/verticals/medicine/sensitive-intake.md): what the sensitive label does, where the fail-closed default protects you, and what conformance rejects.
3. [Dependents and booking](/guides/verticals/medicine/dependents-and-booking.md): create a dependent as a subject, book for them, and echo everything back.

Prerequisite: a Live API key and a Provider API v1 implementation that passes the core conformance checks, per [zero-to-live](/guides/zero-to-live/zero-to-live.md).

{% hint style="info" %}
Nerova relays intake data and enforces channel policy; your platform remains the system of record and the authority on validation. Nothing in this guide changes who owns the clinical record.
{% endhint %}


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.