NURS 6412 Week 9 Secondary Use Proposal Example

Course	NURS 6412 Information and Knowledge Management
Week	Week 9
Paper type	Secondary use proposal
Length	About 1,010 words, 6 pages
Format	APA 7 student paper
School	Walden University
Program	Master of Science in Nursing (MSN)
Updated	September 2026

Free sample paper for NURS 6412 Week 9

Proposal for Secondary Use of Documented Repositioning and Pressure Injury Data on Two Medical Units, With Every Element Justified

Student Name

College of Nursing, Walden University

NURS 6412: Information and Knowledge Management

Instructor Name

Month Day, Year

What this page is doingThe title promises a justification for every element, the discipline that keeps a data request small enough to approve.

Proposal for Secondary Use of Documented Repositioning and Pressure Injury Data on Two Medical Units, With Every Element Justified

1. Question

1.1 Among adult patients at risk of pressure injury on two medical units, is a longer documented interval between repositioning entries associated with a new hospital-acquired pressure injury during the stay? 1.2 The question is deliberately narrow. It asks about documented intervals, not about repositioning as care, and it concerns one outcome on two units over twelve months. Reusing data collected for care to answer questions about groups of patients is valuable and carries obligations to the patients whose records are used, which is why a formal framework for secondary use calls for transparency about purpose, data handling and oversight (Safran et al., 2007).

2. Elements Requested

2.1 Only the elements the question needs are requested. Each has one line of justification. A reviewer is more likely to approve a short, reasoned list than a request for everything.

Table 1

Elements Requested and Why Each Is Needed

Element	Why the question needs it
Study code (replacing record number)	Links a patient's entries without identifying the patient
Unit	Allows comparison between the two units' documentation practices
Admission and discharge dates, shifted	Defines each patient's time at risk
Braden scale total at admission and each reassessment	Defines the at-risk population and adjusts for risk over time
Repositioning entries with timestamps	The exposure: intervals between documented repositioning
Support surface documented	A likely confounder, since specialty surfaces change turning schedules
New pressure injury entries with stage and date	The outcome
Present-on-admission indicator for pressure injuries	Excludes injuries that did not develop during the stay
Age group in ten-year bands	Adjusts for age without exact birth dates

2.2 Not requested: names, addresses, exact dates of birth, diagnoses beyond pressure injury, notes and staff identifiers. Staff identifiers are excluded because the question concerns units and practice, not individual nurses.

3. Identifier Handling

3.1 The hospital's data analyst, who already has access for operational reporting, runs the extract. 3.2 Record numbers are replaced with study codes, and the key linking codes to record numbers is held by the analyst on a secure hospital drive, never sent to the project team. 3.3 All dates are shifted by a random number of days per patient, preserving intervals while removing calendar dates. 3.4 The project team receives only the coded, date-shifted file, stored on the hospital's approved research drive. 3.5 The key is destroyed when the analysis is complete and verified, no later than twelve months after the extract, and the destruction is recorded.

What this page is doingIdentifier handling says who holds the key, where, and when it is destroyed, which are the three questions a reviewer asks first.

4. Approvals

4.1 The first decision is whether this work is research or quality improvement, because it determines the approval route. Under the federal regulations for human subjects research, the regulation treats as research any systematic investigation intended to produce knowledge that applies beyond the setting studied (45 C.F.R. § 46.102). The same records can therefore fall under either route depending on what the team intends to do with the results, which is why intent must be stated before extraction rather than decided afterward. 4.2 If the aim is limited to improving practice on these two units, the work may be classed as quality improvement and reviewed by the nursing quality council and the privacy office. If the team intends to publish findings as knowledge applicable elsewhere, the institutional review board must decide whether the work is research and whether it is exempt. 4.3 This proposal anticipates publication and therefore requests an institutional review board determination before any data are extracted. 4.4 The data steward for nursing documentation must also approve the release, and the privacy office must confirm that the coded file meets the hospital's standard for a limited or de-identified dataset.

5. What the Record Can and Cannot Support

5.1 This section is the most important in the proposal, because the data were created for care, not for research. A repositioning entry shows that a nurse documented a turn at a time. It does not show that the turn happened at that time, that it relieved pressure effectively or that turns were not done and left undocumented. Busy shifts may produce fewer entries without fewer turns, which would bias the results toward finding an association where the true cause is workload. 5.2 Record data quality is usually judged on dimensions such as completeness, correctness and currency (Weiskopf & Weng, 2013). The team will report the proportion of shifts with no repositioning entry at all, which will indicate how complete the exposure data are. 5.3 The clinical evidence on repositioning frequency is itself uncertain. A Cochrane review of eight trials found the certainty of evidence on different repositioning frequencies to be low, with all studies at high risk of bias (Gillespie et al., 2020). This study cannot resolve that uncertainty; it can describe whether, on these units, longer documented gaps accompany new injuries. 5.4 Findings will therefore be reported as associations in documented practice, not as effects of repositioning, and will be shared with both units before any wider use.

6. Data Security and Access

6.1 Only the three members of the project team named in the approval will have access to the coded file. 6.2 The file will not be copied to personal devices, email or cloud storage outside the hospital's approved environment. 6.3 Analysis will be done on hospital-managed computers. 6.4 Any results shared outside the team will be aggregated so that no cell contains fewer than eleven patients, reducing the risk that an individual could be recognized from a small group. 6.5 A breach or suspected breach will be reported to the privacy office on the day it is discovered.

7. Dissemination

7.1 Results will first be presented to the staff and leaders of the two units, who produced the data and are best placed to judge whether the documented patterns reflect practice. 7.2 A summary will go to the nursing quality council with any recommendations. 7.3 If the institutional review board approves the work as research, a manuscript may be submitted for publication, describing the data source and its limits as set out in section 5.

References

Gillespie, B. M., Walker, R. M., Latimer, S. L., Thalib, L., Whitty, J. A., McInnes, E., & Chaboyer, W. P. (2020). Repositioning for pressure injury prevention in adults. Cochrane Database of Systematic Reviews, 2020(6), Article CD009958. https://doi.org/10.1002/14651858.CD009958.pub3

Protection of human subjects: Definitions, 45 C.F.R. § 46.102 (2024).

Safran, C., Bloomrosen, M., Hammond, W. E., Labkoff, S., Markel-Fox, S., Tang, P. C., & Detmer, D. E. (2007). Toward a national framework for the secondary use of health data: An American Medical Informatics Association white paper. Journal of the American Medical Informatics Association, 14(1), 1-9. https://doi.org/10.1197/jamia.M2273

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

NURS 6412 Week 9 instructions, in plain terms

For Week 9 the course usually wants a proposal to reuse clinical data for quality improvement or research, specifying the question, the data elements needed, how identifiers will be handled, what approvals are required and the limitations of the data. Many prompts ask you to justify each element and to distinguish research from quality improvement. Proposals typically run four to six pages in a structured format. Keep the question narrow so the element list stays short. Write the proposal as a document that would go to a committee, not as a request that has already been approved, and describe the data source as a composite. Name the approval route you expect.

Inside the NURS 6412 Week 9 example

Section 1 states the question and why it is deliberately narrow, citing a framework for secondary use. Section 2 gives a table of nine elements, each with one line of justification, and lists what is not requested, including staff identifiers. Section 3 sets out who runs the extract, how record numbers become study codes, how dates are shifted and when the key is destroyed. Section 4 explains the federal definition of research and the approval routes. Section 5 argues the limits of documented repositioning and cites the Cochrane review. Sections on security and dissemination complete the proposal. The table is kept short on purpose, and the proposal says so.

Where the marks sit in the NURS 6412 Week 9 rubric

Secondary use proposal rubrics usually score the clarity of the question, justification of data elements, protection of privacy, understanding of approvals, discussion of data limitations and writing. Element justification is often decisive: a short list with a reason for each scores better than a broad request. Privacy protection is judged on specifics, such as who holds the key and when it is destroyed. The approvals row rewards a correct account of research versus quality improvement. Limitations earn credit when they address how documentation differs from care. Writing covers the proposal format, tables and APA references. A dissemination plan that returns results to the staff who produced the data is credited in some sections.

Common NURS 6412 Week 9 mistakes, and how to avoid them

The most common loss is requesting everything in case it is useful, which invites a reviewer to decline. Another is treating de-identification as a single step without saying who holds the linking key. Some proposals assume quality improvement status to avoid review. Others ignore the gap between documented care and delivered care. Keep the question narrow, justify each element in one line, describe identifier handling in steps, state which approval route you expect and why, and spend real space on what the data can and cannot prove. Before submitting, ask whether a reviewer could approve the proposal without writing back with questions. If not, the missing answers belong in the document.

Get a NURS 6412 Week 9 example written to your instructions

Send the prompt, the rubric and the dataset your section named, whether that is pressure injury documentation, medication timing or screening completion. The desk writes the proposal around it, first one free, returned in 24-48h with an element table you can extend for your own question.

More NURS 6412 papers and MSN samples

NURS 6412 Week 9 questions, answered

Do I need actual approval to write this?

No. The assignment is the proposal itself, and the example is written as a document that would go to a committee rather than as one that already went. Real submissions require institutional processes that sit well outside a course. What the example does is name the route accurately, which is the part being assessed.

Can I propose reuse of data from my employer?

The example proposes reuse of a described dataset. A genuine proposal at work travels through channels that exist for it, and a classroom paper is not one of them. Writing the proposal against a composite dataset exercises exactly the same reasoning about elements, identifiers and limits without moving anything out of the organization that holds it.

What is the difference between research and quality improvement here?

It changes the approval route and often the publication path, and reviewers care about the distinction more than students expect. The example states which determination it anticipates and gives its reasoning in three sentences. Getting the classification wrong is a substantive error, not a formatting one, so most rubrics treat it as content.

Where can I find a free NURS 6412 Week 9 sample paper?

All seven numbered sections of the proposal, with the element table and references, are shown free on this page. A custom proposal for the question and data your section assigns can be written by the desk at no cost.

How do I decide if my NURS 6412 proposal is research or quality improvement?

Look at intent. Work designed to produce knowledge that applies beyond your setting usually counts as research; work aimed only at improving local practice may be quality improvement. When in doubt, the proposal should request a determination.

NURS 6412 Week 9 secondary use proposal example