Connect REDCap

Nobody Diffs the Codebook

Somewhere in the second year of a study, a monitoring meeting stalls on a question that should be trivial: was the systolic blood pressure field always integer-validated, or did that change after the pilot?

Six Questions Your REDCap Project Can Suddenly Answer

Ask a team what changed about their REDCap work after putting a project under governance, and the honest answer is: nothing. They still design instruments in REDCap. They still enroll participants, still branch, still export. Nobody handed over an API token, and nothing outside the team ever writes to the instance.

Recipe: First governed REDCap import

The Powers We Deliberately Did Not Take

A tool that governs a research study's schema could be given a great deal of authority. It could hold an API token and read the project directly. It could reconcile your model to the latest upload automatically. It could push corrected instruments back into REDCap. Each of those would demo well.

The Dictionary Travels Further Than the Data

A REDCap data dictionary gets around. It is emailed to a collaborating site so they can stand up the same instruments. It is attached to a protocol so a reviewer can see what is being collected. It is handed to a statistician who needs the codebook, to an engineer who needs to build a load, to the next study that wants to reuse a validated instrument. The participant data stays behind an access committee. The dictionary circulates freely, because it carries meaning rather than records.

Recipe: Data-dictionary round trip

The Agent Cannot Tell Which Column Is the Key

Give a capable AI assistant two REDCap exports and ask it to join them. Watch what it has to do.

REDCap to CoreModels: Zero to First Audit with One CSV

Most schema estates take real work to extract: information-schema queries, catalog exports, manifest builds. A REDCap project is the pleasant exception — the entire schema estate is one stable file, the data dictionary CSV, and you almost certainly already know how to download it. That makes the distance from "nothing governed" to "first drift audit" unusually short. This tutorial walks the whole distance: export the dictionary, import it into a governed CoreModels project, run your first audit, and read what comes back. No REDCap credentials are ever shared with CoreModels at any point.

Recipe: Blank REDCap project · First governed REDCap import

Every REDCap Route in CoreModels: the Full HTTP Reference

The CoreModels REDCap connector declares all three capabilities — **Import, Audit, Generate** — which means every integration verb on our HTTP surface is live for it. This article is the complete route-by-route reference: what each endpoint takes, what it returns, which role it requires, and which of the two HTTP surfaces it lives on. If you're writing a script, a service, or an internal tool against the REDCap integration, this is the page to keep open.

Give Your Agent the Dictionary: REDCap Governance over MCP

When the caller is an AI agent rather than a shell script, the interesting question stops being "what's the route?" and becomes "what is the agent allowed to know, and what is it allowed to do?" CoreModels answers that with an MCP server whose vendor-integration tools mirror our HTTP surface exactly — same audit engine, same additive import, same read-only posture — but packaged as typed tools an agent can discover, reason about, and chain. This article walks the four tools that matter for REDCap, with the real arguments, and shows the pattern we recommend for agents that govern clinical research schemas: discover, audit, and only then (with a human's admin endpoint) import.

The Dictionary Changed on a Tuesday: CI Drift Gates for REDCap

REDCap's greatest operational strength is also its governance problem: a data manager with the right permissions can change a production instrument in minutes. A validation type quietly switches from `integer` to plain text, a choice list gains a code, a required flag disappears — and every downstream extract, harmonization script, and statistical pipeline inherits the change without a review. The fix isn't to slow REDCap down. It's to make the data dictionary a versioned, gated artifact like any other piece of production configuration. This article builds that gate with CoreModels: a CI audit that fails on drift, a status badge, a rolling history, one-call re-audits, and the scheduled heartbeat that catches drift nobody pushed.

Recipe: CI Drift Gate for REDCap

Inside the REDCap Connector: How a Data Dictionary Becomes a Governed Graph

To trust a governance tool you should be able to predict what it does with your data — row by row, column by column. This deep dive opens the hood on the CoreModels REDCap connector: how the data dictionary CSV is parsed, how each REDCap concept lands in the governed graph, which facts ride vendor metadata rather than governed meaning, what triggers each audit rule, and precisely where the mapping is lossy.

Recipe: Data-dictionary round trip