Obtain API credentials from the Medable platform admin and authenticate using the platform's OAuth 2.0 client credentials flow to retrieve a bearer token for API calls
Query the Medable API for consent task completion events by subject identifier (participant ID) to determine when an eConsent form has been completed, withdrawn, or requires re-consent
Map Medable participant IDs to EDC subject IDs using a cross-reference maintained in the CTMS; transmit consent completion status to the EDC via the EDC's import API to update the subject's eligibility or consent date field
Subscribe to Medable webhook events for consent status changes (completed, declined, withdrawn) to trigger real-time updates in the EDC and CTMS rather than polling
For re-consent workflows triggered by protocol amendments, use the Medable API to create a new consent task for existing subjects and track the re-consent deadline against the amendment effective date
Confirm that the integration preserves the audit trail: each consent event in Medable must record participant identity, timestamp, version of the consent document signed, and authentication method used
Known gotchas
Medable's participant IDs are internal to the platform; always use the sponsor-assigned subject ID as the linking key and validate the mapping table before automating consent status pushes to the EDC
Consent withdrawal events must trigger immediate downstream actions (e.g., locking EDC data collection for that subject); failure to handle withdrawal webhooks in real time creates a compliance gap
Consent document versions are tightly coupled to IRB-approved amendment dates; the integration must capture the specific document version signed, not just a boolean consent flag
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