Nested Database Structure for Custom Medical Data Sheets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional medical data sheet management software lacks the ability to enable physicians to generate custom data sheets and report pages, providing limited configuration and customization options, which often lead to dissatisfaction among clinicians.
Innovation Solution
A system and method for creating customized electronic data sheets using a nested database structure that includes page objects, panel objects, and panel item objects, allowing for the definition of binding rules that automate operations based on clinical data, such as cross-validation, visibility, and data filtering, enabling dynamic customization of page layouts and rules through a graphical user interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional medical data sheet management software provides predetermined layouts with limited customization options, then the software is easier to implement and maintain, but clinicians cannot generate custom data sheets and report pages according to their specific needs
Solution Approach 1:
The system segments the data sheet into hierarchical components including pages, panels, and panel items. Each component can be independently configured and customized. The page contains multiple panels, and each panel contains multiple panel items, allowing granular control over the structure and content of custom data sheets without overwhelming system complexity.
Solution Approach 2:
The system implements a nested structure where pages contain panels, and panels contain panel items. This nested organization allows for complex, customized data sheet layouts while maintaining manageable complexity through hierarchical abstraction. The binding rules are also nested within the panel item structure, enabling sophisticated data operations at appropriate levels of the hierarchy.
2Ease of operation
If conventional software provides limited configuration options prepared in advance by developers, then the system is simpler to operate, but clinicians are unable to create tailored reports for specific clinical workflows
Solution Approach 1:
The system enables clinicians to self-configure custom data sheets and report pages without requiring developer intervention. Through the graphical user interface, clinicians can directly create, modify, and customize pages, panels, and panel items according to their specific clinical needs. The binding rules can also be configured by clinicians to automatically perform operations on clinical data, eliminating the need for pre-prepared custom pages by developers.
3Adaptability or versatility
If the system enables dynamic customization of page layouts and binding rules through GUI, then clinicians can generate highly customized reports, but the system complexity and development effort increase significantly
Solution Approach 1:
The system implements a universal configuration framework that handles multiple customization functions through a unified approach. The same hierarchical structure (pages, panels, panel items) and binding rule mechanism serve various customization needs across different clinical workflows. This multi-functional design allows the system to handle diverse customization requirements without requiring separate implementation mechanisms for each function.
Solution Approach 2:
The system enables customization through parameter configuration rather than structural changes. Binding rules define operations based on data parameters (source panel item, target panel item, operation type). By changing parameters such as binding rules, panel configurations, and data source associations, the system can adapt to different clinical needs without requiring complex reprogramming or structural modifications.
Data Source
AI summary
A computer-implemented method is provided for creating a customized electronic data sheet (EDS), which involves receiving inputs at a graphical user interface (GUI), and executing program instructions at one or more processors to perform operations that include:receiving layout instructions, through the GUI, in connection with a page layout to be rendered on a display in connection with entering and viewing clinical data of an EDSbuilding a nested EDS database structure, based on the layout instructions, that includes page objects, panel objects and panel item objects nested within one another, the nested EDS database structure defining a manner in which the GUI renders the page layout on the displayreceiving a rule designation through the GUIgenerating a binding rule, based on the rule designation, that binds clinical data to at least one of the page objects, panel objects or panel item objects, the binding rule designating an operation to be automatically performed based on the clinical data.Corresponding systems and computer programs are also disclosed.