Fit the technology to the service

Zild provides configurable clinical workflows, shared records, questionnaires, booking, communication, billing and analytics. We assess which components suit your needs and which functions should stay in your existing systems. Cross-organisation coordination is designed around the specific service and its responsibilities.

01

One component

Add a questionnaire, documentation or communication capability to a defined part of your service.

02

A coordination layer

Bring roles, tasks and data together across your systems, with an agreed source of truth for each record.

03

A clinical platform

Support an end-to-end clinical service where broader platform adoption fits your organisation.

Security, data & interoperability

Make the technical conversation concrete.

We design solutions around GDPR and UK GDPR requirements, with information security practices aligned with ISO/IEC 27001. We work with European hosting regions on AWS and Microsoft Azure and support FHIR-compatible integrations. Data location, access arrangements and integration requirements are agreed as part of each deployment.

Identity, roles and auditability

The platform’s technical description includes role-based access, service-level authorisation, audit trails and session logging. It describes support for Estonian e-ID / TARA, OAuth 2.0 and OpenID Connect. The appropriate identity and permission model is agreed for each deployment.

Integration with national and partner systems

The documented integration approach uses APIs, including X-Road and HL7 FHIR. Existing clinical, laboratory and organisational systems are assessed during discovery. Interfaces, data ownership and the scope of each connection are specified before implementation.

AI processing and professional control

AI support is embedded in clinical workflows as editable suggestions and draft documentation. The technical description sets out server-side processing, data minimisation and auditable request and output logs. Data sent to each model and the professional approval steps are reviewed for the specific use case.

Deployment and procurement review

We address hosting and data location, processors, retention, GDPR responsibilities and the intended use of any AI capability as part of the solution design. Request the technical description and a deployment-specific review to assess your requirements.

Technical capability descriptions are based on HeBA’s November 2025 platform document and April / September 2026 service material.

Could this work for your service?

Share the overview with colleagues or send Ain your question.