JP7046526B2 - Medical support systems, medical support methods and programs - Google Patents

Description

The techniques disclosed herein relate to medical support systems, medical support methods and programs.

When the display means displays the information input to the electronic medical record, the information may not fit in the display area because the number of characters is larger than that in the display area.

When the number of characters is large with respect to the display area, a technique for reducing and displaying the characters themselves is known (Patent Document 1).

JP-A-2015-162190

However, the above technique has a problem that the visibility of the character is lowered because the character itself becomes small. That is, the above technique has a problem that information cannot be displayed properly.

One of the purposes of the technique disclosed in the present specification is to appropriately display the information input to the electronic medical record or the like.

Not limited to the above-mentioned purpose, it is also an action and effect derived by each configuration shown in the embodiment for carrying out the invention described later, and it is also another purpose of the present invention to exert an action and effect which cannot be obtained by the conventional technique. It can be positioned as one.

The medical support system disclosed herein is via a conference body information acquisition means for acquiring information about a conference and an input item for inputting information about a patient, which has at least one input item. The information input to the electronic medical record is predetermined for each of the input items according to the electronic medical record information acquisition means for acquiring the information input to the electronic medical record from the electronic medical record for a plurality of patients selected according to the information about the conference and the information about the patient. The input item which is the information acquired by the electronic medical record information acquisition means according to the input template information acquisition means for acquiring the information indicating the attribute to be obtained and the information indicating the attribute acquired by the input template information acquisition means. Information about the plurality of patients acquired by the electronic medical record information acquisition means by a determination means for determining the size of a display area displayed on the screen of the conference and a sort condition determined according to information about the conference. The information acquired by the electronic medical record information acquisition means for the plurality of patients in the order of the sorting means for sorting the patients and the patients sorted by the sorting means is displayed in a list on the screen of the conference, and each of them in the list display. It has a display means for displaying the input item for a patient in a display area having a size determined by the determination means .

According to the disclosed technology, it is possible to appropriately display the information input to the electronic medical record or the like.

It is a figure which shows an example of the whole structure of a conference support system. It is a figure which shows an example of the internal structure of an information processing apparatus. It is a figure which shows an example of the screen of a conference support application. It is a figure which shows an example of a rehabilitation plan template. It is a figure which shows an example of a nutrition instruction template. It is a figure which shows an example of a sample shipping template. It is a figure which shows an example of a data type definition table. It is a figure which shows an example of a medical record article table. It is a figure which shows an example of a patient information table and a staff information table. It is a figure which shows an example of the patient table for a meeting. It is a figure which shows an example of a meeting information table and a meeting body information table. It is a figure which shows an example of the notation used in a flowchart. It is a flowchart which shows an example of the process of creating the HTML DOM of the patient list part. It is a flowchart which shows an example of the process which creates the HTML DOM of a patient line part. It is a flowchart which shows an example of the process of creating the HTML DOM of the patient remarks part. Remarks It is a flowchart which shows an example of the process which creates the HTML DOM of the item part. It is a flowchart which shows an example of the process which creates the DOM for HTML in the case of TEXTAREA. It is a flowchart which shows an example of the process which creates DOM for HTML in other cases. It is a figure which shows the example of the patient line in the case of a rehabilitation plan template. It is a figure which shows the example of the patient line in the case of a nutrition instruction template. It is a figure which shows the example of the patient line in the case of a sample delivery template. It is a figure which shows the flowchart and the example of the sort condition at the time of changing the sort condition. It is a flowchart which shows an example of the processing procedure when it has a personal information protection function. It is a figure which shows the example of the patient line in the case of having a personal information protection function. It is a figure which shows an example of the whole structure when the server function is integrated into one server.

Hereinafter, the medical support system according to the present embodiment will be described with reference to the attached drawings. The configuration shown in the following embodiments is only an example, and the present invention is not limited to the following embodiments. In this embodiment, the conference support system is taken as an example of the medical support system, but the present invention is not limited to this.

<Embodiment 1>
FIG. 1 shows an example of the overall configuration of the conference support system in this embodiment. The conference support system shown in FIG. 1 corresponds to an example of a medical support system. The conference support system includes an electronic medical record server 1, a conference support server 2, a plurality of clients 3 (1 to N), and an in-hospital network 4. Here, the electronic medical record server 1, the conference support server 2, and the plurality of clients 3 (1 to N) are connected to each other so as to be able to communicate with each other via the in-hospital network 4. Although the number of clients 3 is a plurality in FIG. 1, the number of clients 3 may be one.

The electronic medical record server 1 has a memory that functions as a data storage area 11. The data storage area 11 may be, for example, an HDD or an SSD as long as it can store information. Further, the data storage area 11 may be realized by a plurality of memories or the like. The data storage area 11 stores a medical record article table 111, a data type definition table 112, a patient information table 113, a staff information table 114, and an input template HTML 115. In this embodiment, the data storage area 11 holds a plurality of types of input templates HTML.

An example of the chart article table 111 is shown in FIG. The medical record article table 111 contains information on electronic medical records. Specifically, the chart article table 111 includes an article ID, a patient ID, a chart input date and time, a chart content (article content), a template name used for chart input (input template name), and at least one of the input templates. The data (DATA1-6) input to one input item includes the associated information. The medical record article table 111 is not limited to the format shown in FIG.

An example of the data type definition table 112 is shown in FIG. The data type definition table 112 contains attribute information regarding the input items included in the input template. Specifically, the data type definition table 112 is input to the input item type (data type name), information indicating whether or not the end can be omitted when displaying the information input to the input item, and the input item. Information indicating whether the information is personal information, placeholder character string (character string displayed when the user has not entered the input item), maximum number of characters in the input item, and input items can be entered. Contains information associated with the number of characters per line. The data type definition table 111 shows information indicating whether or not the end can be omitted when displaying the information input in the input item, and information indicating whether or not the information input in the input item is personal information. And may not contain at least one of the placeholder strings. That is, the data type definition table 112 is not limited to the format shown in FIG. 7. The numerical values and the like shown in the data type definition table 111 are examples, and other numerical values and the like may be used.

An example of the patient information table 113 is shown in FIG. 9 (a). The patient information table 113 includes information associated with the patient ID, patient name, gender and date of birth. That is, the patient information table 113 includes patient identification information. The patient information table 113 is an example and may include other information or omit some information. That is, the patient information table 113 is not limited to the format shown in FIG. 9A.

An example of the staff information table 114 is shown in FIG. 9 (b). The staff information table 114 includes information associated with a staff ID, a staff name, and a staff occupation. The staff information table 114 is not limited to the format shown in FIG. 9B.

Examples of the input template HTML115 are shown in FIGS. 4 (b), 5 (b) and 6 (b). The input template HTML 115 is a template for inputting to an electronic medical record. By processing each input template HTML by the processor, the input templates shown in FIGS. 4 (a), 5 (a) and 6 (a) are displayed on the display screen. Here, FIGS. 4 (b), 5 (b), and 6 (b) are an input template for a rehabilitation plan, an input template for nutritional guidance, and a template for sample delivery, respectively. The input template HTML 115 is not limited to the above three, and may include other input template HTML. The content of the input template HTML 115 is not limited to FIGS. 4 (b), 5 (b), and 6 (b).

The conference support server 2 has a memory that functions as a data storage area 12. The data storage area 12 may be, for example, an HDD or an SSD as long as it can store information. Further, the data storage area 12 may be realized by a plurality of memories or the like.

The data storage area 12 stores the meeting target patient table 121, the meeting information table 122, the meeting body information 123, the data type definition table 124, the patient information table 125, the staff information table 126, and the input template HTML127. The data type definition table 124, the patient information table 125, the staff information table 126, and the input template HTML 127 are the data type definition table 112, the patient information table 113, the staff information table 114, and the input template HTML 115 held by the electronic medical record server 1. It is a duplicate.

An example of the conference target patient table 121 is shown in FIG. Information on patients targeted at each conference is recorded in the conference target patient table 121 in association with the conference ID. The conference target patient table 121 is a table associated with the conference ID, the patient ID, the input template name, and DATA1-6 showing the data input to the input template.

An example of the conference information table 122 is shown in FIG. 11 (a). The conference information table 122 includes a conference ID, a conference body ID, a conference holding date and time, an extraction date and time, and information associated with the conference participants. The conference information table 122 is not limited to the format shown in FIG. 11A.

An example of the conference body information table 123 is shown in FIG. 11 (b). The conference body information table 123 includes information associated with the conference body ID, the conference name, the periodical holding date and time, and the patient extraction condition. The conference body information table 123 is not limited to the format shown in FIG. 11B.

Here, each of the electronic medical record server 1, the conference support server 2, and the clients 3 (1 to N) is realized by, for example, the information processing apparatus 100 shown in FIG. The information processing device 100 shown in FIG. 2 includes a UI device 101, a CPU 102, a RAM 103, a communication IF 104, a UI display unit 105, a program storage area 106, and a data storage area 107.

The UI device 101 includes at least one such as a touch sensor that detects a position touched by a mouse, a keyboard, a finger, or the like. The UI device 101 is not limited to the above-mentioned device such as a mouse as long as it is used for inputting a user's instruction to the information processing device 100.

The CPU 102 realizes various functions by expanding the program read from the program storage area 106 to the RAM 103. For example, by executing the program by the CPU 102, various controls, calculations, and UI displays in the device can be performed. Two or more CPUs may be provided, or the GPU may be used in place of or in combination with the CPU. That is, various functions are realized by executing a program by one or more processors.

The communication IF 104 is connected to the hospital network 4 and is a communication interface used when acquiring information from the electronic medical record server 1 and the conference support server 2. UI
The display unit 105 is an LED (Light Emitting Diode), a liquid crystal panel, or the like that displays the state of the device or the processing content.

The program storage area 106 and the data storage area 107 are realized by a hard disk, a flash memory, or the like, but do not depend on a specific storage medium.

The user can display and operate the electronic medical record application by accessing the electronic medical record server 1 using the information display clients 3 (1 to N). Similarly, by accessing the conference support server 2, it is possible to display and operate the conference support application.

Next, an example of the screen configuration of the conference support application displayed on the UI display unit 105 of the information processing apparatus 100 will be described with reference to FIG. In this embodiment, the display layout of the application screen is described by HTML (HyperText Markup Language), but the display layout description language is not limited to HTML. That is, it is possible to carry out this embodiment by replacing the attribute name and the element name with other display layout description languages such as XAML (Extensible Application Markup Language).

In FIG. 3, the patient list 201 exists inside the application window 200, and the patient rows 202 (1, 2, ...) Are present inside the patient list 201. At the top of the patient list 201, there are the conference name 203, the date and time 204, the date and time of extraction 205, and the conference participants 206. These screen displays can be changed by the CPU 102 rewriting the HTML DOM (Document Object Model) corresponding to the view of the screen.

The UI display unit 105 of the information processing apparatus 100 can display various input templates possessed by the electronic medical record application. Doctors who use this system can use this input template to input standard medical record articles without hassle. In the present embodiment, the display layout of the input template is described by HTML, but the present invention does not limit the display layout description language to HTML.

An example of the input template will be described with reference to FIGS. 4 to 7.

FIG. 4 shows the screen display and the corresponding HTML in the case of the rehabilitation plan template. As shown in the 14th, 17th, 18th, 21st, 22nd and 25th lines of the input template HTML shown in FIG. 4B, the input item (input element) has a name attribute, a data-type attribute, and a data-quired attribute. Various item attributes are attached.

Here, the name attribute takes a value from DATA1 to DATA6 and is used to distinguish the input information. In this embodiment, the value of the name attribute is set to 6 types, but the value is not limited to this.

The data-type attribute is used to specify what kind of information is input to the input item. In the data-type attribute, the dataType name defined in the data type definition table 112 of FIG. 7 is specified. When the CPU 102 detects the data-type attribute when trying to display the input template on the UI display unit 105, the CPU 102 sets the display attributes of various input items with reference to the data type definition table 112 of FIG. For example, if the dataType name is "DisseaseName" as in the 14-line name of the input template HTML shown in FIG. 4B, the CPU 102 refers to the maximum number of characters in the data type definition table 112 of FIG. 7, and the size of the input element. Set the value of the attribute or maxlength attribute to 10.

The data-required attribute takes a value of "true" or "false" and is used to specify whether or not the input item is a required input item. When the CPU 102 detects the data-required attribute when trying to display this input template on the UI display unit 105, if the attribute value is "true", the background color of the input item is changed and the input is required. Clarify that there is. Further, the CPU 102 checks whether or not all the information of the required input items is input at the time of registering the medical record article.

FIG. 5 shows the screen display and the corresponding HTML in the case of the nutrition guidance template. When the size attribute and maxlength attribute are explicitly described as in the 14th line of the input template HTML shown in FIG. 5 (b), the explicit description is more than the maximum number of characters in the data type definition table of FIG. have priority.

FIG. 6 shows the screen display and the corresponding HTML in the case of the sample shipping template. When the input item is a textarea element as in the 14th line of the input template HTML of FIG. 6B, the CPU 102 refers to the number of characters per line in the data type definition table of FIG. 7 and the width of the element. Set (cols attribute).

Next, the preparation process of the conference will be described with reference to FIGS. 10 and 11. In the conference body information table 123 shown in FIG. 11B, the preparation process of the conference will be described by taking as an example the “rehabilitation planning conference” having the conference body ID of 101. First, a conference having a conference ID of 1 (held at 10:00 on April 18, 2016) is created in the conference information table 122 shown in FIG. 11A according to the regular holding date and time of the conference body information table 123. Next, 30 minutes before the date and time of the meeting, the CPU 102 refers to the chart article table 111 of FIG. 8 and extracts patients that meet the conditions according to the patient extraction conditions of the conference body information table 123. This time, since the extraction condition is "patients who have a medical record article entered in the" rehabilitation plan "template within one week", patients with a patient ID of "123456878" are extracted. Further, the CPU 102 also extracts the input template names and DATA1 to DATA6 recorded in the medical record article (article ID 101) at that time, and records them in the conference target patient table 121 of FIG. A patient with a patient ID of "23456789" (not shown in FIG. 8) is also extracted by the same process, and preparation for a conference with a conference ID of 1 is completed.

In the extraction date and time of the conference information table 122 shown in FIG. 11A, the date and time when the above-mentioned patient extraction was performed is recorded. In the above example, the extraction was performed only once 30 minutes before the conference was held, but it may be configured to perform the extraction multiple times. In this case, the extraction date and time at the time of the last extraction is recorded.

The staff ID of the staff who participated on the day of the conference is recorded in the conference participants in the conference information table 122 shown in FIG. 11 (a). The collection of staff IDs can be carried out by means such as reading the staff ID card using a card reader or the like provided at the entrance of the conference room.

Using the flowcharts of FIGS. 13 to 18, the process in which the CPU 102 creates the HTML DOM of the patient list 201 portion of FIG. 3 will be described. FIG. 12 shows a legend of the notation used in the flowchart. These HTML DOM creation processes are executed by the information processing apparatus 100 of FIG. 2 corresponding to the conference support server 2 of FIG. Specifically, according to the program stored in the program storage area 106, the CPU 102 reads various data stored in the data storage area 107 into the RAM 103, and the result of performing various arithmetic processing is obtained by the UI display unit 105 or the UI display unit 105. It is executed by outputting to the data storage area 107.

"Patient list HtmlDom creation" is started in S100 of FIG. Then, in S101, the CPU 101 acquires the "current conference ID". First, the base div element is created in S102 and substituted into the DOM tree "$ patient list HtmlDom". In S103, the "patient ID" is acquired as a sort condition when selecting a patient in S104. In S104, the CPU 102 selects the target patient of the current conference based on the "current conference ID" acquired in S101 from the conference target patient table 121 of FIG. Then, the selected target patients are assigned to the list "list of patients subject to this meeting" in a state of being sorted by the "patient ID" which is a sort condition. In S105, the CPU 102 repeats the process of S106 for each object "meeting target patient line" in the "current meeting target patient list". In S106, the CPU 102 calls the process of "creating a patient line HtmlDom" described with reference to FIG. 14 with the "meeting target patient line" as an argument, and adds the result to the "$ patient list HtmlDom". Finally, in S107, the CPU 102 outputs "$ patient list HtmlDom", and the patient list 201 in FIG. 3 is rewritten.

The process of "creating a patient line HtmlDom" will be described with reference to FIG. "Patient line HtmlDom creation" is started in S200 of FIG. Then, the CPU 102 acquires the “meeting target patient line” shown in FIG. First, a table element as a base is created in S203 and substituted into the DOM tree "$ patient line HtmlDom". In S204, a text node describing the patient ID is added to "$ patient line HtmlDom". S204 corresponds to generating item 301 of patient row 300 shown in FIG. 19 (a). In S205, the CPU 102 acquires the patient name, gender, and date of birth, which are information not included in the “meeting target patient line”, from the patient information table 125 shown in FIG. 9A using the patient ID as a key. Then, the CPU 102 additionally adds the acquired information to the "$ patient line HtmlDom". This corresponds to generating items 302-304 of patient row 300. In S206, the CPU 102 calls the process of "patient remarks HtmlDom creation" described with reference to FIG. 15 with the "meeting target patient line" as an argument, and adds the result to the "$ patient line HtmlDom". Finally, in S207, the CPU 102 outputs "$ patient line HtmlDom" and is added to "$ patient list HtmlDom" in S107 of FIG.

Here, FIG. 19 is a patient line created when the input template name is "rehabilitation plan", but is created when the input template names are "nutrition guidance" and "sample shipping" in FIGS. 20 and 21. An example of a patient line is shown.

Next, the procedure for creating the remarks item 311-316 included in the remarks 305 of FIG. 19 will be described with reference to FIG. "Patient remarks HtmlDom creation" is started in S300 of FIG. In S301, the CPU 102 acquires the object "meeting target patient line". Further, in S302, the number mark character string is assigned to the associative array "number mark", the constant "maximum number of remarks data" is set, and the constant "maximum number of items per line" is set. It should be noted that the present embodiment can be implemented even if these constant values are changed. The "maximum number of remarks data" and the "maximum number of items per line" are set in advance by the user, for example. Next, in S303, the CPU 102 reads the HTML file of the input template from the input template HTML127 of FIG. 1 by using the “input template name” of the “meeting target patient line”. Next, the CPU 102 parses (converts into a displayable data structure) the HTML file of the input template and assigns it to the DOM tree "$ input template HtmlDom". In S304, the CPU 102 calculates the "number of remarks data" from the number of "name = DATA *" attributes ("*" is an integer) in the input template. As a specific example, the “number of remarks data” is 6 for the rehabilitation plan template of FIG. 4 and the nutrition guidance template of FIG. 5, and the “number of remarks data” is 2 for the sample shipping template of FIG. In S305, a table element as a base is created and substituted into the DOM tree "$ Patient Remarks HtmlDom". The process of S304 corresponds to the generation of remark 305 of FIG. 19 (a). In S306, the CPU 102 executes the processes of S307 and S308 while increasing the variable i from 1 to the “number of remarks data”. In S307, the CPU 102 inserts a line break in "$ patient remarks HtmlDom" according to the "maximum number of items per line". In S308, the CPU 102 adds a numerical mark to the "$ patient remarks HtmlDom", and then performs the process of "remarks item HtmlDom creation" described in FIG. 16 with the "meeting target patient line" and the remarks item index "i" as arguments. Call and add the result to "$ Patient Remarks HtmlDom". Finally, in S309, the CPU 102 outputs "$ patient remarks HtmlDom" and adds it to "$ patient line HtmlDom" in FIG.

In S400 of FIG. 16, the process of "remark item HtmlDom creation" is started. As shown in S308 of FIG. 15, the CPU 102 acquires the object “meeting target patient line” and the remarks item index “i” as inputs. In S402, the input item element in the input template is assigned to the DOM tree "$ elem", and the item data (DATA1-6) of the "meeting target patient line" is assigned to the character string "remark item character string". .. The CPU 102 acquires the information input to each input item of the input template in S400. That is, the CPU 102 corresponds to an example of information acquisition means for acquiring information input to an electronic medical record via an input template having an input item.

In S403, the process is branched to S404 and S405 depending on whether the input item element in the input template is a textarea element or another element. Inside S404 and S405, the CPU 102 creates a DOM tree "$ remarks item HtmlDom" as described with reference to FIGS. 17 and 18. Finally, the CPU 102 outputs the DOM tree "$ remarks item HtmlDom" in S406 and adds it to the "$ patient remarks HtmlDom" in FIG.

In S500 of FIG. 17, "Remarks item HtmlDom creation in the case of TEXTREA" is started. In S501, the CPU 102 attempts to acquire the maxlength attribute representing the maximum number of characters from the input item element in the input template. However, if the maxlength attribute is not defined in the input template, the default "maximum number of characters" according to the dataType name is obtained from the data type definition table 112 shown in FIG. 7 and used as the maxlength value.

In S502, the CPU 102 attempts to acquire the cols attribute representing the number of columns from the input item element in the input template. However, if the cols attribute is not defined, the default "number of characters per line" according to the dataType name is acquired from the data type definition table 112 shown in FIG. 7 and used as the cols value. That is, the CPU 102 corresponds to an example of an attribute acquisition means for acquiring an attribute of "maximum number of characters" or "number of characters per line".

In S503, the CPU 102 attempts to acquire the rows attribute representing the number of lines from the input item element in the input template. However, if the rows attribute is not defined, the value calculated from the maxlength value and the cols value is used as the rows value. For example, the CPU 102 sets the value obtained by dividing the maxlength value by the cols value as the lows value. In S504, the CPU 102 substitutes the textarea element for displaying the "remarks item character string" into the DOM tree "$ remarks item HtmlDom". In S505, the CPU 102 sets the width of the remarks item according to the cols value. However, if the cols value is undefined, the width automatically adjusted to fit the width of the patient line is set. In S506, the CPU 102 sets the height of the remarks item according to the rows value. However, if the rows value is undefined, the CPU 102 sets the height automatically adjusted to match the height of the patient row. In this way, in S505 and 506, the CPU 102 determines the size of the display area of the remarks item. That is, the CPU 102 corresponds to an example of a determination means for determining the size of a display area in which information is displayed.

In S507, the CPU 102 acquires from the data type definition table 112 shown in FIG. 7 whether or not the input item element in the input template is set to be optional at the end, and if it is set to be optional at the end, the CPU 102 is set to be optional at the end. Remarks Set the scroll bar to appear in the item. Specifically, it is displayed as shown in the scroll bar 318 of FIG. 21 (a). If the tail is not set to be optional, the CPU 102 is set not to display the scroll bar in the remarks item. For example, the CPU 102 sets the scroll bar to be erased from the remarks item.

In S600 of FIG. 18, the process of "remark item HtmlDom creation in other cases" is started. In S601, the CPU 102 attempts to acquire the maxlength attribute representing the maximum number of characters from the input item element in the input template. However, if the maxlength attribute is not defined, the CPU 102 obtains the default maximum number of characters according to the dataType name from the data type definition table 112 shown in FIG. 7 and uses it as the maxlength value. In S602, the CPU 102 attempts to acquire the size attribute representing the number of columns of the input item element in the input template. However, if the size attribute is not defined, the CPU 102 uses the maxlength value as the size value. In S603, the CPU 102 assigns an input element for displaying the "remarks item character string" to the DOM tree "$ remarks item HtmlDom". In S604, the CPU 102 sets the width of the remarks item according to the size value. However, if the size value is undefined, the CPU 102 sets the width automatically adjusted to fit the width of the patient line. In S605, when the input item element in the input template is set so that the tail can be omitted, the CPU 102 sets the remarks item to have the trailing omission symbol "...". Specifically, it is displayed as shown by the trailing abbreviation symbol 317 in FIG. 20 (a).

By the above processing, the remark item 311-316 included in the remark 305 is generated, and as a result, the patient line as shown in FIG. 19A is generated. FIG. 19B is the HTML corresponding to the patient row generated by the above process. In addition, the patient rows shown in FIGS. 20 (a) and 21 (a) are also created by the above processing. Here, the HTML shown in FIGS. 20 (b) and 21 (b) is the HTML corresponding to the patient row shown in FIGS. 20 (a) and 21 (a). As can be seen by comparing FIGS. 19 (a), 20 (a), and 21 (a), the arrangement of a plurality of display areas in which the remarks are displayed is determined according to the type of the input template. As described above, in the present embodiment, the display layout of the patient list displayed at the conference is changed according to various attributes of the input item elements in the input template used at the time of chart input. Specifically, the number of remarks items and the remarks item layout of the patient line are changed. This makes it possible to prevent the character string in which important information is written from being missing or difficult to see. Specifically, since the end cannot be omitted according to the type of information input in the data type definition table 112 shown in FIG. 7, it is necessary to prevent the character string in which important information is written from being omitted in the middle. Can be done.

Moreover, even if the number of input templates increases, the display layout of the patient list is automatically generated, so that the user's effort does not increase.

<Embodiment 2>
As another embodiment, in order to change the sort condition of the patient list according to the input template, S103 in FIG. 13 is replaced with S103_0 to S103_4 in FIG. 22 (a). By replacing them in this way, it is possible to change the sort condition according to the "data-required" attribute of the input item in the input template.

Specifically, as shown in FIG. 22B, the sorting conditions are different for each input template.

In S103_1 of FIG. 22A, the CPU 102 selects the input template names of all the patient lines to be displayed in this conference, and substitutes the ones without duplication into the “input template name array”. Next, in S103_2, the CPU 102 determines whether or not only one input template is used. If there is not only one, the process proceeds to "No", and in S103_0, the CPU 102 substitutes the "patient ID" into the "sort condition" as in the first embodiment. On the other hand, if only one input template is used, the sort condition can be changed according to the input template, so proceed to "Yes". In S103_3, the CPU 102 reads the HTML file of the input template from the input template HTML127 of FIG. 1 by using the “input template name array [0]”. Next, the CPU 102 parses the HTML file of the input template and assigns it to the DOM tree "$ input template HtmlDom". In S103_4, the CPU 102 first selects an input item element having "data-required = true" from the input template, and assigns the name attribute value of that element to the "item name array". Next, the CPU 102 omits duplicate items in the "item name array" and adds "patient ID" as a final sort condition. Since all patient IDs are different, they are added at the end of the sort condition in order to prevent the sort order from becoming undefined.

Generally, in medical conferences, patients are often sorted by items that are required to be entered and the meeting is proceeded in order, so it is possible to efficiently proceed with the meeting by automatically sorting by the required items. It is possible.

<Embodiment 3>
As yet another embodiment, there is an embodiment in which a process for protecting personal information is inserted between S402 and S403 in FIG. 16 and modified as shown in FIG. 23. In the newly added process S703, the CPU 102 determines whether or not the data item corresponds to the personal information by referring to the datatype name and the personal information column of the data type definition table 112. Furthermore, if it is personal information, it is determined whether or not the student is participating in the conference participants. Then, the CPU 102 masks the remarks item character string with "*" when a student is participating. This makes it possible to prevent personal information from being displayed. The characters used as the masking method are not limited to the above example. Further, another method may be used as long as the information can be concealed.

For example, the conference participants whose conference ID is 11 in the conference information table 122 shown in FIG. 11A include students whose staff ID is “9876”. Since this conference is a rehabilitation plan conference with a conference body ID of 101, an example of a patient line generated when using the rehabilitation plan template is shown in FIG. In the data type definition table 112 of FIG. 7, since the data item whose dataType name is "PersonName" is defined as personal information, the patient name and the cooperating relative name are masked with "*" in the screen display of FIG. 24 (a). Has been done.

In this embodiment, the judgment is made based on whether or not the student is participating, but it is also possible to make a judgment based on other occupations. In addition to masking with "*", it is also possible to prevent personal information from being displayed by emptying the remarks item character string.

<Embodiment 4>
As another embodiment, as shown in FIG. 25, the conference support function is mounted on the electronic medical record server and integrated into one server. In this case, it is not necessary to duplicate the data type definition table 515, the patient basic information table 516, the staff basic information table 517, and the input template HTML 518 and keep them separately.

<Other embodiments>
Although examples of embodiments have been described in detail above, the present invention can be implemented as, for example, a system, an apparatus, a method, a program, a recording medium (storage medium), or the like. Specifically, it may be applied to a system composed of a plurality of devices (for example, a host computer, an interface device, an image pickup device, a Web application, etc.), or may be applied to a device consisting of one device. good.

Needless to say, the object of the present invention is achieved by doing the following. That is, a recording medium (or storage medium) in which a program code (computer program) of software that realizes the functions of the above-described embodiment is recorded is supplied to the system or device. Needless to say, the storage medium is a computer-readable storage medium. Then, the computer (or CPU or MPU) of the system or device reads and executes the program code stored in the recording medium. In this case, the program code itself read from the recording medium realizes the function of the above-described embodiment, and the recording medium on which the program code is recorded constitutes the present invention.

Although the preferred embodiments of the present invention have been described in detail above, the present invention is not limited to the specific embodiment, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed.

Claims (14)

Meeting body information acquisition means to acquire information about the conference,
An input item for inputting information about a patient, the information input to an electronic medical record via an input template having at least one input item, for a plurality of patients selected according to the information about the conference. Electronic medical record information acquisition means acquired from electronic medical records and
An input template information acquisition means for acquiring information indicating an attribute predetermined for each input item according to the information about the patient, and an input template information acquisition means.
The size of the display area in which the input item, which is the information acquired by the electronic medical record information acquisition means, is displayed on the screen of the conference according to the information indicating the attribute acquired by the input template information acquisition means. The decision-making means to decide,
A sorting means for sorting information about the plurality of patients acquired by the electronic medical record information acquisition means according to a sorting condition determined according to the information regarding the conference, and a sorting means.
The information acquired by the electronic medical record information acquisition means for the plurality of patients in the order of the patients sorted by the sorting means is displayed in a list on the screen of the conference, and the input items for each patient in the list display are displayed. A display means to be displayed in a display area of a size determined by the determination means, and a display means.
A medical support system characterized by having. The electronic medical record information acquisition means selects a patient whose information has been input via an input template of a type determined according to the information about the conference acquired by the conference body information acquisition means.
The medical support system according to claim 1, wherein the sorting means sorts information acquired by the electronic medical record information acquisition means according to a sorting condition determined according to the type. The medical support system according to claim 2, wherein the sort condition uses an input item which is an essential item in each input template. The medical support system according to any one of claims 1 to 3, wherein the attribute is a type of the input item. Further, a holding means for holding information in which the number of characters per line predetermined for the input item and the maximum number of characters predetermined for the input item are associated with the type of the input item is further provided. Prepare,
The determination means determines the size of the display area in which the information acquired by the electronic medical record information acquisition means is displayed on the screen of the conference based on the type of the input item and the information stored in the holding means. The medical support system according to claim 4, wherein the medical support system is determined. The determination means determines the size of the display area in which the information acquired by the electronic medical record information acquisition means is displayed on the screen of the conference by dividing the maximum number of characters by the number of characters per line. The medical support system according to claim 5. The determination means receives the electronic medical record information when displaying the information acquired by the electronic medical record information acquisition means on the screen of the conference according to the information indicating the attribute acquired by the input template information acquisition means. Determine whether the display at the end of the information acquired by the acquisition means can be omitted.
When it is determined by the determination means that the display at the end can be omitted, the display means displays the information acquired by the electronic medical record information acquisition means on the screen of the conference without displaying the end. The medical support system according to any one of claims 1 to 6, wherein the medical support system is characterized. The display means displays a scroll for an item whose end display is optional on the conference screen, and does not display a scroll for an item whose end display cannot be omitted on the conference screen. The medical support system according to claim 7, which is characterized. The input template information acquisition means acquires information indicating whether or not the input item of the input template is personal information, and obtains information.
The medical support according to any one of claims 1 to 8, wherein the display means prevents the personal information from being displayed on the screen of the conference when the input item is personal information. system. Further equipped with a means of acquiring participant information to acquire information on the participants of the conference,
The medical support system according to claim 9, wherein the display means prevents personal information from being displayed on the screen of the conference when the participant includes a participant of a specific attribute. The display means is characterized in that the information acquired by the electronic medical record information acquisition means and the patient identification information corresponding to the information acquired by the electronic medical record information acquisition means are displayed side by side. The medical support system according to any one of 10. The determination means determines the arrangement of a plurality of display areas in which a plurality of information input to the electronic medical record is displayed via a plurality of input items according to the information acquired by the input template information acquisition means. ,
The medical support system according to any one of claims 1 to 11, wherein the display means displays the plurality of information in a plurality of display areas determined by the determination means. Meeting body information acquisition process to acquire information about the conference,
The information entered into the electronic medical record via an input template having at least one input item that fits in the input items for inputting information about the patient, said for a plurality of patients selected according to the information about the conference. Electronic medical record information acquisition process acquired from electronic medical records and
An input template information acquisition process for acquiring information indicating an attribute predetermined for each input item according to the information about the patient, and an input template information acquisition process.
According to the information indicating the attribute acquired in the input template information acquisition process, the size of the display area in which the input item, which is the information acquired in the electronic medical record information acquisition process, is displayed on the screen of the conference. The decision process to decide and
A sorting step of sorting information about the plurality of patients acquired by the electronic medical record information acquisition step according to a sorting condition determined according to the information about the conference, and a sorting step of sorting the information about the plurality of patients.
The information acquired by the electronic medical record information acquisition step for the plurality of patients in the order of the patients sorted by the sorting step is displayed in a list on the screen of the conference, and the input items for each patient in the list display are displayed. A display step to be displayed in a display area of a size determined by the determination step , and a display step.
A medical support method characterized by having. A program comprising causing a computer to execute each step of the medical support method according to claim 13.

Images