| Course | DNP 966 Project Continuation I-VIII |
|---|---|
| Topic | Topic 3 |
| Paper type | Data integrity report |
| Length | About 1,040 words, 4 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DNP |
| Updated | September 2026 |
Free sample paper for DNP 966 Topic 3
Two Systems, One Variable Name: A Data Integrity Report on Fracture Liaison Records Held Across a Record System Replacement
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
DNP-966: Project Continuation I
Topic 3 Assignment
[Instructor Name]
February 10, 2030
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Two Systems, One Variable Name: A Data Integrity Report on Fracture Liaison Records Held Across a Record System Replacement
What Was Collected Before the Extension
Data for the fracture liaison project were collected in three periods, and the records from each are reported separately because they came from different places. The baseline period, the 12 months before launch, produced 612 eligible patients from the orthopedic group's original record system. The first implementation period, June 24 to August 4, 2029, produced 148 enrolled patients from the same system. The second implementation period, from October 18, 2029, when access was restored, to January 31, 2030, has produced 97 patients from the health system's record, extracted by its analytics office. Between August 5 and October 17 the pathway kept running in the clinics, but no data were collected, and the 61 patients the nurse's log shows were seen in that gap will be recovered in one extraction or reported as missing.
Holding data for a long project is not the same as holding it safely. Records collected for one purpose in routine care carry errors and gaps that only appear when they are reused, and the longer they sit the more ways they can drift from what they claim to record (Hersh et al., 2013). This report therefore accounts for every record before any further analysis is done.
Custody: Where Each Set Is Held and Who Can Reach It
Table 1 records where each data set sits, who can open it and when a verified copy was last made.
Table 1
Custody and Copies of Project Data
| Data set | Where held | Who can reach it | Last verified copy |
|---|---|---|---|
| Baseline, 612 patients | University secure drive, project folder | Student and chair | January 20, 2030 |
| Implementation 1, 148 patients | University secure drive; second export on the student's personal laptop | Student and chair; laptop copy, student only | January 20, 2030 |
| Implementation 2, 97 patients | Health system analytics workspace, copy on university secure drive | Student, analytics office, chair | February 3, 2030 |
| Nurse call log | Paper binder at main clinic, scanned monthly | Fracture clinic nurses, student | January 31, 2030 |
The Laptop Copy
One export exists outside approved storage. In July 2029, before the system change, I exported the first implementation data to my own laptop to work on it during travel, intending to delete it afterward. I did not, and I found it while preparing this report. The file is encrypted by the laptop's disk encryption, but a personal device is not where the site agreement allowed project data to be kept. I have reported it to my chair, confirmed that the secure drive copy is identical by comparing record counts and a checksum, and deleted the laptop copy on February 4. It is listed here as a risk that existed for seven months, not as a risk that never occurred.
Reconciliation Against the Collection Log
The nurse's log and the extracted records were compared patient by patient for the first implementation period. The log lists 151 enrolled patients; the extract contains 148. Three patients appear in the log and not in the extract. Rather than adopting the larger figure, I traced each one. Two had fractures recorded under a different diagnosis code, a code for fracture of the lower end of the radius that the original extraction did not include, and they meet the eligibility criteria; they will be added. The third was a patient the nurse enrolled and later found to have a high-energy injury from a motor vehicle crash, which excludes him; the log was not corrected at the time. The corrected count for the first period is therefore 150.
Reconciliation for the second period is not yet complete because the limited data set removes the record numbers the log uses. The analytics office has agreed to run the match on its side and return only the count of discrepancies, which keeps identifiers inside the health system.
A Field Whose Definition Changed
Two variables kept their names across the system replacement and changed their meaning. The first is the outcome. In the original system, a field labeled scan completed was set when the scan was ordered and scheduled; in the health system's record, a field with the same label is set only when a result is filed. Under the old definition, a patient who was scheduled but never attended counted as completed. When I checked the baseline data against the imaging schedule, 9 percent of scans marked completed had never been performed. Pooling the two periods would compare an inflated baseline with an accurate follow-up and understate the pathway's effect.
The second is the fracture mechanism. The original system recorded mechanism as a coded choice between low-energy and high-energy injury. The new system records it as free text, and about one note in five does not describe the mechanism at all. Measurement changes of this kind are an instrumentation threat to any before-and-after comparison (Shadish et al., 2002). Data quality work treats them as a problem of concordance between what a field is said to hold and what it actually holds (Weiskopf & Weng, 2013).
How Each Side of the Change Will Be Handled
Records either side of August 5 will not be pooled on the old definitions. For the outcome, every baseline and first-period record will be rederived from the imaging schedule, so that a completed scan means a performed scan in all three periods. For mechanism, the second-period records will be classified by two readers using a written rule, with disagreements settled by the fracture clinic nurse, and records with no mechanism described will be reported as unclassified rather than assumed to be low-energy.
What the Current Holdings Can Still Support
The holdings still support the primary comparison, completion within 16 weeks before and after the pathway, once the outcome is rederived and the missing gap months are recovered or declared. They support a subgroup comparison by clinic for the first period but not the second, because the limited data set does not carry the clinic field reliably. They no longer support the planned analysis of outside scans after October, which the approval review for this course already described. The final report will list each planned comparison, whether it was run, and why any the data could not bear were dropped.
References
Hersh, W. R., Weiner, M. G., Embi, P. J., Logan, J. R., Payne, P. R. O., Bernstam, E. V., Lehmann, H. P., Hripcsak, G., Hartzog, T. H., Cimino, J. J., & Saltz, J. H. (2013). Caveats for the use of operational electronic health record data in comparative effectiveness research. Medical Care, 51(8 Suppl. 3), S30-S37. https://doi.org/10.1097/MLR.0b013e31829b1dbd
Shadish, W. R., Cook, T. D., & Campbell, D. T. (2002). Experimental and quasi-experimental designs for generalized causal inference. Houghton Mifflin.
Weiskopf, N. G., & Weng, C. (2013). Methods and dimensions of electronic health record data quality assessment: Enabling reuse for clinical research. Journal of the American Medical Informatics Association, 20(1), 144-151. https://doi.org/10.1136/amiajnl-2011-000681
The DNP-966 Topic 3 assignment instructions
Topic 3 in DNP-966 asks the student to show that the data collected so far are still complete, secure and usable after the delay. The instructions look for an inventory of the holdings by collection period, a statement of where each data set is stored and who can access it, and a check of the records against the original collection log. Students are also asked to consider whether anything about the data changed while the project was paused, such as a system upgrade or a change in how a field is recorded. The paper ends by stating what analyses the current data can still support, which links it to the revised timeline later in the course.
How this DNP 966 Topic 3 example is built
The example accounts for every record before trusting any number computed from it. Holdings are counted by period and source, and a custody table gives location, access and the last verified copy for each set. A laptop export kept outside approved storage for seven months is named as a risk that existed, compared with the secure copy by checksum and deleted. The reconciliation traces three missing patients one by one, adding two and excluding one. Two variables are shown to have changed meaning at the system replacement, the scan outcome and the fracture mechanism, and the paper explains how each side of the change will be handled before closing on what the data still support.
Where the marks sit in the DNP 966 Topic 3 rubric
GCU faculty grade this report on whether each claim about the data can be checked. Excellent work counts records by period and source rather than giving one total, and it records custody with access and copy dates. The reconciliation criterion is met when discrepancies are traced individually rather than settled by taking the larger number. The rubric gives weight to finding definition changes by testing a field against an independent source, since a label can stay the same while its meaning shifts. Handling rules for records on either side of the change should be stated before analysis begins. The closing statement on supported analyses completes the paper.
DNP 966 Topic 3 help before you submit
Reports asserting that the data is secure and complete, with nothing behind the assertion, are the weakest version and the easiest to test. A second failure is pooling records either side of a definition change, which produces a variable meaning two things and a comparison meaning nothing. Marks also go for custody described without access, since who can reach a set matters as much as where it physically sits. Reconciliations reporting only a total conceal the records appearing in one source and not another. A single copy on a personal device is a risk whether or not it has yet caused trouble. Holdings reported with no statement of what they support leave a reader unable to judge.
Get a DNP-966 Topic 3 example written to your instructions
Send the DNP-966 Topic 3 assignment instructions and the rubric your classroom posts, with any data management plan your section requires. We write a custom example to those criteria, with holdings counted by period, custody recorded and a definition change traced through the affected records, in 24 to 48 hours. The first one is free.
More DNP 966 papers and DNP samples
- DNP 966 Topic 1: Extension Justification
- DNP 966 Topic 2: Approval Currency Review
- DNP 966 Topic 4: Site Continuity Report
- DNP 966 Topic 5: Delay Confounding DQ Pair
- DNP 966 Topic 6: Revised Timeline
- DNP 966 Topic 7: Changed Conditions Analysis
- DNP 966 Topic 8: Completion Plan
- DNP 801A Topic 3: Primary Study Collection
- DNP 965A Topic 3: Bounded Interpretation Section
- DNP 805 Topic 3: Decision Support Evaluation
- DNP 960A Topic 3: Fidelity Monitoring Plan
DNP 966 Topic 3 questions, answered
Why would data integrity change during an extension?
Because time acts on systems and on people. Source definitions get revised, staff with access move on, a laptop is replaced, and an export made eighteen months ago sits somewhere nobody has verified since. None of that is negligence, and all of it is discoverable now rather than during the final analysis when the position is much harder to repair.
Do you handle, store or analyze the data itself?
Never, under any arrangement. The records were collected by you under permissions issued in your name, they belong to your site and your doctoral project, and they are not sent here. A sample can only illustrate the written report built around holdings you already have: how counts get reconciled, and how a definition change is disclosed rather than absorbed.
What do I do about a field that was redefined?
Report where the change falls, keep the two periods apart until you can show they are comparable, and say what you did. Pooling them silently is the version that fails, because the resulting variable carries two meanings and no reader can tell which applies. If the definitions reconcile, show the working rather than asserting equivalence.
Where can I find a free DNP 966 Topic 3 sample paper?
This page contains the complete data integrity report, including counts by period, the custody table, the laptop copy, the three-record reconciliation and the two redefined fields. A free model report for your own project is available on request.
How was the changed field found in DNP 966 Topic 3?
By checking baseline records marked as scan completed against the imaging schedule, which showed that 9 percent had never been performed. The old system set the field at ordering and the new one at result, so the same label measured two different things.