Dynamic Electronic Form Data Segmentation and History Retention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic data entry forms in healthcare lack the ability to maintain a history of inputted data for multiple-use forms, leading to inefficiencies and the need for complex rule management, which becomes unsustainable as new form types are developed.
Innovation Solution
A computer system that stores and visualizes structured dynamic electronic forms by separating form template data and input data, allowing for the storage of historical values and conditional visibility/ordering of form fields, and sending a form filler package to the user device for rendering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If electronic data entry forms store historical values for multiple-use forms, then data completeness and traceability are improved, but storage complexity and data management burden increase
Solution Approach 1:
The patent segments the electronic form data into two distinct components: form template data (defining structure, fields, and validation rules) and form data (containing actual input values including historical values). This segmentation allows historical data to be stored efficiently without complicating the overall form structure, as each component is managed independently with its own data model.
Solution Approach 2:
The patent introduces a temporal dimension to form data storage by maintaining arrays of historical values for each form field. Instead of storing only the current value, the system stores sequences of values over time, enabling multiple-use forms to retain their complete data history while maintaining a clear separation between the form definition and the data instances.
2Productivity
If form template data and form data are stored separately, then data retrieval and processing efficiency are improved, but system complexity increases
Solution Approach 1:
The patent implements segmentation by storing form template data and form data in separate database tables or data structures. The form template data contains the schema, field definitions, and validation rules, while form data contains the actual user inputs and historical values. This separation enables independent processing, indexing, and querying of each data type, improving overall system efficiency.
Solution Approach 2:
The patent introduces an intermediary layer (form management system) that handles the coordination between template data and form data. This intermediary manages the relationships between the two separate data components, handling operations such as form instantiation, data validation, and historical value management, thereby simplifying the interface between the separated components.
3Adaptability or versatility
If forms adapt dynamically based on user input, then user experience and form functionality are improved, but rule management complexity increases
Solution Approach 1:
The patent implements dynamic forms by allowing the form structure and behavior to change based on user input and form state. Form fields can be conditionally displayed, required, or disabled based on values entered in other fields. The form management system evaluates rules and constraints dynamically during form interaction, enabling adaptive behavior without hardcoding complex logic in the user interface.
Solution Approach 2:
The patent incorporates feedback mechanisms where user input triggers rule evaluation, which in turn modifies the form state or provides validation feedback. The system continuously monitors form data against defined rules and constraints, providing real-time feedback to users about data completeness, validity, and required actions, thereby managing complexity through systematic feedback loops rather than complex conditional logic.
Data Source
AI summary
Computer systems, methods, and devices for structured dynamic electronic forms are provided. The system includes a user device comprising a client form management application and a server comprising a server form management application. The client form management application generates and sends a request for a dynamic electronic form to the server. The server form management application stores the dynamic electronic form comprising separately stored form template data and form data; and merges and sends the form template data and the form data to the user device for rendering. The client form management application sends a request for a form filler package (“FFP”) comprising rules for filling out and rendering the dynamic electronic form. The server form management application sends the FFP to the user device and the client form management application renders the dynamic electronic form using the merged form template data and form data and the FFP.