Summary

• Hyland has announced a consolidated set of Guidewire-validated integrations for ClaimCenter, PolicyCenter and BillingCenter, available through Guidewire Marketplace.
• Content Federation Service can connect existing OnBase repositories to Hyland Content Innovation Cloud, allowing insurers to use documents without necessarily migrating the underlying archive.
• Intelligent document processing and AI agents are optional capabilities, while customer-specific implementation savings and new deployment figures remain undisclosed.

Hyland has brought together integrations for Guidewire’s principal insurance applications, allowing claims handlers, underwriters and billing teams to work with documents held in existing content systems without requiring a complete migration before modernising their processes.

Announced on 19 October, Hyland for Guidewire connects the company’s Content Innovation Cloud with Guidewire ClaimCenter, PolicyCenter and BillingCenter. The integrations are validated through Guidewire’s partner programme and offered through Guidewire Marketplace.

Hyland is positioning the offering around a recurring problem for property and casualty insurers: business records can be distributed across document repositories that were introduced long before the applications now used to manage policies, claims and customer accounts.

The latest announcement consolidates capabilities into a common commercial proposition rather than introducing every underlying connector for the first time. Hyland’s technical documentation establishes that individual Guidewire integrations were available before the October release.

Insurance processes depend on historical information

An insurer’s records can span many years and include information created in different systems during the life of a customer relationship.

Claims handlers may need photographs, correspondence, repair estimates, policy wording and previous decisions before they can determine how to process a case. Underwriters examine submissions and supporting evidence, while billing teams require access to payment information and communications concerning individual accounts.

Although those activities use related information, insurers may operate separate applications for content management, customer administration and core insurance processing.

Employees can therefore spend time searching for documents in one system before returning to another to complete their work. Repeatedly downloading, transferring or recreating records can introduce delays and increase the risk that people work from outdated information.

The problem becomes more demanding when insurers replace or upgrade their main business applications but retain repositories containing large amounts of historical information.

A complete migration may require records to be extracted, checked, transformed and loaded into a new environment. Existing permissions, retention rules and metadata also need to be preserved if the records are to remain useful and compliant.

Those requirements can make content migration a substantial project in its own right, potentially delaying improvements to claims or policy systems that do not otherwise depend on replacing the document archive.

Federation retains existing content repositories

Hyland’s integrations use Content Federation Service to connect existing OnBase repositories with Content Innovation Cloud and the relevant Guidewire applications.

Under that arrangement, employees can retrieve and work with documents through Guidewire while the underlying content remains in its existing managed location.

For ClaimCenter, the integration provides access to documents, images and related information used in claims handling. PolicyCenter makes supporting content available during quoting, underwriting and policy administration, while BillingCenter connects records with customer account and payment processes.

The integrations also support document uploads to compatible repositories and workflows that can act on information retrieved through the platform.

This approach can avoid a wholesale migration where a business is using a suitable supported OnBase configuration, although the original repository still needs to remain operational and accessible.

Federation changes the relationship between systems rather than eliminating their dependencies. Insurers may need to maintain the original archive, the connection to Content Innovation Cloud and the Guidewire applications through which users request information.

If one component is unavailable, employees may lose access to records required for a transaction even though the files themselves remain stored safely elsewhere.

Performance will also depend on network arrangements, document size, access permissions and the condition of the existing repository.

The company describes the integrations as ready to deploy, but its implementation documentation still requires configuration of application credentials, content services and document security settings.

Replacing bespoke development with a supported connector can reduce some engineering work without removing the need for testing or integration with each insurer’s operating environment.

Information access supports further automation

Hyland is also presenting the integrations as infrastructure for intelligent document processing and AI applications.

Insurance processes often involve information contained in letters, photographs, forms and supporting documents that cannot always be handled through structured transaction fields alone.

Intelligent document processing can help extract or classify information from those records, while AI agents may be able to retrieve supporting documents or undertake defined activities through connected applications.

In a claims workflow, an automated system could potentially identify which documents are available for a case and prepare information for a handler to review. In underwriting, software might bring relevant records into the application where a decision is being prepared.

The reliability of such functions depends on the quality of the source documents and the accuracy with which information is extracted and associated with the appropriate customer or transaction.

A document may contain an outdated address, incomplete information or a statement that conflicts with another record. Faster retrieval does not establish which version is authoritative or resolve questions requiring professional judgement.

Hyland describes AI agents and intelligent document processing as capabilities that can be added through Content Innovation Cloud. They should not be treated as functions automatically deployed or suitable for every insurer purchasing the Guidewire integrations.

The company has not published independently verified savings figures comparing implementation costs or claims processing times across new customers using the consolidated offering.

Any commercial benefit will depend on the particular records, applications and processes involved, alongside the costs of deploying and maintaining the integrations.

Permissions must cross application boundaries safely

Insurance records contain personal information, financial details and commercially sensitive material, making permission management central to a federated architecture.

Employees authorised to process a claim may not require access to every record belonging to the policyholder, while underwriting and billing teams can have different information needs.

Integrating systems therefore requires administrators to understand how the source repository’s permissions interact with the identity and authorisation arrangements used by the application requesting the document.

Hyland’s technical documentation includes configuration of content security, application registration, service users and authorised scopes. These requirements reflect the need to connect software without giving every user or connected service unrestricted access to the underlying archive.

Audit records and document retention obligations also remain important. Insurers may need to establish who accessed sensitive information, how long records should be retained and what happens when a document is amended through a connected workflow.

Adding AI processing introduces further responsibilities because automated applications may retrieve information at a scale or frequency different from the patterns expected from employees.

Appropriate controls must cover the data available to those systems and whether they are permitted to take actions beyond preparing or retrieving information.

Modernisation without an immediate replacement programme

Hyland has worked with Guidewire for more than a decade, supplying integration capabilities to insurers using the Guidewire InsuranceSuite applications.

The consolidated offering is most relevant to organisations seeking to modernise core processes while retaining content infrastructure that continues to meet their operational and regulatory requirements.

A federated approach could reduce the need for large migration projects and provide a more consistent employee experience, but it also preserves dependencies that insurers must maintain until any longer-term replacement becomes commercially sensible.

For some organisations, continuing to operate a legacy archive may be appropriate because the records are stable and expensive to move. Others may ultimately find that maintaining several connected platforms costs more than consolidation.

Those decisions require an assessment of infrastructure costs, software compatibility, security and operational performance, rather than assuming that federation is always preferable to migration.

Hyland for Guidewire is available through Guidewire Marketplace, with integrations covering claims, policy and billing processes. Customer implementations will provide the evidence needed to establish how effectively the package reduces project complexity and improves access to insurance information.