Construct a FHIR R4 ServiceRequest conforming to the SDOHCC ServiceRequest profile from the Gravity SDOH Clinical Care IG
Set category to the appropriate SDOH category code (e.g., food-insecurity) from the SDOH Service Request Category value set
Set code to the specific service being requested using SNOMED CT or a locally defined code from the Gravity service request codes value set
Reference the patient, the requesting practitioner, and any related Condition or Observation that prompted the referral
Set intent to order or proposal and status to active when the referral is sent
Create a companion Task resource referencing the ServiceRequest to track fulfillment status through the closed-loop workflow
Known gotchas
The SDOHCC ServiceRequest profile mandates several must-support elements; omitting them will cause profile validation failures even if the base resource is valid
Using a Task to track the ServiceRequest is a Gravity-required pattern for closed-loop referrals; the ServiceRequest alone does not convey fulfillment state
Value sets for SDOH categories and service codes are still evolving in the Gravity IG; pin to a specific IG version to avoid breaking changes
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