AI School · Level 3 · Practical case · Clinical, with a safety net

The child’s amoxicillin: checking a paediatric dose without letting AI decide it

Léelo en español →

Reading time: about 11 minutes

The situation. A father brings in a prescription for amoxicillin suspension for his son. The prescription gives the product and "5 mL every 8 hours". He tells you the child weighs about 14 kilos. There is a queue, and you want to confirm in a minute that the dose makes sense before dispensing and explaining how to measure it.

Checking a paediatric dose is the pharmacist’s job, and doing it well is arithmetic with the right inputs: the weight, the strength of the product, the dosing and the reference range. AI can help you lay out the calculation and then explain it to the parent, but it has two serious weaknesses exactly here: it confuses per-day units with per-dose units, and it reads strengths carelessly. This case is about using it as a second pair of hands, never as the source of the range.

What you need to hand: The prescription (it does not go into the chat: you type only the product and the dosing), the weight the father gives you, the paediatric dosing calculator on this site — which works from a reviewed catalogue — and the lesson on checking against the SmPC. Neither the child’s name nor the doctor’s is needed for anything.

Step by step

  1. Write down the four figures before doing any maths

    A dose check almost always goes wrong in the starting data, not in the multiplication. So before opening any chat, write the four numbers on paper:

    Weight: 14 kg (and note that it is what the father says, not a measured weight). Product: amoxicillin 250 mg/5 mL, that is, 50 mg per mL. Prescribed dosing: 5 mL every 8 hours, three doses a day. Reference range: whatever a reviewed source says, not your memory and not the chat.

    Notice that you have already converted the strength to mg per mL yourself. That step prevents more errors than any other: "250 mg/5 mL" and "250 mg/mL" differ by a factor of five, and in the rush at the counter they read the same.

  2. Take the range from the reviewed source, not from the chat

    In the catalogue behind this site’s calculator, amoxicillin has a range of 40 to 90 mg/kg/day, divided every 8-12 hours, with an absolute maximum of 3,000 mg a day, and a note that acute otitis media and strep throat use the top of the range, 80-90 mg/kg/day. That is the figure that governs this check, together with the SmPC if you are unsure.

    Look at the unit: per kilo per DAY, not per dose. Everything else depends on that detail, and it is exactly the one a model tends to lose.

    For 14 kg, the daily range is between 560 mg (14 × 40) and 1,260 mg (14 × 90). That is what the child should receive in total in a day, divided into however many doses the prescription says.

  3. Use AI to lay out the calculation, giving it all the data yourself

    With the data written down and the range taken from the source, AI can help you do the calculation step by step and, above all, let you see whether your reasoning and its reasoning agree. The key is that you do not ask it for the range: you give it.

    Check this calculation step by step, without adding any data I do not give you.
    
    - Child’s weight: 14 kg.
    - Product: amoxicillin suspension 250 mg/5 mL (= 50 mg per mL).
    - Prescribed dosing: 5 mL every 8 hours.
    - Reference range (already checked in a reviewed source):
      40 to 90 mg/kg/DAY, maximum 3,000 mg a day.
    
    Calculate:
    1. The mg in each dose.
    2. The total mg per day.
    3. The resulting mg/kg/day.
    4. Whether it falls within the range I have given you.
    
    If any figure looks inconsistent to you, say so. Do not give me your own range.

    With these numbers the maths is: 5 mL × 50 mg/mL = 250 mg per dose; × 3 doses = 750 mg a day; ÷ 14 kg = about 53.6 mg/kg/day. Inside the general 40-90 range. Do the calculation yourself too: if its answer and yours differ, yours wins until you find out why.

  4. A dose outside the range is not corrected: it is queried

    If the prescribed dose falls within the range, you dispense and explain. If it falls outside, or you suspect the indication calls for the top of the range and the dose is at the bottom — an ear infection treated at 53 mg/kg/day, for example — you do not change it and neither does the chat: you contact the prescriber.

    You do not know the indication for certain. The father may tell you "it is for his ear" or "for his throat", and that is useful when deciding whether to call, but it is not a diagnosis. The doctor may have chosen that dose for a reason you are unaware of.

    AI can help with one specific thing here: drafting, in two lines, the question you will put to the doctor, with the numbers in front of you, so the call takes thirty seconds. "I have a prescription for 5 mL every 8 hours of amoxicillin 250 mg/5 mL for a 14 kg child, about 54 mg/kg/day; is that the dose you intended, or did you want the high-dose regimen?"

  5. Explain to the father how to measure it, with the syringe from the pack

    A correct dose measured badly is a wrong dose. Here AI is genuinely useful: ask it for a short, clear explanation for the parent — but based on the dosing you have already checked, not on anything it calculates.

    Write an explanation for the parent of a child, in no more than
    6 lines, of how to give an antibiotic suspension:
    - Dose: 5 mL every 8 hours, for the number of days the doctor said.
    - Measure it with the oral syringe from the pack, not a kitchen spoon.
    - Shake before each dose.
    - Finish the course even if the child gets better sooner.
    Do not add any dose, storage or side-effect information I have not given you.

    How to store the made-up suspension and how long it keeps depend on the specific product: read them in the leaflet and tell the parent yourself. That is exactly the kind of detail a model states generically and that varies from one product to another.

A full example, and what is wrong with it

This is what a model replied when asked directly "is 5 mL every 8 hours of amoxicillin 250 mg/5 mL a correct dose for a 14 kg child?", without being given the range or the converted strength. It is shortened and not polished.

What it replies

"The recommended dose of amoxicillin in children is 40-90 mg/kg per dose. For a 14 kg child, this means between 560 and 1,260 mg per dose.

With the 250 mg/5 mL suspension, 5 mL provides 250 mg, so the prescribed dose would be below the recommended range. At least 11 mL per dose would be needed to reach the minimum effective dose.

It is advisable to consult the paediatrician to adjust the dose and ensure the treatment is effective."

And now, what is wrong with that reply:

  1. It has confused "per day" with "per dose". The 40-90 range is in mg/kg per day, and it has applied it to each dose. That triples what it considers the correct dose. It is the exact error this site’s calculator corrects, and the most dangerous of all, because it turns a correct prescription into an "insufficient" one.
  2. The arithmetic is flawless, and that is why it misleads. 14 × 40 = 560, 14 × 90 = 1,260, 5 mL of 250/5 is 250 mg, and 560 mg is 11.2 mL. Everything adds up. The only thing wrong is the starting unit, and that is enough to make the conclusion the opposite of the truth.
  3. It proposes a new dose. "At least 11 mL per dose" is 560 mg three times a day: 1,680 mg daily, about 120 mg/kg/day, well above the ceiling of 90. If anyone followed that suggestion, the child would receive considerably more than the range allows, with no warning at all that this might be a problem.
  4. The final advice looks cautious and is not. "Consult the paediatrician to adjust" sounds responsible, but it is framed to raise a dose that was correct. Calling the doctor with a unit error as your opening line is worse than not calling.

This is why step 2 comes before step 3. With the range written down by you, in the right unit, and the strength already converted, the same calculation comes out right first time: 750 mg a day, about 53.6 mg/kg/day, within range.

And this is why in step 4 AI decides nothing. When it gets it wrong, it gets it wrong with figures, workings and cautious advice at the end: every appearance of a check done properly.

← All practical cases Back to the school →