Clinical services · Test and treat

The programme gets the work, in the format it reads

A pharmacist tests, reads the result and treats under a state protocol. Attergo enrols the facility in the programme that sponsors that work and exports the activity to it in the layout the programme reads. The testing half records as testing, carrying everything that service line carries.

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

The two halves of one visit are settled by two different mechanisms

The test is a familiar billable service. The assessment and the decision that follow it are what a state protocol authorised a pharmacist to do, and they are settled by whoever sponsors the arrangement. Sites routinely capture one and lose the other, and which one they lose is decided by whichever system somebody happened to be standing in front of.

What the platform does

The mechanism behind it.

Programme enrolment is per facility

A facility is enrolled in the programme that sponsors the work, and its activity is exported in the layout that programme reads. The export is built, not transcribed.

The testing half records as testing

That encounter carries its catalogue entry, its documentation template, its attesting practitioner and its time, exactly as any other recorded service does.

Authorization is checked before a claim is transmitted

Where a procedure requires an authorization, the scrubber blocks the claim rather than letting a denial explain it to you six weeks later.

The clinical decision stays with the pharmacist

Attergo records the work and moves the money. It holds no chart, writes no prescription and decides nothing clinical, so it adds no second opinion to a protocol your state already wrote.

Ask what a service costs you to deliver.

A read-only connection and credentials you can revoke. We come back with what the last month of clinical work produced, using your own numbers.