Specialty
Hospital management software for pediatrics
Immunization schedules, measurements at every visit, and a parent as the point of contact.
What makes this specialty operationally hard
- The patient is a child; the contact, consent, and payer is a parent or guardian.
- Immunization and growth follow a schedule, not an episode.
- Growth is judged against a reference population, which is a different question from whether a child is growing.
- Weight-based dosing has to be right every time.
How the platform supports it
- The consultation opens with a pediatric summary: age, how the child was born, what is overdue, and any development already flagged. For a baby born preterm it shows the corrected age beside the real one, and leaves the judgment to the clinician.
- As many named guardians as a child has, each with a relationship and separate marks for who to call first, who to call in an emergency, and who may consent.
- The immunization schedule works out from the date of birth which doses are given, due, overdue and upcoming, and recording one closes the right dose. A clinic-wide board shows which children are behind. It does not send reminders.
- A printed immunization card for the parent, dated, listing what has been given and what is still to come.
- Weight, height and head circumference captured at the precision a pediatrician measures them, and plotted against the WHO growth reference from birth to nineteen years, with the centile and z-score for the latest reading. The reference tables were read directly from WHO’s own published data and checked back against the cut-offs WHO prints beside them.
- A second view compares a child to their own earlier measurements rather than to a reference population, with the change per month between visits, because a child tracking along their own line and one who has flattened off look different long before a centile does.
- Birth and feeding history on the record: gestation as weeks and days, birth weight, delivery, an NICU stay, and a 63-item milestone checklist a clinician fills in.
- Weight-based dosing on the prescription itself: enter mg/kg and the dose is worked out from the recorded weight, checked against a ceiling you supply, and written into the field only when you accept it.
- The recorded allergies sit on the prescribing screen, and prescribing the exact drug an allergy names is flagged.
- Follow-ups are booked from the consultation, with the date of the next due vaccination already filled in. Family and dependant linking, and automated recall reminders, are planned.
The modules a practice like this turns on
Modules are entitlements: enable what you need now, add the rest when you are ready. Nothing is re-implemented per specialty.
Patient ManagementAppointment ManagementClinical Workflow (EMR)PharmacyBilling & Payments
What gets configured for you
Setup is data, not development, which is why a new specialty does not need a new build.
Guardian contact on the patient recordVitals captured per visitImmunization and review visit scheduling
Specialties differ in configuration, not in code: the same modules are enabled and set up differently. Where a specialty needs a capability the platform does not have yet, we say so during the demo rather than after you buy.
See it running with your own workflows.
Book a walkthrough and we will map your clinic or hospital onto the platform, module by module.