Question 1

What is MedNAIS™?

Accepted Answer

Software for carrying out the written procedures an organisation already has, and it does three named things with them: Educate, Assist, Monitor efficiency. You write a procedure — or draft one from a document you upload — a qualified person publishes it, people learn it and run it step by step on a phone or a watch at the point of work, and afterwards you can see what was done and how long each step took.

Question 2

What do Educate, Assist and Monitor efficiency mean?

Accepted Answer

They are the names of the three things the product does, and each one is a promise rather than a feature. Educate: somebody learns the procedure by being taken through it step by step, rather than by reading the document beforehand — which is not a course, has no examination and issues no certificate. 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, with KPIs drawn from your own organisation’s runs and a compliance record you can export. The third one measures a procedure, not a person: there is no ranking of employees, no productivity score and no comparison with anybody outside your organisation.

Question 3

Is it a medical product?

Accepted Answer

No. It is not a medical device, does not diagnose, treat or monitor anybody, and makes no decision about any patient. Healthcare and laboratories are one of four kinds of work it is addressed to, alongside manufacturing and maintenance, logistics and warehousing, and construction and workplace safety. Earlier versions of this site described MedNAIS as a medical SOP platform for hospitals and laboratories; that was too narrow and it was wrong. One consequence worth spelling out, because the public half of the product invites the question: publishing a procedure to a printed QR code is not an eIFU system in the regulatory sense. We make no claim under the EU medical device or IVD regulations and none to the FDA, and we take on none of a manufacturer’s obligations for instructions for use — not the form they must take, not the languages, not how long they must stay available, and not a paper copy a customer may be entitled to request.

Question 4

Who makes it?

Accepted Answer

Samplify FZCO, a company registered in Dubai, United Arab Emirates, at DDP, Building A2, office 101.

Question 5

What are the parts of it?

Accepted Answer

A console in a browser at sop.mednais.com, where procedures are written and published, people are invited and given roles, and the records are read. A phone and tablet app for running a procedure at the job, with a watch companion for hands that are busy. And a printed QR code, which hands the same procedure to somebody outside your organisation — a customer holding your product — who follows it in a browser with no app and no account. One account covers all of it, and there are no separate products to license.

Question 6

Can we publish instructions for our customers on a QR code?

Accepted Answer

Yes — that is the public half of the product, and it is why the application is called MedNAIS — SOPs and IFUs in both app stores. You write the procedure in the console, publish it to a code, and download the QR as an SVG to print on the box, the instrument or the leaflet. Somebody scanning it gets the steps one at a time in a browser: no app to install, no account, no sign-up, and no cookie set on them. Timed waits count themselves down and end on their own, the page carries your organisation’s name, logo, support contact and chosen look rather than ours, and the reader picks their interface language from six. Every run comes back to you with the time spent on each step, identified by an eight-digit number because nobody signed in. Three things it is not: it is not offline — a printed code opens a web page, which is deliberately never cached so that taking a procedure down actually takes it down; it does not update itself — correcting a procedure leaves the printed link serving what it served until you publish it to that code again, and the console tells you when the two have come apart; and it is not a regulatory product — 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 for instructions for use.

Question 7

Can I see it without signing up?

Accepted Answer

Yes. The demonstration at sop.mednais.com/demo needs no account and no sign-up: four short example procedures in a warehouse, a production line, a laboratory and a building site. Nothing you do in it is recorded or sent anywhere. If you accepted cookies, Meta learns only that the demonstration was opened.

Question 8

What does it cost?

Accepted Answer

Free to start, and using it with your own procedures needs no arrangement: sign in at sop.mednais.com, create an organisation, and write a procedure. Nobody has to approve it and no card is asked for. Past the free allowances there are two meters and no tiers: a licence is $159.99 per person for the year, charged once, and a publication pack is $159.99 for five public SOPs for the year, charged once. Tax is added at checkout, so a buyer outside the United States pays more than the figure. What costs nothing: one shared organisation you create yourself, two procedures and two people in it, and one procedure published to a printed code for the public to read — with nothing to renew. A licence is spent when somebody is admitted to an organisation and lets them write procedures; reading one and carrying one out needs no licence, so the people doing the work are not what you are counting. Everything is bought in the browser at sop.mednais.com; nothing is sold inside the mobile apps, which draw no price and offer no purchase control. An organisation that already exists gets at least thirty days notice and an export of everything before anything changes for it, and that is in the terms rather than a promise made here.

Question 9

What file formats can I upload to draft a procedure from?

Accepted Answer

PDF, Word (.docx) and plain text. The type is decided by the contents of the file rather than by its name. A scanned PDF with no text layer is refused with an explanation, because there is nothing in it to write from.

Question 10

Does uploading a document give me a finished procedure?

Accepted Answer

No — a draft. A language model can state an incorrect quantity, temperature or interval, omit a control or a safety step the source document requires, or attribute a requirement to a standard that does not contain it. So a person qualified in that work has to read the draft in full and publish it before anybody may perform it, and the product will not publish a version by itself. That gate cannot be switched off.

Question 11

Where do the documents I upload go?

Accepted Answer

Into your own organisation’s area. They are shown to no other customer and are not used to train or fine-tune any model. To draft from a document, its extracted text is sent to Anthropic and OpenAI as our processors — which matters if the document is a standard licensed on terms that forbid disclosure outside the licensed entity. Our privacy policy names everyone who receives what.

Question 12

Does MedNAIS keep a library of standards I can use?

Accepted Answer

No. Procedures are written from the documents you supply and from nothing else. Where you have no document to hand, MedNAIS can name the documents that ordinarily govern that work and check each name against the register of the body that issues it, so you see the designation, title and edition the register returned. Obtaining the document is yours to do; we do not supply, license or resell standards.

Question 13

What do the timing figures mean?

Accepted Answer

Median and 90th-percentile time per step, calculated from your own organisation’s recent runs of that step. They answer "how long does this usually take here". They are not a norm, a target, a limit or a violation, and they are never compared with an outside standard — a step can be entirely typical for the people doing it and still be too slow for the work, and this data cannot tell the difference.

Question 14

Is it a way of ranking staff?

Accepted Answer

No, and there is no leaderboard in the product. There is a per-performer breakdown, which is a different thing. The useful question the data answers is which step of a procedure loses the time, which is a question about the procedure.

Question 15

Does the app work without a network?

Accepted Answer

Yes, for procedures already fetched. What is recorded is kept on the device and sent when the network returns. We deliberately stop short of promising delivery while the app is closed: background delivery is unreliable on several Android builds, and advertising it would not be honest. The question has a different answer for a public procedure opened off a printed QR code: that is a web page and has to be fetched, and it is deliberately never cached, because whether a code still answers has to be decided when the reader asks rather than when a cache expires. Offline is the app’s property, not the printed code’s.

Question 16

Which devices does it run on?

Accepted Answer

The console runs in a browser. The app runs on iPhone and Android phones and tablets, with companion apps for Apple Watch and Wear OS. A watch app needs its paired phone and shows short steps; the full text of a step is on the phone.

Question 17

Does the app use voice control or the camera?

Accepted Answer

There is no voice control, no voice commands, no gesture navigation and no audio prompts — earlier versions of this site advertised all four and none was ever built. The camera is used on Android only as a barcode detector: frames are analysed on the device and discarded, never stored and never uploaded. On iPhone the camera is not opened at all and a code is typed in.

Question 18

Is MedNAIS HIPAA compliant? Do you have ISO 27001 or SOC 2?

Accepted Answer

No, to all three. We hold no security certification, no attestation, no independent audit report and no HIPAA arrangement, and we cannot sign a Business Associate Agreement. MedNAIS is not designed to hold protected health information and should not be used to hold it. We would rather you read that here than discover it in a procurement review.

Question 19

Does it integrate with our hospital or laboratory system?

Accepted Answer

No. There is no HL7 FHIR interface, no LIS or LIMS connector and no hospital-information-system integration. Earlier versions of this site claimed FHIR support; that claim was false. Data leaves the product as CSV, exported from whatever the analytics filters select.

Question 20

What does MedNAIS record about the person or thing the work concerns?

Accepted Answer

Nothing, by design. The execution part of the product stores no patient identifier, no diagnosis, no observation — and equally no customer, no vehicle registration and no name of whoever the work was done for. A procedure describes how work is done; it does not need anybody’s name. Free-text and code fields at the point of work are where such data could arrive anyway, and the app asks you not to put it there.

Question 21

How do I delete my account?

Accepted Answer

Yourself, at once, without asking us: on your account screen in the app, under Sign-in and security in the console, or from mednais.com/delete-account, which anybody can open without an account. You confirm by typing the address the account belongs to. It cannot be undone. What your organisation keeps — the record of procedures you carried out, no longer naming you — is set out on that page and in our privacy policy.

Question 22

Can we get a data processing agreement?

Accepted Answer

Yes. That we can do now, independently of any commercial arrangement, and we will answer a security questionnaire as candidly as our security page does. Write to mednais@samplify.org.

Frequently Asked Questions