~300K
Correspondence governed across enterprise communications.
~730 TB
Object storage supporting the shared enterprise information layer.
UP TO 10
Orchestrated across the lifecycle of a single administrative act.
< 10 MIN
through digitization and operational orchestration.
1. The Enterprise Challenge
A large public healthcare authority in Southern Europe serves approximately 900,000 residents across 104 municipalities, through 11 health districts, seven hospitals and a broad network of territorial, specialist and administrative services. At this scale, fragmentation is not simply a document-management problem.
Clinical systems produce healthcare documentation. Administrative applications generate official resolutions and digital cases. Formal correspondence enters and leaves the organization. Consent services acquire legally significant patient information. Financial operations create dossiers and evidence. Existing and future applications continuously need to create, retrieve and act upon information generated elsewhere.
The authority therefore chose not to modernize each requirement as another isolated application.
The objective was to establish a shared enterprise foundation providing common content services, persistent business objects, lifecycle governance, process orchestration, digital trust, compliant preservation, search and interoperability across the organization.
Coopera became that horizontal operational layer: specialist applications could continue owning their domains while relying on shared capabilities for the context and execution that must remain coherent across them.
2. Why it was complex
The challenge was not to centralize every function into one application. It was to create common operational capabilities across radically different domains without introducing another silo.
Many operational realities
Clinical records, administrative resolutions, informed consent, correspondence, digital cases and financial operations all have different lifecycles, users, responsibilities and evidence requirements.
Content must survive the application that created it
Documents and evidence need to remain governed and accessible to authorized systems beyond the lifecycle or boundaries of the application that originally produced them.
The document is not always the operation
A communication can create an issue lasting weeks or months. An administrative proposal can evolve through composition, review, approval, multiple signatures, publication and preservation. A consent document can influence what another healthcare application is permitted to do. The content matters, but so does the persistent business context that gives it operational meaning.
Trust is part of execution
Digital signatures, electronic seals and compliant preservation must remain connected to the business context, authorization and lifecycle that required them.
The architecture must remain open
Applications already operating today — and systems not yet built — must be able to participate without requiring another bespoke integration layer for every new requirement.
The architectural question was therefore: How can many specialist systems share one operational foundation while remaining specialist?
3. How Coopera Holds the Operation Together
Coopera provides a shared operational layer across the healthcare authority, allowing different clinical and administrative systems to participate in the same enterprise environment without forcing them into one monolithic application. Content produced by clinical applications, administrative systems, correspondence channels, consent services and digital processes remains governed beyond the application that originally created it. Metadata, lifecycle, relationships, permissions, history and evidence stay connected as operations evolve.
At the center of this model are the persistent Living Business Objects the organization actually needs to manage: Administrative Resolution · Correspondence-to-Resolution Case · Informed Consent · Digital Case · Invoice Dossier.
Each can maintain its own: Identity · State · Content · Relationships · Responsibilities · History · Evidence · What can happen next. Different processes can start and finish around them. Different systems can contribute information or perform their specialist responsibilities. Documents and evidence can arrive over time and influence the operation.
The Living Business Object remains the persistent point of continuity. This allows the same enterprise foundation to support very different operational domains while preserving their individual rules, lifecycles and responsibilities.
One shared foundation. Different operational lives.
4. How the Foundation Becomes Real Operations
Administrative Resolution
From proposal to legally preserved evidence. An Administrative Resolution begins before its final document exists. Its operational context can evolve through: Proposal · Composition · Review · Approval · Digital Signature · Registration · Publication · Certification · Preservation.
Information already available within the business context can be used to compose the official document as the operation progresses.
Approval may involve several responsible parties and up to ten digitally attributable signatures. Coopera coordinates the signing lifecycle through integrated digital trust services while preserving explicit human authorization. After final approval, the operation can continue through official publication, management of the publication period, generation and signature of the publication certificate and compliant preservation.
The final document is therefore not the operation itself. It is evidence produced by the operation.
Correspondence-to-Resolution
The communication starts the issue. It does not define it. Formal correspondence must be registered, classified and routed. But the business issue created by that communication can continue for days, weeks or months.
People, teams and organizational units may become involved. Additional documents arrive. Responses are produced. Activities take place. Decisions are made before the matter is finally resolved.
The Correspondence-to-Resolution Case preserves that evolving context, connecting the original communication with the people, content, responsibilities and actions that accumulate around it. Formal registration remains part of the operation where legally required, but it no longer has to become the object around which the organization works.
Registration records the communication. The business object carries the issue to resolution.
Informed Consent
One governed consent context across clinical services. The same enterprise foundation supports informed-consent management across different clinical areas. Configurable consent models can use the shared content, governance, digital trust and preservation capabilities already available across the organization.
Consent information can then remain available to authorized healthcare applications through integration services and participate in policies determining whether particular access or actions are legitimate according to factors such as acquired consent, document context, user role and intended purpose. The result is not another isolated consent repository.
Consent becomes a persistent governed business context that can participate across the healthcare environment.
Connecting Existing and Future Applications
From API request to governed operation. The shared enterprise layer must remain open to systems already in production and applications that have not yet been built. New ingestion APIs can be configured and connected directly to governed execution.
An incoming request can therefore trigger: Validation · Content Acquisition · Metadata Enrichment · Object Creation · Correlation · Routing · Workflow Activation · External-System Interaction. New endpoints can be configured and published within minutes.
The important point is not simply faster integration. An API can become an entry point into a governed business operation.
Clinical and administrative applications can contribute information, create or update business context and activate the appropriate execution without requiring the complete operational logic to be rebuilt inside every individual system.
5. Shared Trust and Evidence
Digital signatures, electronic seals and compliant preservation participate directly in these operations rather than becoming disconnected downstream services.
Depending on the business context, Coopera can coordinate qualified and advanced electronic signatures, graphometric signatures, electronic seals and preservation activities while keeping authorization, resulting evidence and the Living Business Object that required them connected. External trust and preservation providers continue performing their specialist responsibilities.
Coopera preserves the operational context around their actions.
6. Enterprise Scale
The architecture reflects the horizontal nature of the project. The environment operates across two data centers and includes approximately 732 TB of S3-compatible object-storage capacity, designed to support the broader information estate of the healthcare authority rather than one departmental application.
Storage, search, processing, interoperability and governance operate as shared enterprise capabilities. New applications and operational domains can therefore participate in the same foundation without recreating the infrastructure and common operational services they need.
The enterprise can evolve while the operational foundation remains coherent.
7. The Outcome
The healthcare authority is moving away from a landscape in which each application must independently own its content, processes, integrations and operational history.
- Clinical systems remain responsible for clinical functions.
- Financial systems retain financial transactions.
- Formal correspondence services continue providing legally required registration.
- Trust and preservation providers continue performing their specialist roles.
What changes is the operational layer connecting those responsibilities.
Across Administrative Resolutions, correspondence cases, informed consent, digital cases and other Living Business Objects, Coopera provides persistent operational context, shared content governance, orchestration, trust integration, interoperability and evidence.
New systems can participate without requiring the organization to rebuild those capabilities application by application, while the underlying environment provides enterprise-scale information infrastructure across two data centers and approximately 732 TB of object-storage capacity.
The result is not a collection of digitized processes. It is a shared enterprise operational foundation that keeps different business realities coherent while specialist systems continue doing what they were designed to do.
5. What This Case Proves
One foundation can support many Living Business Objects
Administrative Resolutions, correspondence cases, informed consent and other operational objects can retain different lifecycles and responsibilities while sharing the same enterprise foundation.
Content can remain connected to the operation it affects
Documents, communications and evidence do not have to become isolated artifacts when work moves between applications, teams and processes.
Specialist systems can remain specialist
Clinical, administrative, financial, trust and preservation systems can continue owning their domains while Coopera maintains operational continuity across them.
Enterprise scale does not require one monolithic application
A shared operational model can support multiple healthcare domains, two data centers and approximately 732 TB of enterprise content capacity without collapsing specialist responsibilities into a single system.
