JP2019016040A - Screen transition information output program, screen transition information output method, and screen transition information output device - Google Patents

Abstract

To output data indicating screen transition when a correct operation is performed.SOLUTION: An operation pattern list generation unit 46 extracts an operation pattern corresponding to a normal operation from an operation history DB 60 in which history information of a series of operations acquired by an operation history acquisition unit 42 by referring to a return DB 62 in which return data is stored, and displays the extracted operation pattern information while being contained in an operation pattern list. When one pattern in the displayed selection pattern list is selected, a screen transition data generation unit 50 generates screen transition data corresponding to the selected series of operations, and a screen transition data output unit 52 outputs the screen transition data.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a screen transition information output program, a screen transition information output method, and a screen transition information output device.

  Due to the complexity of medical affairs and the complexity of systems used in medical affairs, a great deal of time and effort is required for education and training of the staff of the medical department engaged in medical affairs. For example, since the staff of the medical department needs to operate an electronic medical record system in addition to the medical system, it is necessary to provide education and training for each system. Manuals describing operation methods are often used for staff education and training.

JP 2006-227730 A JP-A-6-67864 JP-A-10-105444 JP 2014-10735 A

  When creating a practical manual, it is preferable to create a manual based on the contents actually operated by an expert. However, when manualizing the operation content, it is necessary to take a hard copy of the screen, and the work takes a lot of time. In addition, since there is no guarantee that the operation content performed at the time of manualization is appropriate, a manual based on an erroneous operation may be created. It should be noted that not only medical office work but also other fields have similar problems when manualizing operation contents.

  In one aspect, an object of the present invention is to provide a screen transition information output program, a screen transition information output method, and a screen transition information output device capable of outputting screen transition information when a correct operation is performed. And

  In one aspect, the screen transition information output program associates a series of operations with result information indicating that processing by the series of operations is normal or abnormal from a log including a history of the series of accepted operations. The log corresponding to the normal process is extracted with reference to the storage unit, the log corresponding to the extracted normal process is displayed, and when the selected one of the displayed logs is received, the selected A screen transition information output program for causing a computer to execute processing for outputting information of screen transition corresponding to a series of operations included in a log.

  Information on screen transitions when correct operations are performed can be output.

It is a figure showing roughly composition of a medical office system concerning one embodiment. FIG. 2A is a diagram illustrating a hardware configuration of the client terminal, and FIG. 2B is a diagram illustrating a hardware configuration of each server in FIG. It is a functional block diagram of a data processing server. FIG. 4A is a diagram illustrating an example of an electronic receipt, and FIG. 4B is a diagram illustrating an example of return data. FIG. 5A and FIG. 5B are diagrams (No. 1) for explaining the operation history acquisition process. FIGS. 6A and 6B are diagrams (part 2) for explaining the operation history acquisition process. FIGS. 7A and 7B are views (No. 3) for explaining the operation history acquisition process. FIGS. 8A and 8B are diagrams (part 4) for explaining the operation history acquisition process. FIGS. 9A and 9B are diagrams (No. 5) for explaining the operation history acquisition process. FIGS. 10A and 10B are views (No. 6) for explaining the operation history acquisition process. FIGS. 11A and 11B are views (No. 7) for explaining the operation history acquisition process. 12A and 12B are views (No. 8) for explaining the operation history acquisition process. FIGS. 13A and 13B are views (No. 9) for explaining the operation history acquisition process. FIGS. 14A and 14B are views (No. 10) for explaining the operation history acquisition process. FIG. 15A and FIG. 15B are views (No. 11) for explaining the operation history acquisition process. FIGS. 16A and 16B are views (No. 12) for describing the operation history acquisition process. FIGS. 17A and 17B are views (No. 13) for explaining the operation history acquisition process. 18A and 18B are diagrams (No. 14) for explaining the operation history acquisition process. It is a flowchart which shows the production | generation process of an operation pattern list. It is a figure which shows an example of the operation pattern list. It is a flowchart which shows a screen transition data production | generation / output process. It is a figure which shows an example of screen transition data (the 1). It is a figure (example 2) which shows an example of screen transition data. It is a figure which shows the modification of screen transition data. FIG. 10 is a diagram for describing an example of processing when an “Esc” key is pressed. It is a flowchart which shows the modification of the process of FIG. It is a figure for demonstrating the modification which performs a masking process to transition screen data.

  Hereinafter, an embodiment will be described in detail with reference to FIGS. FIG. 1 schematically shows the configuration of a medical office system 100 according to an embodiment.

  As shown in FIG. 1, the medical office system 100 includes a client terminal 70, a medical server 10, an electronic medical record server 20, and a data processing server 30 as a screen transition information output device. Each device provided in the medical office system 100 is connected to a network 80 such as the Internet or a LAN (Local Area Network).

  The client terminal 70 is an information processing terminal such as a PC (Personal Computer) used by a member of the medical department (medical office worker) or the like. In the following, the user of the client terminal 70 is referred to as a user. FIG. 2A shows the hardware configuration of the client terminal 70. As shown in FIG. 2A, the client terminal 70 includes a CPU (Central Processing Unit) 190, a ROM (Read Only Memory) 192, a RAM (Random Access Memory) 194, and a storage unit (here, an HDD (Hard Disk Drive)). 196, a network interface 197, a display unit 193, an input unit 195, a portable storage medium drive 199 that can read information stored in the portable storage medium 191, and the like. Each component of the client terminal 70 is connected to the bus 198. The display unit 193 includes a liquid crystal display and the like, and the input unit 195 includes a keyboard and a mouse. The client terminal 70 receives input from the user via the input unit 195 and executes various processes according to the input. In addition, the client terminal 70 displays various screens and various information on the display unit 193 in cooperation with each server connected to the network 80.

  The medical server 10 communicates with the client terminal 70 and provides various screens related to medical office work to the client terminal 70 according to user operations, and collects and stores information input on the provided screens. . That is, the client terminal 70 can use a medical system provided by the medical server 10. The medical server 10 acquires user operation history information (log) for the medical system and transmits it to the data processing server 30. FIG. 2B shows the hardware configuration of the medical server 10. As shown in FIG. 2B, the medical server 10 includes a CPU 90, a ROM 92, a RAM 94, a storage unit (HDD) 96, a network interface 97, a portable storage medium drive 99, and the like. Each component of the medical server 10 is connected to the bus 98.

  The electronic medical record server 20 communicates with the client terminal 70 to provide various screens related to the electronic medical record to the client terminal 70 in accordance with a user's operation, and collect and store information input on the provided screen. To do. That is, the client terminal 70 can use the electronic medical record system provided by the electronic medical record server 20. The electronic medical record server 20 acquires history information (log) of user operations on the electronic medical record system and transmits it to the data processing server 30. Similar to the medical server 10, the electronic medical record server 20 has a hardware configuration as shown in FIG.

  The data processing server 30 communicates with the medical server 10 and the electronic medical record server 20 to acquire user operation history information, and executes various processes based on the acquired information. Similar to the medical server 10 and the electronic medical record server 20, the data processing server 30 has a hardware configuration as shown in FIG. In the data processing server 30, a program (including a screen transition information output program) stored in the ROM 92 or the HDD 96, or a program (a screen transition information output program is read from the portable storage medium 91 by the portable storage medium drive 99). 3), each unit functions as shown in FIG. FIG. 3 also shows various DBs and tables stored in the HDD 96 of the data processing server 30.

  FIG. 3 shows a functional block diagram of the data processing server 30. As shown in FIG. 3, in the data processing server 30, the CPU 90 executes a program, whereby an operation history acquisition unit 42, a return data acquisition unit 44, an operation pattern list generation unit 46, a selection reception unit 48, screen transition data. It functions as the generation unit 50 and the screen transition data output unit 52.

  The operation history acquisition unit 42 acquires user operation history information (log) from the medical server 10 or the electronic medical record server 20 and stores it in the operation history DB 60. The operation history DB 60 has a data structure as shown in FIG. 5B and the details will be described later.

  The user operates the client terminal 70, creates an electronic receipt using the medical system, and transmits the created electronic receipt to the payment examination organization via the network 80. Thereafter, the return data acquisition unit 44 acquires the return data transmitted from the examination payment organization (payment fund) via the network 80 and stores it in the return DB 62. FIG. 4A shows an example of an electronic reception. In the example of FIG. 4A, two electron receptors (A, B) are displayed. When the examination / payment institution determines that the electronic receipt is incomplete, return data is transmitted as result information from the examination / payment institution. FIG. 4B shows an example of return data. In the return data of FIG. 4B, it is shown that the electronic receipt B of FIG. The return DB 62 stores return data as shown in FIG. 4B acquired by the return data acquisition unit 44. Note that since the return data includes patient information such as a patient ID and processing date information, it is possible to confirm which operation of the user is incomplete. That is, it can be said that the return DB 62 is a storage unit that stores return data that associates a series of operations with result information indicating that processing by the series of operations is abnormal.

  Returning to FIG. 3, the operation pattern list generation unit 46 divides the operation history information stored in the operation history DB 60 into a series of operations as processing units, and data divided for each processing unit (operation pattern data). Among these, operation pattern data not corresponding to the return data stored in the return DB 62, that is, operation pattern data corresponding to normal processing is extracted. Then, the operation pattern list generation unit 46 adds the extracted operation pattern information to the operation pattern list stored in the operation pattern table 64. The operation pattern list is tabular data as shown in FIG. When there is a display request from the user at the client terminal 70, the operation pattern list generation unit 46 transmits the operation pattern list to the client terminal 70 and displays it on the display unit 193.

  The selection reception unit 48 transmits information on the selected operation pattern to the screen transition data generation unit 50 when the client terminal 70 receives that the user has selected an operation pattern from the operation pattern list.

  When the screen transition data generation unit 50 receives the information on the operation pattern selected by the user, the screen transition data generation unit 50 extracts the operation history information corresponding to the selected operation pattern from the operation history DB 60 and the screen data corresponding to the extracted history information. Is obtained from the screen DB 66. The screen DB 66 stores data of screens (screens transmitted to the client terminal 70) used by the medical server 10 and the electronic medical record server 20. Then, the screen transition data generation unit 50 generates screen transition data using the acquired screen data and the extracted history information. Here, the screen transition data is data indicating screen transitions (transitions) as shown in FIGS.

  The screen transition data output unit 52 transmits the screen transition data generated by the screen transition data generation unit 50 to the client terminal 70 and displays it on the display unit 193 of the client terminal 70.

(About processing)
Next, processing by the data processing server 30 will be described in detail. In the following, an operation history acquisition process executed by the operation history acquisition unit 42, an operation pattern list generation process executed by the operation pattern list generation unit 46, a selection reception unit 48, a screen transition data generation unit 50, and Screen transition data generation / output processing executed by the screen transition data output unit 52 will be described.

(Operation history acquisition process)
Hereinafter, the operation history acquisition process executed by the operation history acquisition unit 42 will be described. The operation history acquisition unit 42 acquires information on the screen displayed on the display unit 193 of the client terminal 70 and information input on the screen by the user from the medical server 10 and the electronic medical record server 20 and stores them in the operation history DB 60. To do. In the following, transition of the screen displayed on the display unit 193 of the client terminal 70 and an example of user input contents will be described, and a specific example of data stored in the operation history DB 60 will be described.

  First, when the user turns on the power of the client terminal 70, the medical server 10 displays the initial screen (screen A) of the medical system on the display unit 193 of the client terminal 70, as shown in FIG. In this screen A, it is assumed that the user inputs his / her operator number “010” in the operator number column and presses the “OK” button. The operation history information at this time is stored in the operation history DB 60 as shown in FIG. Here, as shown in FIG. 5B, the operation history DB 60 includes “serial number”, “processing date”, “processing time”, “terminal name”, “user”, “system”, “screen name”. , “Input / output”, “input / output information”, “button name”, “operation”, and “patient ID” fields. The serial number field stores the serial number of the operation history information, and the “processing date” and “processing time” fields store date and time information indicating the timing of screen display and the timing of user operations. The The name of the client terminal 70 is stored in the “terminal name” field, and the user information is stored in the “user” field. The “system” field stores which system such as a medical system or an electronic medical record system is used. In this embodiment, “X-W” is stored when the medical system is used, and “EGMAIN” is stored when the electronic medical record system is used. In the “screen name” field, the name of the screen displayed on the display unit 193 is stored. The “input / output” field stores “OUT” in the case of display (output) on the display unit 193, and “IN” in the case of input to the screen by the user. In the “input / output information” field, information input by the user and information output by the medical server 10 or the electronic medical record server 20 are stored. Information on the button pressed by the user is stored in the “button name” field, information on the operation contents of the user is stored in the “operation” field, and which patient is related in the “patient ID” field. Information indicating whether the operation is an input operation is stored.

  Note that the serial number “001” in FIG. 5B is a history related to the display of the screen A, the serial number “002” is a history related to the input to the operator number column of the screen A, and the serial number “003”. "Is a history related to pressing of the" OK "button on screen A.

  When the “OK” button is pressed on the screen A, the medical server 10 displays the screen B as shown in FIG. 6A on the display unit 193 of the client terminal 70 (the serial number “ 004 "). In this case, if the user clicks the “window service” button, the history information of the serial number “005” is stored in the operation history DB 60 as shown in FIG. In the operation history DB 60, the “window service” button is indicated as “Button1”.

  When the “window service” button is clicked on the screen B, the medical server 10 displays a screen C as shown in FIG. 7A on the display unit 193 of the client terminal 70 (FIG. 7B). No. “006”). In this case, if the user clicks the “medical accounting” button, the history information of the serial number “007” is stored in the operation history DB 60 as shown in FIG. In the operation history DB 60, the “medical accounting” button is indicated as “Button 21”.

  When the “medical accounting” button is pressed on the screen C, the medical server 10 displays a screen D as shown in FIG. 8A on the display unit 193 of the client terminal 70 (sequence number in FIG. 8B). (See “008”). In this case, if the user inputs “280720” in the column of medical treatment date on screen D, inputs “P001” in the column of patient number, and presses the “Enter” key on the keyboard, the operation history DB 60 stores As shown in FIG. 8B, history information of serial numbers “009” and “010” is stored. When “P001” is input in the patient number column of the screen D, the input “P001” is stored in the “patient ID” field of the operation history DB 60.

  When the “Enter” key is pressed while the screen D is displayed, the medical server 10 displays a screen E as shown in FIG. 9A on the display unit 193 of the client terminal 70 (FIG. 9B). ) (See “011”). In this case, if the user inputs “Department” or “Insurance SEQ” on the screen E and clicks the “OK” button, the operation history DB 60 stores a serial number as shown in FIG. 9B. History information “012” to “017” is stored.

  When the “OK” button is clicked while the screen E is displayed, the medical server 10 reflects the information obtained based on the information input on the screen E, as shown in FIG. The screen D is displayed on the display unit 193 of the client terminal 70 (see the serial number “018” in FIG. 10B).

  Here, the user wants to confirm the contents of the electronic medical chart system (confirms the numerical value of the patient's examination results), and in order to change the system, the shortcut keys for displaying the desktop screen ("Alt" key on the keyboard and " Suppose you press the Tab key. In this case, the history information of the serial number “019” shown in FIG. Then, when the shortcut key is pressed, the desktop screen shown in FIG. 11A is displayed.

  When the user clicks the “electronic medical record” icon on the desktop screen (see the serial number “020” in FIG. 11B), the electronic medical record server 20 displays the screen F as shown in FIG. Are displayed on the display unit 193 (see the serial number “021” in FIG. 12B). In this case, if the user inputs “User ID” and “Password” on the screen F and clicks the “Start medical treatment” button, the operation history DB 60 stores the operation history DB 60 as shown in FIG. , History information of serial numbers “022” and “023” is stored. In the operation history DB 60, the “start medical treatment” button is indicated as “ButtonA1”.

  When the “Start Medical Treatment” button is pressed on the screen F, the electronic medical record server 20 displays a screen G as shown in FIG. 13A on the display unit 193 of the client terminal 70 (FIG. 13B). (See serial number “024”). In this case, if the user inputs “P001” in the column of patient ID on the screen G and presses the “Enter” key on the keyboard, the serial number in the operation history DB 60 is as shown in FIG. The history information “025” is stored. When “P001” is input in the patient number column, the input “P001” is stored in the “patient ID” field of the operation history DB 60.

  When the “Enter” key is pressed while the screen G is displayed, the electronic medical record server 20 displays a screen H as shown in FIG. 14A on the display unit 193 of the client terminal 70 (FIG. 14 ( b) serial number “026”). In this case, if the user clicks the “reference only” button on the screen H, the history information of the serial number “027” is stored in the operation history DB 60 as shown in FIG. In the operation history DB 60, the “reference only” button is indicated as “Button Sansho”.

  Thereafter, various screens are displayed according to the user's input, and on the screen Y shown in FIG. 15 (a), the user confirms the numerical value of the test result of the patient, and when the user refrains, the screen Y is displayed. In this state, the “Alt” key and the “Tab” key are pressed simultaneously (see the serial number “041” in FIG. 15B). In this case, the medical server 10 displays the screen D as illustrated in FIG. 16A on the display unit 193 of the client terminal 70 again. Then, when the user inputs the numerical value of the patient's examination result that he / she has saved on the screen D, history information such as serial numbers “042” to “045”... In FIG. Stored.

  When the user presses the “Enter” key on the screen D (see the serial number “060” in FIG. 16B), the medical server 10 displays a screen Z (confirmation screen) as shown in FIG. The information is displayed on the display unit 193 of the client terminal 70. The user checks the screen Z, and if there is no problem, presses the “Pause” key on the keyboard (see the serial number “063” in FIG. 17B). As a result, the medical server 10 displays a screen D as shown in FIG. 18A on the display unit 193 of the client terminal 70. At this stage, the input process of information related to the patient “P001” is completed. Therefore, as shown in the serial number “064” in FIG. 18B, the patient ID “P001” is displayed in the “patient ID” field. "Is not stored.

  In the present embodiment, as described above, after the ID of a patient (for example, P001) is stored in the “patient ID” field of the operation history DB 60, the process is performed until another patient ID is stored. The broken operation is a series of operations for inputting information related to a certain patient (for example, P001), and can be said to be one operation pattern.

  As described above, the operation history DB 60 appropriately stores user operation history information.

(Operation pattern list generation processing)
Next, the operation pattern list generation processing will be described in detail with reference to the other drawings as appropriate along the flowchart of FIG.

  The process of FIG. 19 is a process in which the operation pattern list generation unit 46 generates an operation pattern list. The operation pattern list is a table that displays a list of information on each operation pattern obtained from the operation history DB 60. The process in FIG. 19 is assumed to be executed at a timing (for example, once a month) after the return data is sent from the examination / payment institution.

  In the process of FIG. 19, first, in step S10, the operation pattern list generation unit 46 divides the data obtained within a predetermined period (for example, for one month) stored in the operation history DB 60 for each processing unit. , Each is an operation pattern. Specifically, the operation pattern list generation unit 46 pays attention to the patient ID of the data of the operation history DB 60, and history information from when the first patient ID is stored until another patient ID is stored. Is a processing unit, and the data is divided into operation patterns.

  Next, in step S12, the operation pattern list generation unit 46 specifies data of one operation pattern. For example, operation pattern data having the earliest processing time in a predetermined period is specified.

  Next, in step S14, the operation pattern list generation unit 46 determines whether or not the specified data is data corresponding to the return data. Specifically, the operation pattern list generation unit 46 refers to the return DB 62 and determines whether there is return data that matches the patient ID and the processing date of the data of the specified operation pattern. If the determination in step S14 is affirmed, the process proceeds to step S18. If the determination is negative, the process proceeds to step S16.

  In step S <b> 16, the operation pattern list generation unit 46 adds information on the specified operation pattern to the operation pattern list stored in the operation pattern table 64. Here, the operation pattern list has a data structure as shown in FIG. Specifically, as shown in FIG. 20, the operation pattern list includes “processing date”, “processing time”, “terminal name”, “user”, “system”, “patient ID”, “disease name”, It has each column of "diagnosis act". Each column of the operation pattern list stores information based on the specified operation pattern data. Note that the columns provided in the operation pattern list are not limited to the columns illustrated in FIG. 20, but other columns may be provided, or some of the columns in FIG. 20 may be omitted. After the process of step S16 is performed, the process proceeds to step S18.

  After the determination in step S14 is affirmed, or after the processing in step S16 is performed, when the process proceeds to step S18, the operation pattern list generation unit 46 performs all operations within a predetermined period stored in the operation history DB 60. It is determined whether or not a pattern is specified. If the determination in step S18 is negative, the process returns to step S12, and the processes and determinations in steps S12 to S18 are repeated. As a result, of the operation patterns extracted from the operation history DB 60, information on operation patterns corresponding to normal processing that does not correspond to the return data is stored in the operation pattern list. On the other hand, if the determination in step S18 is affirmative, the entire process of FIG.

(Screen transition data generation / output processing)
Next, the screen transition data generation / output process will be described in detail along the flowchart of FIG. 21 with appropriate reference to other drawings. The process of FIG. 21 is a process in which the data processing server 30 creates and outputs screen transition data when the user needs screen transition data to create an operation manual.

  In the process of FIG. 21, first, in step S30, the operation pattern list generation unit 46 determines whether or not there has been a display request for an operation pattern list. That is, when the selection receiving unit 48 receives from the client terminal 70 information that the user has input a command or the like for displaying an operation pattern list via the input unit 195, the determination in step S30 is affirmed.

  When the determination in step S30 is affirmed and the process proceeds to step S32, the operation pattern list generation unit 46 reads the operation pattern list from the operation pattern table 64, transmits it to the client terminal 70, and displays it on the display unit 193.

  Next, in step S34, the selection receiving unit 48 waits until an operation pattern is selected. When the selection receiving unit 48 receives information from the client terminal 70 that the user has selected one operation pattern from the operation pattern list, the selection receiving unit 48 proceeds to step S36.

  In step S36, the screen transition data generation unit 50 extracts data from the operation history DB 60 based on the selected operation pattern. In this case, for example, with reference to the patient ID and the processing date of the selected operation pattern, another patient ID appears from the data in which the patient ID of the selected operation pattern first appears among the data of the same processing date. Extract the data until

  Next, in step S38, the screen transition data generation unit 50 generates screen transition data based on the extracted data. In this case, the screen transition data generation unit 50 acquires the screen data from the screen DB 66 based on the extracted data, and adds information input by the user or automatically input information to the screen data. 22 and FIG. 23, screen transition data arranged in the order in which screen data is output is generated.

  Next, in step S <b> 40, the screen transition data output unit 52 transmits the generated screen transition data to the client terminal 70 and displays it on the display unit 193. The user can create a manual by processing the displayed screen transition data. In this case, it is not necessary for the user to actually operate and take a hard copy of the screen or the like, so that the user can easily create a manual. In addition, after the process of step S40 is complete | finished, all the processes of FIG. 21 are complete | finished.

  As is clear from the above description, the operation pattern list generation unit 46 of this embodiment is an example of a display unit that extracts and displays operation patterns corresponding to normal processing. Further, the screen transition data generation unit 50 and the screen transition data output unit 52 implement a function as an output unit that outputs screen transition data corresponding to the selected operation pattern.

  As described above in detail, according to the present embodiment, the operation pattern list generation unit 46 stores return data from the operation history DB 60 in which history information of a series of operations acquired by the operation history acquisition unit 42 is stored. By referring to the return DB 62, an operation pattern corresponding to normal processing is extracted (S10 to S16) and displayed (S32). When one of the displayed selection pattern lists is selected (S34: Yes), the screen transition data generation unit 50 generates screen transition data corresponding to the selected series of operations (S36, S38). The screen transition data output unit 52 outputs screen transition data (S40). Thereby, in this embodiment, since the selection pattern list in which the operation pattern for the normal process is displayed can be displayed and the screen transition data corresponding to the operation pattern selected in the selection pattern list can be output, the user can The screen transition data corresponding to normal processing can be obtained without taking a hard copy of the screen when the operation is actually performed. Therefore, the user can easily create an operation manual without taking time and effort. In addition, since screen transition data is generated based on the history information of actual operations, it is more realistic and practical than a manual created by a person without specialized medical knowledge, such as a system developer. A manual can be created. Further, as in the present embodiment, even when a plurality of systems are operated when a user performs input related to a patient, it is possible to create manuals regarding the operation of the plurality of systems.

  In this embodiment, the operation while inputting information about the same patient is a series of operations (processing units). Therefore, screen transition data in an appropriate range necessary for manual creation is generated. Can be output.

  In the above-described embodiment, the case where data in which screens are arranged in the output order is generated as screen transition data has been described. In addition to this, for example, as shown in FIG. Information on buttons and pressed keys may be displayed in an identifiable state. In this case, the screen transition data generation unit 50 can acquire information on buttons and keys operated by the user from the operation history DB 60 and include the information in the screen transition data. Note that the screen transition data generation unit 50 may highlight and display the button clicked by the user or the field in which the character is input on each screen displayed in the screen transition data. As described above, by outputting the button pressed at the time of the screen transition so as to be identifiable, the user can easily create a manual.

  In the above embodiment, the user may perform a return operation. More specifically, the user is performing a process (operation) related to a patient, but may cancel all the operations related to a patient by pressing a cancel key (for example, the “Esc” key) on the way. . In such a case, it is only necessary to discard from the operation history DB 60 all the information on the operations performed until the “Esc” key is pressed among the operations related to a certain patient. For example, when the user is performing an operation related to the patient “P001” as in the operation history DB 60 illustrated in FIG. 25, the user presses the “Esc” key as illustrated by the serial number “012”. In this case, all the operations related to the same patient “P001” (serial numbers “009” to “012”) are discarded from the serial number “012”. Thereby, it is possible to prevent generation of inappropriate screen transition data including the discarded operation content.

  In the above-described embodiment, a case has been described in which a normally processed operation pattern is added to the operation pattern list. However, the present invention is not limited to this, and an operation pattern that has not been normally processed (corresponding to return data) You may add it to the list. In this case, it is preferable to display the operation pattern processed normally and the operation pattern not processed normally in a recognizable state. For example, it is possible to change the character color of an operation that has been processed normally and an operation that has not been processed normally, a different mark to be added, or a separate list. FIG. 26 is a flowchart showing the processing when the list is divided separately. In the processing of FIG. 26, the same processing as in FIG. 19 is executed from step S10 to S14. If the determination in step S14 is negative, that is, if the specified data is not data corresponding to the return data, the process proceeds to step S16A, and the operation pattern list generation unit 46 determines the specified operation pattern. Add information to the normal operation pattern list. On the other hand, if the determination in step S14 is affirmative, that is, if the specified data is data corresponding to the return data, the process proceeds to step S16B, and the operation pattern list generation unit 46 determines the specified operation pattern. Information is added to an abnormal operation pattern list different from the normal operation pattern list. And after the process of step S16A or S16B is performed, it transfers to step S18. When the process of FIG. 26 is performed, the selection reception unit 48 transmits both the normal operation pattern list and the abnormal operation pattern list to the client terminal 70 and displays them on the display unit 193 in step S32 of FIG. . In this case, the user can create a document (manual) about a bad operation example by selecting an operation pattern from the abnormal operation pattern list.

  In the above embodiment, when generating the screen transition data, the personal information may be masked. In this case, the screen transition data generation unit 50 acquires personal information corresponding to the patient ID from a patient DB or the like (not shown). Then, the screen transition data generation unit 50 performs character recognition in the generated screen transition data. As a result, when the acquired personal information is included in the screen transition data, a masking process is performed on the personal information. do it. FIG. 27 shows an example of a screen on which the name and date of birth are masked as personal information. By performing the masking process in this way, personal information can be protected. Not only the masking process, but the screen transition data generation unit 50 may not display the personal information on the screen when generating the screen transition data.

  In addition, although the said embodiment demonstrated the case where screen transition data were produced | generated based on the log | history information of operation in a medical office system, it is not restricted to this. That is, based on operation history information in systems in other fields (for example, office systems for public institutions, systems for financial institutions, office systems for educational institutions such as schools), screen transition data is obtained in the same manner as in the above embodiment. It may be generated.

  In the above embodiment, the case has been described in which the data processing server 30 collects operation history information and executes the above-described processing based on the history information. However, the present invention is not limited to this. For example, instead of the data processing server 30, a DB server is provided on the network 80, history information (log) and return data are collected in the DB server, and other terminals (for example, the client terminal 70) perform the above-described processing (operations). Pattern list generation processing and screen transition data generation / output processing) may be executed.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the processing apparatus should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium (except for a carrier wave).

  When the program is distributed, for example, it is sold in the form of a portable recording medium such as a DVD (Digital Versatile Disc) or a CD-ROM (Compact Disc Read Only Memory) on which the program is recorded. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. Further, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

  The above-described embodiment is an example of a preferred embodiment of the present invention. However, the present invention is not limited to this, and various modifications can be made without departing from the scope of the present invention.

In addition, the following additional remarks are disclosed regarding description of the above embodiment.
(Supplementary note 1) With reference to the storage unit in which the history information of a series of operations and the result information indicating that the processing by the series of operations is normal or abnormal, the history information corresponding to the normal processing is Extract and display,
Upon receiving a selection of any of the displayed history information, the screen transition information corresponding to a series of operations included in the selected history information is output.
Screen transition information output program for causing a computer to execute processing.
(Supplementary Note 2) In the process of extracting and displaying,
Further extract history information corresponding to abnormal processing,
Display the history information corresponding to the extracted abnormal process and the history information corresponding to the normal process in an identifiable state;
The screen transition information output program according to Supplementary Note 1, wherein
(Supplementary note 3) The screen transition information output program according to supplementary note 1 or 2, wherein in the process of outputting the information of the screen transition, the button pressed at the time of the screen transition is output in an identifiable manner.
(Supplementary note 4) The screen transition information output program according to any one of supplementary notes 1 to 3, wherein the series of operations is an operation while inputting information on the same subject.
(Supplementary note 5) The screen transition information output program according to any one of supplementary notes 1 to 4, wherein in the process of outputting the information of the screen transition, a masking process is performed on the personal information included in the screen.
(Supplementary Note 6) With reference to the storage unit in which the history information of a series of operations and the result information indicating that the processing by the series of operations is normal or abnormal, the history information corresponding to the normal processing is Extract and display,
Upon receiving a selection of any of the displayed history information, the screen transition information corresponding to a series of operations included in the selected history information is output.
A screen transition information output method, wherein the computer executes the process.
(Supplementary Note 7) Referring to a storage unit in which history information of a series of operations and result information indicating that processing by the series of operations is normal or abnormal is associated, history information corresponding to normal processing is obtained. A display for extracting and displaying;
When receiving selection of any of the displayed history information, an output unit that outputs information of screen transition corresponding to a series of operations included in the selected history information;
A screen transition information output device comprising:
(Appendix 8) The display unit
Further extract history information corresponding to abnormal processing,
Display the history information corresponding to the extracted abnormal process and the history information corresponding to the normal process in an identifiable state;
The screen transition information output device according to appendix 7, which is characterized in that.
(Supplementary note 9) The screen transition information output device according to supplementary note 7 or 8, wherein the output unit outputs the button pressed in the screen transition in an identifiable manner.
(Supplementary note 10) The screen transition information output device according to any one of Supplementary notes 7 to 9, wherein the series of operations is an operation while inputting information on the same subject.
(Additional remark 11) The said output part performs a masking process to the personal information contained in a screen, The screen transition information output device in any one of Additional remarks 7-10 characterized by the above-mentioned.

30 Data processing server (screen transition information output device)
46 Operation pattern list generator (display unit)
50 Screen transition data generation part (part of output part)
52 Screen transition data output part (part of output part)
60 Operation history DB (log)
62 Return DB (storage unit)

Claims (7)

The history information corresponding to the normal process is extracted and displayed by referring to the storage unit in which the history information of the series of operations and the result information indicating that the process by the series of operations is normal or abnormal are associated. And
Upon receiving a selection of any of the displayed history information, the screen transition information corresponding to a series of operations included in the selected history information is output.
Screen transition information output program for causing a computer to execute processing. In the process of extracting and displaying,
Further extract history information corresponding to abnormal processing,
Display the history information corresponding to the extracted abnormal process and the history information corresponding to the normal process in an identifiable state;
The screen transition information output program according to claim 1.   The screen transition information output program according to claim 1 or 2, wherein in the process of outputting the information of the screen transition, the button pressed at the time of the screen transition is output so as to be identifiable.   The screen transition information output program according to any one of claims 1 to 3, wherein the series of operations are operations while inputting information on the same subject.   5. The screen transition information output program according to claim 1, wherein in the process of outputting the screen transition information, a masking process is performed on the personal information included in the screen. The history information corresponding to the normal process is extracted and displayed by referring to the storage unit in which the history information of the series of operations and the result information indicating that the process by the series of operations is normal or abnormal are associated. And
Upon receiving a selection of any of the displayed history information, the screen transition information corresponding to a series of operations included in the selected history information is output.
A screen transition information output method, wherein the computer executes the process. The history information corresponding to the normal process is extracted and displayed by referring to the storage unit in which the history information of the series of operations and the result information indicating that the process by the series of operations is normal or abnormal are associated. A display unit to
When receiving selection of any of the displayed history information, an output unit that outputs information of screen transition corresponding to a series of operations included in the selected history information;
A screen transition information output device comprising:

Images