What the CDI Pocket Guide Actually Is and Why People Keep Searching for It
Most people hitting this search term are either setting up a new clinical data workflow or scrambling to validate one before an audit. The CDI Pocket Guide — often styled as a quick-reference card for the Clinical Data Interchange standards — is exactly what it sounds like: a condensed mapping of element names, value sets, and formatting rules pulled from the longer CDISC documentation. It lives on the CDISC website and gets updated whenever standards change. You don't need to hunt for third-party mirrors if you know where to look. Go to cdisc.org, navigate to Standards > Downloads > Pocket Guides, and grab the latest PDF. There's no paywall, no account gate, no "request access" form. Just direct download. The file itself is usually around 2 to 4 megabytes depending on whether it bundles the full value set appendix. If you're doing data submission work, that appendix matters. If you're just checking element names, the front pages are enough. I've been pulling this guide since the 2014 revision cycle. The thing nobody tells you is that the Pocket Guide gets outdated faster than you'd expect between releases. I ran into a real problem last year when a sponsor's SDTM domain reference was built off the 2018 pocket guide, but the agency was accepting submissions against the 2021 update. A handful of value set codes had shifted. Specifically, the lab result status flags — they reorganized the hierarchy and renamed three of them. My team caught it during internal reconciliation, but it would have been a clean rejection at submission if we'd shipped without checking. The workaround was simple: I layered the current guide against the prior version using a diff tool, flagged the delta rows, and cross-referenced the official change log. Takes about twenty minutes if your dataset isn't massive.
Here's the nuance that trips people up: the Pocket Guide is not a standalone compliance document. It's a summary. The actual submission rules live in the full SDTM Implementation Guide and the metadata specifications. I've seen teams treat the Pocket Guide as authoritative and miss edge cases around derivation logic, especially for derived domains like AE and SUPPxx. The guide will tell you the element exists and what code set to use. It won't walk you through the derivation rules or the special handling for co-existing origin and derived records. Another common mistake is assuming the guide covers every domain equally. Some domains get abbreviated treatment because they're considered straightforward. Others like PM and EX have extensive footnotes and conditional applicability that the pocket format compresses heavily. If you're working primarily in pharmacology domains, you need the full implementation guide open beside the pocket reference. Don't skip it. The file itself is readable in any PDF viewer but works best when you open it in a program that supports text selection and search. I use a local search function to pull every instance of a specific domain code across the document. That's how you catch inconsistencies between sections that the formatting hides.
One more thing worth noting: there are older versions floating around on random sites claiming to be the latest. Check the revision date on the PDF metadata. If it's older than two years, verify it against the current release. The CDISC site stamps the revision clearly. Anything without that stamp is probably a cached copy someone archived and never updated. Using stale value sets in a submission is one of those quiet failures that shows up as a query cycle later. If you need something more interactive than a PDF, the CDISC website also offers XML-based reference files that some teams parse directly into their validation scripts. That's a separate download path but the same source material. I prefer the PDF for quick lookups and the XML when I'm building automated checks. Both are free, both require the same basic understanding of what you're validating against.
Get the Full Details
