Clario Forms

Challenge

Forms are how regulated and operational industries still capture structured data: HR onboarding, performance reviews and leave flows; anamnesis and referrals in healthcare; KYC and onboarding in finance; intake and consent for legal mandates; vendor onboarding and incident reports in industrial settings; request and qualification flows in public services. The pattern is the same: someone fills a paper or PDF, the data is re-typed into a system of record, the audit trail lives in handwritten notes, and the export to a downstream system is a separate, error-prone step.

Clario wanted a single forms platform that solves the structural problem once: design a form by uploading a PDF, capture data with field-level provenance, route every submission to the right destination - whether that’s a webhook back to a source system, a secure inbox, or a regulated archive. HR was the first vertical to deploy it - employee onboarding, performance reviews, leave and compliance flows, all under role-aware field access and an immutable audit trail. Healthcare followed as the most regulated integration to date, hardening the platform against medical-secrecy rules, qualified-actor gating and EPD delivery. The same primitives now serve any branch that needs structured intake under audit.

The bar: someone fills a structured form in 90 seconds; the back office sees who entered what, with which qualification, in 15 seconds; a submission lands at every required destination without a second tool.

Approach

Three platform primitives, applicable to any vertical:

• Schema in 2 minutes from a PDF. Drop a PDF; the platform extracts fields, suggests types and validation rules, and produces a live, branded web form ready to issue. No drag-and-drop builder, no engineering ticket.
• Qualified actors and field classes. Every field carries a sensitivity class (administrative, sensitive, regulated). The platform gates edits and signatures against the actor’s verified qualification - employee role, professional licence, regulator-issued ID. In HR it means employee / manager / HR-partner gating with role-based field access on personal data; in healthcare it means physician / nurse / medical-assistant gating with the GLN cross-referenced against MedReg, NAREG or PsyReg; in finance it means RBAC against your IDP plus a qualified e-signature; in any vertical it means the right person signed the right field.
• Multi-destination delivery. A submitted form ships as a structured webhook back to the source system (HRIS, CRM, practice system), as a PDF/A-2b archive through secure messaging, and (in healthcare) as a CDA-CH or FHIR CH-EPR document into the patient’s EPD via IHE XDS.b after consent check. New destinations plug in as adapters; existing forms ship to them without redesign.

Quarkus + Next.js on PostgreSQL, hosted in Switzerland. Every field change becomes an immutable revision with actor, qualification, ID and timestamp - the long-term audit trail regulated industries are required to keep (ten years for medical practices in Switzerland, varies by sector and jurisdiction elsewhere).

HR: where Clario Forms first went into production

HR was the first deployment because the form-and-audit pattern is universal there: an employee onboarding form, a performance review routed manager-to-HR-partner, a leave request that has to land in the HRIS and an archive PDF, a compliance training certificate that must hold up at the next regulator visit. Clario Forms covers this end to end - schema in two minutes from a PDF, role-aware field access, structured delivery into the HRIS via webhook plus an archive-grade PDF/A. The same instance hosts the next vertical’s forms without a separate platform.

eHealth: the deepest standards integration today

Healthcare carries the strictest constraints, so the Swiss eHealth feature set is where Clario Forms goes deepest in standards compliance: a session opens with a FHIR Bundle (CH Core Patient, Conditions, Allergies, Medications) launched from the practice system; field auto-completion runs via JSONata navigation of the bundle; submissions deliver as CDA-CH or FHIR CH-EPR into the patient’s EPD via IHE XDS.b after consent. This is the proof that the platform’s primitives hold under audit at the toughest posture, and serves any other vertical that needs structured intake, role-aware capture, and multi-destination delivery.

Deployment

Clario Forms is available as a white-label product for organisations that want to issue forms under their own brand and choose their own data residency:

• Single-provider - an HR shared-services group, a hospital, a large practice, an insurer, a bank, a public agency or an industrial group runs its own branded instance (“Forms by [your name]”) with its own support contract and data location, and connects only its own organisation and staff.
• Community-provider - a federation, cantonal network, professional association or industry consortium operates one shared, co-branded instance for its members, with central administration and a separate tenant per member.

A cloud edition operated by Luzid in Switzerland remains available for smaller organisations that prefer a turn-key option.

Outcome

The platform serves the workflow each tenant designs it for. An HR shared-services team runs employee onboarding with role-based field access, performance reviews routed manager-to-HR-partner, leave requests pushed to the HRIS with an archive-grade PDF/A copy. A Swiss medical practice runs anamnesis-before-appointment, referrals-out-of-the-consult, EPD-upload with one click. A financial intermediary runs KYC intake, qualified e-signature, archive-grade PDF/A delivery to its compliance system. A public-service operator runs request and qualification flows with role-based field access. The architecture targets the audit and retention rules each industry already operates under, so a deployed instance answers its regulator on its own terms rather than through bolt-on tooling.

For Luzid’s broader Swiss eHealth practice, see the eHealth services page.