Glossary

MedNAIS™ Terms and Definitions

The words the product uses, in the sense the product uses them.

Educate, Assist, Monitor efficiency

The names of the three things MedNAIS does, in the order a reader meets them. Educate: somebody learns a procedure by being taken through it step by step rather than by reading the document beforehand. Assist: while the work is happening, the full step on a phone or tablet and one short line on a watch when a phone is out of your hands. Monitor efficiency: which published version was performed, by whom and in what order, how long each step took — the efficiency of the procedure, measured against your own organisation’s history. Not a ranking of people, not a productivity score, and never compared with anything outside your organisation.

SOP (standard operating procedure)

The written instruction for how a piece of work is done, as a sequence of steps. In MedNAIS a procedure has versions, and a version has to be published by a person before anybody can run it.

Organisation

The account everything belongs to: one site, department or employer. Procedures, documents and execution records belong to an organisation rather than to a person, and are separated from every other organisation at the database level.

Step

One instruction inside a procedure, and what it asks for when it is performed: a confirmation, a checklist, a timed wait, a yes-or-no answer, or a code that can be scanned or typed in.

Execution (a run)

One performance of one published version of a procedure by one person: which steps were done, in what order, which were skipped, which were returned to, and how long each took.

IFU (instructions for use)

The instructions a manufacturer supplies with a product, traditionally a printed leaflet in the box. MedNAIS can publish a step-by-step procedure to a printed QR code so that the person holding your product follows it in a browser instead, which is what the application’s name in both app stores — MedNAIS — SOPs and IFUs — refers to. It is not an eIFU system in the regulatory sense: we make no claim under the EU medical device or IVD regulations, none to the FDA, and we take on none of a manufacturer’s obligations about the form, languages, availability or paper supply of instructions.

Public procedure (a printed code)

A published version put on an eight-character code with a QR you download and print. Anybody holding the code can open it without an app, an account or a sign-up, and no cookie is set on them. The code is minted once and never reissued, so correcting the procedure needs no reprinting — but the link keeps serving the version it was last published to until you publish to that code again. Unlike the app, it needs a network: the page is deliberately never cached, so that withdrawing a procedure actually withdraws it.

Draft

What a language model produces from a document you upload or a description you type. It is not a procedure until somebody qualified in the work has read it in full and published it, and the product will not publish a version on its own.

Time per step

How long a step took on a given run, and — aggregated — the median and 90th percentile for that step across your own organisation’s recent runs. It describes your practice. It is not a norm, a target or a limit.

Role

Owner, administrator or member. What each may do is enforced by the database rather than by which buttons are shown: an administrator can invite and remove members but cannot create another administrator, and an organisation is never left without an owner.

Invite

A link that lets somebody join an organisation, carrying an expiry, a limit on how many times it can be used, and optionally a restriction to one e-mail domain.

Identity entry mode

Whether a code was scanned or typed in by hand. The record keeps the difference because they are evidence of different strength, and passes no judgement on either: typing a code in has legitimate causes that only somebody who knows the work can weigh.

Execution record

The organisation’s account of its own work: what was performed, by which version, when and in what order. Useful evidence that a procedure was followed. Not an audit, not a certificate, and not proof of compliance on its own.

Sub-processor

A company that processes customer data on our behalf. Ours are Supabase, Vercel, Anthropic, OpenAI, Google and Apple; what each receives and where it is are listed in the privacy policy.