AI Document Processor - UK Healthcare
Connectbatch Limited · Operations & Productivity
Certification per Microsoft Marketplace.
Evidence tier Publisher Attested · 7 captures on record
What the publisher says
As described on Microsoft Marketplace.
What’s new
This release updates the service endpoint used by the agent to the production environment.
Show the rest of the publisher’s description (17 more lines)
There are no changes to the agent’s functionality, user experience, or permissions.
Connectbatch’s AI Document Processor is a secure, NHS‑ready SaaS platform for the automated ingestion, processing, orchestration, and clinical coding support of clinical documents across Microsoft 365 environments.
Designed for Trusts, ICSs, PCNs, and healthcare organisations, the platform streamlines the handling of high‑volume clinical correspondence and unstructured documents while aligning with NHS data governance requirements.
The platform consolidates multiple NHS document entry points, including shared email inboxes, SharePoint libraries, and agents for Microsoft Copilot interactions in Microsoft Teams, Outlook, and chat, into a single, auditable, multi‑tenant processing pipeline.
Documents can be submitted by clinical teams, administrators, or directly through natural‑language requests in agents for Copilot.
Using Azure AI Document Intelligence, AI Document Processor extracts text, tables, key‑value pairs, and clinical entities from letters, referrals, discharge summaries, diagnostic reports, and other healthcare documents. The platform generates clinical coding suggestions to support coding teams and downstream workflows, with outputs transformable into structured, FHIR‑aligned formats or routed through Human‑in‑the‑Loop review workflows for safety‑critical validation.
Each document follows a fully traceable processing journey, including correlation IDs, run identifiers, timestamps, and audit envelopes aligned with NHS operational and governance expectations. No PHI is stored in control‑plane components, and strict tenant isolation ensures secure, multi‑organisation deployment across ICS environments.
Through agents for Copilot, clinicians and staff can initiate document processing directly within Microsoft Teams and Outlook using natural language, for example: “Upload this discharge summary and suggest the relevant clinical codes.” Requests are securely routed via Azure API Management into the AI Document Processor’s ingestion and processing services, enforcing tenant entitlement and access controls.
Connectbatch’s AI Document Processor helps healthcare organisations reduce manual workload, minimise delays in correspondence handling, improve the accuracy of clinical data capture and coding, and accelerate the flow of critical information across pathways of care while maintaining NHS‑aligned security, observability, and governance.
Getting started and onboarding
To use the AI Document Processor, your organisation must have an active subscription and complete one‑time tenant onboarding by a Microsoft 365 administrator.
- [Get started and onboarding guide: ] (https://www.connectbatch.co.uk/ai-document-processor-agent-support/)
- [Support and help: ](https://www.connectbatch.co.uk/ai-document-processor-agent-support/)
Limitations
The AI Document Processor agent is designed for document ingestion and status workflows via Microsoft Teams chat, Outlook, Copilot chat, and supported document hubs (for example Word and PowerPoint).
The current version does not provide meeting‑specific functionality (such as meeting summaries, transcript analysis, or post‑meeting insights). Copilot experiences in Meeting Chat and Meeting Recap are therefore not supported in this release and may be addressed in a future update.
Note: Full document processing and clinical functionality require an active subscription. The service is currently available to UK healthcare organisations. Availability may expand to additional regions over time.
Preview
5 images
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Sources
Publisher resources
2 linksLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.