## Patient Intake Workflow

Planning this workflow?

The [Intake & Registration Decision Guide](/content/docs/decision-guides/intake/index.html) walks through requirements questions and FHIR modeling decisions for intake — use it alongside these docs.

Patient intake is the process of collecting demographic, insurance, medical history, and consent information when a patient first interacts with your practice or returns for a visit. In FHIR terms, this means capturing a [`QuestionnaireResponse`](/content/docs/api/fhir/resources/questionnaireresponse/index.html) and transforming it into structured resources — [`Patient`](/content/docs/api/fhir/resources/patient/index.html), [`Coverage`](/content/docs/api/fhir/resources/coverage/index.html), [`Consent`](/content/docs/api/fhir/resources/consent/index.html), [`Condition`](/content/docs/api/fhir/resources/condition/index.html), and more — that the rest of your clinical system can use.

This section covers how to model, design, and automate intake workflows in Medplum:

- [**Intake Data Model**](/content/docs/intake/intake-data-model/index.html) — The FHIR resources created during intake, how they relate to each other, and which US Core profiles apply
- [**Intake Questionnaires: Design and Extraction**](/content/docs/intake/intake-questionnaires/index.html) — How to structure intake questionnaires so their responses can be reliably transformed into FHIR resources, using either SDC extraction or Bot-based processing
- [**Post Intake Automation**](/content/docs/intake/post-intake-automation/index.html) — Triggering processing with Subscriptions, post-intake workflows, and optional PlanDefinition-based orchestration

For a working reference app, see the [Patient Intake Demo](https://github.com/medplum/medplum/tree/main/examples/medplum-patient-intake-demo).