POPH90068 Chap.6 Partner Management
Partner Management
Partner management connects an index diagnosis to information, testing and treatment for people who may have been exposed. Its direct control pathway often involves earlier partner care and shorter infectious duration, but the route must respect confidentiality, safety, preferences and infection-specific guidance. The key distinction is between an attempted contact and completed care.
Evaluation follows each transition without compromising privacy. A cascade makes losses between identification, contact and care visible while preventing message volume from standing in for a clinical outcome. Safety assessment and supported alternatives belong at the start of the pathway because direct contact is not appropriate in every circumstance.
What this chapter covers
- 01
Purpose of partner notification
- 02
Patient and provider referral
- 03
Testing and treatment links
- 04
Safety and confidentiality
- 05
Infection-specific differences
- 06
Pathway completion measures
Worked example · free
Choose a supported pathway
- 1Check safety and confidentiality risks before choosing a route.
- 1Explain available confidential and provider-supported options.
- 1Link the partner to infection-specific testing or treatment guidance.
- 1Record care completion and delay using privacy-protecting procedures.
Key terms
- Index case
- The diagnosed person from whom a partner-management process begins.
- Patient referral
- A pathway in which the diagnosed person informs partners with suitable support.
- Provider referral
- A pathway in which an authorised service confidentially contacts partners.
- Expedited treatment
- A regulated approach that may provide partner treatment without a standard prior consultation.
- Completion
- The point at which the intended partner care step has actually occurred.
Partner Management FAQ
How does partner notification support control?
It can bring exposed partners to testing and treatment sooner, shortening untreated duration and reducing complications or onward transmission. The size of that effect depends on completion, timeliness and infection-specific management.
Why can methods differ between infections?
Clinical urgency, symptoms, testing, treatment, recurrence, resistance and public health priorities vary. Local law and guidance also shape which partner-management options are appropriate in a specific setting.
What should a partner-notification dashboard report?
Use eligible partners, contact attempts, successful contact, testing or treatment completion and delays, alongside safety and acceptability. A message count without completion cannot establish the intended pathway.
Assessment move
Draw the pathway from index diagnosis to partner identification, contact, testing or treatment and completion. At each arrow, list one reason a person could be lost and one respectful design response. Next compare two infections and explain why management may differ without inventing clinical rules. Practise safety-first cases in which direct contact is unsuitable.
For evaluation, always use an eligible denominator and distinguish attempts from outcomes. Close answers with the effect on infectious duration or complications rather than a vague statement that notification is important. Use a cascade rather than a single notification count.
Begin with index cases eligible for partner management, then show partners identified, contact attempts, successful contact, attendance, testing or treatment as appropriate, and completion. Write a numerator and denominator for every transition. An activity measure such as messages sent belongs early in the pathway; it cannot stand in for a completed clinical outcome.
When a stage performs poorly, propose a response aimed at that transition rather than redesigning the entire pathway without evidence. Build safety into the first decision, not the final disclaimer. For each scenario, check whether direct contact could create interpersonal violence, coercion, disclosure or other harm.
If risk is present or unclear, describe a supported, confidential alternative and the need for trained assessment rather than giving a universal script. Consider communication preferences, literacy, language, privacy of devices and the possibility that the named person is not safe to contact. Respectful partner management makes safety and autonomy conditions of implementation.
Compare infections through supplied public-health features rather than memorised clinical instructions. Ask what the case says about infectious period, asymptomatic infection, complications, testing, treatment and urgency. Explain how those features alter the purpose or timing of partner management, while keeping recommendations within the evidence provided and current guidance.
If a prompt lacks operational details, state what must be checked instead of inventing a window, regimen or eligibility rule. This is especially important when translating course concepts into a proposal. Practise writing neutral communication. Draft a short message that protects the index person's identity, explains the reason for action without blame, offers a clear next step and identifies a trustworthy service.
Then audit it for assumptions about relationships, gender, behaviour and responsibility. A message can be concise without being alarming or moralising. Pair communication quality with a practical route to care; successful contact has little value if appointments, cost or confidentiality make completion impossible. Finish with a two-level evaluation.
At the service level, measure timeliness, successful contact and completion using eligible denominators. At the public-health level, explain the intended contribution to earlier diagnosis, shorter untreated duration, prevention of complications or interruption of onward transmission. Add qualitative feedback about safety and acceptability, and specify a trigger for revising the pathway.
This links operational performance to the control mechanism without claiming that one local count proves a population effect.
