For programs
See what happens in the field, act on it, and report it.
Every visit, referral and follow-up lands in one record. Supervisors see what needs a person today. Every report comes from the same numbers your team works from.
Supervision
Every escalation followed to its outcome.
Follow-up rates, lost contact and time to outcome for every escalation. Rapid-test quality by health worker. Visits reviewed answer by answer.
Illustration of a backoffice dashboard. Data is illustrative.
An escalation loop that closes
Emergency, within 24 hours, or routine, each with a deadline of 24, 72 or 168 hours before supervisors are alerted. The outcome is recorded: went and treated, went but not treated, did not go.
Supervision that teaches
Field observations are triaged with feedback or promoted into a new clinical pattern. Any visit can be reviewed answer by answer, and every diagnosis in a patient's record says how it was made.
Rapid-test quality, tracked
Positivity and invalid-run rates by kit, expired lots refused at the point of use, and health workers whose positivity runs at twice the clinic's flagged for review.
Reporting and DHIS2
One set of numbers, from the visit to the report.
The figures a supervisor sees on Monday are the figures in the period report, and the figures a ministry would receive once it connects. Nobody copies them into a spreadsheet in between.
Captured once
Each visit records its answers, vital signs, rapid tests, treatments and referrals as it happens, offline or not.
Worked from daily
Eight dashboards: health worker performance, disease, protocol, escalation, laboratory, immunization dropout, pattern and survey activity.
Reported for any period
A report for any date range, in the eight sections a ministry of health asks for, read on screen or exported.
Ready for the national system
One person prepares the month's figures and a second approves them before they go to DHIS2. Each submission is recorded and read back. Shown working with a test DHIS2; the national one connects once a ministry agrees.
- Population
- Registered, women 15 to 49, under five, pregnant
- Service delivery
- Visits, completion and abandonment, treatments given
- Disease burden
- Top conditions, age bands, chronic share
- Quality
- Vitals capture, threshold breaches, satisfaction
- Escalations
- Follow-up, lost contact, compliance
- Immunization
- Penta-1 to 3 and BCG to Measles-1 dropout
- Laboratory
- Runs, invalid rate, positivity
- Workforce
- Active and rostered health workers
Your data
Your program, your instance, your records.
- Its own instanceEach program runs on its own server, database and backoffice. Nothing is shared with other programs.
- Hosted where you agreeHosting location is agreed with each program, including servers in country where national rules require it.
- Yours to takeThe program owns its data. Reports, the patient registry and the audit trail can be exported at any time.
- Built for a field phoneAndroid phones of the kind programs already buy, with the reasoning on the phone itself and work kept safe until a signal returns.
Working with us
How a program comes onto TPAS.
Scope
Agree the services, protocols, roles, pilot sites and reporting with your clinical and program leads.
Your own instance
A dedicated server, database and backoffice, with roles for health workers, clinicians, approvers and observers.
Author and sign
Your medical director adapts or writes the protocols. Two signatures before anything goes live.
Walk every protocol
Each protocol is walked on a handset against its expected outcomes before activation.
Train and pilot
Health workers start in a pilot group, with supervisors working from the backoffice.
Supervise and refine
Escalations, observations and the period report show what to improve. Changes pass through the same approvals.
Questions programs ask
Straight answers.
Can it connect to DHIS2 and the national health information system?
Yes. Each month one person prepares the figures and a second approves them; TPAS sends them to DHIS2 and reads them back to confirm every value arrived. This has been shown with a test DHIS2. Sending to a national DHIS2 needs the ministry's agreement and an account from it. Until then, the same figures are in the period report.
Can other systems read from TPAS?
Yes, through a documented API, with the same permissions and the same record of every action as the rest of TPAS. Hospitals that run Intellicare exchange referrals and outcomes with TPAS directly.
Does it really work without a signal?
Once a visit is open, yes. Questions, scoring, vitals, rapid tests, medicines given, referrals and escalations are recorded on the phone and sent when it reconnects. The decision engine runs on the phone itself, so the advice is the same offline as online.
Where is TPAS today?
In demonstration, with four protocols for childhood illness and malaria walked on handsets, and preparing for its first program deployment. We are glad to show exactly what works and what is next.
Request a demonstration
See your program's week in TPAS.
In one hour, with demonstration data:
- The escalation, disease and health worker dashboards
- A period report for any dates you choose
- How reporting to DHIS2 would work for you
- What deployment would take for your program
info@diggysolutions.com · +231 775 711 477
We reply within one business day. Oldest Congo Town, Monrovia, Liberia.