Identify the target Questionnaire canonical URL and confirm it carries SDC population extensions (item-level population context or launch context extensions)
POST to Questionnaire/$populate with a Parameters resource supplying the subject (Patient reference) and any additional context resources
Receive the returned QuestionnaireResponse with pre-populated answers derived from the patient's FHIR data
Display the pre-populated QuestionnaireResponse to the user, highlighting auto-filled items so they can be reviewed and corrected
On completion, POST the finalized QuestionnaireResponse and optionally invoke $extract to produce structured FHIR resources
Known gotchas
$populate requires the server to have read access to the patient's clinical data; if the Questionnaire references CQL or FHIRPath expressions that query resource types not covered by the session token's scopes, those items will be left blank without error
Population context expressions must match the FHIR version of the server; expressions written for R4 may not evaluate correctly on an R4B or R5 server
The returned QuestionnaireResponse from $populate is transient and not persisted; the client must POST it explicitly after user review
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp