FluentPRN shows clinical staff exactly where to click in new hospital systems, one step at a time, using walkthroughs your educators have reviewed and published.
Now selecting our first pilot hospitals in Ohio.
Classes and videos land weeks before go-live. By the time staff meet the real screen, the details have faded.
Super-users and help desks cover whole units and whole systems. On a night shift there may be nobody nearby to ask.
When nobody can show the right way, people invent their own. Those shortcuts get passed along and are hard to undo.
“How do I add an allergy?”
Example for illustration. Real walkthroughs are written for your systems by your educators.
Press a keyboard shortcut from inside the application and ask, for example, “How do I add an allergy?”
FluentPRN outlines the button or field to use, with one short instruction. Do the step and the next one appears. Staff always make the click themselves.
Educators draft walkthroughs with AI help in a test environment, check each step, then publish. Staff only ever see published walkthroughs. A question with no approved answer is sent to the education team as a request.
How FluentPRN is built to behave on a hospital floor.
FluentPRN highlights and explains. It never clicks, types or submits anything. The person at the keyboard makes every decision.
Each step is matched to a control the application actually shows. If the software changes and a control is missing, the walkthrough stops and goes back to your educators for review.
Each AI draft is generated twice. If the two disagree, the step is flagged for an educator instead of being presented as confirmed.
Steps that delete, sign, submit or discharge carry a clear warning before they are shown.
Questions about doses, diagnoses or treatment get a fixed reply pointing staff to clinical resources. FluentPRN only explains how to use the software.
We do not hold these today. Until we do, pilots use test environments and sample data only.
Your learning system assigns and tracks training. FluentPRN helps at the moment someone is stuck, inside the application itself.
FluentPRN highlights the specific button or field, not just the window, in applications that expose their controls to Windows accessibility.
It sits on top of the application and changes nothing inside it. How much it can see varies by application, so each pilot starts by testing the systems your staff use.
PRN is the clinical abbreviation for “as needed.” FluentPRN works the same way: guidance appears only when a member of staff asks for it, and stays out of the way the rest of the time.
No. It highlights the control and gives a short instruction. Staff make every click and keystroke themselves.
Windows desktop applications that expose their controls to Windows accessibility. Coverage varies by application, so every pilot begins by testing the specific systems your staff use.
Pilots run on test environments with sample data only. Before any live use we require redaction of on-screen text, a signed business associate agreement and a SOC 2 audit.
Staff see a short message saying none exists yet. The question is sent to your education team as a request, so they can see what people need and publish an answer.
Your LMS assigns and tracks training ahead of time. FluentPRN helps in the moment, inside the application, when someone is stuck on a real task.
If a step no longer matches the screen, FluentPRN stops, tells the user, and marks the walkthrough for review. Your educators update it and publish it again.
A team of four students at Miami University in Oxford, Ohio. You can read more on our About page.
FluentPRN is in active development and has no customers yet. We are looking for our first Ohio hospitals to build alongside.
We hold no security certifications yet. SOC 2 and a BAA come before FluentPRN is used with real patient data.
