Medplum captures consents and signatures as structured, versioned FHIR data rather than as opaque PDFs. The Consent resource is the primitive: it records what a patient agreed to, when they agreed, which policy governed the agreement, and — because every write is versioned — who recorded it and what changed afterward.
A patient intake form captures a wide range of information in a single interaction — demographics, insurance, medical history, medications, allergies, family history, and consent. In FHIR, this information fans out into many discrete resource types. This page maps out that resource graph, explains how the resources relate to each other, and identifies the US Core profiles that apply.
An intake questionnaire is different from a typical clinical form (like a PHQ-9 or wound assessment) because a single response fans out into many different FHIR resource types — Patient demographics, allergies, medications, conditions, insurance, consents, and more. This means the Questionnaire structure needs to be designed with extraction in mind: the way you organize items and name linkIds directly determines how reliably the response can be transformed into structured data.
The patient submitted their intake form — now what? This page covers the patterns for triggering intake processing and the workflows that follow once intake data has been ingested into FHIR resources.
This guide describes a practical workflow for testing SMART Health Links (SHLs) between independent healthcare applications.