System and method for overloading one or more applications

Abstract

The invention relates to a device and a method for overloading one or more application programs. A method performed by a computer includes first allowing a user to open and control a layout of a web application and a desktop application in an application, and then allowing the web application and the desktop application to be loaded and run in a native state. The method continues by allowing a user to control records of web application and desktop application loading, and ultimately allows the user to control window positions / layouts of web applications and desktop applications.

Description

Related applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 415,181, filed October 11, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present application relates to a system and method for overlaying one or more application programs in a single shell program. Background Art

[0003] Overlaying is a feature that allows applications to appear on top of other applications. For example, some messaging apps can display a chat bubble on top of an open application such as a browser.

[0004] Building overlays involves manually dividing the program into self-contained object codeblocks called overlays or links, arranged in essentially a tree structure. Sibling segments at the same depth level share the same memory, called the overlay area or target area. An overlay manager, either part of the operating system or part of the overlay program, loads the required overlays from external memory into their target areas when needed; this can be automatic or implemented through explicit code. Linkers typically provide support for overlays. Summary of the Invention

[0005] A computer-implemented method comprising: allowing a user to open and control the layout of web applications and desktop applications within a single application; allowing the web applications and desktop applications to load and run in a native state; allowing the user to indicate a record of web application and desktop application loading; and allowing the user to control the window position and layout of the web applications and desktop applications.

[0006] The computer-implemented method further includes: allowing a user to select one or more graphical analysis features and automatically refine record data in a grid; and automatically opening records in multiple different target applications. The graphical analysis is displayed in a graphical user interface; and the data source is allowed to change in real time from the program data grid to any other table / database / source. Hovering a cursor over a portion of a first graphical representation of data provides more detailed information about that portion of the first graphical representation. Right-clicking the patient data grid allows filtering the patient data grid based on preset data categories, wherein the preset data categories are user-defined. Selecting an "Apply to Dash" checkbox updates the first graphical representation to display a second graphical representation of the filtered data. Both the web application and the desktop application include a modular overlay ticketing system (MOTS) configured to create tickets automatically refined from patient record information sources. The MOTS includes a ticket template button configured to open a template selection page. The template selection page includes a ticket creation button configured to open a ticket manager window and allow the user to create a new ticket automatically associated with a preloaded record for a selected patient. The ticket manager window is set to open an external desktop application in a multi-overlay window.

[0007] A computer-readable storage medium having instructions stored thereon that, when executed by a processor, cause the following operations: allowing a user to open and control the layout of web applications and desktop applications within one application; allowing web applications and desktop applications to load and run in a native state; allowing a user to indicate a record of web application and desktop application loading; and allowing a user to control the window position / layout of web applications and desktop applications.

[0008] The computer-readable storage medium, wherein further instructions executed by a processor cause the following operations: allowing a user to select one or more graphical analysis features and set automatic refinement of record data in a grid; and automatically opening records in multiple different target applications, wherein further instructions executed by the processor cause the following operations: displaying the graphical analysis in a graphical user interface; and allowing the data source to be changed from the program data grid to any other table / database / source in real time. wherein hovering a cursor over a portion of a first graphical representation of data provides more detailed information about that portion of the first graphical representation. wherein right-clicking the patient data grid allows filtering the patient data grid based on preset data categories. wherein the preset data categories are set by the user. wherein selecting an "apply to center panel" checkbox updates the first graphical representation to display a second graphical representation of the filtered data.

[0009] The web application and the desktop application both include a modular overlay ticketing system (MOTS) configured to create tickets automatically extracted from patient record information sources. The MOTS includes a ticket template button configured to open a template selection page. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which are included to provide a further understanding of the embodiments of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the principles of the embodiments of the application.

[0011] Figure 1 diagrammatically illustrating one or more processes coupled to a distributed computing network;

[0012] Figure 2 is an exemplary flow chart of a method according to an embodiment of the present application;

[0013] Figure 3A An example homepage in a shell program according to an embodiment of the present application is shown;

[0014] Figure 3B An example overlay procedure in a graphical user interface (GUI) according to an embodiment of the present application is shown;

[0015] Figure 4 An example overlay procedure for loading electronic medical records (EMR) in a GUI is shown in use according to an embodiment of the present application;

[0016] Figure 5 An example patient billing page in a GUI according to an embodiment of the present application is shown;

[0017] Figure 6A shows an example analysis feature in a GUI according to an embodiment of the present application;

[0018] Figure 6B Shows an example analysis feature for performing data refinement in a GUI according to an embodiment of the present application;

[0019] Figure 6C An example of EMR patient data extracted in a GUI according to an embodiment of the present application is shown;

[0020] Figure 6D An example of information of a patient selected in a GUI according to an embodiment of the present application is shown;

[0021] Figure 6Eis an example EMR for a selected patient of interest opened in the web application information in the GUI according to an embodiment of the present application;

[0022] Figure 7A FIG. 1 shows an example multi-window view of an overlay program in a GUI according to an embodiment of the present application;

[0023] Figure 7B An example of filtered data records in a multi-window view in a GUI according to an embodiment of the present application is shown;

[0024] Figure 7C FIG. 1 shows an example graphical representation of filtered data records in a multi-window view in a GUI according to an embodiment of the present application;

[0025] Figure 8A An example patient information page in a modular overlay ticketing system (MOTS) in a GUI is shown according to an embodiment of the present application;

[0026] Figure 8B An example of a MOTS ticket template selection page in a GUI according to an embodiment of the present application is shown;

[0027] Figure 8C shows an example of a MOTS Ticket Manager window in a GUI according to an embodiment of the present application; and

[0028] Figure 8D An example of an external application in a multi-window view in a GUI according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0029] Reference will now be made in detail to the embodiments of the present application, examples of which are illustrated in the accompanying drawings. However, the present application may be embodied in many different forms and should not be construed as limited to the embodiments described herein; rather, these embodiments are provided so that this application is thorough and complete and fully conveys the concepts of the present application to those skilled in the art. In the accompanying drawings, the thickness of multiple layers and multiple regions may be exaggerated for clarity. Like reference numerals in the figures represent like elements.

[0030] refer to Figure 1, showing method 10, which may be located on and executed by server computer 12, which may be connected to a network 14 (e.g., the Internet or a local area network). Examples of server computer 12 include, but are not limited to, a personal computer, a server computer, a series of server computers, a minicomputer, and a mainframe computer. Server computer 12 may be a network server (or a series of servers) running a network operating system, examples of which may include, but are not limited to, Microsoft Windows XP Server. tm 、Novell Netware tm or Redhat Linux tm Additionally and / or alternatively, the method may be provided on a client electronic device, such as a personal computer, a notebook computer, or a personal digital assistant.

[0031] The instruction set and subroutines of method 10, which may be stored on a storage device 16 coupled to server computer 12, may be executed by one or more processors (not shown) and one or more memory architectures (not shown) incorporated into server computer 12. Storage device 16 may include, but is not limited to, a hard disk drive, a tape drive, an optical drive, a Redundant Array of Independent Disks (RAID) group, random access memory (RAM), and read-only memory (ROM).

[0032] The server computer 12 can execute a web server application. Examples of web server applications include, but are not limited to, Microsoft IIS that allows HTTP (HyperText Transfer Protocol) access to the server computer 12 through the network 14. tm 、Novell Webserver tm or Apache Web Server tmThe network 14 may be connected to one or more second-level networks (eg, the network 18 ). Examples of the one or more second-level networks include, but are not limited to, a local area network, a wide area network, or an intranet.

[0033] Server computer 12 may execute one or more server-side applications (e.g., server-side application 20). Examples of one or more server-side applications include, but are not limited to, Lotus Domino™ Server and Microsoft Exchange™ Server. Server-side application 20 may interact with one or more client-side applications (e.g., client applications 22, 24, 26, 28) to perform method 10. Examples of client applications 22, 24, 26, 28 include, but are not limited to, development verification tools, such as those available from the assignee of the present application. These applications may also be executed by server computer 12. In some embodiments, method 10 may be a stand-alone application that interacts with server-side application 20, or method 10 may be an applet / application that executes within server-side application 20.

[0034] The instruction sets and subroutines of the server-side application 20 , which may be stored on a storage device 16 coupled to the server computer 12 , may be executed by one or more processors (not shown) and one or more memory architectures (not shown) incorporated into the server computer 12 .

[0035] As described above, in addition to / as an alternative to a server-based application on the server computer 12, the method can be a client-side application (not shown) located on one or more client electronic devices 38, 40, 42, 44 (the client-side application being stored, for example, on storage devices 30, 32, 34, 36, respectively). Thus, the method can be a standalone application that interfaces with a client application (e.g., client applications 22, 24, 26, 28), or the method can be an applet / application that executes within a client application. Thus, the method can be a client-side method, a server-side method, or a hybrid client-side / server-side method that can be executed in whole or in part by the server computer 12 or one or more client electronic devices 38, 40, 42, 44.

[0036] The instruction sets and subroutines of the client applications 22, 24, 26, 28, which may be stored on storage devices 30, 32, 34, 36 coupled to the client electronic devices 38, 40, 42, 44, respectively, may be executed by one or more processors (not shown) and one or more memory architectures (not shown) incorporated into the client electronic devices 38, 40, 42, 44, respectively. The storage devices 30, 32, 34, 36 may include, but are not limited to, hard disk drives; tape drives; optical disk drives; RAID arrays; random access memory (RAM); read-only memory (ROM), compact flash (CF) storage devices, secure digital (SD) storage devices, and memory stick storage devices. For example, examples of client electronic devices 38, 40, 42, 44 may include, but are not limited to, personal computers 38, laptop computers 40, personal digital assistants 42, notebook computers 44, data-enabled cellular telephones (not shown), and dedicated network devices (not shown). Users 46 , 48 , 50 , 52 may use client applications 22 , 24 , 26 , 28 to verify a particular integrated circuit configuration using formal analysis, testbench simulation, and / or mixed technology features.

[0037] Users 46, 48, 50, 52 may directly access server-side application 20 through devices executing client applications (e.g., client applications 22, 24, 26, 28), i.e., client electronic devices 38, 40, 42, 44. Users 46, 48, 50, 52 may access server-side application 20 through network 14 or through secondary network 18. In addition, server computer 12 (e.g., a computer executing server-side application 20) may be connected to network 14 through secondary network 18, as indicated by phantom link line 54.

[0038] In some embodiments, method 10 can be a cloud-based method, as any or all of the operations described herein can be performed in whole or in part in the cloud or as part of a cloud-based system. Various client electronic devices can be directly or indirectly coupled to network 14 (or network 18). For example, personal computer 38 is shown as being directly coupled to network 14 via a hardwired network connection. Additionally, laptop computer 44 is shown as being directly coupled to network 18 via a hardwired network connection. Laptop computer 40 is shown as being wirelessly coupled to network 14 via a wireless communication channel 56 established between laptop computer 40 and a wireless access point (WAP) 58, which is shown as being directly coupled to network 14. WAP 58 can be, for example, an IEEE 802.11a, 802.11b, 802.11g, Wi-Fi, and / or Bluetooth device capable of establishing wireless communication channel 56 between laptop computer 40 and WAP 58. The personal digital assistant 42 is shown as wirelessly coupled to the network 14 via a wireless communication channel 60 established between the personal digital assistant 42 and a cellular network / bridge 62 , which is shown as being directly coupled to the network 14 .

[0039] As is well known, all IEEE 802.11x specifications can use the Ethernet protocol and carrier sense multiple access with collision avoidance (CSMA / CA) to achieve path sharing. For example, different 802.11x specifications may use phase-shift keying (PSK) modulation or complementary code keying (CCK) modulation. As is well known in the art, Bluetooth is a telecommunications industry specification that allows, for example, mobile phones, computers, and personal digital assistants to interconnect using short-range wireless connections.

[0040] The client electronic devices 38, 40, 42, 44 can each execute an operating system, examples of which may include but are not limited to Microsoft Windows tm 、Microsoft Windows CE tm 、Red hat Linux tm , Apple iOS, ANDROID or customized operating system.

[0041] Now refer to Figure 2, a flowchart illustrating an embodiment consistent with method 10 (method 10 may include one or more processes or sub-processes, such as a first process, a second process, a third process, etc.) is provided. The first process may include allowing a user to open and control the layout of web applications and desktop applications in one application (202). The process may also include allowing these applications to load and run in a "native" state (e.g., to be used in the same or similar experience as standalone applications) (204). The process may also include allowing the user to indicate the records loaded by these applications (206), and allowing the user to control the window position / layout of the web applications and desktop applications (208). The second process may include allowing the user to select a graphical analysis feature and set automatic refinement of record data in a grid (210), and automatically open the records in multiple different target applications (e.g., within an overlay) (212). The third process may include displaying the graphical analysis on a graphical user interface (214), and allowing the data source to be changed in real time from the program data grid data to any other table / database / source (216). Many other operations are also within the scope of this application, as described below.

[0042] In some embodiments, the methods provided herein may include an "overlay" application that can be located within a program shell to host and interact with web applications and desktop applications. Embodiments of the present application may include a software application, which may be referred to herein as BLIS™. A key feature may be the ability of BLIS to overlay web applications and desktop applications, providing a user with one or more software applications that can be hosted by and interact with a common shell. Within the common shell, the applications can operate normally, for example, as if the user were using the applications in their native or normal state. Within BLIS, a user can simultaneously coordinate the loading and interaction of records between multiple desktop applications and web applications. The graphical user interface (GUI) of the BLIS may be designed to allow a user to perform standard functions or operations, including but not limited to quickly searching, viewing, and / or editing records.

[0043] In some embodiments, the methods provided herein may include multiple components, including, but not limited to, a BLIS Windows (.NET) application shell and a BLIS web application shell. The BLIS Windows (.NET) application shell enables BLIS to create one or more instances and / or run any .NET Windows application. The BLIS Windows (.NET) application shell may also enable a user to interact with the running Windows application GUI to perform operations including, but not limited to, logging in a user, performing a log search, loading a log, etc. The BLIS web application shell may enable BLIS to load and run any web application within the shell. The BLIS web application shell may also enable BLIS to interact with the running web application GUI to perform operations including, but not limited to, logging in a user, performing a log search, loading a log, etc.

[0044] In some embodiments, a BLIS overlay application can be created as a Windows desktop application and a web application using a computer with one or more of the following elements: Microsoft Windows 10 operating system, .NET Framework 4.7.2, and Microsoft Visual Studio IDE (2019). These examples are provided by way of example only, as other versions, operating systems, development frameworks, and integrated development environments may also be used without departing from the scope of this application. During operation, different operations can be used to create the shell and overlay.

[0045] For example, creating a BLIS Windows (.NET) application shell may include, but is not limited to, one or more of the following operations. A first operation may include creating a project called "BLIS Windows Shell" with a form. A second operation may include, upon successful form instance creation of the target form, calling the "CreateInstance" method of the Assembly Class located in the System.Reflection namespace, loading the target .exe / .dll located form with all necessary parameters. A third operation may include applying the form to the form control collection created in the first step and calling the Show method of the form. A fourth operation may include creating mappings of target controls to enable BLIS application integration. These controls and their corresponding mappings may be required to access these controls, perform operations according to workflow requirements, access properties, methods, and events using reflection, pull and push data, and trigger one or more events.

[0046] By way of further example, creating a BLIS web application shell may include, but is not limited to, one or more of the following operations. A first operation may include creating a project "BLIS web application shell" with a form. A second operation may include creating a CefSharp browser instance with the application URL. A third operation may include applying the CefSharp browser instance to the form created in the first step. A fourth operation may include searching for a GUI element by ID. A fifth operation may include executing JavaScript to perform an operation on the target GUI element, thereby pulling and pushing data and triggering one or more events.

[0047] By way of further example, creating a BLIS overlay may include, but is not limited to, one or more of the following operations. A first operation may include creating a project called "BLIS Overlay" with a form. A second operation may include assigning one or more references to the "BLIS Windows Shell" and "BLIS Web App Shell" projects to the project. A third operation may include assigning a grid to the form to host the corresponding data of interest, ensuring that the data contains all the details required to load the corresponding window and web applications and their records. A fourth operation may include assigning a tab control to the form with two tabs, including assigning the "BLIS Windows Shell" to the first tab and the "BLIS Web App Shell" to the second tab. A fifth operation may include filling in details to load a Windows application in the "BLIS Windows Shell" and a web application in the "BLIS Web App Shell." A sixth operation may include initiating an event on the BLIS overlay form to perform one or more login steps in both applications. The seventh operation may include, when the grid row changes, obtaining a program name and a unique ID of a corresponding record of interest from the grid, passing the program name and the unique ID to two application programs, and loading the programs using the corresponding record.

[0048] In some embodiments, the methods provided herein may include application embedded graphical analytics driving application record interaction, which may allow users to select graphical analytics features, automatically refine record data into a grid, and automatically open records in multiple different target applications.

[0049] In some embodiments, application-embedded graphical analytics can include multiple components, including, but not limited to, an entity grid, a dashboard viewer, and a BLIS shell. The entity grid can include a custom grid control enabler to receive a list of records to be loaded as a dataset. The dashboard viewer can include a dashboard control with a custom BLIS layer to extract the dataset from the dashboard. The BLIS shell can be configured to load different applications in an overlay.

[0050] In some embodiments, the method can utilize a computing device with the Microsoft Windows 10 operating system, .Net framework 4.7.2, Microsoft Visual Studio IDE (2019), and DevExpress controls. During operation, this can be generated by creating a window form with an entity control, a BLIS shell, and a center panel viewer. Within the center panel viewer, a method can be applied to refine the corresponding dataset. Within the form, a method can be created for the grid to receive a list of records, filter them, and load only the received list of records. Upon a click event in the center panel viewer, the refined dataset can be passed to a new instance of the form. This refined dataset can be used by the newly launched form instance, which can pull database records and load them into the grid. These grid records can then be loaded into other applications within the BLIS shell, depending on the settings.

[0051] In some embodiments, the method provided herein may include embedded graphical analytics that can be interchanged in real time from the program data grid to any other table / database / source. Programs currently can focus embedded graphical analytics on a specific program grid, or have standard data sources such as database tables, but the graphical data source may not change in real time. The graphical analytics may include multiple components, namely an entity grid and a center panel viewer. The entity grid may include a custom grid control with user-friendly filters that allow users to quickly obtain a target data set. The center panel viewer may include a center panel control provided by Devexpress that has a custom BLIS layer to receive grid available data sets as input to build a center panel. This allows users to visualize grid data in the center panel and enable options to drill down into the center panel to obtain meaningful insights.

[0052] In some embodiments, a computing device having a Microsoft Windows 10 operating system, .Net framework 4.7.2, Microsoft Visual Studio IDE (2019), and DevExpress controls may be provided. Generating may include creating a window form having entity controls and a center panel viewer. In the center panel viewer, a method may be implemented to enable the center panel to receive an incoming data set from the entity grid control. In addition, a checkbox may be implemented in the entity grid control to push the data set to the center panel viewer. In addition, a method may be implemented in the entity grid control to push data to the center panel viewer when any event occurs to which a filter is applied.

[0053] refer to Figures 3A to 5 , providing embodiments of graphical user interfaces 300, 304, 400, and 500 consistent with embodiments of the present application. These figures may illustrate an overlay application 306 that can host and interact with a web application 310 and a desktop application 312 within a program shell 308. During operation, a user can open and control the layout of web applications 312 and desktop applications 314 in one application. The user can enable these applications to load and run in a "native" state (e.g., to be used in the same or similar experience as a standalone application). The user can instruct the record of these applications to load. The user can also control the window position / layout of the web application 312 and the desktop application 314.

[0054] In one embodiment, Figure 3B As shown, a user can load multiple tabs with web applications 312 and tabs with desktop applications 314 within a shell window 316. For example, the software user may be a healthcare professional managing a patient who has medical records in the desktop application 314, which displays electronic medical records (EMRs). Figure 4 As shown in the overlay 400 in FIG. 1 , the billing record 502 is also displayed in the web application 312, as shown in FIG. Figure 5 500 in the overlay. The healthcare provider can have both the desktop electronic medical record and billing web applications launched in the same program shell and use each application (desktop application and / or web application) in its normal state.

[0055] Applications can automatically start and log in the user. These applications can be used with their normal functionality. The user can easily switch between applications and control their window sizes. For example, the user can click on the tab of the desktop application 314 under the common shell 316, and the program can display the desktop application 314 started and working normally (such as Figure 4 Similarly, the user can click on the tab of the web application 312 under the common shell 316, and the program can display the web application launched and working normally (such as Figure 5 316 ). A healthcare professional can efficiently view a patient list and launch both the EMR desktop application 314 and the billing web application 312 in the same shell 316 , with the patient record automatically loaded into both applications.

[0056] In another embodiment, the graphical user interface 400 may allow the user to have a record grid 402 that the user may click to cause one or more records to be loaded into one or both of the web application 312 and the desktop application 314 .

[0057] refer to Figures 6A to 6E , provides a method for application embedded graphical analytics driven application record interaction and illustrates the method through a graphical user interface 600. During operation, the method may allow a user to select a graphical analysis feature and automatically refine the record data in a grid and automatically open the record in multiple different target applications. In one embodiment, by hovering a cursor over a portion of the graphical presentation 602, a more detailed breakdown of the graphical data may be presented to the user. In addition, by right clicking on a particular portion of the chart 602, the user may choose to refine the records 604 associated with the selected portion 602 of the chart. The refined data 606 may be displayed in Figure 6C The desktop application 608 is shown with multiple overlay windows 610. In addition, the user can select a specific record 612 of interest, such as Figure 6D The user can then open the patient file directly in the selected application, here the patient billing file in the web application 612, as shown in the multi-overlay window 610 of FIG. Figure 6E The multi-overlay window 610 is shown.

[0058] refer to 7A to 7C , provides a graphical analysis method 700, wherein the data source 702 can be changed in real time from the program data grid to any other table / database / source 704. Figure 7A As shown in the graphical analysis view 700 , the grid 702 on the left may not be the data source of the chart 704 on the right. Figure 7B A filter grid 706 of patient files is shown, filtered to display only the medical records on the left, which include only 63 records, as highlighted by the record count 708, while the chart continues to display a presentation of all patient files, which may include hundreds of files in total. The graphical display 710 here is different because the "Apply to center panel" checkbox 712 has not been selected. Figure 7C The same, filtered patient file grid 706 is shown, along with an updated graphical representation 714 , since, in this example, the “Apply to Center Panel” checkbox 712 is now selected.

[0059] Now refer to Figures 8A to 8D , provides an embodiment illustrating a modular overlay ticketing system 800 (MOTS). MOTS 800 is a ticket creation application that recognizes and interacts with records loaded from external applications and can coordinate related processes between multiple external applications. An overlay window 802 displays a patient data grid and also includes a ticket template button 804, which ultimately allows for the creation of a ticket that automatically extracts information from the loaded record to identify the "source" for the ticket creation. Button 804 can be located on the record grid, within a form, or above a form.

[0060] In some embodiments, after clicking the Ticket Template button 804, the Ticket Template Selection page 806 may open in a new window, such as Figure 8B As shown. For example, when the user selects the ticket template 808 "Make Espresso", the focus and origin of the ticket will be the loaded record "A000075". A configurable ticket template has been created that identifies the source and focus of the ticket. Depending on the selected configurable ticket template, the "focus" of the ticket may also include information extracted from the loaded record associated with the +T button. The focus information will target the program that the newly created ticket will load and the record that should be loaded in the overlay. If the user then clicks the "Create Ticket" button 810, a new ticket TK003264 is created with the focus and origin record A000075, as shown. Figure 8C The Ticket Manager window 812 is shown. The focus program is the "Example Multi Overlay" that determines the program that will be opened in the overlay when a ticket is opened. By clicking on the ticket of interest, a new multi-overlay window 814 opens, allowing the opening of an external desktop application or web application with tasks related to the newly created ticket located next to it, such as Figure 8D shown.

[0061] The ticketing system doesn't interact with external applications, or requires integration to automatically associate tickets with records in external systems. MOTS (Modular Overlay Ticket System) automatically identifies the record in the external application from which the ticket originated and the record to which the ticket relates.

[0062] For example, an external medical record system, EMRABC, may have a patient identified as medical record "MR12345," and MOTs are created from a ticket originating from the patient record that focuses on a suspect test result record, "TR789," generated from LabInfoSystem LISXYZ. A ticket is automatically created with Origin=MR12345 in the EMRABC application and focus=TR789 in the LISXYZ application. The user can click on the ticket, which then opens record TR789 in LISXYZ within the MOTs overlay, allowing the user to perform the necessary actions on the ticket. It is possible to change the setting so that record IDs are automatically identified as both the source and the focus. These tickets then have functional modules, such as workflow, analysis, and communication, that can be linked.

[0063] In some embodiments, a ticket can be created that recognizes and interacts with records loaded in external applications and can coordinate related processes between multiple external applications. In some embodiments, a computing device having a Microsoft Windows 10 operating system, .Net Framework 4.7.2, Microsoft Visual Studio IDE (2019), and DevExpress controls can be provided. The controls are configured to create a window form, apply a +T button, and apply source and target details to the +T button 804. In addition, when the +T button is clicked, the controls can load a ticket template form. On the ticket template form, select a ticket template record (see Figure 8A ). After selecting a ticket template record, there is a Create Ticket button 810 that can be used to create a ticket, such as Figure 8B shown.

[0064] Those skilled in the art will appreciate that various modifications and variations may be made to the existing estimation scheme and debugging process of the embodiments of the present application without departing from the spirit or scope of the present invention. Therefore, the embodiments of the present application are intended to cover such modifications and variations as fall within the scope of the appended claims and their equivalents.

Claims

1. A computer-implemented method, comprising: Allow users to open and control the layout of web apps and desktop apps in one application; Allowing the web application and the desktop application to load and run in a native state; allowing the user to control the recording of loading of the web application and the desktop application; as well as The user is allowed to control the window position and layout of the web application and the desktop application.

2. The computer-implemented method of claim 1 , further comprising: Allows the user to select one or more graphical analysis features and configures automatic refinement of recorded data into a grid; as well as Automatically open records in multiple different target applications.

3. The computer-implemented method of claim 1 , further comprising: Displaying graphical analysis on a graphical user interface; as well as Allows data source to be changed live from the program data grid to any other table / database / source. 4 . The computer-implemented method of claim 3 , wherein hovering a cursor over a portion of a first graphical representation of data provides more detailed information about the portion of the first graphical representation. 5 . The computer-implemented method of claim 3 , wherein right-clicking on a patient data grid allows filtering of the patient data grid based on preset data categories. The computer-implemented method of claim 5 , wherein the preset data category is user-set.

7. The computer-implemented method of claim 3 , wherein selecting an “Apply to Center Panel” checkbox updates the first graphical representation to display a second graphical representation of the filtered data.

8. The computer-implemented method of claim 1, wherein the web application and the desktop application each include a modular overlay ticketing system configured to create tickets automatically distilled from a patient record information source.

9. The computer-implemented method of claim 7, wherein the modular overlay ticket system includes a ticket template button configured to open a template selection page.

10. The computer-implemented method of claim 8, wherein the template selection page includes a ticket creation button configured to open a ticket manager window and allow user creation of a new ticket automatically associated with a preloaded record for a selected patient.

11. The computer-implemented method of claim 9, wherein the ticket manager window is configured to open an external desktop application in a multi-overlay window.

12. A computer-readable storage medium having stored thereon instructions which, when executed by a processor, cause the following operations: Allow users to open and control the layout of web apps and desktop apps in one application; Allowing the web application and the desktop application to load and run in a native state; allowing the user to instruct the web application and the desktop application to load records; The user is allowed to control the window position / layout of the web application and the desktop application.

13. The computer-readable storage medium of claim 12, wherein further instructions executed by the processor result in the following operations: Allowing a user to select one or more graphical analysis features and to arrange for automatic refinement of recorded data into a grid; and Automatically open records in multiple different target applications.

14. The computer-readable storage medium of claim 12, wherein further instructions executed by the processor result in the following operations: displaying the graphical analysis at a graphical user interface; and Allows data source to be changed live from the program data grid to any other table / database / source. 15 . The computer-readable storage medium of claim 14 , wherein hovering a cursor over a portion of a first graphical representation of data provides more detailed information about the portion of the first graphical representation.

16. The computer-readable storage medium of claim 14, wherein right-clicking the patient data grid allows filtering of the patient data grid based on preset data categories.

17. The computer-readable storage medium of claim 16, wherein the preset data category is set by a user.

18. The computer-readable storage medium of claim 14, wherein selecting an "Apply to Center Panel" checkbox updates the first graphical representation to display a second graphical representation of the filtered data.

19. The computer-readable storage medium of claim 12, wherein the web application and the desktop application each include a modular overlay ticketing system configured to create tickets automatically extracted from a patient record information source.

20. The computer-readable storage medium of claim 19, wherein the modular overlay ticket system includes a ticket template button configured to open a template selection page.

Images