Identify the correct CDex Task profile from the Da Vinci CDex IG for your scenario (data request vs. attachment request) and read the profile's must-support and required element definitions.
Set Task.requester to a reference to the Organization or Practitioner initiating the request, and set Task.owner to the Organization or Practitioner expected to fulfill the request.
Populate Task.input elements as defined by the profile — inputs typically include the requested data type, the patient reference, and any search parameters or document references relevant to the request.
Include the purpose-of-use extension on the Task if required by the CDex IG version in use; the value should be drawn from the applicable purpose-of-use value set (verify against the current IG).
As the fulfilling system processes the Task, update Task.status and populate Task.output with references to the resources or documents being returned.
Ensure Task.for references the correct Patient and Task.basedOn or Task.reasonReference links to the originating claim, prior authorization, or order where applicable.
Known gotchas
Purpose-of-use codes are governed by a specific value set in the CDex IG — using a code outside the defined set may cause rejection; verify permissible values in the current IG.
Requester and owner must be resolvable references; if the receiving system cannot dereference them, the Task may be rejected or left unprocessed.
Task.status transitions must follow the allowed state machine in the FHIR specification and any additional CDex constraints — skipping states or setting unsupported statuses will cause conformance issues.
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