Get started
ClinicalLive · in the productRegister

FieldGuide

The health camp captured with no signal, and sent when the signal returns.

What it is

The camp screen for the places a camp actually happens. Before leaving, the worker downloads the camp and its list onto the phone or tablet, or starts a camp on the device. Out there, with no signal, each person is registered and screened on the device — a name, an age, a phone, the complaint, a blood pressure, a sugar and a referral — with the server’s own limits checked as they type, and a phone already on the camp’s list flagged while the person is still standing there. Back in signal the round goes up through CampKit’s field sync on its own, keyed by identifiers the device made, so a round sent twice because the first answer never arrived writes nothing the second time and says so. What the server refuses — a duplicate phone, a camp that is no longer on the list — is marked on the row that caused it, never dropped. The round is CampKit’s: the camp desk reads the same register.

Who uses it
Built for: Every specialty
Reads
The camps on the desk and their lists
Writes
Camp registrations, findings and referrals, through the field sync
Never
It does not decide between treating and referring — no protocol pathway is typed into this product, so that decision stays with the worker and the supervising doctor.
Access
Only people whose role includes it — the clinic owner decides who
Your data
Full PHI. Hosted in Boston, United States. On uninstall: Every record stays; only the workflow leaves.

How it works

  1. Download the camp before you leaveUnder Before you leave, press Download on a camp from the desk while there is signal; its list comes onto the device. Or fill Start a camp on this device with a name, a date and a place.
  2. Register and screen with no signalOn Register and screen, type the name, age, phone and complaint, and under Screening and referral the blood pressure, sugar, a note and where to refer. Keep on this device saves it there; the screen checks the server’s limits as you type and warns when the phone is already on the camp’s list.
  3. Send when the signal returnsThe round sends itself when the device comes back online, or press Send now. Each person goes up keyed by the device’s own identifier, so a round sent twice writes nothing twice and shows already on the server.
  4. Settle what needs a lookA person the server refused — a phone already registered at that camp, a camp no longer on the list — is marked needs a look with the reason. Remove them if they are a duplicate, or press Send again. Signing out deletes the round from the device, so send everything first.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not decide between treating and referring — no protocol pathway is typed into this product, so that decision stays with the worker and the supervising doctor.
It does not survive sign-out: the round lives on the device only until the session ends, and the screen says how many people are unsent before that.
A page reloaded with no signal lands on the sign-in page; the round stays on the device, and the tab is best kept open out there.

AI in FieldGuide

AskQuestions about what is on screen — “What needs attention in FieldGuide today?” — answered with the records it read.
DraftSummaries and notes for the team, marked as drafts until a person signs.
Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

Live product
01Field Round — Register and screen people at a camp with no signal, and send them laterCaptured from the running demo clinic
FieldGuide — Field Round — Register and screen people at a camp with no signal, and send them later
1 of 1

Questions clinics ask

What does FieldGuide do?
The health camp captured with no signal, and sent when the signal returns. The camp screen for the places a camp actually happens. Before leaving, the worker downloads the camp and its list onto the phone or tablet, or starts a camp on the device. Out there, with no signal, each person is registered and screened on the device — a name, an age, a phone, the complaint, a blood pressure, a sugar and a referral — with the server’s own limits checked as they type, and a phone already on the camp’s list flagged while the person is still standing there. Back in signal the round goes up through CampKit’s field sync on its own, keyed by identifiers the device made, so a round sent twice because the first answer never arrived writes nothing the second time and says so. What the server refuses — a duplicate phone, a camp that is no longer on the list — is marked on the row that caused it, never dropped. The round is CampKit’s: the camp desk reads the same register.
What data does FieldGuide read and write?
FieldGuide reads the camps on the desk and their lists and writes camp registrations, findings and referrals, through the field sync. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
What does FieldGuide deliberately not do?
It does not decide between treating and referring — no protocol pathway is typed into this product, so that decision stays with the worker and the supervising doctor. It does not survive sign-out: the round lives on the device only until the session ends, and the screen says how many people are unsent before that. A page reloaded with no signal lands on the sign-in page; the round stays on the device, and the tab is best kept open out there.
What happens to our data if we uninstall FieldGuide?
Every record stays; only the workflow leaves.
Is FieldGuide available today?
Yes — FieldGuide is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see FieldGuide running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More in Clinical

All 437 →
Featured inGeneral Practice