For regulatory & quality teams

Here’s why regulatory & quality teams love Steago, explained via FAQs.

Every answer on this page is a design constraint we hold ourselves to, not a configuration option.

No generated textVersion-lockedNo personal data by default

Does it generate text?: No. Steago retrieves and displays passages from documents you supplied. It does not paraphrase, summarise, translate, or combine passages from different documents into a new statement.
So what is the output, in labelling terms?: Your own approved labelling, reproduced exactly, with attribution. If a passage was acceptable in the IFU, it is acceptable in the answer, because it is the same text.
What happens when there's no good answer?: It says the instructions for use don't cover that question and directs the user to your support channel. It never approximates.
Which version does it quote?: The version you published. Version, document ID and language are attached to every passage and shown with every answer. Withdraw a version and it stops being served.
Does it translate?: No. It returns the passage in the language it was approved in, from the language edition you published. Machine-translated labelling is not something we will ship.
Do you collect patient data?: No login, no accounts, no personal data collected by default. There is nothing for a BAA to cover in the standard configuration.
Can we see what people asked?: Yes, and this is the part worth paying attention to. Question logs show you which sections of your IFU users can't find, which error codes come up most, and which devices generate the most confusion — with no identifiers attached.
Who's accountable for the content?: You are, as you already are for your IFU. Steago doesn't change that, and doesn't add to it.

Is there a question here we haven’t answered here?

Please ask away. Send it to team@steago.com and it gets answered by the people who build the engine, not a sales team.

Email us See it running on your own IFU