JP2003058680A - Operation management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an internal operation management system for a hospital, etc., which makes it possible to freely set and rearrange an operation flow, prevents a processing omission and misoperation by standardizing the operation flow, can be easily restructured corresponding to change of the layout of operations, and can perform one operation by squeezing another operation into the operation flow. SOLUTION: The operation management system is equipped with a system control part, a storage means, a display means, an input means, an information processing means, and a graphical user interface. The information processing means is equipped with a system manager and function modules; and the system manager combines function modules at a request inputted from the input means to set and alter or rearrange the operation flow. The operation flow is stored in a storage means and displayed by a display means. The functions modules are equipped with a database including application data and application components.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a business management system, and more particularly to a system for managing hospital business such as hospitals, clinics, and dental clinics.

[0002]

2. Description of the Related Art Workflow management, medical care information management, accounting management, and the like are used for management of operations in clinics and the like, and these are performed using existing computer programs.
The contents of the conventional program cannot be changed by the user.

For this reason, when the conventional system for in-hospital work management is used, the in-hospital work is operated in accordance with the function provided by the system. When it was not possible to match some of the work to the functions provided by the system, the system was individually customized to handle it. Further, when the system and the work contents cannot be matched, a new system is constructed or the work flow in the clinic is changed.

Further, since one work is often composed of a combination of a plurality of works, in the conventional system, a plurality of works are listed in a list format, or one icon representing one work is displayed according to the number of works. A menu screen for arranging a plurality of them is displayed on the display device. Then, when performing a task, from the menu screen, select the first task from a plurality of tasks related to the task, expand the window related to that task, and when that task ends,
Return to that menu screen, select another work item to be performed next, and finish that work. When that work ends, return to the menu screen and select the next work to expand and perform that work. Every time you perform a task, you can select a task item from the menu screen, execute the content indicated by the task item, finish the task, display the menu screen, and select the next task It was processing business. When performing another business, the same procedure was performed for that business.

[0005]

[Problems to be Solved by the Invention] It takes time to complete customization and construction of a new system, and the cost becomes huge. In addition, since it is necessary to change the system each time due to changes in personnel, equipment, medical care policy, etc. of the clinic and changes in the environment outside the clinic, the time and cost for that need increase. The trade-off between time and cost does not lead to a fundamental solution to those problems.

[0006] Further, for example, since the environment and medical care policy in a hospital such as a dental clinic are different from each other, it is desired that a doctor or a person in charge of business management can easily customize a workflow optimal for the environment and medical care policy. ing.

Further, it is necessary for the operator to select the work items displayed on the menu screen in order and perform the work. Since the operator must return to the menu screen to select the work item each time the work is performed, Execution is complicated. Further, since the work items displayed on the menu screen are not related to each other, the operator may mistake the order of the work items or forget to select some of the works. As a result, the work may have to be redone.

Furthermore, when one work is being performed and another work is to be performed, the work being executed must be terminated and the menu screen must be displayed. Then, select a new work to be performed from that menu screen, perform that work, and when that work is completed, return to the menu screen, select the work that was being performed before, and redo the work. It was very complicated.

[0009]

In order to solve such a problem, the present invention provides a business management system including a system control unit, a storage unit, a display unit, an input unit and an information processing unit. The information processing means includes a system manager and a functional module, and in response to a request input from the input means, the system manager sets a business flow by combining the functional modules,
It is characterized in that the business flow is changed or rearranged, and the business flow is stored in the storage means and displayed on the display means. Functional modules can include application data and application components. The functional modules can also include a process controller and a graphical interface. The business management system according to the present invention further comprises a graphical user interface, and in response to a request input from the input means,
The system manager can set up, modify or rearrange business flows by combining application components and graphical user interfaces.

Further, the present invention comprises an information processing means, a plurality of business management devices each provided with the information processing means, and a shared data storage means, wherein the information processing means comprises a system manager and functional modules. Provided is a business management system in which business management devices are connected to each other. The system manager configures the same business flow as the system manager's business flow that functions in another business management apparatus by combining functional modules, and functions in another business management apparatus by using the data in the shared data storage means. Enables execution of the same business flow as the system manager's business flow. The function module includes an application component and a graphical user interface, and a system manager sets, changes or rearranges a business flow by combining the application component and the graphical user interface in response to a request input from the input means. You can

Further, the present invention is a business management system comprising a system control unit, a storage unit, a display unit, an input unit and an information processing unit, wherein the information processing unit comprises a system manager, and the system manager operates from the input unit. Provided is a business management system that responds to an input interrupt request, interrupts a business flow that is being executed, executes the requested business flow, and when the business ends, restarts the interrupted business flow. The information processing unit further includes a functional module and a graphical user interface, and the system manager combines the functional module and the graphical user interface in response to a request input from the input unit during an interrupt process to perform a business flow. It can be set, changed or rearranged.

Furthermore, the present invention is a business management system including a system control unit, a storage unit, a display unit, an input unit and an information processing unit, wherein the information processing unit includes a system manager, application data and application components. It is equipped with a database containing it, a process controller, a flexible frame consisting of a large number of programs corresponding to each business process, and a graphical user interface. When this system is started, the process controller stores the flexible frame and application data in the storage means. Along with loading, stores a copy of the application data and application components from the database in the flexible frame in response to the input request from the input means. The flexible frame is stored in the storage means, and when a request is made by one of the methods of the process controller, a copy of the application data and the application component stored in the storage means is used, and the database directly stores the application data and Provide a business management system that does not require application components.

[0013]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 shows a work management apparatus 1 used in a system according to the present invention. Here, an example will be described in which the work management apparatus 1 is used as a work management apparatus for a dental clinic, but the system according to the present invention is not limited to a dental clinic. The device 1 includes a personal computer body 2, a display 3 as a display device, a keyboard 4 and a mouse 5 as an input device, and a printer 6 as an output device.

FIG. 2 shows a block diagram of the device. Figure 2
As shown in FIG.
0, memory 11 as storage means, input device controller 1
2, a display device control unit 13, a printing device control unit 14, and a file unit 15. Input devices such as a keyboard 4 and a mouse (or a pointing device) 5 are connected to an input device controller 12, and a display 3 is a display device controller 1.
3 and the printer 6 is connected to the printer control unit 14
It is connected to the.

FIG. 3 is a diagram for explaining the concept of the dental information processing system. The dental information processing system operates on the device 1 shown in FIG. 1 to perform various information processing in a dental clinic, for example, input of treatment contents, issuance of a receipt, processing of a partial burden of a counter, and other tasks. It can be performed. In the dental information processing system, the user can design the layout of the menu,
Also, other business functions can be used.

FIG. 4 is a diagram for explaining the concept of menu layout design. This diagram illustrates the behavior of the system for the user. In the figure, the behavior of the system is enclosed by an ellipse. They are achieved by combining and modifying functional modules. Among them, 5 of "define tab name", "define button function", "define button name", "define button color" and "define button layout" Two functions are directly provided to the user by the menu layout design function. Four of the functions, namely "Define button function", "Define button name", "Define button color" and "Define button layout" are It is generalized to “manage” and further to “manage menu”. "Manage menu" includes "manage layout space".

Further, "define tab name" is generalized to "manage tab page", and is further generalized to "manage menu".

In FIG. 4, the system manager outside the frame of "menu layout design" manages all the functions of the menu layout design by managing the behavior of "managing the menu".
As a result, the business management system according to the present invention has a scheduler function, and even when the number and position (business layout) of PCs or the like regarding business is changed, the system can be reconstructed and it can be easily dealt with. Further, while one job is being processed, another job can be interrupted and executed.

FIG. 5 is a diagram showing the relationships and elements of the classes used in the menu layout design function shown in FIG. The "system manager" manages the entire system in cooperation with the "other managers" and has a one-to-one relationship with the "layout space" used in the menu layout design function. The "layout space" is associated with 1 to a maximum of 7 "tab pages". Further, one to "maximum 12" of "function buttons" are associated with one of the "tab pages". All of these numbers are exemplary and not limiting.

FIG. 6 is a diagram showing the flow of the system until the menu is displayed at the time of system startup.
As shown in the figure, the menu screen is different when the menu is customized by the user and when it is not customized. That is, when the system is started and the menu display is started, the standard definition is read and the standard menu is displayed if it is not customized. If it is customized, the menu definition is loaded and then the custom menu according to the definition is displayed.

FIG. 7 is a diagram for explaining the temporal interaction of each object. This figure shows the temporal interaction of objects inside the system caused by three kinds of events when the user starts the system, clicks the standard button, and clicks another page. "GUI (menu screen)", "System Manager", "Layout Space", "Tab Page", "Function Buttons", and "Functions" arranged side by side in the upper part of the figure
Represents a generated object. In this figure, the passage of time is shown from the top to the bottom, and the arrows between objects and the accompanying descriptions represent messages from object to object. This represents the timing of message exchange and generation between objects. The timing of exchanging messages between these objects will be described below with reference to FIGS. 8 to 10.

FIG. 8 is a diagram for explaining the structural interaction of each object when the system is activated.
In particular, this figure is a diagram in which only the event of "at system startup ()" shown in FIG. 7 is extracted, and the configuration of the object at that time is focused and expressed. From this figure, it can be seen that messages are exchanged between objects centering on the system manager. That is, when the user performs "1 system start ()", a "GUI (menu screen)" is generated, and the object sends a message "2 menu is displayed ()" to the system manager. After that, the system manager sends the message "3 layout space display ()" to the "layout space", followed by the message "4 tab page display ()" to the "tab page",
Then, the message "5 button display ()" is sent to the "function button". Subsequently, the "function button" sends a "6 display complete ()" message to the system manager, which causes the "function" to send a "7 boot ready ()" message.

FIG. 9 is a diagram for explaining the constructive interaction of each object when the user clicks the function button. In particular, this figure is a diagram in which only the event of "button click ()" shown in FIG. 7 is extracted and focused on the configuration of the object at that time. From this figure, it can be seen that messages are exchanged between objects centering on the system manager. In other words, when the user clicks "1 function button ()", a "GUI (menu screen)" is generated, and that object causes "2" to appear in the system manager.
Click the button () "message is sent. After that, the system manager sends a message "execution of three functions ()" to the "function", while a message "end of four functions" is sent from the function to the system manager.

FIG. 10 is a diagram for explaining the constructive interaction of each object when the user clicks another page. In particular, this figure is a diagram in which only the event of “clicking another page ()” shown in FIG. 7 is taken out and the object configuration at that time is focused on. From this figure, it can be seen that messages are exchanged between objects centered on the system manager. In other words, when the user clicks "1 Click another page ()", a "GUI (menu screen)" is generated and the message "2 Click another page ()" is sent from that object to the system manager. Sent. After that, the system manager sends a message of "display 3 different pages ()" to the "tab page" and a message of "display 4 buttons ()" to the "function button". On the other hand, the "function button" sends a message "5 display completed" to the system manager.

FIG. 11 to FIG. 20 are diagrams for explaining the work flow when the user customizes the menu screen. All of these tasks are managed by the system manager.

FIG. 11 is a diagram for explaining a flow of operations when the user performs a "define tab name" operation in order to customize the menu screen using an input device such as a mouse or a keyboard. is there. As shown in the figure, the user first activates the menu management screen.
Next, select the tab to be defined and define the tab name.
Once the decision is made, the change is recorded. The work is completed when the management screen is closed. If you select "Stop work" immediately after activating the menu screen, the work ends at that point. Even if the definition of the tab name is changed and then the change is canceled, the work is terminated at that point.

FIG. 12 is a diagram for explaining the state transition of the system when the “define tab name” operation described in FIG. 11 is performed. As shown in the figure, when the menu management screen is activated, it shifts to "waiting for menu definition".
When the tab to be defined is selected, it shifts to "wait for tab name change". When the name change is started, the name is changed to "during name change", and when the confirmation button is clicked, the state is changed to "during change record". When the recording end is selected, the work is completed.
On the other hand, when the work stop is selected in the "waiting for menu definition", the work ends at that point. Also, when the cancel of the change is selected in the state of "renaming", the work is finished at that point.

FIG. 13 is a diagram for explaining the flow of the operation when the user performs the "define button color" work in order to customize the menu screen. As shown in the figure, the user first activates the menu management screen. Next, select the button to be defined and define the button color. Once the decision is made, the change is recorded. The work is completed when the management screen is closed. If you select "Stop work" immediately after activating the menu screen, the work ends at that point. Even if you change the definition of the button color and then cancel the change, the work ends at that point.

FIG. 14 is a diagram for explaining the state transition of the system when the “define button color” operation described in FIG. 13 is performed. As shown in the figure, when the menu management screen is activated, it shifts to "waiting for menu definition". When the button to be defined is selected, it shifts to "wait for button definition change". Then, when the color palette is activated, the button color is being changed, the confirmation button is clicked, the change recording is in progress, and when the recording end is selected, the operation is completed. On the other hand, when the work stop is selected in the "waiting for menu definition", the work ends at that point. Also, when the change cancel is selected in the state of "changing button color", the work is finished at that point.

FIG. 15 is a diagram for explaining the flow of the operation when the user performs the "define button function" operation to customize the menu screen.
As shown in the figure, the user first activates the menu management screen. Next, the button to be defined is selected and the button function is defined. Once the decision is made, the change is recorded. The work is completed when the management screen is closed. If you select "Stop work" immediately after activating the menu screen, the work ends at that point. Even if you change the definition of the button color and then cancel the change, the work ends at that point.

FIG. 16 is a diagram for explaining the state transition of the system when the “define button function” operation described in FIG. 15 is performed. As shown in the figure, when the menu management screen is activated, it shifts to "waiting for menu definition". When the button to be defined is selected, it shifts to "wait for button definition change". Next, when the button function is selected, the button function is being changed, and when the confirmation button is clicked, the change is recorded, and when the recording end is selected, the work is completed. On the other hand, when the work stop is selected in the "waiting for menu definition", the work ends at that point. Also, when the change cancel is selected in the state of "changing button function", the work is finished at that point.

FIG. 17 is a diagram for explaining the flow of the operation when the user performs the "define button layout" work to customize the menu screen.
As shown in the figure, the user first activates the menu management screen. Next, the function button to be used is determined, then the button layout page is specified, and further, the button layout location is specified. Once the decision is made, the change is recorded. The work is completed when the management screen is closed. If you select "Stop work" immediately after activating the menu screen, the work ends at that point. Even after the button placement location is specified and the previous specifications have been changed, if the change is canceled, the work ends at that point.

FIG. 18 is a diagram for explaining the state transition of the system when the "define button layout" operation described in FIG. 17 is performed. As shown in the figure, when the menu management screen is activated, it shifts to "waiting for menu definition". When the button to be used is selected, it moves to "Waiting for page selection", when a page is specified, it moves to "Waiting for button layout", and when the layout location is specified, it becomes "Waiting for confirmation" Transition. Then, when the confirmation button is clicked, the state is changed to "change recording in progress", and when the recording end is selected, the work is completed. On the other hand, when the work stop is selected in the "waiting for menu definition", the work ends at that point. Also,
Even when the change cancel is selected in the "fixed waiting" state, the work ends at that point.

FIG. 19 is a diagram for explaining the flow of the operation when the user performs the "define button name" work in order to customize the menu screen.
As shown in the figure, the user first activates the menu management screen. Next, the button whose name is to be changed is selected and the button name is defined. Once the decision is made, the change is recorded. The work is completed when the management screen is closed. If you select "Stop work" immediately after activating the menu screen, the work ends at that point. Even if the definition of the button name is changed and then the change is cancelled, the work ends at that point.

FIG. 20 is a diagram for explaining the state transition of the system when the “define button name” operation described in FIG. 19 is performed. As shown in the figure, when the menu management screen is activated, it shifts to "waiting for menu definition". When the button whose name is to be changed is selected, the screen shifts to "wait for button definition". Subsequently, when the name change start is selected, the button is in the process of changing the name of the button, and when the confirmation button is clicked, the change is recorded, and when the recording end is selected, the work is completed. On the other hand, when the work stop is selected in the "waiting for menu definition", the work ends at that point. Also, when the change cancel is selected in the state of "changing button name", the work is finished at that point.

FIG. 21 is a flow chart for performing operations such as changing the positions of the above menu buttons on the menu management screen. When performing menu management, first, the setting screen is displayed and the menu management screen is activated. If the cancellation is not made at that point, the operation shifts to work such as changing the button color. After making the change, select Save to save the changed content. When the menu management screen is closed, the work is completed.

FIG. 22 shows a work flow for changing the position of the menu button in managing the menu in FIG. First, the setting screen is displayed and the menu management screen is activated. If it is not canceled at that point, the process moves to the selection of the button position, and when the selection is made, the changed button is displayed. When changing the position of another button, selection of the position of the button is repeated in response to the request. The work is completed when the changed data is saved and the menu management screen is closed.

FIG. 23A is a diagram for explaining the function of the system manager. The system manager includes an event manager, a status manager, a process controller and a message controller, and controls these states. In the system according to the present invention, application data, which are all elements of each business process constituting a workflow, and metadata (data for managing data) that manages application data, forms, lists, objects, and properties. The application components and are all stored in the database. The process controller corresponds to each virtual program data,
Variable data can be manipulated.

As shown in FIG. 24, when a program constituting the system is activated, the process controller
A structure called a flexible frame, which is composed of a large number of programs and data corresponding to each business process, is loaded into the memory. Further, the process controller stores a copy of the data and application components from the database in the flexible frame and stores in memory in response to the request. When a request is issued from one of the process controller methods when the flexible frame is stored in memory in this state,
A copy of the requested data and application components stored in memory is used, eliminating the need for the database to provide the requested data and application components directly to the program. As a result, the database access overhead can be reduced.

As can be seen from FIG. 24, the GUI operation from the method of the process controller corresponding to each business process is performed as follows through the flexible frame. Process controller to GU
Create a bond for I. Create a GUI to process controller binding. Processes messages from the GUI to the process controller. These will be briefly described below.

First, in order to create a GUI binding from the process controller, the process control method stores the GUI handle in the flexible frame. The GUI handle acquired by this method corresponds to the G handle corresponding to various methods of the process controller.
Used to specify the UI.

Next, in order to create a binding from the GUI to the process controller, the specified GUI is associated with the process controller. This association is
When the method of the process controller generates GUI
This is done by getting the process controller's object reference to I. The obtained object reference is stored in the flexible frame, and other methods use it above to associate the GUI with the process controller by converting the GUI handle into a process controller object reference.

As shown in FIG. 24, the program according to the present invention uses a mechanism called a flexible frame relationship when associating the process controller with the GUI through the flexible frame. The flexible frame relationship is a mechanism that once receives a message from the GUI with a simple procedure and calls a method of the object from there.

Message processing from the GUI to the process controller is performed as follows. First, when the GUI arrives from the address of the GUI procedure of the GUI stored in the flexible frame, the process controller passes the message to the message processing handler indicated by this address. Next, the process controller creates a flexible frame relationship. Flexible frame relationships work with two supplemental cords. A method pointer is stored in the flexible frame relationship, and when the flexible frame relationship is called, the flexible frame relationship calls an auxiliary code. The auxiliary code puts a pointer to the method pointer in a register to pop up the return value. Next, the auxiliary code calls a function, looks at the method pointer pointed to by the register, and calls the method of the object indicated by the method pointer.

As described above, the flexible frame relationship is used as the GUI procedure of the GUI and the GU.
By creating a mechanism for setting in the I procedure, it becomes possible to send a message directly from the GUI to the method of the process controller.

When an interrupt occurs as shown between the process controller 23-1 and the process controller 23-2 in FIG. 23 (a), the system manager interrupts the interrupt as shown in FIG. 23 (b). The manager operates another process controller to operate the GUI for interrupt work as described in FIG. 24, and when the interrupt is cleared thereafter, it is recognized and the flow is interrupted in FIG. 23 (a). Return to the original flow when cleared.

Next, procedures for creating, changing, deleting and adding a work flow will be described with reference to FIGS. 25 to 28.

When creating a business flow as shown in FIG. 25, first, the setting screen is displayed and the business flow management screen is activated. Next, the request flow is selected, and the flow is added, changed, or deleted, and the result is saved. The work is completed when the contents of the flow are confirmed and the business flow management screen is ended.

When changing the work flow as shown in FIG. 26, first, the setting screen is displayed and the work flow management screen is activated. Next, the request flow is selected, and the item number of the flow is selected, the work is selected, and the result is saved until there are no changed items. The work is completed when the contents of the flow are confirmed and the business flow management screen is ended.

When deleting a business flow as shown in FIG. 27, first, similarly, the setting screen is displayed and the business flow management screen is activated. Next, the request flow is selected and the flow is deleted. The work is completed when the contents of the flow are confirmed and the business flow management screen is ended.

As shown in FIG. 28, when adding a work flow, the setting screen is first displayed and the work flow management screen is activated, as in the conventional case. Next, the request flow is selected, and the new flow is displayed. Then, until there are no changed items, the item number of the flow is selected, the work is selected, and the result is saved. The work is completed when the name of the flow is created, the contents of the flow are confirmed, and the workflow management screen is closed.

Next, referring to FIGS. 29 to 31,
An example of setting / changing / deleting a business flow by the system according to the present invention will be specifically described based on the screen specifically displayed on the display 3 (FIG. 1). First, the personal computer main body 2 (FIG. 1) is started, and the main menu screen shown in FIG. 29 is called on the display 3 (FIG. 1). This is the setting screen. When "Setting / Other special" is clicked in the middle of the right side of this screen, a screen "terminal setting, business setting" shown in FIG. 30 is called. There is shown a case where the basic process shown as, for example, is set as the basic process. Further, as shown in FIG. 31, the normal business is set to the normal business. On this screen, a business flow can be set for each terminal device. If "Edit order / selection" is clicked here, the screen shown in FIG. 32 is displayed. Here, it is possible to select an item, redo the editing, and create a new business flow. At that time, as shown in FIG. 33, "Concatenate final screen here", "Add next screen", "Add previous screen", "Change this screen name", "Delete this screen" and A screen showing "Cancel" is displayed, a required work is selected from the screen, and as shown in FIG. 34, a floating window showing "Select screen name of work" in which work names are listed is displayed. , Select the screen name of the job from among them as necessary and confirm it. When the confirmation screen is displayed as shown in FIG. 35, the business flow name can be saved. As shown in FIG. 36, a screen for deleting a flow is displayed, and when "Delete flow [F1]" is pressed there, the selected business flow can be deleted.

Next, the case of using the set business flow will be described.

As shown in FIG. 37, in the system according to the present invention, in executing the business flow, it is the first system start of the day, the routine work is executed, or the system is executed after the business end. Will be selected.

In the case of system activation for the first time on the day, as shown in FIG. 38, first, the system activation for the first time on the day of performing the business is performed, and the business flow is executed until the flow item is completed. In the meantime, if interrupt work occurs and it is a non-flow work, the selection screen is displayed, data is input, and if OK, the interrupt ends and returns to the continuation of the original flow. When it is finished, the main menu display is returned to the end.

When the routine work is executed in the work flow, as shown in FIG. 39, the main menu is displayed and the routine work flow is executed until the end of the work.
In the meantime, if an interruption occurs and the work is outside the flow, the selection screen is displayed, data is input, and the process returns to the original flow. After that, when a work other than the routine work occurs, the other work is executed, the process returns to the loop of the original work, and the process ends.

When a business flow is executed when the system is terminated after the set business end time, it is selected, and as shown in FIG. 40, work is first performed until the flow item is completed. If an interruption occurs in the meantime, if it is a work outside the flow, a selection screen is displayed, if data is entered and if it is OK, it returns to the original flow work and the system is terminated.

When manually switching the work flow, the main menu is displayed as shown in FIG.
Start the job switching screen. The requested work flow is selected from the screen, and if it is OK, the work is updated and the work is ended.

When the system is activated for the first time on the day of work, the business start screen shown in FIG. 42 is displayed on the screen of the display 3 (FIG. 1). At this time, "Start today's business. Do you want to automatically execute" Daily business start process "? Is displayed, the main menu shown in FIG. 43 is displayed when "Yes" is selected. At the bottom of this screen, "1. Frequently used screen", "2. Patient registration relations", "3. Accounting work relations", "4. Report entry", "5. Reservation relations" and "Settings / The tab page displayed as "Other special" is set. In FIG. 43, a tab page of "1. Frequently used screen" is displayed, and function buttons such as "patient search", "edit patient information", and "account check" are set therein. When the menu management screen shown in FIG. 44 is called up, the function button name, button color, etc. can be changed on the screen. When "Change button color" is selected, a floating palette for color selection is displayed as shown in FIG.
Thereby, the color can be freely set. Figure 4
When the list of screens shown in FIG. 6 is opened, it is possible to select the business to be assigned to the function button.

Again, returning to the menu screen shown in FIG. 43, from the function buttons at the bottom of the screen, "window accounting"
When is pressed, the window for window accounting processing of FIG. 47 is opened.
When the amount of money is entered in the blank space displayed on it, the billed amount is calculated and displayed, whereby the clearing process can be performed and the receipt can also be printed. OK here
Pressing the button automatically advances to the next set work.

When switching the business, the business switching screen shown in FIG. 48 is displayed.

When the medical examination time has passed, as shown in FIG. 49, the end-of-service screen is automatically displayed on the menu screen, whereby the daily work end processing can be performed. , If necessary, automatic execution can be continued.

[0063]

According to the present invention, the system manager is provided and the architecture of the flexible frame system is implemented, so that it is possible to freely set and reconfigure the flow of the unique work for each clinic. Further, since the flow of the work is automated, the work can be standardized and the omission of processing and erroneous operation can be prevented. In addition, the flow of work unique to the clinic can be freely set and recombined.

Further, according to the present invention, since the reconstruction function by the system manager is installed, for example, the number of chairs and personal computers is increased or decreased, the number of doctors, the number of hygienists,
Rules and changes that are adhered to in performing in-hospital work due to factors such as the number of technicians, the number of assistants and their respective role divisions, medical treatment days and consultation days, consultation hours and consultation hours, medical policies and differences in treatment techniques. It is possible to change / define the contents of the elements to be processed and the work process easily, quickly and flexibly.

Further, while one work is being executed, another work can be interrupted.

[Brief description of drawings]

FIG. 1 is a diagram showing an outline of a configuration of a business management apparatus used in a system according to the present invention.

FIG. 2 is a block diagram of a business management device according to FIG.

FIG. 3 is a diagram for explaining the concept of a dental information processing system.

FIG. 4 is a diagram for explaining the concept of menu layout design.

FIG. 5 is a diagram for explaining the relationships and elements of classes used in the menu layout design function shown in FIG.

FIG. 6 is a diagram for explaining the flow of the system until a menu is displayed when the system is started up.

FIG. 7 is a diagram for explaining a temporal interaction of each object.

FIG. 8 is a diagram for explaining the structural interaction of each object when the system is activated.

FIG. 9 is a diagram for explaining the structural interaction of each object when the user clicks the function button.

FIG. 10 is a diagram for explaining the constructive interaction of each object when the user clicks another page.

FIG. 11 is a diagram for explaining a flow of an operation when the user performs a “define tab name” work in order to customize the menu screen.

FIG. 12 is a diagram for explaining a state transition of the system when the “define tab name” work described in FIG. 11 is performed.

FIG. 13 is a diagram illustrating a flow of an operation when a user performs a “define button color” work in order to customize the menu screen.

FIG. 14 is a diagram for explaining the state transition of the system when the “define button color” operation described in FIG. 13 is performed.

FIG. 15 is a diagram illustrating a flow of operations performed when a user performs a “define button function” operation in order to customize a menu screen.

FIG. 16 “Define a button function” described in FIG.
It is a figure for demonstrating the state transition of the system at the time of performing work.

FIG. 17 is a diagram for explaining a flow of an operation when the user performs a “define button layout” work in order to customize the menu screen.

FIG. 18 “Define button layout” described in FIG.
It is a figure for demonstrating the state transition of the system at the time of performing work.

FIG. 19 is a diagram for explaining a flow of an operation when the user performs a “define button name” work in order to customize the menu screen.

FIG. 20 “Define a button name” described in FIG.
It is a figure for demonstrating the state transition of the system at the time of performing work.

FIG. 21 is a flow chart for performing work such as changing the position of the menu button described above on the menu management screen.

FIG. 22 is a flowchart for explaining a work flow when changing the position of a menu button in menu management in FIG. 21.

FIG. 23 (a) is a diagram for explaining the function of a system manager. FIG. 23B is a diagram for explaining the function of the system manager when an interrupt is made.

FIG. 24: GU from method of process controller
It is a figure for demonstrating operation of I.

FIG. 25 is a flowchart for explaining a procedure for creating a business flow.

FIG. 26 is a flowchart for explaining a procedure for changing a business flow.

FIG. 27 is a flowchart illustrating a procedure for deleting a business flow.

FIG. 28 is a flowchart illustrating a procedure for adding a business flow.

FIG. 29 is a diagram showing a setting screen displayed on the display.

FIG. 30 is a diagram showing a screen for terminal setting and business setting displayed on the display.

FIG. 31 is a diagram showing a screen for terminal setting and business setting displayed on the display.

FIG. 32 is a diagram showing a screen for changing the window processing displayed on the display.

FIG. 33 is a diagram showing a screen for changing the window processing displayed on the display.

FIG. 34 is a diagram showing a screen for changing the window processing displayed on the display.

FIG. 35 is a diagram showing a screen for changing the window processing displayed on the display.

FIG. 36 is a diagram showing a screen for changing the window processing displayed on the display.

FIG. 37 is a flowchart showing a procedure for using a business flow.

FIG. 38 is a flowchart showing a procedure for executing a business flow when the system is activated.

FIG. 39 is a flowchart showing a procedure for executing routine work in a business flow.

FIG. 40 is a flowchart showing a procedure for executing a business flow when the system is terminated after the set business end time.

FIG. 41 is a flowchart showing a procedure for manually switching the business flow.

FIG. 42 is a diagram showing a work start screen shown on the display.

FIG. 43 is a diagram showing a main menu screen shown on the display.

FIG. 44 is a diagram showing a menu management screen shown on the display.

FIG. 45 is a diagram showing a screen when selecting a color shown on the display.

FIG. 46 is a diagram showing a screen showing a list of screens shown on the display.

FIG. 47 is a diagram showing a screen showing an example of window accounting shown on the display.

FIG. 48 is a diagram showing a task switching screen shown on the display.

FIG. 49 is a diagram showing a business end screen shown on the display.

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Keiichi Iwamuro             2-17-15 Yushima, Bunkyo-ku, Tokyo Saito Building 3             F Dental Systems.com Stock Association             In-house

Claims (9)

[Claims] 1. A business management system including a system control unit, a storage unit, a display unit, an input unit, and an information processing unit, wherein the information processing unit includes a system manager and a functional module, and inputs from the input unit. In response to the requested request, the system manager sets up a business flow by combining the functional modules,
A business management system that is changed or rearranged, and the business flow is stored in the storage means and displayed on the display means. 2. The business management system according to claim 1, wherein the functional module includes application data and application components. 3. The business management system according to claim 1, wherein the functional module includes a process controller and a graphical interface. 4. The business management system according to claim 2, further comprising a graphical user interface, wherein said system manager combines said application component and said graphical user interface in response to a request inputted from said input means. A business management system that sets, modifies, or rearranges business flows. 5. An information processing unit, a plurality of business management apparatuses each provided with the information processing unit, and a shared data storage unit, wherein the information processing unit includes a system manager and a functional module. In a business management system in which devices are connected to each other, the system manager configures the same business flow as a business flow of a system manager that combines the functional modules and functions in another business management device, and stores the shared data storage means. A business management system that enables the use of data to execute the same business flow as that of a system manager that functions in another business management device. 6. The business management system according to claim 5, wherein the functional module includes an application component and a graphical user interface, and the system manager responds to a request input from the input means, the system component and the graphical user interface. A business management system that sets, modifies, or rearranges a business flow by combining it with a graphical user interface. 7. A business management system including a system control unit, a storage unit, a display unit, an input unit, and an information processing unit, wherein the information processing unit includes a system manager.
The system manager responds to the interrupt request input from the input means, interrupts the business flow being executed,
A business management system that resumes a suspended business flow when the requested business flow is executed and the business ends. 8. The business management system according to claim 7, wherein said information processing means further comprises a functional module and a graphical user interface, and in response to a request inputted from said input means during interrupt processing, A business management system in which the system manager can set, change, or rearrange a business flow by combining the functional module and the graphical user interface. 9. A business management system including a system control unit, a storage unit, a display unit, an input unit, and an information processing unit, wherein the information processing unit includes a system manager, and a database including application data and application components. A process controller, a flexible frame composed of a large number of programs corresponding to each business process, and a graphical user interface are provided. When the system is started, the process controller causes the flexible frame and the application data to be stored in the storage means. In addition to loading, a copy of application data and application components from the database to the flexible frame in response to a request input from the input means. And storing the flexible frame in the storage means, and when a request is made by one of the methods of the process controller, a copy of the application data and application components stored in the storage means is used, A business management system that eliminates the need for the database to directly provide application data and application components.