Four records kept by someone else, each graded for custody, denominator and retrievability, make up this source audit example for PUBH 8501 in Week 3. Searches like "pubh 8501 week 3 assignment example", "pubh8501 week 3 sample" and "pubh 8501 week 3 example" land here.
What a finished PUBH 8501 Week 3 source audit looks like
A five-column table fills the first two pages, one row per source. Columns record the keeper, what the record counts, the denominator it counts against, the period it covers, and the route a stranger would take to retrieve it. Under the table, every source gets a one-paragraph verdict: confirms the pattern, confirms it partly, or cannot speak to it. The composite state summary reports confirmed infections but never shows who was screened and not confirmed, so it cannot see the gap at all. CDC guidance defines the antibody-then-RNA sequence and so sets the standard the gap is measured against. Published cascade analyses from other settings describe people dropping away between the two tests, which supports the pattern elsewhere. The county laboratory report shows orders placed but not specimens drawn, and earns a partial verdict.
How a PUBH 8501 Week 3 example is structured
Ordering the rows by keeper rather than by how strongly each source agrees is the key choice, because a table sorted by agreement reads as advocacy and hides the source that is silent. The denominator column sits beside the count column so no figure can be read without the thing it divides by; much of the audit's value is showing that two records use different denominators and cannot be compared directly. Verdicts come after the table, not inside it, so each can be argued in a sentence rather than squeezed into a cell. A source that cannot speak to the gap stays in the audit, since knowing where the pattern is invisible matters as much as knowing where it shows. Last comes a statement of what all four together establish and what none of them reaches, which is this particular kind of clinic.
Four keepers
A state health agency, a federal agency, published researchers and a county laboratory, none of them the author.
Counts beside denominators
Each row pairs what is counted with what it is counted against, which exposes that two sources cannot be compared as published.
Retrieval routes
A column states how a stranger would reach each record: public web page, library database, or a request to a named office.
Three kinds of verdict
Confirms, confirms in part, or cannot see the gap, each argued in a short paragraph below the table.
What none of them reaches
No source examines a walk-in sexual health clinic, which leaves the setting itself undocumented outside the author's desk.
Where marks go in PUBH 8501 Week 3
An audit is judged on whether its verdicts follow from what each record can actually see. Declaring that a state summary confirms the problem, when it reports only confirmed infections, is the kind of misreading faculty catch first, and this example avoids it by marking that source as blind to the gap. The denominator column carries weight of its own, since comparing counts built on different bases is a quiet error this course penalizes. Retrievability is scored plainly: a source a stranger cannot reach counts for little however persuasive it is. Honest partial verdicts earn more than a clean sweep of confirmations. Audits tend to lose points for listing sources without verdicts, for treating guidance as evidence that a problem exists, or for relying on the home clinic under another name.
Get a PUBH 8501 Week 3 example written to your instructions
Name the pattern you believe you have seen, list any outside sources you already suspect might hold it, and add the Week 3 prompt and rubric. The audit grades each record for keeper, denominator and retrievability. Expect it within 24 to 48 hours, free for a first request; its state summary and laboratory report are stand-ins.
PUBH 8501 Week 3 questions, answered
Can my own clinic's data appear in a source audit?
It can appear, but not as one of the outside sources, since the week asks whether the pattern holds in records somebody else maintains. The example mentions its own callback log only in the opening line, as the observation being tested. Your audit gains credibility when every verdicted source is one you could not have shaped.
Why keep a source that cannot see the problem?
Because silence is information. A state summary that reports only confirmed infections tells a reader why the gap never appears in official counts, and that absence becomes part of the argument that the problem is under-documented. Dropping it would leave a reader wondering whether the author missed it or chose to hide it.
Is federal testing guidance evidence that a problem exists?
Not by itself. Guidance sets the standard, the sequence people are supposed to complete, and so defines what counts as a gap. Evidence that people fall short of that sequence comes from studies and records. Your audit reads more carefully when it keeps those two roles apart, as the example does by giving guidance its own kind of verdict.