TPAS
A doctor's reasoning at the health worker's side.
- Signed protocols on the phone, offline
- Referrals and follow-up to an outcome
- Supervision and period reports
Ecosystem
Built for the community, ready for the hospital and the health system.
TPAS is the clinical guidance a health worker carries. It hands referrals to the hospital and takes the outcome back. It stands on its own, works with the systems around it, and is ready for a ministry of health that chooses it.
Where TPAS fits
TPAS in the community, and what it connects to.
A program can run TPAS alone. Where a hospital runs Intellicare, or a national program runs HERMIS, TPAS works with them. A connection to Mira, the record patients carry, is planned.
Intellicare
Hospital management and ERP, end to end.
- Clinical records, laboratory and pharmacy
- Billing, procurement and the general ledger
- Defaulter tracing after discharge
HERMIS
TPAS with a workforce mobility platform.
- Health worker registry, certification and supervision
- Shifts, field tracking and routing
- Sync between phones where there is no network
Mira
A health record the patient owns and carries.
- Clinics, labs and pharmacies on one timeline
- Shared with any provider, and taken back
- Bookings that a provider must honor
DHIS2
The national health information system. TPAS, Intellicare and HERMIS are built to report to it, once a ministry chooses to connect.
- TPAS to IntellicareReferralA referral from the village arrives at the hospital with the handoff note, the findings and the first dose already given.
- Intellicare to TPASOutcomeWhat the hospital found and did returns to the health worker's record, so the follow-up visit starts from the facts.
- Intellicare to TPASDefaultersMissed antenatal, immunization and postnatal appointments become visits for the health worker who covers that village.
- TPAS to MiraVisit recordWith the patient's consent, the visit and its referral reach the record the patient carries.
- TPAS, Intellicare and HERMIS to DHIS2ReportingFigures in the form the national system reads, sent on schedule once a ministry connects, each submission recorded.
With Intellicare
For hospitals that run community health.
Intellicare is a hospital management and ERP system, also built by Diggy Solutions. A hospital that runs its own community program adds TPAS for its health workers. The wards and the villages then share one patient, one referral and one follow-up.
The hospital sees who was referred and why before the patient arrives. The health worker learns what happened. The mother who missed her postnatal visit gets a knock on the door from someone she knows.
- One system
- Clinical and business records together, from the bed board to the general ledger.
- Standards
- It uses recognized health data standards, so it can join a national health information exchange.
- A record that holds
- A tamper-evident audit trail, and ward rounds that keep working offline.
- National returns
- Monthly returns in the form DHIS2 reads.
HERMIS
For national programs that manage the workforce as well as the care.
HERMIS puts TPAS's clinical guidance together with a workforce mobility platform. A national program can see who is certified, where they are working, which households they reach, and what they found there.
Workforce
- Health worker registry and certification
- Shifts, work sessions and teams
- Tasks, performance and supervision
- Quality assurance visits and feedback
Mobility
- Field tracking and territories
- Maps and routing to households and facilities
- Work shared phone to phone where there is no network
- SMS for messages that must reach any phone
Care
- Clinical guidance from TPAS
- Immunization and laboratory records
- Emergency alerts and outbreak reporting
- Medicines and supplies in the field
With Mira
A record the patient carries. Planned
Mira is a health record that belongs to the patient, built for Liberia by CEG Health Systems of the Continental Excellence Group. Clinics, laboratories and pharmacies write to one timeline, and the patient decides who may read it.
We are designing the connection between Mira and TPAS. With the patient's consent, a TPAS visit and its referral would reach their Mira record, so the clinic they go to can see why they came. It is a plan, not yet a feature.
- Visits
- The visit, what was found and what was done, added to the patient's timeline with their consent.
- Referrals
- A TPAS referral the patient can book with a facility on Mira.
- Consent
- The patient chooses who sees the record, and can withdraw that choice.
- Status
- Mira is in private beta in Monrovia. The connection is in design.
For ministries and institutions
Ready when a health system is.
TPAS is built so that a ministry of health can adopt it whole, and we hope Liberia's will be the first to see its value. We would welcome health ministries and institutions across the region in the same way.
Its own clinical authority
Each health system writes and signs its own protocols, under its own medical leadership, following its own national guidelines.
Its own data
Each runs on an instance of its own, with its records kept apart from everyone else's and hosted where its rules require.
Room to grow
The infrastructure to host more than one country is already in place. Adding a ministry or an institution does not mean starting again.
Integration and APIs
Open by design, through standards and a documented API.
A health system is many systems. TPAS is built to take its place in one, under the same permissions and audit trail as everything else it does.
- DHIS2TPAS sends its monthly figures once a second person approves them, and reads them back to confirm they arrived. Shown with a test DHIS2; live once a ministry chooses to connect.
- Documented APIWhat the backoffice can do, an authorized system can do, with the same roles checked and the same actions recorded.
- Health data standardsBuilt on recognized health data standards, so hospital systems from other makers can join too.
- Open exportsReports, the patient registry and the audit trail export at any time, in formats any analyst can open.
Each program keeps its own instance and its own data. A connection is switched on only when the program, and where needed the ministry, agree to it.
Talk to us
Tell us where your patients go next.
We will show you, with demonstration data:
- A referral from a TPAS visit, and its outcome coming back
- How reporting to DHIS2 would work for you
- The API, and what your other systems could read
- Which of the three fits your program today
info@diggysolutions.com · +231 775 711 477
We reply within one business day. Oldest Congo Town, Monrovia, Liberia.