Clinical services

The work is already happening. Get paid for it

Attergo records pharmacist-delivered clinical work, reports it to whoever sponsors it, and bills it where a claim path exists. It delivers no care and decides nothing clinical, so nothing here stands between a pharmacist and a protocol your state already wrote.

Attergo: the prior authorization case list, showing cases by stage with the payer and the days remaining on each.

Immunizations

An administration becomes an encounter and a professional claim with nobody keying anything.

Point-of-care testing

A first-class service line with its own documentation template and a built programme export.

Test and treat

Facility enrolment and a built export to the programme that sponsors the work.

Medication therapy management

Reviews captured as fields, signed and timed, then exported as a structured care plan.

Chronic care management

Every contact is its own signed record, with its own practitioner and its own minutes.

Remote patient monitoring

Signed, timed encounters carrying their own minutes, scrubbed claims and remittances held for review.

Durable medical equipment

Evidence as a condition of closing an obligation, with reminders well ahead of the date.

Specialty and limited distribution

Priced per fill against what you actually paid, gated by authorization, traced end to end.

Underneath all eight

One catalogue, one record, one path to the money.

Every service records against a catalogue entry carrying its codes, its modifiers, its place of service, its fee and the fields it has to capture, and that entry is edited by whoever owns the service. Every encounter is signed and timed, and a correction keeps the original alongside the reason for it. Claims are scrubbed against your own payer rows before transmission. Remittances are parsed, matched and held for review.

Adding a required field to a service is configuration on your side, not a release on ours.