One person, one record
Linked to the hospital's patient master, so repeat attendees are never counted twice.
Government medical camps
Government medical camp software has to do three things a register cannot: count every person screened without counting anyone twice, follow each referral until the person reaches the hospital, and hand the programme officer numbers that add up. MedBrains does all three, offline when it has to, on the same patient record the hospital uses.
Book a demoDistrict hospitals, community and primary health centres, medical colleges with an outreach role and teams running national programmes all hold camps: screening for blood pressure and diabetes, eye camps, dental camps, vaccination drives and awareness days. They run in places without a hospital, often without a reliable network, and staffed by people who have been drafted in for the day.
The failures are familiar. The same person registers at two camps and is counted twice. The register says forty people were referred, and nobody can say how many reached the district hospital. A month later the figures are typed into a spreadsheet from paper, and the typing is where the errors come in.
The camp is created with its type, venue (address, pincode and map location), date, coordinator and expected turnout, then approved before it is set up. Approval is recorded with who approved it and when.
The 18-point readiness checklist covers local authority permission, a private area for women and elderly people, drinking water and hand hygiene, sharps and colour-coded biomedical waste bins with an authorised hand-off, red-flag referral rules with the receiving facility's contact and transport, and charged devices with paper fallback forms. The camp shows a readiness score before the team leaves.
Each person gets a camp number. If they already have a record at the hospital they are linked to it; if not, they get a UHID marked as a camp registration. The father's or spouse's name is captured, because that is how rural registers tell two people with the same name apart.
Vitals, random blood sugar and HbA1c, haemoglobin, BMI and visual acuity, a history checklist, findings, ICD-coded diagnoses and advice. Several diagnoses can be coded from one screening.
A referral records the receiving facility and department, urgency, reason, transport, whether an ambulance is needed and an attendant's contact. Its status is updated as the person moves, so a referral is a list to work through, not a number in a register.
Follow-ups are scheduled per person and marked completed, missed or cancelled. The readiness checklist names an owner for the post-camp sync, the biomedical waste hand-off, referral reconciliation and incident review, so closing the camp is somebody's job.
Every number in a camp's report is a count of records, so it can be traced back to people: registered, screened, referred, converted to hospital patients, samples collected, follow-ups scheduled and completed. Across camps, MedBrains shows the screening yield (referrals as a share of people screened), conversion rate, average cost per patient and follow-up compliance.
Because diagnoses are coded at the camp, a district team can count conditions without reading handwriting. Because registration links to the hospital's patient master, a person screened at three camps in a year is one person with three screenings, not three people.
Government camps are where the network is worst. The camp's packet is downloaded before the team leaves, and registration, screening, samples, referrals, incidents, checklist and supply updates are recorded on the device and synced back later. Each sync event carries the device, the user and the time, and a replay never creates the same person twice.
Data is kept per organisation with row-level security in the database, and access follows each user's role. MedBrains can run in our cloud or on servers you control, which matters when a state or institution needs patient data to stay in its own data centre. Our DPDP readiness guide covers the consent and retention side.
Camp attendees who become hospital patients land on the same record the hospital's front desk uses, where an ABHA can be verified or created and linked. ABHA is optional at the camp: nobody is denied care for not having one. MedBrains is built for ABDM (M1 to M3) and is not yet certified by the National Health Authority.
The hub page on health camp software walks through the full camp day, and the software vs manual comparison is useful if your camps still run on paper.
Linked to the hospital's patient master, so repeat attendees are never counted twice.
Diagnoses coded where they are made, several per screening.
Facility, urgency, transport, ambulance and attendant, tracked until the person arrives.
An 18-point checklist covering consent, privacy, biomedical waste and referral routes.
Patient safety, infection control, equipment and privacy incidents with severity and the action taken.
Recorded on the device, synced back without duplicates.
MedBrains does not submit data to government portals itself. The camp's figures come out of MedBrains for your team to report in the format your programme asks for.
Software that a district hospital, health centre or programme team uses to plan a camp, register and screen people, refer those who need care and report the results. MedBrains does this on the same patient record the hospital uses, so a camp referral can be followed into the hospital.
Screening captures blood pressure, random blood sugar, HbA1c, BMI and a history checklist including diabetes, hypertension, smoking and alcohol, with ICD-coded diagnoses and referral. Those are the fields a screening camp for blood pressure and diabetes needs.
Yes. The camp packet is downloaded before departure and registration, screening, samples, referrals and incidents sync back when the connection returns. Billing and follow-up conversion need a connection.
MedBrains can be installed on servers you control instead of our cloud.
No. ABHA can be linked on the patient's hospital record, but nobody is turned away for not having one.