| Course | DNP865 Healthcare Technologies and Informatics |
|---|---|
| Module | Module 6 |
| Paper type | Discussion post |
| Length | About 442 words |
| Format | Discussion post with APA 7 citations |
| School | Aspen University |
| Program | DNP |
| Updated | October 2026 |
Free sample paper for DNP865 Module 6
Module 6 Discussion: Initial Post
A Free Algorithm for Five Years of Records: Privacy, Security, and Fairness in a Data-Sharing Offer
Our health system was recently offered a free readmission-risk prediction tool by a technology company, on the condition that we share five years of de-identified inpatient records to help train and improve its models. The offer is attractive: we cannot afford to build such a tool ourselves, and readmissions carry penalties. But it raises three questions a DNP-prepared leader should insist on answering first.
Privacy. De-identified data can be shared under federal rules without patient authorization, but de-identification reduces risk rather than eliminating it, especially when detailed records are combined with other data sources a technology company may hold. Our patients did not expect their records to train a commercial product. Rosenbaum (2010) argues that data stewardship involves obligations beyond legal compliance, including transparency and accountability to the people the data describe, and she describes stewardship entities that balance the value of access against those obligations. A stewardship review should ask whether patients would reasonably expect this use, whether the contract forbids re-identification and resale, and whether the health system retains rights over derived models.
Security. Five years of records transferred to an outside company create a large target. The agreement should specify encryption in transit and at rest, access limited to named personnel, audit rights, breach notification timelines, and destruction of data at the end of the agreement.
Fairness. The deepest risk may be in the model itself. Obermeyer et al. (2019) showed that a widely used algorithm for identifying patients who need extra care exhibited significant racial bias: at a given risk score, Black patients were considerably sicker than White patients, because the algorithm predicted health care costs rather than illness, and unequal access means less is spent on Black patients. Correcting the bias would have raised the share of Black patients identified for additional help from 17.7 to 46.5 percent. An algorithm trained on our records will learn our inequities unless someone checks what it is actually predicting. Before adoption, the model's target, the variables it uses, and its performance across racial, ethnic, and insurance groups in our own population should be tested. Accuracy cannot be taken on trust either: when one widely implemented proprietary sepsis model was validated externally, it performed far below its developer's reported figures and missed most sepsis cases (Wong et al., 2021).
My recommendation would be to decline the offer as written and propose a counteroffer: a data use agreement with stewardship protections, security terms, and a requirement for local fairness testing before clinical use. Has anyone's organization accepted a similar arrangement, and what protections did it negotiate?
References
Obermeyer, Z., Powers, B., Vogeli, C., & Mullainathan, S. (2019). Dissecting racial bias in an algorithm used to manage the health of populations. Science, 366(6464), 447-453. https://doi.org/10.1126/science.aax2342
Rosenbaum, S. (2010). Data governance and stewardship: Designing data stewardship entities and advancing data access. Health Services Research, 45(5, Pt. 2), 1442-1455. https://doi.org/10.1111/j.1475-6773.2010.01140.x
Wong, A., Otles, E., Donnelly, J. P., Krumm, A., McCullough, J., DeTroyer-Cooley, O., Pestrue, J., Phillips, M., Konye, J., Penoza, C., Ghous, M., & Singh, K. (2021). External validation of a widely implemented proprietary sepsis prediction model in hospitalized patients. JAMA Internal Medicine, 181(8), 1065-1070. https://doi.org/10.1001/jamainternmed.2021.2626
What the DNP865 Module 6 instructions ask for
The Module 6 discussion in Aspen's DNP865 typically asks you to examine a privacy, security or data ethics issue in health care technology. Choose one concrete decision, such as a data-sharing offer or a new monitoring tool. Separate the issues: what the law permits, what patients would reasonably expect, how the data will be protected and whether the tool is fair and accurate. Use evidence for each, especially on algorithmic bias. Make a recommendation, which may be a conditional yes rather than a flat answer. Stay inside the length cap, close by asking peers something, and avoid naming a real company. In replies, add a contract term, a law or a case your classmates have not raised, since replies are graded on what they contribute.
How this DNP865 Module 6 example is built
The post opens with the offer and why it is attractive: no budget for a home-built tool and penalties for readmissions. It then frames three questions. The privacy paragraph explains that de-identified data can be shared under federal rules but can be re-identified when combined with other sources, and applies Rosenbaum's stewardship obligations. The security paragraph lists encryption, named access, audit rights, breach timelines and destruction at the end. The fairness paragraph reports Obermeyer's finding that fixing the algorithm's target would have lifted the proportion of Black patients flagged for added care to 46.5 percent from 17.7, and adds Wong's sepsis validation. The final paragraph declines the offer as written, proposes a counteroffer and asks classmates what protections their organizations negotiated.
DNP865 Module 6 rubric: what earns full marks
Discussion posts in DNP865 are graded on a defined issue, accurate use of law and evidence, a reasoned recommendation and engagement. This post earns credit by separating privacy, security and fairness instead of treating data ethics as one concern. Rosenbaum's 2010 article in Health Services Research supplies the stewardship argument, Obermeyer and colleagues' 2019 Science study supplies the bias evidence and Wong and colleagues' 2021 validation supports the warning about vendor claims. The recommendation is conditional, which graders read as judgment rather than caution or enthusiasm. The post stays within length while citing three sources, and its closing question asks for practical experience, which invites useful replies from classmates working in different systems.
DNP865 Module 6 help: mistakes that cost marks
Data ethics posts often say patient privacy is important and stop. Name the specific risk and the protection. Another common gap is assuming de-identification ends the privacy question; explain how records can be linked back to people. Students also skip fairness, which may be the largest risk in a prediction tool. Ask what the model predicts and test it across groups. Separate legal permission from ethical expectation. Give a recommendation, conditional if needed. Keep within the word count. Avoid naming a real vendor. In replies, bring a new protection or case rather than agreement. Finally, connect the post to the DNP role: someone with clinical and informatics knowledge should be at the table when the contract is negotiated.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
More DNP865 and DNP sample papers
- DNP865 Module 1: Data to Knowledge Paper
- DNP865 Module 2: Interoperability Failure Analysis
- DNP865 Module 3: Documentation Workflow Map
- DNP865 Module 4: Decision Support and Alert Fatigue Paper
- DNP865 Module 5: System Selection Paper
- DNP865 Module 7: Go-Live Plan
- DNP865 Module 8: Informatics Governance Recommendation
- DNP 899 Module 5: Leadership Development: Decisions and Conflicts
- DNP 830 Module 2: An Emerging Infection Expanding Its Range
- DNP 810 Module 6: Reading a Control Chart
- DNP 820 Module 3: A Federal Law and Advanced Practice
DNP865 Module 6 questions, answered
What does DNP865 Module 6 usually ask for?
The module's discussion often asks you to weigh privacy, security and ethical questions in the use of patient data, such as data sharing, secondary use or algorithms. Aspen does not publish module deliverables, so your classroom's instructions govern.
Can de-identified data be shared without patient permission?
Federal rules allow sharing of properly de-identified data without authorization, but re-identification risk remains, and stewardship principles call for transparency, contractual protections and consideration of patients' reasonable expectations.
How can an algorithm be racially biased without using race?
By predicting a proxy that reflects unequal access. A widely used algorithm predicted health care costs rather than illness, and because less was spent on Black patients, it underestimated their needs at the same risk score.
Where can I find a free DNP865 Module 6 sample paper?
The complete DNP865 Module 6 post is above, weighing a free readmission-risk tool offered in exchange for five years of de-identified records.
How can an algorithm be biased in a DNP865 data ethics post?
By predicting the wrong target. The study cited found an algorithm that predicted health care costs, not illness, so at any given score the Black patients it flagged carried more illness than the White patients.