Software Object Conversion via Properties File Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Medicaid management information systems (MMIS) face challenges in interoperability due to differences in software technologies used across various state systems, leading to difficulties in seamless data exchange and transaction processing between disparate software platforms.

Innovation Solution

A computer program product and method that employs a system with distinct software modules, including converter modules and a properties loader, to convert data objects between different software technologies, enabling the construction and processing of healthcare management information system transactions by identifying and mapping attributes and methods between classes associated with different software technologies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If different software technologies are used across state systems, then each system can be developed with specialized technologies, but interoperability and data exchange between systems deteriorate

Engineering Contradiction:
Improvesoftware technology flexibilityVSAvoidinteroperability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a properties file as an intermediary component that stores mapping relationships between classes of different software technologies. This properties file acts as a mediator that enables data objects to be converted between technologies without requiring direct integration logic, thus maintaining interoperability while allowing systems to use different specialized technologies.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter of data representation by converting data objects from one software technology format to another through systematic attribute mapping. The conversion process transforms the structural parameters of data objects based on predefined mappings, enabling seamless interoperability between systems using different software technologies.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If conversion between different software technologies is implemented, then interoperability is improved, but system complexity increases

Engineering Contradiction:
ImproveinteroperabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the conversion logic from the core business application and places it in a separate properties file. This extraction isolates the complexity of technology conversion into a standalone configuration component, allowing the main system to remain simple while still supporting interoperability through external mapping definitions.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a simplified copy of class structures in the properties file that represents the mapping relationships without implementing full conversion logic. This copying approach allows the system to work with lightweight representations of data structures, reducing the complexity of actual conversion operations while maintaining interoperability.

Inventive Principle:
Principle #26Copying

3Manufacturing precision

If manual mapping of attributes between classes is performed, then conversion accuracy is improved, but development time and maintenance effort increase

Engineering Contradiction:
Improveconversion accuracyVSAvoiddevelopment and maintenance time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements self-service conversion where the system automatically performs attribute mapping between different software technology classes using predefined properties files. The conversion process is autonomous and does not require manual intervention, thereby maintaining high conversion accuracy through systematic mapping while eliminating the time cost of manual attribute-by-attribute mapping.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8103683B2Converting between software objects
Publication Date: 2012.01.24 CONDUENT BUSINESS SERVICES LLC
  • US8103683B2 patent drawing
  • US8103683B2 patent drawing
  • US8103683B2 patent drawing

AI summary

A computer program product is provided. The product comprises a computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to be executed to implement a method for converting between data objects constructed according to different software technologies. The method comprises providing a system comprising distinct software modules to perform the converting between data objects and processing a properties file to identify a first class associated with a first software technology based on a second class associated with a second software technology. The method also comprises analyzing the first class to identify a first attribute of the first class. The method also comprises constructing a first object of the first class and assigning a first value to the first attribute of the first object based on a second value of a second attribute of a second object of the second class.