VideoSuite

Video consultations with health data: isolation enforced by the database

Clinical meetings do not go through the general analysis engine or the shared memory, and the database enforces it. How it works with TrichoSuite and what it does not promise.

Health data has special protection under the GDPR (Article 9). In VideoSuite a clinical meeting is flagged as such by the system that creates it, and from then on the database prevents it from using the general analysis engine: a constraint of the database itself, not an instruction to a model. Its data is not sent to MemoryFirst either.

Who it is for

For clinics and practices that run video consultations and need a room with their own brand and domain, and for sensitive data not to leave a bounded circuit.

What it does, step by step

  • The meeting is created from the clinic's system through a server-to-server integration.
  • The database enforces isolation: a clinical meeting cannot use the general transcription and analysis engine.
  • The clinic has its own domain (for TrichoSuite, video.trichosuite.com) and single sign-on with its accounts.
  • The summary can be sent as a link-only email, with no clinical content inside the message.

Honest limits

  • VideoSuite is a communication tool, not a medical device, and makes no promises about clinical results.
  • Compliance (legal basis, patient information, retention periods) remains the clinic's obligation.
  • Today the integration is in production with TrichoSuite; other clinics are set up with our help.

Which plans include it

What each plan includes, with prices and the own-brand extra, is in the plans section of the site: VideoSuite's features are described here as they work today in production, and some (such as own brand or own domain) depend on the plan.

See all articles