Frequently Asked Questions

What is hema.to?
How does hema.to differ from traditional softwares?
What training resources are available for hema.to?
What kind of support does hema.to offer?
Can I adjust the results after the automated data analysis?
Do I have to use a specific cytometer / panel / workflow?
How many files per disease do the algorithms need in order to be trained?
How does hema.to protect against data breaches?
How does hema.to handle security vulnerabilities?
How are security incidents reported and resolved in hema.to?
Does hema.to have a disaster recovery plan?
How is user access managed in hema.to?
What measures are in place to ensure the security of mobile or remote access?
How do I know that sensitive data is being encrypted? What kind of encryption does hema.to use to protect data?
What is the GDPR and is hema.to compliant with it?
Is hema.to complying with the evolving regulatory requirements?
Do you have a Quality Management System in place to ensure compliance with relevant healthcare regulations?
Do you provide training and support to users to ensure they understand the regulatory requirements related to your healthcare products?
How do you prepare for and handle audits or inspections by regulatory authorities such as the Notified Bodies?
Have you conducted clinical evaluations or performance studies for your software?
Is hema.to compliant with the EU's In Vitro Diagnostic Regulation (IVDR) or the previous In Vitro Diagnostic Directive (IVDD)?
How do you monitor the performance of your medical devices or diagnostic software after they have been placed on the market?
What types of businesses benefit most from using hema.to?
Can hema.to scale with my business?