DocumentsHub

It handles form filling and signing where it actually happens: on the tablet in the practice. The patient fills the form and signs on screen, and the finalised document keeps proof of who signed it and when. Use it standalone or integrate it over its API, so you do not rebuild a signing flow inside every application.

Modules and capabilities

• Tablet kiosk mode

  A separate interface for the tablet handed to the patient: fill, read and sign on screen, with no access to the rest of the application.

• Versioned templates

  Every form has published versions. A published version is never edited again — corrections produce a new version, so you know exactly which text the patient signed.

• Immutable documents

  A finalised document can no longer be changed. That is the difference between a signed PDF and evidence that holds.

• Admin portal

  The practice manages its templates, documents and users. The portal consumes exactly the same public API as external integrators.

• API for integration

  Another system can request a document signature and receive the result, without the patient leaving the practice's usual flow.

• Long-term archiving

  Documents sit in storage protected against deletion and overwriting, for the required retention period.

What sets it apart

• Independent of your current software

  It works standalone, alongside any practice software — the first user runs it with no integration at all.

• Proof of signing, not just the document

  Who, when and against which version of the text — the data that turns a PDF into usable evidence.

By domain

• Medical clinics
• Companies and SMEs

Price on request

Pricing depends on user count and the modules you need, so I discuss it case by case.

Request a quote