| Course | HLTH 8136 Leadership, Professionalism, and Ethics in Public Health Practice |
|---|---|
| Week | Week 4 |
| Paper type | Position paper |
| Length | About 1,080 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | PhD in Public Health |
| Updated | October 2026 |
Free sample paper for HLTH 8136 Week 4
Decline the Identifiable Transfer, Offer Aggregates and Put It in Writing: A Position on a County Executive's Request to Load Partner Services Records Into a Shared Data Warehouse
Student Name
Walden University
HLTH 8136: Leadership, Professionalism, and Ethics in Public Health Practice
Instructor Name
Month Day, Year
Decline the Identifiable Transfer, Offer Aggregates and Put It in Writing: A Position on a County Executive's Request to Load Partner Services Records Into a Shared Data Warehouse
Ruling
The health department's data steward should decline to transfer identifiable partner services records into the county's shared data warehouse, offer aggregate and de-identified data that meet the executive's coordination goals, and record the refusal and the offer in writing. The obligation that governs is confidentiality of information that can harm individuals or communities if disclosed. The obligation that yields, in part, is the duty to cooperate with elected leadership in building integrated services. It yields only in part, because the steward's offer of aggregate data honors that duty as far as confidentiality allows.
The Request
The county executive's office, drawn as a type rather than a portrait of any real official, is building a data warehouse that several county departments use for coordinated case management: housing, social services, behavioral health and corrections. The executive has asked the health department to load client-level records from its partner services program. Partner services is the public health work of contacting people diagnosed with HIV or other sexually transmitted infections, eliciting the names of sexual or needle-sharing partners, and notifying those partners confidentially so that they can be tested and treated. The records contain diagnoses, partners' names and contact details, and notes from sensitive conversations. The executive's office argues that merged records would help case managers serve people with complex needs and avoid duplicated effort.
The Obligations
Two obligations conflict. The first is confidentiality. One of the field's ethical practice principles commits agencies to the rule that public health institutions should protect the confidentiality of information that can bring harm to an individual or community if made public, with exceptions justified only by a high likelihood of significant harm to the individual or others (Thomas et al., 2002). Partner services data fit that description precisely: disclosure of an HIV diagnosis or a list of sexual partners can bring stigma, discrimination, loss of housing or employment and, in some cases, violence. The second obligation is cooperation. A health department is part of county government, answers to elected leadership and shares its goal of serving residents with complex needs well. The Principles also call on public health to collaborate in ways that build public trust (Thomas et al., 2002).
Why Confidentiality Governs
Three reasons lead to the ruling. First, the purpose of the data. Partner services work depends on people naming partners to a public health worker under a promise that the information will be used only to notify and protect those partners. Lee and Gostin (2009) argued that ethical use of public health data requires that information collected for public health purposes be used for those purposes, with strong protections against use for other ends. Loading the records into a warehouse used by corrections and social services would use them for purposes the people who gave them were never told about.
Second, the consequences for the program. Fairchild and Bayer (2004) described how public health surveillance has long depended on public confidence that the state will not turn health information against the people it concerns. If clients learn that partner names may reach other agencies, fewer will name partners, and the program's ability to find and treat infections will fall. The harm would not stay within the program; untreated infections spread.
Third, the justificatory conditions for infringing a public health value. Childress and colleagues proposed that infringing a general moral consideration such as privacy requires showing effectiveness, proportionality, necessity, least infringement and public justification (Childress et al., 2002). The executive's goal fails the necessity and least-infringement tests. Coordinated case management can be supported without identifiable partner data: aggregate figures can show where needs cluster, and individual clients can consent to share their own information with their case managers.
What the Steward Offers Instead
The ruling is not a refusal to help. The steward should offer three things. The first is aggregate data, such as counts of new diagnoses by area and by broad demographic group, suppressed where cells are small enough to identify individuals. The second is a referral pathway: partner services staff can ask clients whether they want help with housing or other services and, with written consent, connect them directly to a case manager. The third is a standing meeting with the warehouse team to identify other health department data that could be shared without identifying anyone. These offers meet much of the executive's goal while keeping the promise made to clients.
Putting It in Writing
The refusal should be written. A memo to the health director, copied to the executive's office through the director, should state the request, the decision, the reasons and the offer. Writing protects the steward from later claims that the department was uncooperative, gives the executive's office a clear account it can respond to, and creates a record that the next steward can follow. If the executive pursues the request through the county attorney, the memo becomes the department's first statement of its position. It also matters inside the department. Partner services staff need to know that their promise to clients has been defended at the top, because they are the ones who will ask the next client to name a partner, and their confidence shapes how that conversation goes.
Objection: Elected Leadership Decides
The strongest objection is that the executive is elected and the steward is not. In a democracy, should a staff member's ethical view override an elected official's policy decision? The answer is that the steward is not overriding a policy decision. The steward is declining to carry out one part of a request in a way that would breach a specific confidentiality promise, while offering to carry out the rest. If the executive believes identifiable sharing is justified, the proper route is a public decision, with legal review and notice to clients, not a data transfer arranged between staff. That route meets the condition of public justification that the steward's refusal protects.
Limits
This paper does not analyze the specific privacy laws that apply, which vary by state and would need legal review. It assumes that the warehouse lacks protections strong enough to keep partner data within public health use; a warehouse with strict role-based access might change the analysis for some fields. It also assumes that clients were promised confidentiality, which is standard in partner services but should be confirmed.
References
Childress, J. F., Faden, R. R., Gaare, R. D., Gostin, L. O., Kahn, J., Bonnie, R. J., Kass, N. E., Mastroianni, A. C., Moreno, J. D., & Nieburg, P. (2002). Public health ethics: Mapping the terrain. Journal of Law, Medicine & Ethics, 30(2), 170-178. https://doi.org/10.1111/j.1748-720X.2002.tb00384.x
Fairchild, A. L., & Bayer, R. (2004). Ethics and the conduct of public health surveillance. Science, 303(5658), 631-632. https://doi.org/10.1126/science.1094038
Lee, L. M., & Gostin, L. O. (2009). Ethical collection, storage, and use of public health data: A proposal for a national privacy protection. JAMA, 302(1), 82-84. https://doi.org/10.1001/jama.2009.958
Thomas, J. C., Sage, M., Dillenberg, J., & Guillory, V. J. (2002). A code of ethics for public health. American Journal of Public Health, 92(7), 1057-1059. https://doi.org/10.2105/AJPH.92.7.1057
The Walden HLTH 8136 Week 4 instructions
Students write a position paper that resolves a conflict between two professional obligations in a specific case. The paper should open with its ruling, naming the obligation that governs and the one that yields. Background should describe the request or situation clearly. Each obligation needs a footing in a code or principle, and the argument should draw on published ethical reasoning. The paper should propose specific actions and answer the strongest objection. Legal questions can be noted and left to counsel. Six to eight pages in APA style is common. The offer of an alternative that meets part of the competing duty is usually expected, since a bare refusal is hard to defend.
How the HLTH 8136 Week 4 example is put together
The ruling paragraph names confidentiality as governing and cooperation as yielding in part. The request section describes the warehouse, the departments that use it and what partner services records contain. The obligations section cites the Principles on confidentiality and on collaboration. Three reasons follow, each from a different source: Lee and Gostin on using public health data for public health purposes, Fairchild and Bayer on public confidence in surveillance, and Childress and colleagues on necessity and least infringement. The offer section proposes aggregate counts with small-cell suppression, a consent-based referral pathway and a standing meeting. A section explains why the refusal should be written and what it means for frontline staff. The objection that elected leaders decide is answered by distinguishing a refusal to breach a promise from an override of policy. Limits close the paper.
Where the marks sit in the HLTH 8136 Week 4 rubric
Position papers this week are graded on the clarity of the ruling and the quality of its defense. A paper that weighs both sides without deciding loses most of the credit. The rubric rewards naming the governing and yielding obligations at the start, grounding each in a principle and supporting the ruling with distinct reasons. Faculty look for alternatives that meet part of the competing duty, since a bare refusal reads as uncooperative. Actions at the end should be specific enough to carry out. Opponents' best point deserves a fair statement and an answer. Acknowledging what the paper does not analyze, such as state privacy law, is credited. A well-organized paper with accurate references finishes the grade.
HLTH 8136 Week 4 help from the desk
Papers on data-sharing requests often argue that privacy matters without saying which obligation governs or why. Others drift into legal analysis that belongs with counsel. Some refuse the request without offering anything in its place, which makes the ruling hard to defend to elected leaders. To write a stronger paper, state the ruling and both obligations in your first paragraph. Explain exactly what the data contain and why disclosure could harm people. Give two or three reasons from different sources. Offer alternatives that serve the requester's goal. Answer the objection that elected officials have the final say. A position paper on another conflict from your course can be written for you if a model would help.
Get a HLTH 8136 Week 4 example written to your instructions
Forward the scenario, the Week 4 prompt and rubric, and any required position statement format; a paper that rules in its opening paragraph and defends the ruling comes back in 24 to 48 hours, free on a first request. A length ceiling or an assigned side changes what gets argued, so include either one.
More HLTH 8136 papers and PhD in Public Health samples
- HLTH 8136 Week 1: Professional Duties Framing Post
- HLTH 8136 Week 2: Syringe Services Pressure Post
- HLTH 8136 Week 3: Outreach Count Duty Analysis
- HLTH 8136 Week 5: Filter Vendor Conflict Case
- HLTH 8136 Week 6: Interpreter Cut Peer Critique
- HLTH 8136 Week 7: Overdose Report Disclosure Case
- HLTH 8136 Week 8: Colleague Concern Discussion Post
- HLTH 8136 Week 9: Cooling Center Accountability Brief
- HLTH 8136 Week 10: Cluster Review Counterargument
- HLTH 8136 Week 11: Ethics Synthesis Paper
- HLTH 8054 Week 4: Life Course Risk Trajectory
- HLTH 8052 Week 4: User Fee Removal Position Paper
- HLTH 8048 Week 4: Trades Council Applicability Brief
- HLTH 8035 Week 4: Study Design Appraisal
HLTH 8136 Week 4 questions, answered
Can the paper rule in favor of sharing the data?
Yes, if the argument supports it. A paper could hold that coordinated services outweigh the confidentiality risk under strict safeguards. What matters is that the ruling is stated, the competing duty is taken seriously, and the conditions are specific. Your grade depends on the defense, not on which obligation you pick.
Should the paper discuss privacy law?
Mention that legal questions exist and belong with counsel, then argue the ethics. The prompt asks what the practitioner owes, and a paper that turns into a legal memo answers a different question. A sentence acknowledging that law sets a floor, and that the ethical obligation may ask for more, usually strikes the right balance.
How specific should the actions at the end be?
Specific enough that a practitioner could carry them out: a written response, a proposed alternative, a request for review. General statements about upholding ethical standards do not count as actions. The closing section shows the ruling can survive contact with a real organization, which is part of what your reader is assessing.
Where can I find a free HLTH 8136 Week 4 sample paper?
Shown in full above, the Week 4 position paper rules on a request to load identifiable partner services records into a county data warehouse, gives three reasons and alternatives, and cites four sources.
What does the steward offer in place of identifiable data?
Aggregate counts by area and broad group with small cells suppressed, a consent-based referral pathway connecting willing clients to case managers, and a standing meeting to find other shareable data.