Managing chronic clients when the register sits off-system

Chronic members are usually the smallest group by headcount and the largest by claims activity. They are also the group most often managed outside the system, in a spreadsheet or a notebook that one person maintains.

Why the separate list appears

The list is a reasonable response to a real gap. If the administration system records a condition but not the authorisation status, the repeat script date or the last collection, someone builds a side file to keep the work moving. The file works until the person maintaining it is on leave.

What a register inside the system gives you

NEXMAS and NEXPHARM both carry a chronic register. In NEXMAS it sits on the member record used at adjudication: registered conditions, authorisation status, repeat scripts and review dates. In NEXPHARM it is visible at the counter: which chronic clients are due for a repeat, when they last collected, and when a review is scheduled.

The difference is not the fields. It is that the register is maintained by the team doing the work, on the record they are already using, so it cannot fall out of step with the claims or dispensing activity around it.

Three practical effects

• Authorisation status is visible when a claim is assessed, so a chronic claim is not queried for a document the scheme already holds
• Repeat collections are anticipated rather than discovered, which smooths stock planning
• Review dates are attached to the client, so follow-up is a task in the system rather than a note on a desk

A note on scope

The register is a record of who the chronic client is and what has been authorised. It is not a clinical decision-support tool, and it does not replace the pharmacist's judgement on a repeat script. Its value is administrative continuity: the same client, the same authorisation, the same review date, visible to everyone who serves them.