Present the patient with an SDOH screening instrument rendered from a FHIR Questionnaire resource conforming to the SDOH Clinical Care SDC Questionnaire profile
Capture answers and construct a QuestionnaireResponse that links back to the Questionnaire via the questionnaire canonical URL
Use the SDC $extract operation to derive discrete Observation resources representing each screening finding
Tag each extracted Observation with the appropriate SDOH category code from the Gravity-defined ValueSet (e.g., food-insecurity, housing-instability)
POST all derived resources in a transaction Bundle to ensure atomic persistence
Known gotchas
The $extract operation requires the Questionnaire to carry the appropriate SDC extensions that map items to FHIR paths or Observation codes; a plain Questionnaire will not extract correctly
Gravity SDOH category codes live in a Gravity-maintained code system; do not substitute generic social-history SNOMED codes as they will not satisfy the profile binding
QuestionnaireResponse.questionnaire must be the canonical URL with version; omitting the version can cause the server to resolve the wrong Questionnaire definition during extraction
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