Skip to content

Step 2: Giving the dose

This is the second half of the dose form, Phase 02 Prashan. You reach it by pressing Next: Prashan at the end of screening. Here you give the drops and record that you did. This page is for health workers (GeneralUser) and anyone else who doses children.

The batch code names the dose preparation the drops came from. It is written on the child’s record for good, so it must be right. A dose is recorded only with a batch that is attached to this camp day.

  • No batch attached. No dose can be recorded. The form says No dose batch is attached to this camp day, so no dose can be recorded. Ask an admin to attach a dose preparation (batch) to the camp day. and Next: Prashan stays disabled. Ask the site admin to attach a batch in Admin → Camp Days.
  • One batch attached to the camp day. It is selected for you and shown in the yellow Recommended Dosage box and in the fixed Batch Code field on the screening step. Nothing to do.
  • Several batches. The Batch Code dropdown on the screening step must be filled before Next: Prashan works. The page remembers the batch you last used on this camp day and pre-selects it for your next child. The memory is per camp day, per site and per user, so two workers on the same day never inherit each other’s choice. It is only a default; check it for every child, and change it when you open a new bottle.

The batch code is not shown again on the Prashan step. If you realise it is wrong, click Back to Screening, change it, and press Next: Prashan again.

A large checkbox: Guardian Informed. Confirm that the guardian has been informed about the next dose date and potential side effects. Tell the parent when to come back and what a normal reaction looks like, then tick it. Complete Dose stays disabled until you do. The tick is not stored as a separate field; a completed dose means it was ticked.

A text box for anything the parent reports about the previous dose, for example Mild rash on the chest the next day, gone in two days. On a child’s first dose the box is disabled and reads N/A for first visit, because there is no previous dose to report on. Leave it empty when there is nothing to report; do not type None. What you write here is counted and listed under Adverse Events in the camp-day report.

This section exists in the form for asking that the child’s next dose be at a different site, but it is hidden at present and cannot be opened. If a family is moving sites, dose them here as normal and change the preferred site on the child’s profile afterwards.

Give the drops, then press the black Complete Dose button. While it works it reads Submitting…. The server then writes, in one step:

  • the dose session becomes Completed and locked, with the screening values, the batch, the accompanying person, any adverse event text, and the time you pressed the button;
  • a dose record for the child with the batch code, the dose date (today, unless this is a paper entry), the camp site name and the dose number (paper doses plus doses on this system plus one);
  • an audit entry under your username.

Then the success screen appears: Mission Accomplished. Dose record locked and synced successfully. with two buttons:

  • View profile opens the child’s profile with a back arrow that returns you to this camp day.
  • Return to intake goes back to search for the next child.

These checks run when you press Complete Dose, even if the page missed them.

The camp day must be open. A camp day that is Completed, cancelled or deleted refuses the dose with, for example, This camp day is already marked Completed. Doses can no longer be recorded on it. A camp day dated after today refuses it with This camp day is on date and has not started yet.

The batch must belong to this camp day. A batch from another camp day, or a code that does not exist, is refused with Batch code is not assigned to this camp day. With several batches and none chosen, the dose is refused rather than guessed. With exactly one, that batch is used.

One dose per child per camp day. If a completed dose already exists for this child on this camp day, nothing new is recorded. This also covers the same dose being sent twice: a retry after the network dropped, a double press, or a colleague finishing the same child on a second device in the same second. Instead of an error, the form reloads the child and shows the read-only Already dosed on this camp day view (see below), with a message such as:

This child was already dosed by name at time at site (Token no. n). A child can only receive one dose per camp day. If that earlier record is wrong, ask an admin to correct it rather than recording a second dose.

Name, time (Nepal time), site and the day’s token number are filled in from the earlier record. Do not try again; find the colleague named in the message, or give the guardian the token number shown.

The same rule stops a child who was dosed today from also being recorded as screened out (Filter Out & End, or Not dosed in Org Mode): the child would otherwise count twice in the day’s report. Screening a child out first and dosing them later the same day is still allowed.

The 60-dose lifetime cap. A child may receive at most 60 doses in total, counting paper doses recorded at registration and doses on this system. At 59 the form shows an amber Final dose notice. At 60 it shows a red 60-dose limit reached box with the split (prior + on this system), and both Next: Prashan and Complete Dose are disabled. The server refuses too: 60-dose lifetime cap reached. This child cannot receive any further doses.

An age rule must match. If no dose rule covers the child’s age on the camp day date, the dose is refused with the allowed range and the child’s age. A child under the starting age (12 months) is always refused. A child above the top band is accepted only with the over-age box ticked and a reason. The page checks the same before Next: Prashan, so you will rarely see it here. See Age limits.

An accompanying person is required. A guardian from the list, or Other with name and relation.

Find the child again on the same camp day and the form opens read-only with a blue banner:

Already dosed on this camp day Dose #n was already given to this child on this camp day (date, site) at time. A child can only be dosed once per camp day. Given by name.

Below it a box shows Token number for today with the child’s token, the same number the success screen showed. To find a child’s token again, for example when a guardian has lost it, search for the child on the dosing screen or in Prashan Mode: the token appears here and on the child’s Dosed today tile (Token no. n). Doses recorded offline, from the camp-day report’s Mark dosed list, or before tokens existed have no token, so no token is shown for them.

The Given by line appears when the record names the worker. Every field shows the completed session’s values, the Guardian Informed box is ticked, and there are no buttons. Use it to check what was recorded. Nothing can be edited from this form; a locked session stays as it was recorded.

A child dosed on an earlier camp day is not locked. Their earlier dose appears in Previous Doses and the form opens normally for today’s dose.

  • The batch dropdown is empty, or the form says no dose batch is attached. No dose preparation is attached to this camp day, or it is still a draft. Nothing can be recorded until the site admin locks the batch and attaches it in Admin → Camp Days.
  • The page says no camp day is running today. The camp day has not started yet, has already been marked Completed, or does not exist. See A Prashan day, start to finish.
  • Complete Dose is greyed out. Tick Guardian Informed. If it is still grey, the child is at the 60-dose cap.
  • I pressed Next: Prashan on the wrong child. Click Cancel & Restart in the page header. The Started session stays open and shows in Screened, not dosed. Do not mark it dosed; leave the row, since a Started session is never counted as a dose.

Next: Recording a dose given earlier (paper entry), or skip to Screened but not dosed.