Misuse of software

In a regulated workflow, a misunderstanding of a feature can lead to processing the wrong data, mis-classifying a result or producing a report that does not reflect the evidence. Misuse usually stems from configuration steps that look similar to other actions, or from features being used outside their intended purpose.

Hazardous situation: The software processes incorrect data, or produces misleading output, because a user did not use a feature as intended.

• Detailed feature guides. Each module has step-by-step documentation: Create a Search, Define a Search Strategy, Understanding Operators, Evaluate Reports, and the corresponding pages under Literature Evaluation and Regulatory Monitoring.
• Work-instruction templates. Flinn provides editable templates you can adapt for your SOPs — see Work Instructions Template for your SOPs.
• Search-quality safeguards. Common pitfalls in search execution are documented in the FAQ — see Why does my search execution fail?, I have too many poor relevancy results. How can I improve my search? and Can I get help to create a search?.
• Help where you need it. The in-app chat (see What is the web chat?) is the fastest way to clarify whether a feature is being used as intended.
• Audit and recover. All actions are logged in the Audit Trail so misconfigurations can be identified and reverted.

When in doubt, prefer the documented path or ask support — see How can I report a problem?.