Security & Trust

Regulated work calls for clear controls and accountable decisions.

Regulated work requires more than a useful output. It requires appropriate information handling, clear responsibilities and confidence in the process.

DahliaIvy is developing Dahlia for regulated life-sciences organisations where controlled information, professional accountability and supplier qualification are part of everyday operations. Our approach is to make the work, its supporting evidence and the responsibilities around delivery understandable and assessable.

The founding-client service is being established around controlled Microsoft 365 collaboration, defined AI-processing permissions and accountable review. The arrangements applicable to each engagement are confirmed before client information is provided.

Implementation status

What is available and what is being developed.

Current public engagement

DahliaIvy offers discussions about defined regulated-work engagements. The public website's enquiry forms are for initial contact, not confidential work submission.

Public website enquiries currently use Formspree, a third-party form service. These forms are not for confidential or regulated work submissions. Founding-client collaboration is being developed separately through Microsoft 365.

Founding-client capacity service — being implemented

Separate client workspaces, at-any-time structured submission, a central work queue, controlled processing authorisation, workflow execution, founder technical review and return of draft outputs.

Future direction

Controlled connections to client document repositories and quality systems, subject to technical development and client approval.

The founding-client model below describes the intended operating arrangement. Delivery will begin only after internal workflow and end-to-end testing are complete, readiness for the proposed engagement is confirmed and the applicable controls are agreed. These arrangements should not be treated as already implemented or independently certified.

Your systems remain the authoritative record

Dahlia is a work-processing layer, not a replacement for your quality management system or controlled document repository.

Your organisation's QMS, eQMS, SharePoint environment or other approved repository remains the authoritative location for controlled records.

Dahlia prepares work for review and returns agreed deliverables to the client. Your authorised personnel determine what is accepted, approved, implemented and filed within your controlled systems. Direct integrations are a future capability, not a requirement for initial engagements.

Separate workspaces for founding clients

Founding-client engagements are intended to use a DahliaIvy-hosted Microsoft 365 workspace established separately for each participating organisation.

The workspace is intended to support work submission at any time across agreed workflows, submission of agreed evidence, collaboration and access to review-ready outputs. At-any-time submission does not imply a 24/7 staffed response or instant turnaround. Access and file organisation will be configured to keep each client's information separate from that of other clients.

The precise configuration, authorised participants and sharing arrangements will be agreed during onboarding. A separate workspace does not necessarily mean a separate Microsoft 365 tenant.

Access and sharing

The founding-client access model is designed around named, authenticated users and permissions appropriate to their responsibilities.

Planned controls include restricted membership, least-privilege access, controlled external sharing, access review and removal of access when it is no longer required. Routine anonymous access is not part of the intended approach for regulated client work.

The available authentication, sharing and activity-recording controls will be confirmed for each deployed workspace before use.

AI processing is a controlled step

Ivy is the AI inside Dahlia. Within an agreed workflow, it supports evidence review, structured analysis, identifying gaps and preparing draft documents or other work products.

Scope, data handling, permitted information, any permitted AI use, relevant technology providers and review responsibilities will be agreed before controlled client materials are accepted. Uploading a file is not intended to constitute permission for AI processing.

Work must pass a defined processing decision before it is routed to an approved AI workflow. AI-generated work is subject to founder technical review before delivery and then client review; Dahlia does not make the client's final quality, technical or regulatory decisions.

Only the information needed for the work

DahliaIvy's intended approach is to request information proportionate to the agreed workflow.

Clients will be asked to avoid unnecessary patient, trial participant, staff or other personal and sensitive information. Where such information may be necessary, its suitability for the engagement must be assessed and explicitly addressed in agreed data-handling arrangements before submission or processing.

Initial website enquiries must not include confidential documents, patient information or other sensitive records.

Traceability and review

Dahlia's workflow model is designed to make the basis and status of work understandable to the people reviewing it.

The intended record includes the work-item identifier, relevant source and evidence references, workflow and version information, review status, proposed deliverables and client acceptance or rejection. Where supported by the underlying platform and its configuration, access and activity records may also support investigation and oversight.

The completeness, availability and retention of these records will depend on the implemented workflow and agreed engagement controls. These capabilities should not be interpreted as a claim of a fully validated electronic audit trail.

Retention and engagement closeout

Data-handling and retention arrangements are intended to be established before substantive client work begins. They will address working copies, returned deliverables, access, retention requirements and closeout responsibilities.

At engagement completion, workspace access and temporary working information will be managed according to the agreed arrangements and applicable technical limitations. The client's approved records remain under its own document and records-management controls.

Technology providers and subprocessors

DahliaIvy's intended service model uses third-party technology for collaboration, infrastructure and AI-assisted processing.

Microsoft 365 is the proposed founding-client collaboration environment. AI provider selection and processing routes are subject to workflow requirements, agreed permissions and implementation controls.

Relevant information about technology providers, processing arrangements and applicable contractual terms will be disclosed during client qualification. Provider arrangements may differ depending on the services and processing configuration agreed for an engagement.

Founder review, followed by client decision

Dahlia prepares the work and adds founder technical review before the client assesses the output.

DahliaIvy's intended delivery model includes founder technical review of each founding-client output before it is returned for client assessment.

Your designated qualified or authorised personnel review the work, request amendments, accept or reject outputs, exercise professional judgement and control final approval, controlled filing and implementation. Founder review supplements rather than replaces the client's review and approval responsibilities.

Supplier qualification

Information for Quality, IT, Security, Privacy and Procurement.

Prospective clients can request available assurance information to evaluate DahliaIvy for a defined engagement. We recognise the need to assess what the service does, what information it handles and how responsibility is assigned.

We will identify which arrangements are operational, which are being implemented and where additional evidence or controls are required before an engagement can proceed. The scope of information reflects the actual service configuration rather than a generic certification claim.

Information available for discussion, as applicable

  • Service description and operating boundaries
  • Information flows, data handling and retention
  • Access and workspace configuration
  • AI-processing permissions and technology-provider arrangements
  • Security and privacy controls
  • Supplier qualification information
  • Relevant testing and validation evidence
  • Insurance and supporting documents, where available

Discuss a proposed ongoing service

Discuss security and qualification

We can discuss your organisation's qualification requirements and the controls needed for reserved capacity across proposed workflows. Initial contact uses our existing general enquiry form.

Please do not send confidential records, patient information or other sensitive material through the public enquiry form.

Discuss security and qualification

DahliaIvy is preparing the founding-client operating model described on this page. Delivery is subject to completed internal workflow and end-to-end testing, engagement-specific readiness review and agreed controls. This page does not claim independent security certification, regulatory approval or operational readiness for every use case.