DevMilestones

Who uses it

Built for: Paediatrics

Reads

Assessments, surveillance schedule, test results

Writes

Screens, referrals, completed and due screenings

Never

It does not label a child from a screen — screens route to assessment, and the language stays careful.

Access

Only people whose role includes it — the clinic owner decides who

Your data

Full PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record; operational history stays queryable.

In the product

1. 1Enrol on the date of birthThe date of birth starts the care plan, so the screens at 9, 18, 24 and 36 months date themselves as ages rather than as calendar appointments.
2. 2Record the screen’s five domainsCommunication, gross motor, fine motor, problem solving and personal–social each take pass, monitor or refer; the same screen month twice for one child is refused.
3. 3A refer opens an action in the same transactionAny domain marked refer writes an action row naming which domains referred, in the same transaction as the screening — not afterwards, and not by a sweep.
4. 4Record the M-CHAT, and close every action with what was doneA score on 0–20 at 18 or 24 months; the risk band is computed in the select, and a high score opens its own action row in the same transaction. The registry’s loudest column is the open-action count, and closing one states what was done.
5. 5Run a condition’s surveillance scheduleThe Surveillance tab holds your practice’s own schedule per condition — Down syndrome first — each item with the age it falls due, any repeat and its source; a child’s items are dated from the birth date, done ones are recorded with the result as reported, and the child with the most overdue comes first. Retiring an item never rewrites what was recorded.