| Course | DNP 966 Project Continuation I-VIII |
|---|---|
| Topic | Topic 1 |
| Paper type | Extension justification |
| Length | About 1,090 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 1
Four Delays, Two Still Running: An Extension Justification for a Nurse-Led Fracture Liaison Project, Measured Against the Original Milestones
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
DNP-966: Project Continuation I
Topic 1 Assignment
[Instructor Name]
January 13, 2030
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Four Delays, Two Still Running: An Extension Justification for a Nurse-Led Fracture Liaison Project, Measured Against the Original Milestones
The Project as Approved
The project approved in DNP-955 tested whether a nurse-led fracture liaison pathway would raise the share of adults aged 50 and older who complete a bone density scan or start osteoporosis treatment within 16 weeks of a low-trauma fracture seen at a four-clinic orthopedic group. The pathway had three parts: a fracture clinic nurse screened each day's list for eligible wrist, proximal humerus and vertebral fractures, ordered a scan under a standing protocol, and sent the primary care provider a letter with the result and a treatment recommendation, followed by a telephone call at 12 weeks. Models in which a coordinator identifies patients and arranges testing, rather than only telling them they need it, have produced the largest gains in testing and treatment after fracture (Ganda et al., 2013). The baseline, drawn from the 12 months before launch, was 14 percent. The comparison was the same practice before and after, with implementation planned from April through September 2029 and the final report due at the end of DNP-965A in December 2029. Everything that follows reports against that paragraph.
Four Causes, Each With the Time It Consumed
Four causes delayed the work, and they did not cost the same amount of time. Table 1 lists them with the period each consumed and the evidence for it.
Table 1
Causes of Delay, Time Consumed and Current Status
| Cause | Period consumed | Evidence | Status now |
|---|---|---|---|
| Site determination and data use agreement | About 5 months (planned 2) | Committee minutes, email thread with dates | Resolved |
| Record system replacement and loss of access | About 11 weeks without usable data | Go-live notice, access termination, analytics ticket | Still operating: field definitions changed |
| Closure of the east clinic scanner | Ongoing since September 2029 | Imaging consolidation memo, scheduling reports | Still operating: longer waits |
| Family leave | 6 weeks | Leave approval, chair's agreement | Resolved |
The approval took five months instead of the two I had planned. The orthopedic group had never received a quality improvement determination request from a student, so its quality committee referred the question to the group's attorney, who asked for a data use agreement that the university's template did not cover. The committee's minutes and my correspondence date each step. Launch moved from April to late June 2029, which by itself would have pushed the final report into the following term.
The data source changed owners. In July 2029 a regional health system acquired the orthopedic group, and on August 5 the group's electronic health record was replaced by the health system's. The report I had used to identify eligible fractures stopped existing overnight, and my access ended with it. Rebuilding the extraction through the health system's analytics office took until October 18.
The satellite scanning service closed. The group's bone density scanner at its east clinic, which had handled about 40 percent of scans, was retired in September when the health system consolidated imaging at its main campus. Wait times for a scan rose from about 9 days to about 31 days, and patients from the east clinic now travel 22 miles further.
I took six weeks of family leave from October 21 to December 1, 2029, arranged with my chair and the practice in advance.
Causes Still Operating and Causes Resolved
Two of the causes are finished and two are not, and only the second pair bears on the remaining work. The approval is complete and the leave is over; neither will affect anything from here. The record system replacement is still operating because two fields changed meaning when the system changed. In the old record, a scan counted as done when it was ordered; in the new one, it counts only when a result is filed. The fracture mechanism field, which I used to separate low-trauma from high-trauma injuries, became free text. Any comparison across August 2029 has to deal with both changes, and the data integrity report for this course will say how. The scanner closure is also still operating: longer waits push some scans past the 16-week window, which works against the pathway for reasons unrelated to whether it works.
Completion Against the Original Milestones
Against the milestones approved in DNP-955, the project is about four months behind. The baseline data collection and the literature synthesis are finished. Staff training is finished, and the pathway has run since June 24, 2029. Implementation data are partial: 148 eligible patients were enrolled before the system change and 97 since access was restored, against a planned total of about 300 for the six months. The analysis has not begun, and neither has the final report. Measured against the original schedule rather than a redrawn one, three of seven milestones are complete, one is partial and three have not started.
The extension also has costs beyond time. The implementation period now spans two record systems, two imaging arrangements and the winter months, when fracture volumes rise with icy conditions. A before-and-after comparison is weaker than it would have been under the original schedule, and the final report will have to say so rather than treat the extra months as more data of the same kind. Evidence that liaison services raise testing and treatment after fracture still holds (Wu et al., 2018), but the local comparison that tests them has become less clean.
The Decision That Would Have Prevented It
One decision, taken earlier, would have prevented most of this extension. I waited for the university's approval before asking the orthopedic group for its own determination, because I assumed the second would follow quickly from the first. Submitting both requests in the same month would have exposed the data use agreement problem in the autumn instead of the spring, and launch would probably have happened in April as planned. The acquisition and the scanner closure were outside my control, but a project that launched on time would have completed most of its enrollment before either took effect.
A second lesson concerns data. I built the extraction on a report that belonged to the practice's old system, and I never asked who would own it if the practice changed hands. Rates of evaluation after fracture have been low for years (Solomon et al., 2014), which is why the project is worth finishing, but a project that depends on one report needs a backup plan for that report. The remaining work, described in the revised timeline for this course, uses the health system's analytics office as its only data source, and it records who owns each step.
References
Ganda, K., Puech, M., Chen, J. S., Speerin, R., Bleasel, J., Center, J. R., Eisman, J. A., March, L., & Seibel, M. J. (2013). Models of care for the secondary prevention of osteoporotic fractures: A systematic review and meta-analysis. Osteoporosis International, 24(2), 393-406. https://doi.org/10.1007/s00198-012-2090-y
Solomon, D. H., Johnston, S. S., Boytsov, N. N., McMorrow, D., Lane, J. M., & Krohn, K. D. (2014). Osteoporosis medication use after hip fracture in U.S. patients between 2002 and 2011. Journal of Bone and Mineral Research, 29(9), 1929-1937. https://doi.org/10.1002/jbmr.2202
Wu, C.-H., Tu, S.-T., Chang, Y.-F., Chan, D.-C., Chien, J.-T., Lin, C.-H., Singh, S., Dasari, M., Chen, J.-F., & Tsai, K.-S. (2018). Fracture liaison services improve outcomes of patients with osteoporosis-related fractures: A systematic literature review and meta-analysis. Bone, 111, 92-100. https://doi.org/10.1016/j.bone.2018.03.018
DNP 966 Topic 1 instructions, in plain terms
Topic 1 of DNP-966 asks the student to explain why the project needs continuation and where it stands. The instructions look for a short restatement of what was approved, an honest account of what delayed the work and a status report against the milestones set in the proposal. Faculty want to see that the student understands the delay well enough to prevent it from repeating, so the account should include causes the student controlled as well as those that came from the site. Evidence for each cause, such as dated minutes or correspondence, belongs in the paper, and the tone should be factual rather than apologetic.
How this DNP 966 Topic 1 example is built
The finished example accounts rather than reintroduces. One paragraph establishes what the project set out to do, and everything after it reports against that paragraph. Four causes of the delay are listed with the period each consumed: an approval that took five months, a data source that changed owners, a service closure, and the writer's own leave. Two remain in force and two have resolved, which the example distinguishes because only the first pair bears on what comes next. Completion is measured against the original milestones rather than against a schedule quietly redrawn to improve the position. A short passage names the decision that, taken earlier, would have prevented the extension entirely.
Reading the DNP 966 Topic 1 rubric
GCU's rubric rewards an account a chair can verify. Papers in the Excellent column attach a period of time to every cause and back it with evidence, so a five-month approval is not weighed the same as a six-week leave. The rubric also looks for the split between causes that still constrain the work and those that do not, since only the first group affects the plan ahead. Completion earns credit when it is measured against the milestones approved in the proposal rather than a redrawn schedule, with each milestone marked complete, partial or not started. The final criterion is reflection: naming a decision the student could have made differently shows doctoral judgment.
DNP 966 Topic 1 help: mistakes that cost marks
The characteristic failure of this course arrives immediately: a first submission describing the project as proposed and never saying where it currently stands. A second weakness is attributing the delay to circumstance alone, when at least one cause usually traces to a decision the writer took or deferred. Marks also go for progress measured against a revised schedule, since a plan redrawn after the slippage conceals the size of it. Causes listed with no period attached cannot be weighed against one another. Constraints still in force, reported beside resolved ones, mislead a reader about what the remaining work faces. An account with nothing learned reads as an application for more time.
Get a DNP-966 Topic 1 example written to your instructions
Send the DNP-966 Topic 1 assignment instructions and the rubric your classroom posts, with your original milestone schedule. We write a custom example to those criteria, with causes separated by period and status and completion measured against the original plan, in 24 to 48 hours. The project itself, its data and its approvals are yours and are never produced here. The first one is free.
More DNP 966 papers and DNP samples
- DNP 966 Topic 2: Approval Currency Review
- DNP 966 Topic 3: Data Integrity Report
- 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 1: Doctoral Expectations Paper
- DNP 965A Topic 1: Prespecified Analysis Report
- DNP 805 Topic 1: Informatics Competency Analysis
- DNP 960A Topic 1: Site Readiness Report
DNP 966 Topic 1 questions, answered
Does admitting my own role in the delay hurt me?
It helps, provided the account stays specific. Faculty read a continuation report knowing that most projects run long for a mixture of external and personal reasons, and an account naming only external ones invites the question of what the writer could have controlled. One decision identified honestly carries more weight than a page of institutional obstacles.
How much of the original proposal belongs here?
Enough to orient a reader and no more, which in many sections means a paragraph. The temptation is to restate the plan at length because it is already written and reads well. What the assignment asks for is the position relative to that plan, so every page spent reintroducing the project is a page not spent reporting.
What if the delay had no single cause?
Most do not, and the useful move is to give each contributor the period it consumed instead of blending them into a general account of difficulty. Four causes with durations attached let a reader see which mattered and which were absorbed. A narrative in which everything simply took longer supports no judgment about what happens next.
Where can I find a free DNP 966 Topic 1 sample paper?
This page holds the full extension justification, with the approved scope in one paragraph, four causes of delay with their durations, a milestone check and the decision that would have prevented the delay. A version built on your own project can be requested free.
How long is the DNP 966 Topic 1 example?
About 1,090 words over four pages in APA 7 format, with a table of causes, the time each consumed and whether it still operates. Three references support the points about liaison models and treatment gaps after fracture.