One product, four parts
Educate · Assist · Monitor efficiency
Those three promises arrive in four parts: MedNAIS™ is a console in the browser, an app in somebody's hand at the job, the record that comes out of the two, and a printed QR code that hands the same procedure to whoever is holding your product. One account covers all of it, and there is nothing else to bolt on.
The console
Where SOPs are written and published, people are invited and given roles, runs in progress are watched, and the history is read. Writing, publishing and design also work in the phone apps.
In detailWhat it does
- Write a SOP, or draft one with AI from a document, photos of its pages or a link
- A person with the publisher role has to publish a draft before anybody can run it
- Roles for owners, administrators, publishers, authors and members
- Invitation links with an expiry, a use limit and an optional e-mail-domain restriction
- A live board of the runs in progress
At the point of work
The half somebody holds during the job. One step at a time, in the order the procedure sets out, with the full text of each step — and it keeps working when the network does not.
In detailWhat it does
- Confirmations, checklists, timed waits, yes-or-no answers and barcode scans, with pictures and video
- A wait is skipped only with a reason, and a problem can be reported on any step
- Go back a step without erasing the earlier attempt
- Works offline; the record is kept and sent when the network returns
- Write, edit and publish SOPs on the phone too
Records and analytics
Which version of a procedure was performed, by whom, in what order, and how long each step took. Enough to find where a procedure loses time, and enough to answer an incident review.
In detailWhat it does
- Per-step timings drawn from your own organisation’s recent runs
- A filterable history of past runs
- Weekly and monthly summaries, generated automatically
- CSV export of whatever the filters select
- Whether a code was scanned or typed in, without judging either
Public IFUs
The same procedures, published to the people holding your product. They scan the printed code and follow the steps in a browser, without an app and without an account — and the runs come back to you with the time spent on each step.
In detailWhat it does
- An eight-character code and a QR you download as an SVG to print
- No app to install, no sign-up, and no cookie set on the reader
- Timed waits count themselves down; six interface languages for the reader
- Your name and logo first, in one of seven start-page styles with your colours and cover photo
- Correct the procedure and re-publish to the same code — no reprinting
Things this product does not have
- No voice controlSteps are read and confirmed by touch. Earlier versions of this site advertised voice commands and gesture navigation; neither was ever built.
- No integrationsNo HL7 FHIR, no LIS or LIMS connector, no hospital information system. Data leaves as CSV.
- No hardwareNo sensors, no temperature or GPS logger, no transport device. The phone camera reads barcodes and takes the photos you choose to add — nothing more.
- No report builderThe analytics are the screens described above plus a CSV export. There are no saved report definitions, no user-defined metrics and no PDF output.
- No branding of the consoleAn organisation sets its name, logo and timezone, and the console looks like ours throughout. What you do style is everything your customers see: the public SOP a printed code opens leads with your name and logo and takes your design template, colours, start-page style and cover.
- No plans or tiersNothing to compare and nothing to be moved between — see access and pricing.
And a watch, if hands are busy
The watch app shows short steps and hands its record back to the phone. It is a companion to the phone app rather than a separate product: it needs the paired phone, the full text of a step is on the phone, and nothing is sold or licensed for it separately.
Four example procedures, no account
A warehouse, a production line, a laboratory and a building site. Nothing done in the demonstration is recorded or sent anywhere. If you accepted cookies, Meta learns only that the demonstration was opened.
Open the demonstration