Service Granularity Component for SOA Data Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In healthcare enterprises, the integration of heterogeneous applications using Service Oriented Architecture (SOA) leads to the creation of multiple dedicated services, resulting in decreased system efficiency, increased development and maintenance costs, and negatively impacts performance due to differing data granularity requirements across applications.

Innovation Solution

A service granularity component that dynamically customizes a reusable service based on user identity, common service data, and service action elements parsed from service request parameters, allowing for consistent information delivery across various applications and communication channels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple dedicated services are created for each application environment to accommodate different data granularity requirements, then each application can access customized data views, but system efficiency decreases and development and maintenance costs increase

Engineering Contradiction:
Improvedata granularity customizationVSAvoidsystem efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a single reusable service that can serve multiple application environments by dynamically adjusting its behavior based on runtime parameters. The service accepts different data granularity requirements through configurable parameters, allowing one service to fulfill multiple specialized functions that would traditionally require separate dedicated services for each application.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The service incorporates dynamic configuration capabilities that allow it to adapt its data retrieval and processing behavior at runtime based on the specific needs of each application environment. This dynamic adjustment enables the service to optimize performance for different data granularity requirements without requiring static service specialization.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If multiple dedicated services are created for each application environment, then specific data views can be provided, but development and maintenance costs increase

Engineering Contradiction:
Improveapplication-specific data viewsVSAvoiddevelopment and maintenance cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal service framework that can be deployed across multiple application environments without requiring separate service implementations. The service uses configurable parameters and templates to adapt to different application-specific requirements, significantly reducing development effort and maintenance burden compared to creating dedicated services for each application.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The service achieves application-specific functionality through parameter configuration rather than code customization. By changing service parameters, data granularity levels, and query templates, the same service can be adapted to different application environments, eliminating the need for separate service development and reducing maintenance complexity.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple services process similar information with different data granularity, then each application gets tailored data, but system performance negatively affects

Engineering Contradiction:
Improvetailored data deliveryVSAvoidsystem performance
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent implements a single high-performance service that handles multiple application workloads simultaneously, eliminating the performance overhead of running multiple separate services. The service optimizes data retrieval by using parameter-driven query generation that can efficiently fetch data at appropriate granularity levels without redundant processing.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The service extracts only the necessary data elements required by each application based on its specific needs, rather than retrieving and processing complete datasets. This selective data extraction approach maintains tailored data delivery while significantly improving system performance by reducing data transmission and processing volumes.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8484044B2Service identification and decomposition for a health care enterprise
Publication Date: 2013.07.09 AETNA INC
  • US8484044B2 patent drawing
  • US8484044B2 patent drawing
  • US8484044B2 patent drawing

AI summary

In embodiments, a health insurance computer application enterprise system is provided employing a service oriented architecture (SOA) with a service granularity component that dynamically customizes a reusable service based on one or more of user identity element, service data elements, and service action elements parsed from service request parameters. The health insurance enterprise system includes a plurality of applications making use of functionality provided by a reusable service. In an embodiment, the health insurance enterprise system includes a customer service application, a consumer web portal application, and an integrated voice response (IVR) application. The applications provide different channels of communicating health insurance data to various health insurance system constituents by presenting customized views of the data tailored to a given communications method, user access rights, as well as other factors.