Clinical Registry Data Submission Pack
Three documents and three sheets that check every required field against the registry's current specification before you submit, not after it rejects the batch.
Free download · No account needed
Completeness Check, screening view
Seven of 84 records are wrong in the same field
Illustrative rows for a fictional ambulatory surgical center, Cobalt Ridge Surgical Center, reporting colon-surgery infection surveillance to CDC NHSN for the quarter.
| Record ID | Field Checked | Value Charted | Result |
|---|---|---|---|
| CR-Q1-2026-014 | Wound Class | Clean | Needs Correction |
| CR-Q1-2026-027 | Wound Class | Clean | Needs Correction |
| CR-Q1-2026-033 | Wound Class | Clean | Needs Correction |
| CR-Q1-2026-003 | Wound Class | Clean-Contaminated | Pass |
Clean is not a valid wound class for a colon procedure under NHSN's own rule, since entering the gastrointestinal tract is never truly clean. Seven of Cobalt Ridge's 84 COLO records were charted that way this quarter. Caught before submission, all 84 stand in the denominator and the rate reads 5.95 percent. Left in, the same 5 infections divide into 77 instead of 84: 6.49 percent, from one field.
Remaining columns: ASA Physical Status, Diabetes, Duration, Corrective Action, Corrected By.
Every clinical registry publishes a specification: a defined set of required fields, a valid-value rule for each one, and a denominator built the registry's own way, not the convenient way. Almost every facility treats that specification as something read once at enrollment and followed from memory afterward. It does not stand still. NHSN republishes its Outpatient Procedure Component manual every January as a new, separately dated document. A checklist read from last year's version and never reopened against the new one is unverified the moment it publishes, changed or not.
A field that is filled in is not the same as a field that is valid, and that gap is where most rejected submissions come from. NHSN's own rule states plainly that the application does not offer Wound Class Clean as a choice for colon surgery and six other categories, since entering the gastrointestinal tract is never truly clean. A record charted that way reads complete on a check that only asks whether the field holds something. This pack runs the check first, so the record returns for correction while the cycle is open.
At Cobalt Ridge Surgical Center, a fictional surgical center, 84 colon-surgery procedures were eligible for infection surveillance in a quarter, and 7 were charted wound class Clean, invalid for that category under NHSN's rule. Caught before submission, all 84 stand in the denominator and the rate reads 5.95 percent. Left uncorrected, the specification excludes the 7 from the denominator. The same 5 true infections then divide into 77 instead of 84, and the reported rate reads 6.49 percent, 9.1 percent relatively higher, from one required field wrong on 8.3 percent of the batch.
What's in the pack
Required Field Register
Every required field for the current specification version, its valid-value rule per category, the exact chapter it was read from, and the date it was last checked against the registry's own published version. The same version-and-date discipline applies whether the register covers a registry field or a clinical trial site's essential document.
Completeness Check
Every record in a submission batch run against the register before the batch leaves the building, flagged by the exact field and rule it failed rather than a generic incomplete mark. Where a miscode traces back to a charting habit rather than a one-off, a clinical documentation gap review counts it across the whole record instead of just this registry's own denominator.
Submission Log
Every cycle's denominator, numerator, pre-submission completeness result and the specification version it was checked against, so a clean cycle and a corrected one are both on the record. The same before-submission discipline applies whether the registry is disease-specific or the qualified registry a MIPS measure names as its own collection type.
Submission Procedure
The step-by-step sequence this facility actually follows, from where each field is captured and by whom, to who has authority to release a batch once it clears the check and how a post-submission finding gets logged.
Data Definition Note
Where the specification leaves a judgment call to facility policy, such as who assigns a field the registry itself does not define, this is where that policy gets written down, dated, and checked against the current specification.
Validation Approach
How the facility confirms a value is actually true, not just present, through internal sampling on a stated schedule and, where a count is generated electronically, a manual cross-check against it before the electronic count is trusted alone.
Submission Deadline and Completeness Watch
A periodic pass that ranks any flagged record by how little of the reporting cycle is left to fix it, and separately flags any register row whose specification version predates the registry's current one. Where a payer's own value-based contract requires this registry's outcomes as a term of payment, a value-based contract performance review reads what a clean submission is actually worth once a reconciliation statement arrives.
How to use it
- 1
Open the pack, or download it
Open the pack in River and send the registry's current specification directly, or download the blank Word and CSV files and build the register from the manual on your own.
- 2
Send a real extract
The agent runs your most recent cycle's actual records against the register, not a hypothetical batch, and returns which ones fail a rule and on which exact field.
- 3
Correct while the cycle is open
Every flagged record names the field, the rule it failed, and the register row to check the correction against, with enough of the cycle left to fix it and re-check it.
- 4
Submit, log the version, repeat
Log the specification version the batch was checked against on the Submission Log, and the watch flags the register again the moment the registry publishes a newer one.
Frequently asked questions
Is this template free?
Yes. Download the three documents and three sheets as Word and CSV files with no signup and no card. "Edit with AI" is a separate, optional path for facilities that want the agent to build the register from their own specification. The rest of the library is at the template library.
What format are the downloaded files?
Word documents (.docx) for the Submission Procedure, the Data Definition Note and the Validation Approach, and CSV (.csv) for the three sheets, zipped into one download. They open natively in Word, Pages, Google Docs, Excel, Numbers and Sheets.
Why version-stamp the register instead of fixing it when something breaks?
Because a break is a submission that already went out wrong. NHSN republishes its Outpatient Procedure Component manual every January as a new, separately dated document, and a rule can change between versions with no announcement to anyone not reading the new one. A dated register row is treated as unverified the moment a newer version publishes, whether or not it actually changed.
Does the Completeness Check replace the registry's own validation?
No, and it answers a different question. Completeness asks whether a field is present and holds a valid value; it says nothing about whether that value is true. NHSN recommends internal validation annually, at minimum, re-abstracting a sample of records from source documentation and comparing each one against what was originally entered.
What if the specification leaves who assigns a field unclear?
That is what the Data Definition Note resolves and dates, rather than guesses at. NHSN's own manual leaves wound class assignment to facility policy, so this pack records which role assigns it and when that policy was last confirmed accurate, instead of treating "we all know how we do it" as a definition.
Is a rejected submission the only cost of an outdated register?
No. NHSN's own Annual Facility Survey is due March 1 each year, and after that date a facility cannot open a new Monthly Reporting Plan until the survey is complete. A correction backlog and an open survey can compound on the same date, blocking more than the one flagged record.
What if a submitted rate needs to actually improve, not just report correctly?
That is a different project from this pack, and a good next step once a submission is clean. A quality improvement project template freezes a baseline before testing a change to the underlying rate, then checks each new period against it with the same run-chart discipline this pack applies to registry versions rather than trend lines.
Check the register before the registry does
Download the blank pack as Word and CSV files, or open this exact pack in River and let the agent build the Required Field Register directly from your registry's current specification.
Edit with AI