WHAT CHANGES BY APPLICATION
The source document → the reviewer who approves it → where the code is printed
A course syllabus, a discharge template, a package insert. Different material, different approver, different piece of paper.
WHY THERE IS ONLY ONE OF THESE
Three applications. One engine underneath.
Education, hospitals and pharmacy are not three products. They are the same engine fed different source material, approved by a different reviewer, opened from a different piece of paper — and taught, heard, questioned and counted identically.
WHAT DOES NOT CHANGE
Approved material → interactive lesson → read or heard → questions answered → aggregate view
One engine, one set of behaviours. Building a new application is a matter of approved material and a reviewer, not of new software.
WHAT THE SYSTEM RECORDS
Aggregate interaction data. Nothing about a person.
The engine records how its own material was used. It does not record who used it: no name, no identifier, no clinical or academic record, and nothing an organisation has to send us for the lesson to work in the first place.
WHAT AN ORGANISATION SEES
Where the material is landing, and where it is not.
Everything below is counted across a population rather than attributed to a person, and all of it comes out of the lesson itself — there is no system we connect to in order to produce it.
DELIVERY
Opened and finished
How many lessons were opened, how many were finished, and the median time taken to finish one.
COMPREHENSION
Answered and replayed
How the comprehension questions were answered, which concepts were replayed most often, and which segment of a population answers lowest.
LANGUAGE
Which language it ran in
The share of lessons delivered in each language that is live — a fact about a population, never about a person.
OUTCOME CHANGE ATTRIBUTED TO THE ENGINE
—
That box is empty and this page will not fill it. No pilot has reported an outcome to us; the aggregate view above is what the engine produces on its own, and anything in that box would have to come from an organisation’s own instrument, in its own population.
REVIEW, CONTROL AND DEPLOYMENT
Your material, your approval. No integration project.
-
YOUR MATERIAL
Nothing publishes unapproved
Lessons are built only from material the organisation supplies and approves. A named reviewer on that side reads what was built and says yes before it is published — approval is the gate, not a check after the fact.
-
NO INTEGRATION PROJECT
Nothing to integrate
No interface to build, no feed, no portal and no new screen for staff. The lesson opens from a code or a link on paper the organisation already produces, which is why there is no engineering project on the other side.
-
NOTHING IDENTIFYING REACHES NAC
Nothing identifying reaches us
The code carries the material, never the person. There is no account to create, no roster to send and no record to transfer in order for a lesson to open and be answered.
An application is approved material, a reviewer, and somewhere to print the code.
That is the whole of the difference between education, a hospital and a pharmacy. The document changes and the person who signs it off changes; the teaching, the read-aloud, the languages, the questions and the aggregate view are one engine underneath all three.
WHERE TO GO NEXT
Pick the one you came for.
The engine is the same in all three. What each page describes is the material it is fed and the workflow it prints into.
Education
Tutoring and test prep across the program catalogue — the concept taught out loud, drilled until it sticks, then played as a game. From early grades to licensing exams.
SEE THE PROGRAMS →Hospitals
A code on the discharge packet opens the whole discharge, taught: every medication and the recovery itself, read or heard in the language they speak at home, with questions confirming it landed.
HOW IT WORKS FOR HOSPITALS →Pharmacy
A code on the prescription bag opens a lesson about a minute long on that exact medication, in the language they speak at home — read or heard at pickup.
HOW IT WORKS FOR PHARMACY →THE ASK
Send one document you already hand out. We will build the lesson from it.
Thirty minutes, one piece of material your organisation already approves, and the lesson the engine makes of it — read and heard, in English and Spanish — before you decide anything.
Request a Demo