Healthcare
NHS and private healthcare teams can start by assessing how AI could help staff find approved guidance and prepare document drafts. Begin with an agreed purpose, approved sample records and accountable human review. Mickai's on-premise approach is designed to keep processing within a defined customer-controlled boundary. Local hosting does not establish clinical suitability, NHS approval or compliance; those require assessment of the workflow and its operation.
The chief clinical information officer and data protection officer of an NHS Trust or private provider.
Staff need reliable information from sensitive records, but poor scans, conflicting versions and unclear access can make an AI answer unsafe to rely on. Clinical documentation also needs careful review of omissions and terminology.
Assess sources, sensitivity and permissions before ingestion. Scope local extraction, retrieval and assistance, with traceable source passages and a review queue for unreadable records. Agree interfaces to clinical systems and any external services separately; a live external connector is outside a fully isolated workflow.
A testable path from approved records to reviewed assistance. Measure source accuracy, omissions, access restrictions and total staff effort before expanding the workflow or making clinical-use claims.
These architectural choices support control over the workflows in your deployment. Their benefits depend on configuration, integrations and operating practices. Review external connections, physical security, access and compliance responsibilities together.
Scope inference, extraction, retrieval and storage on infrastructure you control. Document and test any external connector, support channel or transfer before describing a workflow as zero-egress.
Workflows with local models, data and supporting services can continue offline. Live external email, calendars and other services need an approved connection or controlled import, with clear unavailable and pending states.
Map prompts, documents, indexes, logs and backups to their processing and storage locations. Local hosting supports control of location; access, retention and any transfers still need review.
Prepare and classify source records, preserve permissions and evaluate answers against the originals. Retrieval and model training are separate choices; agree data use and licences for each.
Compare hardware and licences alongside integration, power, administration, support, updates, evaluation and recovery. Measure cost at the required workload and quality before claiming savings.
Define who holds keys, who can administer the system and which actions need approval. Test denied requests, revoked access and audit records. Physical security, insider risk and incident response remain operational responsibilities.
Agree version selection, signed update procedures, rollback, data export and licence rights. Reassess requirements as software and obligations change; owning hardware does not remove maintenance or compliance work.
Review the requirements relevant to your organisation, jurisdiction and intended use with your responsible teams. Cloud services can be appropriate subject to applicable safeguards; on-premise deployment alone does not establish compliance or remove supplier responsibilities.
The kind of organisation this serves, named illustratively from public information to characterise the market. These are target profiles, not customers: Mickai has no relationship, engagement, trial, or endorsement with any of them.
The enterprise studios that lead in this sector, drawn from the eighteen that sit on the one sovereign substrate. Scope their local processing, operator-held keys and Open Audit Record coverage for the proposed deployment. Confirm availability and any external integrations before relying on a workflow.
Clinical Documentation
Discuss documentation assistance with clinical and information-governance owners. Confirm availability, intended use, evaluation and human review before a patient-data pilot.
Compliance
Prepare policy and governance evidence for the organisation's review, with agreed audit coverage and retention.
Customer Relationship Management
Assess administrative record workflows, access permissions and proposed interfaces before connecting patient information.
Cleo
Evaluate transcription on approved recordings, checking speaker attribution, uncertain names, omissions and correction before notes are accepted.
See all eighteen on the sovereign services catalogue.
An AI Readiness assessment can start with approved policies or administrative documents before considering patient-record workflows. Bring example documents, source owners, access rules and a baseline of the current task. Agree what can be processed, what needs human review and which evidence would justify continuing. Confirm the proposed software version and studio availability during scoping.
Measure value, cost and risk on hardware you control.
Measure staff time including checking and correction, supported answers, omissions and inappropriate disclosures. Test revocation, downtime and recovery with approved data. Use the results to decide whether to expand, change or stop the pilot. Savings, clinical benefits and assurance outcomes remain to be demonstrated for each use case.
Map the sovereign stack to your healthcare estate.
Briefings are for organisations weighing a sovereign, on-premises deployment. Tell us about your estate and we will walk the pack, the regulatory crosswalk, and the deployment that fits your estate.