Good Clinical Data Management Practices (GCDMP)

Good Clinical Data Management Practices (GCDMP) is the published practice-standard document maintained by the Society for Clinical Data Management (SCDM). It sets out, chapter by chapter across the clinical data management (CDM) lifecycle, what a data management function should be doing at a Minimum Standards level (the baseline every study should meet) and at a Best Practices level (higher-maturity practice beyond the minimum). GCDMP is a practices/standards reference, not a piece of software — it does not capture, store, or transmit trial data itself. That distinguishes it from tools like Electronic Data Capture (EDC) systems, which are the technology GCDMP-conformant processes are typically carried out through.

What Makes Something “GCDMP” (Operational Definition)

A CDM process, procedure, or document counts as following GCDMP when it is explicitly built against one of the document’s published chapters — each covering a discrete CDM area of responsibility such as CRF/eCRF design, clinical database design and validation, data collection and processing, quality management, discrepancy (query) management, medical coding, database closure/lock, data transfer and extraction, or archival and retention — and can show which of that chapter’s two tiers it meets:

• Minimum Standards: the baseline level of practice GCDMP holds is necessary for defensible clinical data management on essentially any trial, regardless of size or budget.
• Best Practices: practice that exceeds the minimum — the level a mature, well-resourced CDM function should be working toward, and often what sponsor SOPs or audit programs benchmark against.

A study team, CRO, or sponsor CDM department is “practicing to GCDMP” when its own SOPs, data management plan, and quality-control checks are written to correspond to specific GCDMP chapters and tiers — not merely when it happens to perform similar activities without that explicit reference. GCDMP itself is not a regulation; it functions as an industry consensus reference that sponsor SOPs, CRO service specifications, and audit/inspection readiness programs commonly cite or align to, alongside binding regulatory sources such as ICH E6(R2) / ICH E6(R3) Good Clinical Practice and 21 CFR Part 11.

How GCDMP Relates to Other Clinical Data Standards

GCDMP is easy to conflate with adjacent standards that cover different parts of the same problem. They are complementary, not interchangeable:

• GCDMP vs. CDISC standards (CDASH, SDTM, ADaM). GCDMP governs process — how a CDM function should operate, document, and quality-control its work. CDASH, SDTM, and ADaM, maintained by CDISC, govern data structure and format — how collected fields are named and organized for collection, tabulation, and analysis. A study can be CDASH/SDTM-conformant in its data structure while still varying in how well its underlying process follows GCDMP, and vice versa.
• GCDMP vs. EDC/CDMS technology. See the dedicated section below — GCDMP is the practice standard; EDC and CDMS are the software categories that process is carried out through.
• GCDMP vs. the CCDM credential. SCDM also administers the Certified Clinical Data Manager (CCDM) credential, an individual professional certification. GCDMP is the underlying body-of-knowledge document; CCDM is a personnel credential that draws on it, not the document itself.
• GCDMP vs. ICH GCP. ICH E6(R2)/(R3) is binding regulatory guidance covering the conduct of the trial as a whole, including data governance obligations at a principles level. GCDMP is a narrower, CDM-function-specific practice reference that operationalizes what “good” data management looks like day to day, consistent with but more granular than GCP’s data-integrity expectations.

GCDMP vs. Electronic Data Capture (EDC): Practices vs. Tools

This is the distinction this term exists to make explicit. EDC describes the software category used to capture study data electronically at the point of collection — the technology layer. GCDMP describes the standard a CDM team’s processes should meet, regardless of which EDC platform (or CDMS more broadly) it happens to use. In practice:

• An EDC system can be configured well or poorly; GCDMP’s CRF/database-design and validation chapters give the practice benchmark for judging which.
• Two studies can run on the identical EDC platform and still differ sharply in whether their query-management, coding, or database-lock procedures meet GCDMP’s Minimum Standards or Best Practices tier.
• Buying or licensing a specific EDC/CDMS product is a technology decision; adopting GCDMP is a process/governance decision. A CDM department typically needs both, but they are not substitutes for one another.

Worked Examples

• CRF design against GCDMP’s Minimum Standards vs. Best Practices. A CDM team designing an eCRF for a new study consults GCDMP’s CRF/database design chapter. Meeting Minimum Standards means the eCRF fields map traceably to the protocol and statistical analysis plan, with basic edit checks in place. Meeting Best Practices additionally means the design underwent structured user-acceptance testing with documented sign-off before go-live, and reused a validated, previously piloted field library where possible — a higher bar the team can point to specifically because it maps to a named GCDMP tier, not because it happened informally.
• Discrepancy (query) management. A sponsor’s CDM SOP for handling data queries cites GCDMP’s discrepancy-management chapter, specifying query turnaround targets, documentation of query resolution rationale, and periodic query-metrics review against the chapter’s Best Practices tier. When an auditor or inspector asks how the CDM function’s query process was set, the SOP can point to a specific, citable external standard rather than an ad hoc internal convention.

Counter-Example

A small investigator-initiated study’s data manager resolves queries promptly and keeps a clean database, but the process was never written down against any named standard — there is no SOP referencing GCDMP chapters or tiers, just informal habit. The outcome may look similar day to day, but it is not “practicing to GCDMP” in the operational sense: there is nothing for an auditor, a new team member, or a future inspection to verify the process against, and no documented basis for the team’s claim that its practice meets a recognized minimum. Separately, a team that has simply purchased a well-regarded EDC platform is also not thereby “GCDMP-conformant” — conformance is a property of documented process, not of which software license the study holds.

Related Terms

• Electronic Data Capture (EDC) — the data-capture technology layer GCDMP-conformant processes typically run on; distinct from GCDMP itself.
• Case Report Form (CRF) — the data-collection instrument whose design GCDMP’s CRF/database chapter covers.
• ICH E6(R2) and ICH E6(R3) — the binding Good Clinical Practice guideline GCDMP’s process detail sits alongside.
• Clinical Data Management: Processes, Systems, and Standards — broader guide to the CDM function this term’s practice standard sits within.
• Clinical Data Management Tools — how EDC, CDMS, CTMS, eTMF, RTSM, and RBM fit together as the technology layer.
• Clinical Data Management Certification — covers the CCDM credential SCDM administers alongside GCDMP.
• Clinical Research Administration — this term’s parent topic cluster.

Frequently Asked Questions

Is GCDMP a regulation?

No. GCDMP is an industry practice standard published by SCDM, not a binding regulation. It is widely referenced by sponsor SOPs, CRO service specifications, and audit programs, and is consistent with binding sources like ICH E6 GCP and 21 CFR Part 11, but a sponsor is not legally required to adopt it by name the way it is required to comply with GCP.

Who publishes GCDMP, and is it free to access?

GCDMP is published and maintained by the Society for Clinical Data Management (SCDM), the professional body for the clinical data management field, which also administers the CCDM certification. Access terms (open chapters vs. member access) are set by SCDM directly at scdm.org and can change, so check SCDM’s own site for current access details rather than relying on a fixed rule here.

Does using an EDC system automatically mean a study follows GCDMP?

No. EDC is the software layer used to capture data; GCDMP is the practice standard for how the surrounding CDM process — CRF design, validation, query management, coding, database lock, and the rest — is documented and run. A study can use excellent EDC technology with a CDM process that doesn’t reference GCDMP at all, and vice versa in principle, though in practice mature CDM functions typically align both.

What is the difference between GCDMP’s “Minimum Standards” and “Best Practices”?

Minimum Standards is the baseline GCDMP considers necessary for defensible data management on essentially any study. Best Practices is a higher tier beyond that baseline, describing what a more mature, better-resourced CDM function should be working toward. Both are defined per chapter/topic area, not as a single blanket bar across the whole document.