Obligations in this duty analysis are sorted by whom they bind, so the data coordinator, the manager, the agency and the profession each receive separate findings about the inflated contact counts. Searches like "hlth 8136 week 3 assignment example", "hlth8136 week 3 sample" and "hlth 8136 week 3 example" land here.
What a finished HLTH 8136 Week 3 duty analysis looks like
Five or six pages, with a four-column matrix near the front: obligation, source, party bound, and whether that party is meeting it. The program, funder and staff are fictitious. Sections follow the matrix row by row. The data coordinator's duty to accurate records comes from the ethical practice principles for public health and from research integrity norms. The manager's duty runs to staff as well as to the funder. The agency's duty is institutional, and the paper argues that an agency whose incentives reward inflation shares responsibility for it. The profession's duty to public trust is treated last. Ross's account of prima facie duties is used to explain why a duty can be overridden without disappearing. The conclusion identifies which party's failure matters most.
How a HLTH 8136 Week 3 example is structured
The analysis is organized by party because the prompt asks who each obligation binds, and a paper sorted by principle would answer a different question. The matrix comes first so the reader has the whole distribution in view before any row is argued. Each party's section follows the same order: the obligation, its source, the evidence that the party is or is not meeting it, and what meeting it would require. Ross enters in the agency section, where the paper needs to explain how a duty to accurate reporting can be outweighed by a duty to keep a program funded and still leave a residue that must be addressed. Sources are kept specific: a named code for individual duties, a published argument about institutional responsibility for agency duties. The conclusion ranks the failures and says which correction would change the most.
The matrix is the thesis
Obligation, source, party, status. The table states the paper's findings in compressed form, and the remaining sections argue for each cell. A reader skimming only the matrix already knows who owes what and who is falling short.
Individuals and institutions owe different things
The data coordinator owes accurate records; the agency owes a system that does not reward inaccuracy. The paper keeps these apart because a finding against the coordinator alone would miss the structural cause the scenario was designed to expose.
The manager is bound in two directions
Obligations run upward to the funder and downward to staff. Asking staff to misrecord contacts breaches the second while claiming to serve the first, and the paper treats that as the scenario's central failure rather than a side issue.
Ross explains the residue
Prima facie duties can be outweighed in a particular case, yet the outweighed duty still makes a claim. The paper uses Ross to argue that even if funding pressures were compelling, the duty to accurate reporting would still require disclosure to the funder.
The profession's stake is public trust
Inflated metrics, repeated across programs, erode confidence in public health data generally. This broader harm, the closing section argues, binds every practitioner, which is why the coordinator's silence is not a private matter.
Where marks go in HLTH 8136 Week 3
Duty analysis rewards correct sorting before anything else. A paper that files each obligation under the party it binds, with a source for each, has earned the credit the week centers on; one that lists principles and applies them to the scenario as a whole has missed the prompt's structure. Institutional responsibility draws a separate portion, and papers that recognize the agency's incentive design as a cause, not just the individuals, reach the upper band. Ross is judged on whether prima facie reasoning changes a finding. The matrix earns credit for clarity where sections reward organization. Specificity of sources matters more than their number. A conclusion ranking the failures is expected, and papers that end by saying every party shares responsibility equally have declined to finish the analysis.
Get a HLTH 8136 Week 3 example written to your instructions
Send the Week 3 prompt, the rubric and whatever scenario or reading list came with it; a duty analysis sorted by the party each obligation binds returns in 24 to 48 hours at no charge the first time. Required matrices, page limits or a particular ethical framework are built in from the instructions you forward.
HLTH 8136 Week 3 questions, answered
Why sort obligations by who they bind?
Because the same scenario looks different depending on whose duty is in question. A data coordinator, a manager and an agency each owe something about accurate reporting, though the content of each differs, and a remedy aimed at the wrong party fails. Sorting by party lets your analysis assign responsibility precisely and recommend a correction that reaches the actual cause.
What does Ross add to a duty analysis?
Ross separated prima facie duties, which bind unless outweighed by a stronger duty in the circumstances, from actual duties, which are what one must do all things considered. That lets you explain how a practitioner might justifiably set one obligation aside while still owing something because of it, such as disclosure or repair. It fits cases where duties genuinely conflict.
Can an organization have ethical obligations?
Most public health ethics writing assumes so, and the twelve ethical practice principles for the field are addressed largely to institutions. Your paper can treat the agency as a bearer of duties while noting the philosophical debate. The grade rests more on showing how the agency's structure shaped individual choices, which is where institutional duties become concrete.