JP2013041339A - Electronic medical chart server, display method, and display program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent important information from being overlooked.SOLUTION: A technique disclosed in this application, in one embodiment, comprises a communication control section, a shared information storage section, a determination section, and an output section. The communication control section receives a request including examinee identification information for identifying an examinee from a terminal operated by a user. The determination section acquires shared information corresponding to the examinee identification information included in the request from the shared information storage section for storing the examinee identification information, shared information registered for each attribute according to content, and a registration date when the shared information is registered or a status indicating whether the shared information is browsed or not. The determination section controls a display on a browsing screen on which the shared information is displayed separately depending on attributes in display areas on the basis of a condition set for each attribute and a comparison result with the registration date or the status of the acquired shared information. The output section outputs the browsing screen controlled by the determination section on the terminal.

Description

  The present invention relates to an electronic medical record server, a display method, and a display program.

  In recent years, electronic medical record systems have been widely used in the medical field. A user who uses the electronic medical record system registers medical information such as a medical examination result and a test result of the examinee in the database of the electronic medical record system. The users include medical workers such as doctors, nurses, and pharmacists, for example. In addition, the examinee includes not only patients such as sick persons and injured persons but also healthy persons such as those who undergo a medical examination and pregnant women. Hereinafter, a medical chart used in the electronic medical chart system is referred to as an “electronic medical chart”.

  In an electronic medical chart system, the authority to fill in the electronic medical chart is usually only granted to doctors, and other users such as nurses and pharmacists are only allowed to browse. For this reason, in the electronic medical chart system, there is a function called “patient bulletin board” that can be input and viewed by all users in order to exchange and share information about the patients among the users. On the patient bulletin board, for example, messages exchanged between users, complaints of examinees, and the like are described by each user.

  There is also a technique for determining whether to display or hide each item described in the electronic medical record so that only important information is grasped from the electronic medical record. For example, in this technique, a condition for display or non-display is set for each item described in the electronic medical record. Then, when displaying the electronic medical chart, it is determined whether to display or hide each item in light of the set conditions.

JP 2000-231592 A

  However, in the above prior art, important information may be overlooked. For example, if the displayed patient bulletin board screen is divided into tabs, it is not clear which tab contains important information, and important information may be overlooked by the user. there were. Also, for example, if the patient bulletin board screen requires manual scrolling, it is not clear where important information is included on the scrolled screen, and important information is overlooked by the user. There was a thing.

  The disclosed technology has been made in view of the above, and an object thereof is to provide an electronic medical record server, a display method, and a display program capable of preventing important information from being overlooked.

  In one aspect, the technology disclosed in the present application includes a communication control unit, a shared information storage unit, a determination unit, and an output unit. The communication control unit accepts a request including examinee identification information for identifying a examinee from a terminal operated by the user. The determination unit stores the identification information of the examinee, the shared information registered for each attribute according to the content, and the registration date / time when the shared information is registered or the status indicating whether the shared information is browsed Shared information corresponding to the identification information of the examinee included in the request is acquired from the storage unit. The determination unit controls the display of the browsing screen that displays the shared information by distinguishing the display area for each attribute based on the comparison result between the condition set for each attribute and the registration date or status of the acquired shared information. The output unit outputs the browsing screen controlled by the determining unit to the terminal.

  According to one aspect of the technology disclosed in the present application, it is possible to prevent important information from being overlooked.

FIG. 1 is a block diagram illustrating a functional configuration of the electronic medical record server according to the first embodiment. FIG. 2 is a diagram illustrating an example of a display screen of a patient bulletin board. FIG. 3 is a diagram illustrating an example of a display screen of a patient bulletin board. FIG. 4 is a diagram illustrating an example of a display screen of a patient bulletin board. FIG. 5 is a diagram illustrating an example of the data structure of the browsing history table. FIG. 6 is a diagram illustrating an example of the data structure of the bulletin board table. FIG. 7 is a diagram illustrating an example of a data structure of the instruction history table. FIG. 8 is a diagram illustrating an example of the data structure of the consultation table. FIG. 9 is a flowchart illustrating the processing procedure of the electronic medical record server according to the first embodiment. FIG. 10 is a flowchart illustrating the processing procedure of the initial display determination process. FIG. 11 is a flowchart illustrating the processing procedure of the electronic medical record server according to the second embodiment. FIG. 12 is a diagram for explaining an application example to a data center. FIG. 13 is a diagram illustrating a computer that executes a display program.

  Embodiments of an electronic medical record server, a display method, and a display program disclosed in the present application will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments. In addition, the embodiments may be appropriately combined as long as the processing contents do not contradict each other.

[Constitution]
An example of a functional configuration of the electronic medical record server according to the first embodiment will be described. FIG. 1 is a block diagram illustrating a functional configuration of the electronic medical record server according to the first embodiment. As shown in FIG. 1, the electronic medical record server 100 is connected via a network 10 to clients 20a, 20b, and 20c operated by a user. The electronic medical record server 100 is provided for each medical institution, for example, and includes a database that stores a medical record in which medical information such as a medical examination result and a test result of the examinee is described. The network 10 may be any type of communication network, such as the Internet (Internet), a LAN (Local Area Network), or a VPN (Virtual Private Network), whether wired or wireless. In the example illustrated in FIG. 1, the case where three clients 20 a, 20 b, and 20 c are connected to the electronic medical record server 100 is illustrated, but the configuration is not limited to the illustrated configuration. That is, an arbitrary number of clients may be connected to the electronic medical record server 100. In the following, the clients 20a, 20b, and 20c are collectively referred to as the client 20 when collectively referred to without distinction.

  The client 20 is a terminal used by each user such as a doctor, nurse, or pharmacist, and corresponds to an information processing terminal such as a personal computer or a PDA (Personal Digital Assistant). For example, the client 20 is installed with a client application that supports various operations related to medical care such as entry and browsing of the electronic medical record of the examinee or issuance of orders such as prescriptions and examinations. For example, the client 20 activates the client application when the user logs in with his / her account. This client application provides a function corresponding to the account of the logged-in user among various functions of the electronic medical record server 100 in cooperation with a server application installed in the electronic medical record server 100 described later. The users include medical workers such as doctors, nurses, and pharmacists, for example. In addition, the examinee includes not only patients such as sick persons and injured persons but also healthy persons such as those who undergo a medical examination and pregnant women. Hereinafter, the medical chart used in the electronic medical record server 100 is referred to as “electronic medical chart”. For example, it is assumed that the authority to fill in the electronic medical record is only granted to doctors, and only the authority to view is allowed to users other than doctors such as nurses and pharmacists. The client 20 is an example of a terminal.

  For example, the client 20 receives a request from a user. For example, the client 20 receives a request for displaying an electronic medical record, which is information for instructing display of the electronic medical record of the recipient, from the user. This display request includes, for example, patient identification information for identifying a patient and user identification information for identifying a user. The client 20 transmits the received display request to the electronic medical record server 100. For example, the client 20 receives the display screen of the patient bulletin board from the electronic medical record server 100 and outputs the received display screen. This patient bulletin board is a function that allows users other than doctors to have input and browsing authority in order to exchange and share information about the examinee among users. The patient bulletin board includes, for example, information such as messages exchanged between users and appeals of examinees. Although the case where the display request includes user identification information has been described here, the present invention is not limited to this. For example, when the user logs in using the user identification information and the user identification information is once authenticated in the electronic medical record server 100 described later, the display request does not necessarily include the user identification information.

  Here, when a user who is authorized to view a patient's electronic medical record (medical staff such as doctors and nurses) tries to view the electronic medical record of a patient, the patient bulletin board prior to viewing the electronic medical record. By confirming, it is possible to reduce the risk that information entered on the patient bulletin board is missed. Considering such operations, it is possible to more effectively suppress information oversight by collecting information that the user needs to confirm before displaying the electronic medical chart on the display screen of the patient bulletin board. . For example, it can be said that it is desirable for the user to grasp the history of medical guidance given to the patient by the doctor, the history of medical treatment between clinical departments, etc. before browsing the electronic medical record.

  Therefore, in the following, the display screen of the patient bulletin board displays a bulletin board tag for displaying messages exchanged between users, appeals of the examinee, etc., and a history of medical instruction by the doctor to the patient. The explanation will be made on the assumption that a teaching history tab, a consultation tab for displaying a history of medical treatment between departments, and the like are provided.

  A patient bulletin board display screen displayed on the client 20 will be described with reference to FIGS. 2 to 4. 2 to 4 are diagrams illustrating examples of display screens of a patient bulletin board. The display screen of the patient bulletin board is divided and displayed in, for example, a “bulletin board tab”, a “teaching history tab”, and a “consultation tab” based on the description content. The patient bulletin board is an example of a browsing screen.

  FIG. 2 shows an example of a display screen of a patient bulletin board on which a bulletin board tab is displayed. As shown in FIG. 2, the display screen 2a includes, for example, basic information 2b of the examinee and a bulletin board tab 2c. The basic information 2b of the examinee displays, for example, the examinee ID, name, gender, date of birth, age, etc. of the examinee. On the bulletin board tab 2c, for example, a message addressed to you, a staff message board, a treatment policy, and a patient / family complaint are displayed. The information on the display screen 2a is input by the user via the display screen 2a, for example. The bulletin board tab 2c is set by default to be displayed first when the patient bulletin board is activated.

  FIG. 3 shows an example of a display screen of a patient bulletin board on which an instruction history tab is displayed. As shown in FIG. 3, the display screen 3a includes, for example, basic information 3b of the examinee and an instruction history tab 3c. The basic information 3b of the examinee is the same as the basic information 2b of the examinee shown in FIG. In the teaching history tab 3c, for example, the history of the guidance that has been given to the examinee so far is displayed. The information on the display screen 3a is input by the user via the display screen 3a, for example. The reason why the instruction history tab 3c is shared on the patient bulletin board is to prevent omission of calculation of the instruction fee.

  FIG. 4 shows an example of a display screen of a patient bulletin board on which a consultation tab is displayed. As shown in FIG. 4, the display screen 4a includes, for example, basic information 4b of the examinee and a consultation tab 4c. The basic information 4b of the examinee is the same as the basic information 2b of the examinee shown in FIG. In the consultation tab 4c, for example, a request for diagnosis for another medical department and an answer to the request are displayed. The information on the display screen 4a is input by the user via the display screen 4a, for example. The reason why the consultation tab 4c is shared on the patient bulletin board is to prevent oversight of information related to the examination requested by another medical department.

  Returning to the description of FIG. The electronic medical record server 100 provides various functions to the client 20. The electronic medical record server 100 is installed with a server application that supports various tasks related to medical care, such as entry and browsing of medical records, and issuance of orders such as prescriptions and examinations. When the electronic medical record server 100 receives a login request together with authentication information such as a user ID (Identification) of a user and a password from the client 20, the electronic medical record server 100 executes login authentication. The electronic medical record server 100 starts cooperation with the client application when the login authentication is successful. This server application releases the function corresponding to the account of the logged-in user among the various functions of the electronic medical record server 100 to the client application. Note that the electronic medical record server 100 can identify personal information such as the user's name, occupation, department, and years of service based on the logged-in user's account.

  The electronic medical record server 100 includes a communication control unit 110, a storage unit 120, and a control unit 130. The communication control unit 110 controls communication regarding various information transmitted and received between the electronic medical record server 100 and the client 20. For example, the communication control unit 110 accepts a request including examinee identification information for identifying a examinee from a terminal operated by the user. For example, a network interface card (NIC).

  The storage unit 120 includes, for example, a browsing history table 121, a bulletin board table 122, a guidance history table 123, and a consultation table 124. For example, the storage unit 120 corresponds to a semiconductor memory device such as a random access memory (RAM), a read only memory (ROM), and a flash memory, and a storage device such as a hard disk or an optical disk. The bulletin board table 122, the guidance history table 123, and the consultation table 124 are examples of the shared information storage unit. The shared information storage unit includes, for example, the patient identification information, the shared information registered for each attribute according to the content, the registration date and time when the shared information was registered, or a status indicating whether or not the shared information has been browsed And remember. Among these, the shared information is managed for each attribute, and the attribute is information for distinguishing the contents of the information.

  The browsing history table 121 stores a history of browsing the patient bulletin board. FIG. 5 is a diagram illustrating an example of the data structure of the browsing history table. As illustrated in FIG. 5, the browsing history table 121 stores, for example, “browsing date and time”, “user ID”, and “examinee ID” in association with each other. Among these, browsing date shows the date when the patient bulletin board was browsed. The user ID indicates the user ID of the user who has browsed the patient bulletin board. The user ID is an identification number that uniquely identifies a user who uses the electronic medical record server 100, and is an example of user identification information. The examinee ID indicates the ID of the examinee on the browsed patient bulletin board. The examinee ID is an identification number that uniquely identifies the examinee, and is an example of examinee identification information. The browsing history table 121 is an example of a browsing history storage unit. The browsing history storage unit stores, for example, user identification information and a history browsed by the user.

  As illustrated in FIG. 5, the browsing history table 121 stores, for example, a browsing date “2010/8/27 10:32”, a user ID “0063A”, and a examinee ID “1019” in association with each other. . That is, the browsing history table 121 stores that the user with the user ID “0063A” browsed the patient bulletin board of the patient with the examinee ID “1019” at 10:32 on August 27, 2010. In addition, the browsing history table 121 similarly stores other browsing histories.

  The bulletin board table 122 stores information displayed on the bulletin board tab of the patient bulletin board. Here, the information on the bulletin board is information including messages exchanged between users. For example, in the bulletin board table 122, one record is registered every time information is input via the bulletin board tab of the patient bulletin board. FIG. 6 is a diagram illustrating an example of the data structure of the bulletin board table. As illustrated in FIG. 6, the bulletin board table 122 stores, for example, “examinee ID”, “user ID”, “registration date / time”, “item”, and “content” in association with each other. Among these, the examinee ID indicates a patient bulletin board in which information is input. The user ID indicates the user who has input information. The registration date / time indicates the date / time when the record was registered. The item indicates an item for which information has been input. For example, the item “patient / family complaint” indicates that information has been input to “patient / family complaint”. Further, for example, the item “staff message board” indicates that information is input to the “staff message board”. Further, for example, the item “treatment policy” indicates that information has been input to “treatment policy”. In addition, for example, the item “message to you” indicates that information is input to “message to you”. The content indicates the content of the input information. Note that the information stored in the bulletin board table 122 is an example of information relating to a first attribute indicating a message exchanged between users.

  As shown in FIG. 6, the bulletin board table 122 includes, for example, a visitor ID “1019”, a user ID “0063A”, a registration date “2010/8/27 10:32”, and an item “patient / family member”. “Sue” and the content “sue if you have trouble sleeping” are stored in association with each other. That is, the bulletin board table 122 shows that the user with the user ID “0063A” responds to “patient / family complaint” on the patient bulletin board with the examinee ID “1019” at 10:32 on August 27, 2010. Memorize that I have entered "I am complaining about falling asleep". The bulletin board table 122 stores other information in the same manner.

  The instruction history table 123 stores information displayed on the instruction history tab of the patient bulletin board. Here, the guidance history is information relating to guidance given to the examinee by the doctor. For example, in the guidance history table 123, one record is registered each time a guidance fee is calculated for guidance given to a doctor by a doctor. FIG. 7 is a diagram illustrating an example of a data structure of the instruction history table. As shown in FIG. 7, the guidance history table 123 includes, for example, “examinee ID”, “user ID”, “registration date / time”, “instruction date”, “instructor”, and “content of instruction”. Is stored in association with each other. Among these, the examiner ID, the user ID, and the registration date and time are the same as the examinee ID, the user ID, and the registration date and time shown in FIG. The guidance date indicates the date when the guidance for which the guidance fee was calculated was provided. The instructor indicates the doctor who performed the instruction for which the instruction fee was calculated. The contents of instruction indicate the contents of instruction for which the instruction fee was calculated. Note that the information stored in the guidance history table 123 is an example of information relating to a second attribute indicating a guidance history performed by the doctor on the examinee.

  As shown in FIG. 7, the instruction history table 123 includes a visitor ID “1019”, a user ID “0063A”, a registration date “2010/8/2 10:29”, and an instruction date “2010/8 / 1 ”, the leader“ AA ”, and the guidance content“ epileptic guidance ”are stored in association with each other. That is, the instruction history table 123 stores that the user with the user ID “0063A” calculated the instruction fee for the examinee with the examinee ID “1019” at 10:29 on August 2, 2010. The instruction history table 123 also stores that the instruction for which the instruction fee is calculated is “epilepsy instruction” performed by the doctor “AA” on August 1, 2010. Further, the instruction history table 123 similarly stores other instruction histories.

  The consultation table 124 stores information displayed on the consultation tab of the patient bulletin board. Here, the consultation is information related to a diagnosis requested by another medical department. For example, one record is registered in the consultation table 124 every time a medical examination is requested from another medical department or every time a medical examination request is answered. FIG. 8 is a diagram illustrating an example of the data structure of the consultation table. As shown in FIG. 8, the consultation table 124 includes, for example, a “checker ID”, “user ID”, “registration date / time”, “type”, “request medical department”, and “request source”. “Department”, “request contents”, and “confirmation” are stored in association with each other. Among these, the examiner ID, the user ID, and the registration date and time are the same as the examinee ID, the user ID, and the registration date and time shown in FIG. The type indicates the type of record. The type “request” indicates that it is a request for a medical examination for another medical department, and the type “response” indicates that it is a response to the request. The requested medical department indicates the requested medical department. The requesting medical department indicates the requesting medical department. The request content indicates the content of the request from the requesting department to the requesting department. Confirmation indicates whether the record has been confirmed. Confirmation “Not yet” indicates that the doctor of the requesting department is unconfirmed when the type is “Request”, and that the doctor of the requesting department is unconfirmed when the type is “Answer”. Show. The confirmation “completed” indicates that the doctor of the requested medical department has been confirmed in the case of the type “request”, and the doctor of the requesting medical department has been confirmed in the case of the type “answer”. It shows that. Note that when the doctor of the requested medical department confirms the record of the type “request”, the confirmation “not yet” is updated to “completed”. When the doctor of the requesting department confirms the record of the type “answer”, the confirmation “not yet” is updated to “completed”. The information stored in the consultation table 124 is an example of information relating to a third attribute indicating consultation for requesting medical care between clinical departments.

  As shown in FIG. 8, the consultation table 124 stores the examinee ID “1019”, the user ID “0063A”, and the registration date “2010/8/22 10:32” in association with each other. Further, the consultation table 124 stores the type “request”, the requested medical department “otolaryngology”, the requested medical department “internal medicine”, and the request content “appealing ear pain” in association with each other. . In other words, the consultation table 124, at 10:32 on August 22, 2010, for the examinee with the examinee ID “1019”, the user with the user ID “0063A” requests a diagnosis from another department. Remember what you did. In addition, the consultation table 124 also stores that this request was a request from the internal medicine to the otolaryngologist to “sue ear pain”. The consultation table 124 also stores other consultations in the same manner.

  Returning to the description of FIG. The control unit 130 includes a determination unit 131 and an output unit 132. The function of the control unit 130 can be realized by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). Further, the function of the control unit 130 can be realized, for example, by a CPU (Central Processing Unit) executing a predetermined program.

  For example, the determination unit 131 acquires shared information corresponding to the examinee identification information included in the request from the shared information storage unit. Based on the comparison result between the condition set for each attribute and the registration date / time or status of the acquired shared information, the determination unit 131 displays a browsing screen that displays the shared information by distinguishing the display area for each attribute. Control. For example, the determination unit 131 performs control when the shared information storage unit includes shared information corresponding to a registration date and time after the user's last browsing date and time acquired from the browsing history storage unit.

  For example, when the determination unit 131 receives a request to display the electronic medical record of the examinee from a terminal operated by the user, the determination unit 131 acquires the date and time when the user last viewed from the browsing history storage unit. If there is shared information stored in the storage unit that stores the shared information after the acquired date and time, the determination unit 131 determines shared information to be initially displayed on the terminal based on the shared information stored in the storage unit.

  For example, when the determination unit 131 receives a display request for an electronic medical record from the user, the determination unit 131 obtains from the browsing history table 121 the last browsing date and time indicating the date and time when the user last viewed the patient bulletin board. The determination unit 131 determines whether there is shared information registered after the acquired last browsing date. When there is shared information registered after the last viewing date and time, the determination unit 131 executes an initial display determination process. The condition “whether there is shared information registered after the last browsing date” determined by the determination unit 131 is an example of a condition set for each attribute.

  For example, when the display unit 131 receives a display request for the electronic medical record with the examinee ID “1019” from the user with the user ID “0063A”, the determination unit 131 sets the user ID “0063A” and the examinee ID “1019”. Is used to extract the browsing date and time from the browsing history table 121. In the example illustrated in FIG. 5, the determination unit 131 extracts the browsing date “2010/8/27 10:32”. The determination unit 131 acquires the latest browsing date as the last browsing date among the extracted browsing dates. The determination unit 131 refers to the bulletin board table 122, the guidance history table 123, and the consultation table 124, and whether there is shared information registered after the acquired last viewing date and time for the record of the examinee ID “1019”. Determine whether. In the example shown in FIG. 6, the bulletin board table 122 has a user ID “0189B” corresponding to the “staff message board” of the patient bulletin board with the examinee ID “1019” at 10:45 on August 27, 2010. There is a record indicating that the user has input. In this case, the determination unit 131 determines that there is shared information registered after the acquired last viewing date and time, and executes an initial display determination process.

  Hereinafter, an initial display determination process executed by the determination unit 131 will be described. This initial display determination process is a process for determining information to be initially displayed on the client 20 among the information on the patient bulletin board. For example, when the attribute of the acquired shared information is the second attribute and a predetermined number of days have elapsed since the registration date and time of the shared information, the determination unit 131 initializes the display area of the second attribute to the terminal. Display. For example, when the attribute of the acquired shared information is the third attribute and the status is unconfirmed, the determination unit 131 initially displays the display area of the third attribute on the terminal.

  For example, the determination unit 131 determines whether there is shared information that needs to be viewed in the instruction history table 123. For example, the determination unit 131 refers to the instruction history table 123 for the electronic medical record examinee ID requested to be displayed, and determines whether or not there is an instruction history that has passed a predetermined number of days from the previous instruction date. When there is shared information that needs to be viewed in the guidance history table 123, the determination unit 131 sets a guidance flag. On the other hand, when there is no shared information that needs to be browsed in the guidance history table 123, the determination unit 131 does not set the guidance flag. The predetermined number of days is, for example, 30 days. The condition “whether there is shared information that needs to be viewed in the instruction history table 123” determined by the determination unit 131 is an example of a condition set for each attribute.

  The case where the determination part 131 determines whether there exists shared information which needs browsing in the instruction | indication history table 123 using FIG. 7 is demonstrated. Here, a case will be described in which an electronic medical chart display request for the examinee ID “1019” is received on September 2, 2010. A case where the predetermined number of days is 30 days will be described. In the example shown in FIG. 7, since there is a guidance history calculated on August 2, 2010 for the guidance history of the examinee ID “1019”, the determination unit 131 has passed 30 days or more from the previous guidance date. Determine that there is a record. In this case, the determination unit 131 sets a guidance flag on the patient bulletin board with the examinee ID “1019”.

  For example, the determination unit 131 determines whether there is shared information that needs to be browsed in the consultation table 124. For example, the determination unit 131 refers to the consultation table 124 for the examinee ID of the electronic medical record requested to be displayed, and determines whether there is an unconfirmed consultation. Specifically, the determination unit 131 determines whether or not there is a record in which the type is “request”, the confirmation is “not yet”, and there is a record that matches the department to which the user who requested the display requested belongs. Determine whether. That is, the determination unit 131 determines whether or not there is an unconfirmed medical request from another medical department for the department to which the user who has made the display request belongs. Alternatively, the determination unit 131 determines whether or not there is a record whose type is “answer”, confirmation is “not yet”, and which matches the department to which the requesting department requested the display. To do. That is, the determination unit 131 determines whether or not there is an unconfirmed answer from another medical department for the department to which the user who has made the display request belongs. When there is shared information that needs to be viewed in the consultation table 124, the determination unit 131 sets a consultation flag. On the other hand, when there is no shared information that needs to be browsed in the consultation table 124, the determination unit 131 does not set the consultation flag. The condition “whether there is shared information that needs to be viewed in the consultation table 124” determined by the determination unit 131 is an example of a condition set for each attribute.

  A case where the determination unit 131 determines whether there is shared information that needs to be browsed in the consultation table 124 will be described with reference to FIG. Here, a case where the user who has requested display of the electronic medical record with the examinee ID “1019” belongs to “otolaryngology” will be described. In the example shown in FIG. 8, for the record of the examinee ID “1019”, there is a record in which the type is “request”, the confirmation is “not yet”, and the requested medical department is “otolaryngology”. The determination unit 131 determines that there is shared information that requires browsing. In this case, the determination unit 131 sets a consultation flag on the patient bulletin board with the examinee ID “1019”.

  For example, the determination unit 131 determines shared information to be initially displayed based on a guidance flag and a consultation flag. For example, when both the instruction flag and the consultation flag are not set, the determination unit 131 determines the bulletin board tab as shared information to be initially displayed. For example, when the guidance flag is set and the consultation flag is not set, the determination unit 131 determines the guidance history tab as shared information to be initially displayed. For example, when the consultation flag is set and the instruction flag is not set, the determination unit 131 determines the consultation information to be initially displayed as the shared information. In addition, for example, when both the instruction flag and the consultation flag are set, the determination unit 131 determines the shared information to be initially displayed by setting a tab to be preferentially displayed in advance. That is, when the instruction history tab is set as a tab to be preferentially displayed, the determining unit 131 determines the instruction history tab as shared information to be initially displayed. In addition, when the consultation tab is set as a tab to be displayed preferentially, the determination unit 131 determines the consultation tab as shared information to be initially displayed. Thus, the determination unit 131 determines information to be initially displayed on the client 20 by the initial display determination process.

  For example, the output unit 132 outputs the browsing screen controlled by the determination unit 131 to the terminal. For example, the output unit 132 outputs a browsing screen different from the display screen of the electronic medical record, and outputs the display screen after outputting the browsing screen.

  For example, the output unit 132 outputs a browsing screen on which the shared information determined by the determining unit 131 is displayed as an initial screen to the terminal. For example, the output unit 132 generates a display screen of a patient bulletin board using the shared information determined by the initial display determination process as an initial screen. The output unit 132 outputs a display screen of the generated patient bulletin board. For example, the output unit 132 transmits the generated display screen of the patient bulletin board to the client 20 and causes the client 20 to display the transmitted display screen.

[processing]
Next, a processing procedure of the electronic medical record server 100 according to the first embodiment will be described. FIG. 9 is a flowchart illustrating the processing procedure of the electronic medical record server according to the first embodiment. The process shown in FIG. 9 is executed at predetermined time intervals, for example, while power is supplied from the power source to the illustrated devices.

  As illustrated in FIG. 9, when the electronic medical record server 100 receives a display request for an electronic medical record from the user (Yes in step S <b> 101), the determination unit 131 acquires the last browsing date and time from the browsing history table 121 (step S <b> 102). The display request includes the user ID and the examinee ID. Note that the electronic medical record server 100 displays the electronic medical record of the recipient corresponding to the recipient ID included in the display request by the process described later.

  The determination unit 131 determines whether there is shared information registered for the receiver corresponding to the receiver ID after the last viewing date and time of the user corresponding to the user ID (step S103). When there is shared information registered after the user's last viewing date and time (Yes in step S103), the determination unit 131 executes an initial display determination process (step S104).

  Here, the procedure of the initial display determination process shown in step S104 of FIG. 9 will be described with reference to FIG. FIG. 10 is a flowchart illustrating the processing procedure of the initial display determination process.

  As illustrated in FIG. 10, the determination unit 131 determines whether there is shared information that needs to be viewed in the instruction history table 123 (step S201). For example, the determining unit 131 refers to the instruction history table 123 for the electronic medical record examinee ID requested to be displayed, and determines whether or not there is a record that has passed 30 days or more from the previous instruction date.

  If there is shared information that needs to be browsed in the instruction history table 123 (step S201 Yes), the determination unit 131 sets an instruction flag and proceeds to step S204 (step S202). On the other hand, when there is no shared information that needs to be browsed in the instruction history table 123 (No in step S201), the determination unit 131 sets the instruction flag unset and proceeds to step S204 (step S203).

  The determination unit 131 determines whether there is shared information that needs to be viewed in the consultation table 124 (step S204). For example, the determination unit 131 refers to the consultation table 124 for the examinee ID of the electronic medical record requested to be displayed, and determines whether there is an unconfirmed consultation. Specifically, the determination unit 131 determines whether or not there is a record in which the type is “request”, the confirmation is “not yet”, and there is a record that matches the department to which the user who requested the display requested belongs. Determine whether. That is, the determination unit 131 determines whether or not there is an unconfirmed medical request from another medical department for the department to which the user who has made the display request belongs. Alternatively, the determination unit 131 determines whether or not there is a record whose type is “answer”, confirmation is “not yet”, and which matches the department to which the requesting department requested the display. To do. That is, the determination unit 131 determines whether or not there is an unconfirmed answer from another medical department for the department to which the user who has made the display request belongs.

  If there is shared information that needs to be browsed in the consultation table 124 (step S204 Yes), the determination unit 131 sets a consultation flag and proceeds to step S207 (step S205). On the other hand, when there is no shared information that needs to be browsed in the consultation table 124 (No in step S204), the determination unit 131 sets the consultation flag unset and proceeds to step S207 (step S206). Then, the determination unit 131 determines shared information to be initially displayed (step S207).

  Returning to the description of FIG. The output unit 132 generates a display screen of a patient bulletin board that displays an area for displaying the shared information determined by the initial display determination process (step S105). The output unit 132 outputs the display screen of the generated patient bulletin board (step S106). For example, the output unit 132 transmits the generated display screen of the patient bulletin board to the client 20 and causes the client 20 to display the transmitted display screen. That is, the output unit 132 performs control so that any one display area is initially displayed on the display screen of the patient bulletin board having the bulletin board display area, the instruction history display area, and the consultation display area. As shown in FIGS. 2 to 4, the display area may be separated for each tab, or each display area may be arranged in one display unit.

  If there is no shared information registered after the user's last viewing date and time (No in step S103), the electronic medical record server 100 ends the process. For example, the output unit 132 outputs the electronic medical record information requested to be displayed in step S101 without outputting the patient bulletin board.

  Further, for example, the execution / non-execution of the processing in step S201 and the processing in step S204 may be selected according to the job type of the user who has requested display. For example, if the job type of the user who has requested display is a doctor or a clerk, the process of step S201 is executed, and if not the doctor and the clerk, the process of step S201 is not executed. When the process of step S201 is not executed, the instruction history tab is not selected as the initial screen of the patient bulletin board.

  Moreover, the processing procedure shown in FIG.9 and FIG.10 does not necessarily need to be performed by said processing procedure. For example, if an affirmative determination is made in step S101 in which the electronic medical record server 100 receives a request for displaying an electronic medical record from the user, the process in step S104, which is an initial display determination process, is executed. In step S104, when it is determined that the instruction history tab or the consultation tab is initially displayed, the display screen of the patient bulletin board is generated using the shared information determined by the initial display determination process as the initial screen. The process of step S105 is executed. And the process of step S106 which is a process which outputs the display screen of a patient bulletin board is performed.

  On the other hand, if it is determined in step S104 that neither the teaching history tab nor the consultation tab is initially displayed, the process of step S102, which is a process of acquiring the last browsing date, is executed. And the process of step S103 which is a process which determines whether there exists any shared information registered after the user's last browsing date is performed.

  If the determination in step S103 is affirmative, the process of step S105, which is a process of generating a display screen of a patient bulletin board, is executed using the bulletin board tab as an initial screen. And the process of step S106 which is a process which outputs the display screen of a patient bulletin board is performed. On the other hand, if the determination in step S103 is negative, the electronic medical record server 100 ends the process.

[effect]
Next, effects of the electronic medical record server 100 according to the first embodiment will be described. The electronic medical record server 100 accepts a request including examinee identification information for identifying a examinee from a terminal operated by the user. The electronic medical record server 100 stores the patient identification information, the shared information registered for each attribute according to the content, and the registration date and time when the shared information is registered or a status indicating whether the shared information has been browsed. The shared information corresponding to the identification information of the examinee included in the request is acquired from the shared information storage unit. The electronic medical record server 100 controls the display of the browsing screen that displays the shared information by distinguishing the display area for each attribute based on the comparison result between the condition set for each attribute and the registration date or status of the acquired shared information. To do. The electronic medical record server 100 outputs the browsing screen controlled by the determining unit to the terminal. For this reason, the electronic medical record server 100 can prevent important information from being overlooked.

  For example, when the user views the electronic medical record of the examinee, the electronic medical record server 100 automatically activates the patient bulletin board if there is new information for the user on the patient bulletin board of the examinee. Therefore, the electronic medical record server 100 can efficiently share information newly registered on the patient bulletin board.

  In addition, for example, when the screen of the patient bulletin board displayed by automatic activation is divided into tabs, the electronic medical record server 100 outputs a tab including important information to the terminal as an initial screen. Can be prevented from being overlooked.

  For example, when there is information that needs to be browsed in the instruction history table 123, the electronic medical record server 100 initially displays an instruction history tab instead of the bulletin board tab that is the default initial screen. For this reason, the electronic medical record server 100 can prevent important information from being overlooked.

  Further, for example, when there is information that needs to be viewed in the consultation table 124, the electronic medical record server 100 initially displays a consultation tab instead of a bulletin board tab that is a default initial screen. For this reason, the electronic medical record server 100 can prevent important information from being overlooked.

  Although the embodiments of the present invention have been described so far, the present invention may be implemented in other embodiments besides the above-described embodiments. Therefore, other embodiments will be described below.

[Direct activation of patient bulletin board]
In the first embodiment, the case where the initial screen of the patient bulletin board automatically activated in response to the display request of the electronic medical record is determined has been described, but the present invention is not limited to this. For example, the electronic medical record server 100 shown in the first embodiment can determine the initial screen even when the patient bulletin board is directly activated by the user.

  The case where the initial screen of the patient bulletin board directly started by the user is determined will be described with reference to FIG. FIG. 11 is a flowchart illustrating the processing procedure of the electronic medical record server according to the second embodiment. The process illustrated in FIG. 11 is executed at predetermined time intervals while power is supplied from the power source to each of the illustrated devices, for example.

  As shown in FIG. 11, when the electronic medical record server 100 accepts a display request for a patient bulletin board from the user (Yes in step S301), the determination unit 131 executes an initial display determination process (step S302). This initial display determination processing is the same as the processing procedure of the initial display determination processing shown in FIG.

  The output unit 132 generates a patient bulletin board display screen using the shared information determined by the initial display determination processing as an initial screen (step S303). The output unit 132 outputs the display screen of the generated patient bulletin board (step S304). For example, the output unit 132 transmits the generated display screen of the patient bulletin board to the client 20 and causes the client 20 to display the transmitted display screen.

[Data Center]
In the first embodiment, the case where the electronic medical record server 100 is installed in a medical institution has been described. However, the present invention is not limited to this. For example, the electronic medical record server 100 may be applied to a data center connected to a plurality of medical institutions. FIG. 12 is a diagram for explaining an application example to a data center. As shown in FIG. 12, the data center 200 is connected to clients 220a, 220b,... Via a network 210, for example. The network 210 may employ any type of communication network, such as the Internet or WAN (Wide Area Network), whether wired or wireless. Further, the clients 220a, 220b,... Are distributed and installed in a plurality of medical institutions. The data center 200 includes server devices 201a, 201b,... And storage devices 202a, 202b,. Here, the clients 220a, 220b,... Are collectively referred to as the client 220 when they are described without distinction. In addition, when the server apparatuses 201a, 201b,. In addition, the storage devices 202a, 202b,.

  For example, the data center 200 uses the server device 201 to realize the function of the electronic medical record server 100 illustrated in FIG. 1 as a virtual machine. For example, the data center 200 stores the browsing history table 121, the bulletin board table 122, the guidance history table 123, and the consultation table 124 shown in FIG. .

  For example, in the data center 200, an electronic medical record VM (Virtual Machine), which is a virtual machine responsible for the function of the electronic medical record server 100, accepts a request including examinee identification information for identifying a examinee from a terminal operated by the user. . The electronic medical record VM stores the patient identification information, the shared information registered for each attribute according to the content, and the registration date / time when the shared information is registered or the status indicating whether the shared information has been browsed Shared information corresponding to the identification information included in the request is acquired from the information storage unit. The electronic medical record VM controls the display of the browsing screen that displays the shared information by distinguishing the display area for each attribute based on the comparison result between the condition set for each attribute and the registration date or status of the acquired shared information. . The electronic medical record VM outputs the browsing screen controlled by the determining unit to the terminal. For this reason, the electronic medical record VM can prevent important information from being overlooked.

[Others]
In the first embodiment, when determining the presence of new arrival information, that is, when determining the presence of shared information registered after the last browsing date, the determination unit 131 includes a bulletin board table 122, a guidance history table 123, The case of referring to the consultation table 124 has been described. However, the present invention is not limited to this. For example, the determination unit 131 may refer only to the bulletin board table 122 and may not refer to the instruction history table 123 and the consultation table 124 when determining the presence of new arrival information. In other words, for example, when the determination unit 131 receives a display request for an electronic medical record from the user, the determination unit 131 acquires the last browsing date and time indicating the date and time when the user last viewed the patient bulletin board from the browsing history table 121. The determination unit 131 refers to the bulletin board table 122 and determines whether there is shared information registered after the acquired last browsing date. When there is shared information registered after the last viewing date and time, the determination unit 131 executes an initial display determination process.

  In the first embodiment, the case where the display screen of the patient bulletin board is divided and displayed on the “bulletin board tab”, the “teaching history tab”, and the “consultation tab” based on the description content has been described. It is not limited to. For example, the present invention can be applied even when the screen of a patient bulletin board requires manual scrolling. For example, when the instruction flag is set and the consultation flag is not set, the determination unit 131 determines the area for displaying the instruction history as shared information to be initially displayed. And the output part 132 produces | generates the display screen which has arrange | positioned the area | region which displays a guidance history in the area | region which does not require manual scrolling, and outputs the produced | generated display screen. For example, the output unit 132 transmits the generated display screen to the client 20 and causes the client 20 to display the transmitted display screen. For this reason, the electronic medical record server 100 can prevent important information from being overlooked even when the screen of the patient bulletin board requires manual scrolling.

  In the first embodiment, the case where the client application installed in the client 20 cooperates with the server application to provide various functions of the electronic medical record server 100 is described. However, the present invention is limited to this. It is not a thing. For example, the client 20 may use a service provided by the electronic medical record server 100 via a browser without using a dedicated application for using the function of the electronic medical record server 100.

  Further, for example, among the processes described in the first embodiment, all or part of the processes described as being automatically performed can be manually performed, or have been described as being manually performed. All or a part of the processing can be automatically performed by a known method. For example, when there is shared information registered after the last viewing date and time, it has been described that the initial display determination process is automatically started, but it is manually started by pressing a button for accepting a start instruction by the user May be. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified. For example, the consultation table 124 may store the next consultation date to be examined based on the consultation.

  Further, for example, each component of the electronic medical record server 100 shown in FIG. 1 is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of the electronic medical record server 100 is not limited to the one shown in the figure, and all or a part of the electronic medical record server 100 can be functionally or physically functioned in an arbitrary unit according to various loads or usage conditions. It can be configured to be distributed and integrated. For example, an external storage device may be connected to the electronic medical record server 100 via the network 10 so that the information stored in the storage unit 120 is stored in the external storage device.

  The electronic medical record server 100 can also be realized by installing each function of the electronic medical record server 100 in a known information processing apparatus. Known information processing apparatuses correspond to apparatuses such as personal computers and workstations, for example.

[program]
FIG. 13 is a diagram illustrating a computer that executes a display program. As illustrated in FIG. 13, the computer 300 includes a CPU 301 that executes various arithmetic processes, an input device 302 that receives data input from a user, and a monitor 303. The computer 300 also includes a medium reading device 304 that reads a program or the like from a storage medium, an interface device 305 for connecting to another device, and a wireless communication device 306 for connecting to another device wirelessly. The computer 300 also includes a RAM (Random Access Memory) 307 that temporarily stores various types of information and a hard disk device 308. Each device 301 to 308 is connected to a bus 309.

  The hard disk device 308 stores a display program having the same functions as the processing units of the determination unit 131 and the output unit 132 illustrated in FIG. The hard disk device 308 stores various data for realizing a display program.

  The CPU 301 reads each program stored in the hard disk device 308, develops it in the RAM 307, and performs various processes. In addition, these programs can cause the computer to function as the determination unit 131 and the output unit 132 illustrated in FIG. 1.

  Note that the above display program is not necessarily stored in the hard disk device 308. For example, the computer 300 may read and execute a program stored in a computer-readable recording medium. As the computer-readable recording medium, for example, a portable recording medium such as a CD-ROM, a DVD disk, and a USB memory, a semiconductor memory such as a flash memory, a hard disk drive, and the like are supported. Further, the program may be stored in a device connected to a public line, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), etc., and the computer 300 may read and execute the program therefrom. good.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Additional remark 1) The communication control part which receives the request | requirement containing checker identification information which identifies a checker from the terminal which a user operates,
Shared information storage for storing the identification information of the examinee, the shared information registered for each attribute according to the content, the registration date and time when the shared information was registered, or the status indicating whether or not the shared information was browsed And
From the shared information storage unit, the shared information corresponding to the visitor identification information included in the request is acquired, and based on a comparison result between the condition set for each attribute and the registration date and time or status of the acquired shared information A determination unit that controls display of a browsing screen that displays the shared information by distinguishing display areas for each attribute;
An electronic medical record server, comprising: an output unit that outputs the browsing screen controlled by the determination unit to the terminal.

(Additional remark 2) It further has the browsing history memory | storage part which memorize | stores the said user identification information and the log | history browsed by the said user,
The determination unit performs the control when there is shared information corresponding to a registration date and time after the last browsing date and time of the user acquired from the browsing history storage unit in the shared information storage unit. The electronic medical record server according to Supplementary Note 1.

(Supplementary note 3) The request further includes information for instructing display of the electronic medical record of the recipient,
The electronic medical chart according to appendix 1 or 2, wherein the output unit outputs the browsing screen different from the display screen of the electronic medical chart, and outputs the display screen after outputting the browsing screen. server.

(Additional remark 4) The said shared information is the information concerning the 1st attribute which shows the message exchanged between users, the information concerning the 2nd attribute which shows the guidance history which the doctor performed with respect to the examinee, and Including
When the attribute of the acquired shared information is the second attribute and a predetermined number of days or more have elapsed since the registration date and time of the shared information, the determination unit displays the display area of the second attribute The electronic medical record server according to any one of supplementary notes 1 to 3, wherein the electronic medical record server is initially displayed on a terminal.

(Supplementary Note 5) The shared information further includes information related to a third attribute indicating consultation for requesting medical care between clinical departments,
The determining unit is configured to cause the terminal to initially display a display area of the third attribute when the attribute of the acquired shared information is the third attribute and the status is unconfirmed. The electronic medical record server according to appendix 4.

(Appendix 6) A display method executed by a computer,
A request including the identification information for identifying a patient is received from a terminal operated by the user,
Shared information storage for storing the identification information of the examinee, the shared information registered for each attribute according to the content, the registration date and time when the shared information was registered, or the status indicating whether or not the shared information was browsed A shared information corresponding to the examinee identification information included in the request from the section, and based on a comparison result between a condition set for each attribute and a registration date or status of the acquired shared information Control the display of the browsing screen that displays the shared information by distinguishing the display area for each,
The display method controlled by the process for controlling the display of the browsing screen is output to the terminal.

(Additional remark 7) The process which controls the display of the said browsing screen is the said user acquired from the browsing history memory | storage part which memorize | stores the said user identification information and the log | history browsed by the said user in the said shared information storage part The display method according to appendix 6, wherein the control is performed when there is shared information corresponding to a registration date and time after the last browsing date and time.

(Supplementary note 8) The request further includes information for instructing display of the electronic medical record of the recipient,
The processing to be output to the terminal outputs the browsing screen different from the display screen of the electronic medical record, and outputs the display screen after outputting the browsing screen. How to display.

(Supplementary note 9) The shared information includes information related to a first attribute indicating a message exchanged between users, information related to a second attribute indicating a history of guidance given to a doctor by a doctor, and Including
The process for controlling the display of the browsing screen is the second attribute when the acquired attribute of the shared information is the second attribute, and a predetermined number of days have passed since the registration date and time of the shared information. 9. The display method according to any one of appendix 6 to appendix 8, wherein an attribute display area is initially displayed on the terminal.

(Supplementary Note 10) The shared information further includes information related to a third attribute indicating consultation for requesting medical care between clinical departments,
The process of controlling the display of the browsing screen is performed by initializing the display area of the third attribute in the terminal when the attribute of the acquired shared information is the third attribute and the status is unconfirmed. The display method according to appendix 9, wherein display is performed.

(Supplementary note 11)
A request including the identification information for identifying a patient is received from a terminal operated by the user,
Shared information storage for storing the identification information of the examinee, the shared information registered for each attribute according to the content, the registration date and time when the shared information was registered, or the status indicating whether or not the shared information was browsed A shared information corresponding to the examinee identification information included in the request from the section, and based on a comparison result between a condition set for each attribute and a registration date or status of the acquired shared information Control the display of the browsing screen that displays the shared information by distinguishing the display area for each,
A display program for executing the process of outputting the browsing screen controlled by the process of controlling the display of the browsing screen to the terminal.

(Additional remark 12) The process which controls the display of the said browsing screen is the said user acquired from the browsing history memory | storage part which memorize | stores the said user identification information and the log | history browsed by the said user in the said shared information storage part The display program according to appendix 11, wherein the control is performed when there is shared information corresponding to a registration date and time after the last browsing date and time.

(Supplementary note 13) The request further includes information for instructing display of the electronic medical record of the recipient,
The processing to be output to the terminal outputs the browsing screen different from the display screen of the electronic medical record, and outputs the display screen after outputting the browsing screen. Display program.

(Additional remark 14) The said shared information is the information concerning the 1st attribute which shows the message exchanged between users, and the information concerning the 2nd attribute which shows the guidance history which the doctor performed with respect to the examinee. Including
The process for controlling the display of the browsing screen is the second attribute when the acquired attribute of the shared information is the second attribute, and a predetermined number of days have passed since the registration date and time of the shared information. 14. The display program according to any one of appendices 11 to 13, wherein an attribute display area is initially displayed on the terminal.

(Supplementary Note 15) The shared information further includes information regarding a third attribute indicating consultation for requesting medical care between clinical departments,
The process of controlling the display of the browsing screen is performed by initializing the display area of the third attribute in the terminal when the attribute of the acquired shared information is the third attribute and the status is unconfirmed. The display program according to appendix 14, wherein the display program is displayed.

10 network 20, 20a, 20b, 20c client 100 electronic medical record server 110 communication control unit 120 storage unit 121 browsing history table 122 bulletin board table 123 instruction history table 124 consultation table 130 control unit 131 determination unit 132 output unit 200 data center 201, 201a , 201b Server device 202, 202a, 202b Storage device 210 Network 220, 220a, 220b Client

Claims (7)

A communication control unit that accepts a request including the patient identification information for identifying the patient from a terminal operated by the user;
Shared information storage for storing the identification information of the examinee, the shared information registered for each attribute according to the content, the registration date and time when the shared information was registered, or the status indicating whether or not the shared information was browsed And
From the shared information storage unit, the shared information corresponding to the visitor identification information included in the request is acquired, and based on a comparison result between the condition set for each attribute and the registration date and time or status of the acquired shared information A determination unit that controls display of a browsing screen that displays the shared information by distinguishing display areas for each attribute;
An electronic medical record server, comprising: an output unit that outputs the browsing screen controlled by the determination unit to the terminal. Further comprising a browsing history storage unit for storing the user identification information and a history browsed by the user,
The determination unit performs the control when there is shared information corresponding to a registration date and time after the last browsing date and time of the user acquired from the browsing history storage unit in the shared information storage unit. The electronic medical record server according to claim 1. The request further includes information instructing display of the recipient's electronic medical record;
The electronic device according to claim 1, wherein the output unit outputs the browsing screen different from the display screen of the electronic medical record, and outputs the display screen after outputting the browsing screen. Medical record server. The shared information includes information relating to a first attribute indicating a message exchanged between users, and information relating to a second attribute indicating a teaching history performed by a doctor for the examinee,
When the attribute of the acquired shared information is the second attribute and a predetermined number of days or more have elapsed since the registration date and time of the shared information, the determination unit displays the display area of the second attribute The electronic medical record server according to any one of claims 1 to 3, wherein the electronic medical record server is initially displayed on a terminal. The shared information further includes information relating to a third attribute indicating consultation for requesting medical care between medical departments,
The determining unit is configured to cause the terminal to initially display a display area of the third attribute when the attribute of the acquired shared information is the third attribute and the status is unconfirmed. The electronic medical record server according to claim 4. A display method executed by a computer,
A request including the identification information for identifying a patient is received from a terminal operated by the user,
Shared information storage for storing the identification information of the examinee, the shared information registered for each attribute according to the content, the registration date and time when the shared information was registered, or the status indicating whether or not the shared information was browsed A shared information corresponding to the examinee identification information included in the request from the section, and based on a comparison result between a condition set for each attribute and a registration date or status of the acquired shared information Control the display of the browsing screen that displays the shared information by distinguishing the display area for each,
The display method controlled by the process for controlling the display of the browsing screen is output to the terminal. On the computer,
A request including the identification information for identifying a patient is received from a terminal operated by the user,
Shared information storage for storing the identification information of the examinee, the shared information registered for each attribute according to the content, the registration date and time when the shared information was registered, or the status indicating whether or not the shared information was browsed A shared information corresponding to the examinee identification information included in the request from the section, and based on a comparison result between a condition set for each attribute and a registration date or status of the acquired shared information Control the display of the browsing screen that displays the shared information by distinguishing the display area for each,
A display program for executing the process of outputting the browsing screen controlled by the process of controlling the display of the browsing screen to the terminal.

Images