JP6022206B2 - Information sharing system, information sharing server, and information sharing program - Google Patents

Description

  The present invention relates to an information sharing system, an information sharing server, and an information sharing program capable of providing a specialist's advice to a medical practitioner engaged in community medicine.

  In medical practice, a system has been proposed in which a plurality of doctors cooperate to make a diagnosis (see, for example, Patent Document 1). The system of Patent Document 1 collects information in a server and eliminates office procedures such as request slips, reports, bills, and film exchanges. However, each doctor treats and diagnoses at his own discretion and does not consider seeking advice from other doctors.

  When a doctor needs another examination or a specialist's opinion, conventionally, the symptom and progress are written from the patient's chart, and the examination and opinion are requested from another doctor in the form of a referral letter. The referral letter is to be delivered directly to another doctor by the patient.

JP 2005-165648 A

  In the conventional referral letter system, the doctor introduces another doctor whom he / she knows, so the practitioner cannot always obtain the optimum specialist's opinion and appropriate examination method.

Information sharing system of the present invention, the patient is registered in the information sharing server while electronic medical record and the link of the patient, the contributor terminal for viewing and writing comments on patients who were registered and registered projecting draft terminal set the period in which to comment on the case, select the Advisor terminal for the comment, and declare coordinator terminal the end of the comment, is selected from the coordinator terminal, comments about the registered cases of the projected draft terminal and Advisor terminal for accepting the registration of cases from the investment draft's terminal, along with the cases notified to the coordinator terminal or geographically close to the region matches the region of the post's terminal to the effect that has been registered, the adviser and extracts the terminal which is stored as a candidate of the terminal to display with local of the terminal to the coordinator terminal, the displayed end Notify coordinator terminal selected from the terminals of the registers the terminal which consent has been obtained of the selected terminal from the coordinator terminal Adviser terminal cases, Adviser terminal, the coordinator terminal and contributors disclosed to the period of time that is set the registered cases of projecting draft terminal to terminal, adviser terminal contributors terminal and advisor terminal comments written in the set period from the coordinator terminal, projecting draft terminal and co disclosed coordinator terminal, and Advisor terminal, contributor terminal and the coordinator terminal receives a comment Exit declaration after the consent of the end of the comment by the, to terminate adviser terminal, cases of post terminal and the coordinator terminal reading and the writing of comments An information sharing server.

The information sharing server of the present invention includes a case registration unit that accepts registration of a case from a contributor terminal in a state linked to a patient's electronic medical record, and that a case is registered in the case registration unit, the fact that the case has been registered A coordinator notifying unit for notifying a predetermined coordinator terminal in a region that matches or is geographically close to the region of the poster terminal, and a terminal that is stored as a candidate for a case advisor accepted by the case registration unit The information is displayed on the coordinator terminal together with the area of the terminal, and the advisor notification unit for notifying the advisor that the coordinator terminal has selected from the extracted terminals and the notification that the advisor has been selected. the terminal obtained the consent of the terminals having received the registers advisor terminal of the accepted cases of the case registration unit Advisor Noboru And parts, Adviser terminal, disclose the coordinator terminal and period set cases accepted the case registration unit to the post terminal, written advisor terminal, the coordinator terminal and contributor terminal to the set period advisor terminal registers the comment as a comment of the accepted cases of the case registration section, to disclose the post terminal and the coordinator terminal, advisor terminal, the comment termination declaration by author terminal and the coordinator terminal after acceptance of the end of the comment When received from the coordinator terminal, an advisor terminal , a contributor terminal, and a comment writing unit that terminates browsing of cases and writing of comments on the coordinator terminal are provided.

  In the information sharing server of the present invention, the predetermined coordinator terminal in the coordinator notification unit is a terminal determined according to a priority order predetermined for each coordinator terminal and the number of cases serving as the coordinator. May be.

  In the information sharing server according to the present invention, the predetermined coordinator terminal in the coordinator notification unit may be a terminal having a predetermined number or less of coordinators.

  In the information sharing server of the present invention, the advisor notifying unit may extract a terminal according to a priority order predetermined for each advisor terminal and the number of cases registered in the advisor terminal.

Information sharing program of the present invention is an information sharing program information sharing server performs, and case registration procedure for accepting registration of cases from projecting draft terminal while electronic medical record and the link of the patient, Case is registered and the coordinator notification procedure for the notification to the author geographically close region of the coordinator terminal or matches the region of the terminal that was, and extracts the terminal, which is stored as a candidate of the cases of the advisor that has been received in the previous Symbol cases registration procedure displaying the coordinator terminal with local of the terminal Te, extracted to the coordinator terminal selected from the terminals of the terminals, and Advisor notification procedure for notifying selected advisor, notification of the selected adviser and Advisor registration procedure a terminal acceptance is obtained of the terminal, and registers the advisor terminal of the patients who received, Adviser terminal, disclose the coordinator terminal and set the case to the post terminal duration, advisor terminal, advisor registered as the coordinator terminal and from author terminal the set period with the written comments Case Comments terminal, to disclose to the post's terminal and the coordinator terminal, Advisor terminal, and after the consent of the end of the comment by the author terminal and the coordinator terminal Ru received comments termination declaration from the coordinator terminal, Advisor terminal, contributor terminal and of the coordinator terminal This is a program for causing a computer to sequentially execute a comment writing procedure for ending case browsing and comment writing.

  According to the present invention, it is possible to select an optimal doctor from among specialists who give advice such as examination treatment to be introduced. Furthermore, it is possible to have a plurality of doctors who give advice, optimal treatment is performed, and medical division between general hospitals such as universities and practitioners becomes possible.

1 is a configuration example of an information sharing system according to a first embodiment. An example of a terminal information table is shown. An example of an advisor table is shown. It is a sequence diagram which shows an example of the information sharing method. An example of a case registration table is shown. It is a sequence diagram which shows an example of a case registration procedure. It is a figure which shows the method of storing image data. It is a figure which shows the structure of an authentication server.

  Embodiments of the present invention will be described with reference to the accompanying drawings. The embodiments described below are examples of the present invention, and the present invention is not limited to the following embodiments. In the present specification and drawings, the same reference numerals denote the same components.

(Embodiment 1)
FIG. 1 is an example of an information sharing system according to the present embodiment. The information sharing system according to the present embodiment includes an information sharing server 11, a secretariat terminal 12, an advisor terminal 13, a coordinator terminal 14, and a contributor terminal 15. The information sharing server 11 includes a case registration unit 21, a coordinator notification unit 22, an advisor notification unit 23, an advisor registration unit 24, a comment writing unit 25, and a terminal registration unit 27. Hereinafter, an example in which the information sharing system shares medical information will be described in detail.

  The secretariat terminal 12 is a terminal used by the general secretariat that operates the information sharing system, and a list in which the class of each terminal is defined as shown in FIG. Classes are, for example, board members who manage systems such as the General Secretariat, coordinators who coordinate community medicine, advisors who have expertise in specific cases, and contributors who deal with a wide range of cases such as general practitioners. . A doctor can be a contributor. These classes are determined by the board member and are registered in the terminal registration unit 27 by the board member.

  The terminal registration unit 27 further stores an advisor table for managing advisor advice objects. In the advisor table, as shown in FIG. 3, the advice target and the terminal ID that can be the advisor are described. The secretariat terminal 12 registers a terminal determined by the board member in the advisor table for each advice target.

  FIG. 4 shows an exemplary sequence of the information sharing system. The information sharing method according to the present embodiment includes a case registration procedure, a coordinator notification procedure, an advisor notification procedure, an advisor registration procedure, and a comment writing procedure in this order.

  In the case registration procedure, the poster terminal 15 registers the case in the information sharing server 11 (S101). The case registration unit 21 receives case registration from the poster terminal 15 and adds the case to the case registration table as shown in FIG. The case registration table stores a case, a contributor's terminal ID, a coordinator's terminal ID, an advisor's terminal ID, a status, and a comment in association with each other. The status describes the progress status such as continuing or ending.

  In the coordinator notification procedure, when a case is registered in the case registration unit 21, the coordinator notification unit 22 notifies the coordinator terminal 14 that a case has been registered (S102).

  In the advisor notification procedure, the advisor notification unit 23 extracts a terminal in which the case accepted by the case registration unit 21 is included in the advice target, and displays a list of the extracted terminals on the coordinator terminal 14. The coordinator terminal 14 selects the optimum advisor from the list of terminals displayed as advisor candidates while browsing the cases registered in the information sharing server 11 (S103). The advisor notifying unit 23 refers to the terminal information table and notifies the advisor of the selection to the address of the terminal selected by the coordinator terminal 14 (S104).

  In the advisor registration procedure, the advisor terminal 13 registers permission / inhibition of participation (S105). The advisor registration unit 24 receives an instruction from the advisor terminal 13 notified that the advisor has been selected, and registers the advisor terminal in the case advisor terminal 13 received by the case registration unit. When a predetermined number of users are registered, an advisor group is generated in the information sharing server 11.

  In the comment writing procedure, the advisor terminal 13 of the advisor group inputs advice on the registered case to the comment writing unit 25 (S106). The comment writing unit 25 registers the comment written from the advisor terminal 13 registered by the advisor registration unit 24 in the case registration unit 21 as a comment of the case accepted by the case registration unit 21.

  The comment writing unit 25 discloses the advice registered in the case registration unit 21 to the poster terminal 15 and the coordinator terminal 14 (S107). Thereby, the contributor terminal 15 browses the advice registered in the case registration unit 21 and writes a question or the like for the advice. On the other hand, the coordinator terminal 14 browses comments written by the advisor terminal 13 and the poster terminal 15 and confirms the convergence state of the opinion of the advisor.

  The comment writing unit 25 notifies the advisor terminal 13, the poster terminal 15, and the coordinator terminal 14 when a predetermined comment writing deadline approaches. The advisor terminal 13 and the poster terminal 15 notify the comment writing unit 25 whether or not to approve the termination. The comment writing unit 25 notifies the coordinator terminal 14 whether or not to approve the termination from the advisor terminal 13 and the poster terminal 15. The coordinator determines whether or not to finish writing the comment with reference to this notification. When the writing of the comment may be terminated, such as when the poster has approved the termination or all the advisors have acknowledged the termination, the coordinator terminal 14 notifies the comment writing unit 25 of the comment termination declaration. Thereby, the comment writing unit 25 receives the comment end declaration and ends the browsing of the case and the writing of the comment to the advisor terminal 13. At this time, the comment writing unit 25 also ends browsing of the case on the coordinator terminal 14.

  If it is not desirable to end the writing of the comment, such as the poster does not accept the termination or some of the advisors do not acknowledge the termination, the advisor terminal 13 or the poster terminal 15 does not accept the termination. This is written in the comment writing unit 25 or notified to the coordinator terminal 14. It is preferable that the comment writing deadline can be extended by the coordinator terminal 14, and the coordinator terminal 14 extends the comment writing deadline. It is preferred that the extension can be repeated until the coordinator determines that the discussion about the case is sufficient.

  When the coordinator terminal 14 does not notify the comment writing unit 25 of the comment end declaration and the comment writing deadline is not extended, the comment writing unit 25 automatically estimates that the comment end declaration has been notified from the coordinator terminal 14. At the end of the comment. As a result, the comment writing unit 25 ends the browsing of the case and the writing of the comment to the advisor terminal 13.

  This completes the basic operation of the information sharing system according to the present embodiment. Since the poster terminal 15 can browse the advice written in the information sharing server 11, the poster can use the registered advice for treatment.

  The information sharing server 11 may be realized by causing a computer to execute an information sharing program. The information sharing program is a program for causing a computer to sequentially execute each procedure of the information sharing method.

  In FIG. 1, only one secretariat terminal 12, contributor terminal 15, coordinator terminal 14, and advisor terminal 13 are shown to facilitate understanding of the invention. However, these are one or more arbitrary numbers. Further, in the tables shown in FIGS. 2, 3 and 5, the terminal ID is described as an example, but the name or name of the board member, contributor, coordinator, or advisor may be described instead of the terminal ID in these. Is possible. In this case, it is preferable that the name or name is linked with the terminal ID, and the address of the terminal ID is called when the name or name is selected.

  The information sharing system may further include a secretariat terminal for each region. In this case, the secretariat terminal for each region independently commissions the regional coordinator and advisor and registers them in the terminal registration unit 27. In this case, a region column is further added to the list in which the class of each terminal shown in FIG. 2 is defined. And it is preferable that the coordinator notification part 22 selects and notifies the coordinator terminal 14 of the area | region which corresponds with the area | region of the contributor terminal 15, or is geographically close.

(Embodiment 2)
In this embodiment, the transition of the case browsing state of each terminal will be described.
When the coordinator C1 is notified that the cases S2, S3, and S5 have been registered, the coordinator C1 can view the cases S2, S3, and S5. If the coordinator C1 agrees to be the coordinator for cases S2 and S3 but refuses to be the coordinator for case S5, the coordinator C1 cannot view the case S5.
Regarding the case S5, the fact that the case has been registered is notified to the coordinator C2 different from the coordinator C1, and if the coordinator C2 approves, the coordinator C2 becomes the coordinator of the case S5.

  When the advisor A1 is notified that the advisors of the cases S1 and S2 are selected, the advisor A1 can browse the cases S1 and S2. If the advisor A1 agrees to be the advisor for case S1, but refuses to be the advisor for case S2, the advisor A1 cannot view the case S2.

The contributor can view only the cases that he / she has registered.
For example, when the contributor D5 registers the case S5 and the case S7, the contributor D5 can browse only the case S5 and the case S7, and cannot browse other cases.

  Board members can view all cases at all times, but cannot be involved as coordinators or advisors.

  The terminal registered in the coordinator column in the case registration table can only be involved as a coordinator and cannot comment on advice. The same applies to terminals registered in the advisor column in the case registration table. The terminal can be involved only as an advisor and cannot select an advisor as a coordinator.

  These case browsing states can be set using a case registration table. For example, register the terminal ID in the contributor column at the time of registration of the case, register the terminal ID in the coordinator column of the case registration table when you agree to become the coordinator, and register the case when you agree to become the advisor Register in the advisor column of the table, and make sure that cases cannot be viewed without these registrations, except for board members.

If there is no request from the system side, all classes of terminals can use only the function of the contributor terminal 15 at the time of login, and therefore can only browse cases registered by themselves. Also, user authentication is performed at the time of login.
If you want to use the system as an advisor, log in to the advisor class after logging in to the contributor class. Login to the advisor class is possible for any terminal in which the advisor class is registered in the terminal information table. When logging into the advisor class, the system can be used as an advisor only for cases whose terminal ID is included in the case registration table. The same applies to the coordinator class and board members.

  Note that it is possible to log in to the coordinator class after logging into the advisor class, and then log into the board member class after logging into the coordinator class. In this case, the coordinator registers both the advisor and the coordinator in the class column of the terminal information table, and the board member registers all of the advisor, coordinator, and board member in the class column of the terminal information table.

  The method of authentication performed when logging in to the higher class may be the same for each class or may be different. By authenticating each time you log in to a higher class, it is possible to prevent false advice by a third party or registration of an unqualified doctor or researcher with an advisor.

(Embodiment 3)
In this embodiment, a specific example of a coordinator / advisor selection method will be described.
The poster terminal 15 registers the case in the information sharing server 11. When the poster terminal 15 registers a case, the information sharing server 11 selects a coordinator. Normally, the coordinator specified in the region is automatically selected. The information sharing server 11 entrusts the coordinator of case a to the coordinator terminal 14 using electronic mail and requests approval of the commission. The coordinator terminal 14 accesses the URI included in the mail and answers whether or not to accept it. If the coordinator terminal 14 accepts, the process proceeds to selection of an advisor, and if the coordinator terminal 14 does not accept, the coordinator terminal is reselected.

  In the reselection of the coordinator when the coordinator terminal 14 does not accept, the coordinator notifying unit 22 entrusts the coordinator of the case a to the coordinator terminal 14 that has not been entrusted with the case a, and requests the approval of the commission. . This is repeated until the consent of the commission is obtained.

  If the coordinator terminal 14 accepts, the terminal ID is registered in the coordinator column of the case registration table. The information sharing server 11 permits the coordinator terminal 14 to browse the case, and sends the case file name and the access key for browsing by e-mail. At this time, a URI for displaying the case file list may be sent together with the case file name. The case file name and the access key for browsing are preferably sent to different addresses, and the access key is preferably sent to the mobile terminal. After logging in as the coordinator, the coordinator terminal 14 selects the case file sent from the case list and inputs the sent access key.

If the combination of the selected case file and the access key is correct, the information sharing server 11 permits browsing of the case file and displays the case on the coordinator terminal 14. The coordinator terminal 14 accesses the information sharing server 11 and selects an appropriate advisor from the list of advisors. Here, the list of advisors displayed on the coordinator terminal 14 by the information sharing server 11 may be advisors selected based on expertise such as case information, or may be all advisors. Further, the coordinator terminal 14 may be configured to first select an advisor from the list in which the information sharing server 11 is always selected. If the coordinator terminal 14 cannot be selected from this list, the coordinator terminal 14 manually selects another search means. But you can. At this time, an answer deadline is set together with the advisor.
The advisor notification unit 23 commissions the advisor of the case a to the selected advisor terminal 13 and requests approval of the commission. The advisor terminal 13 replies whether or not to accept in consideration of the reply deadline.

If the advisor terminal 13 does not accept or the number of advisor terminals 13 for which consent has been obtained is less than a predetermined number, the advisor registration unit 24 notifies the coordinator terminal 14 that the advisor will be reselected. To do. The coordinator terminal 14 accesses the information sharing server 11 and selects a new appropriate advisor from the list of advisors.
The advisor notification unit 23 commissions the advisor of the case a to the newly selected advisor terminal 13 and requests the consent of the commission.

  When consent from the advisor terminal 13 is obtained and the number of the advisor terminals 13 reaches a predetermined number, an advisor group is generated. The comment writing unit 25 permits the advisor terminal 13 to obtain the consent to view the case, and sends the case file name and the access key for viewing by e-mail.

Here, a specific example of a combination of a case file name and a browsing access key will be described.
-Even in the same case, the coordinator terminal 14, the advisor terminal 13, and the contributor terminal 15 all have different access keys.
The same access key is shared by the coordinator terminal 14, the advisor terminal 13, and the poster terminal 15 for each case.
In this case, when the poster terminal 15 directly generates an access key, it is necessary to transfer the access key to members who can view it.
For each case, only the advisor terminal 13 shares the same access key.
The coordinator terminal 14, the advisor terminal 13, and the poster terminal 15 use the same access key for a specified period (for example, one month). When the specified period elapses, a new access key is sent from the information sharing server 11.
By not using all different access keys, it is possible to improve convenience when accessing the case of the coordinator terminal 14 that handles many cases.

  The advisor terminal 13 accesses the information sharing server 11, logs in, selects input of advice, selects a case file in charge from the case list, and inputs the sent access key. If the combination of the selected case file and the access key is correct, the information sharing server 11 permits addition of advice to the case file. The advisor terminal 13 inputs advice.

  The coordinator terminal 14 accesses the information sharing server 11 and, after logging in, selects browsing advice, selects a case file in charge from the case list, and inputs the sent access key. At this time, a URI for displaying the case may be input. The access key is preferably sent to the mobile terminal. If the combination of the selected case file and the access key is correct, the information sharing server 11 permits browsing of the case file. When the coordinator terminal 14 may browse the advice and finish writing the comment, the coordinator terminal 14 notifies the information sharing server 11 of the comment end declaration. By this comment end declaration, the advisor terminal 14 and the coordinator terminal 15 cannot view the case.

  When the advice is finished from the coordinator terminal 14, the information sharing server 11 notifies the poster by e-mail that the advice is finished.

(Embodiment 4)
The registered case information is disclosed to the advisor terminal 13 and coordinator terminal 14 of the case, but is preferably not disclosed to other advisor terminals 13 and coordinator terminals 14. Therefore, the information sharing system of the present embodiment is characterized in that access restrictions are provided in each terminal for each registered case.

For example, it is preferable that a case is encrypted at the time of case registration, a different access key is generated for each case, and only a person who has the access key can view and write a registered case.
In this case, the poster terminal 15 generates an access key and registers it in the information sharing server 11. The information sharing server 11 sends the access key only to terminals that have permission to view cases.
The access key is generated by the information sharing server 11, and the access key may be sent only to terminals that have permission to view cases via e-mail or the web. In the case of via the web, for example, an access key is displayed on the screen. The information sharing server 11 may delete the access key after sending the terminal.
The information sharing server 11 may not store the access key. In this case, the access key may be held only by the contributor who registered the case, the coordinator terminal 14 may also be held, and the advisor terminal 13 may also be held.

  The e-mail includes information that can identify the case together with the access key. For example, the file name used for the case file. Accordingly, if the case file name in the information sharing server 11 is not changed even after encryption, a user who has permission to view the case can view the case list. If the correspondence between the case file and the access key is not known, the case file cannot be viewed. In order to prevent this, it is preferable that an e-mail including an access key can be searched for by the case file name on the mail software. In order to maintain the link between the access key and the case file, it is preferable that the subject of the email is the case file name. Thus, if the mail list is sorted, it is possible to easily search for the access key of the case file. Also, rather than normal e-mails that launch e-mail software on the terminal and download and view e-mails, e-mails are viewed using https (HTTP over SSL / TLS), which encrypts and transfers information using a browser. It is preferable to use webmail because it is highly secure.

The access key usage restriction will be described.
The access key is not changed until the coordinator terminal 14 determines the end of the advice after the poster terminal 15 registers the case, and the poster terminal 12 that first registered the case accepts the termination. When the poster terminal 12 accepts the termination, the information sharing server 11 requests the poster terminal 15 to change the access key, and the poster terminal 12 changes or the information sharing server 11 changes the access key independently. When changing the access key, the information sharing server 11 decrypts the case with the old access key and encrypts the case with the new access key.

(Embodiment 5)
Depending on the procedure, it is preferable to set a time limit so that the poster can obtain advice as early as possible.
For example, when registering a case in step S101 described in the first embodiment, the contributor terminal 15 can specify the date and time for which advice is desired.
In step S105, if there is no registration of acceptance / rejection from the advisor terminal 13 after a certain period of time, it is preferable to perform step S103 again and the coordinator terminal 14 selects another terminal that functions as another advisor. .

  In step S106, if there is an advisor terminal 13 that has not entered advice even if the comment writing deadline is near, the comment writing unit 25 notifies the advisor terminal 13 that the comment writing deadline is near. Is preferred.

  In step S106, it is preferable that the coordinator terminal 14 can set the comment writing deadline in consideration of the advice status and the date and time the poster wants advice. The comment writing deadline may be a predetermined time from the time when the advisor group is generated, or may be a predetermined time from the time when the case registration unit 21 accepts registration of a case.

(Embodiment 6)
In the present embodiment, a configuration for selecting one coordinator from a plurality of coordinators will be described.
Coordinators are selected for each region. When there are a plurality of coordinators in the same area, priorities in each area are assigned to the coordinators in the terminal information table. In this case, the coordinator notifying unit 22 refers to the terminal information table, extracts a terminal ID in a region common to the region of the poster terminal 15, and selects a terminal ID having a higher priority from the extracted one. It is preferable that the priority order can be set from the secretariat terminal 12. The coordinator notifying unit 22 may change the priority order according to the busyness of the coordinator. The coordinator notification unit 22 may lower the priority order when the coordinator is busy, and return to the original priority order after the busy time. Good.

  The coordinator notification unit 22 may select the coordinator terminal so that the number of cases in charge is equal. For example, the coordinator notifying unit 22 refers to the case registration table, extracts the coordinator terminal in the area common to the area of the poster terminal 15, and counts the number of cases handled by each coordinator terminal from the extracted one. May be. A coordinator terminal with a high priority is selected from the coordinator terminals that have extracted a coordinator terminal whose number of cases registered in the case registration table exceeds a certain number from the extracted coordinator terminals. Select. Note that this certain number is preferably settable from the secretariat terminal 12. Also, the coordinator notifying unit 22 may change a certain number according to the busyness of the coordinator, and may decrease the fixed number when the coordinator is busy, and return to the original priority after the busy time. Good.

  The coordinator notification unit 22 may select a coordinator terminal for each case. For example, the keyword of the case in charge of the coordinator is stored in the terminal information table, and the coordinator notification unit 22 stores the keyword that matches the case registered in the case registration unit 21 from the coordinator terminals extracted in the region. The coordinator terminal that is being used is extracted. When there are a plurality of extracted coordinator terminals, the coordinator notifying unit 22 selects a coordinator terminal having a higher priority from among them.

  Further, the coordinator notification unit 22 may consider the priority order according to the experience value of the coordinator. For example, it is preferable to increase the priority of each case as the experience value of the coordinator increases. The experience value of the coordinator is, for example, the total number of cases handled by the coordinator terminal in each case in the past.

(Embodiment 7)
In the present embodiment, a configuration for extracting a plurality of advisors suitable for a case from a large number of advisors will be described.
Advisors are selected for each case. When there are a large number of coordinators in the same case or related cases, each advisor in the terminal information table is assigned a priority in each case. In this case, the advisor notification unit 23 refers to the advisor table, extracts the terminal ID of the advisor terminal 13 of the case that matches or is related to the case registered in the case registration unit 21, and has the highest priority from among the extracted terminal IDs. The advisor terminal 13 is selected. It is preferable that the priority order can be set from the secretariat terminal 12.

  Moreover, the advisor notification part 23 may change a priority according to the experience value of an advisor, and it is preferable to raise a priority as the experience value of an advisor becomes high. The experience value of the advisor is, for example, the total number of cases handled by the advisor terminal in the past. When a plurality of cases are registered in the advisor table, it is the total number of cases in each case.

  Further, the advisor notification unit 23 may change the priority according to the busyness of the advisor, lower the priority when the advisor is busy, and return to the original priority after the busy time. Good.

(Embodiment 8)
The information sharing system of this embodiment confirms whether a patient can register a medical record as case information to the information sharing server 11 when a practitioner wants to receive advice on treatment, and registers a case. FIG. 6 shows an example of a case registration procedure.

  The poster terminal 15 logs in to the information sharing server 11 (S201). A terminal authentication unit (not shown) of the information sharing server 11 confirms the information of the poster terminal 15 and performs authentication, and if the authentication is successful, displays a menu on the poster terminal 15 (S202). The terminal authentication unit authenticates each accessed terminal.

  The poster terminal 15 selects case registration from the menu (S203). The case registration unit 21 displays a case registration permission method on the poster terminal 15 (S204). The case registration permission method is a method for proving that a patient is permitted to register a case. As the permission method, for example, a facsimile may be used, a telephone number of a mobile phone may be used, or an e-mail may be used.

The contributor confirms the patient registration permission method with the patient (S205), and selects the method from the permission methods displayed on the poster terminal 15 (S206). The patient executes the selected permission method (S207). The case registration unit 21 displays a case input screen on the poster terminal 15 (S209). The poster terminal 15 inputs the case of the patient 16 (S210).
This completes the case registration procedure.

In step S206, an example of a permission method using a facsimile will be described as a case registration permission method.
When facsimile is selected as the case registration permission method, a patient name input screen is displayed on the poster terminal 15. The contributor inputs the patient's chart number and the patient's name to the contributor terminal 15.
Next, the consent form is displayed on the poster terminal 15 and the contributor confirms the contents of the consent form with the patient.
When the confirmation is completed, a printing method selection method is displayed on the poster terminal 15. The poster terminal 15 selects printing or facsimile on the poster's printer.
The information sharing server 11 creates and transmits a consent form including the poster information, patient chart number, and name. The contributor's printer or facsimile outputs a consent format. Here, the poster information, the patient chart number, and the name may be encoded into a matrix type two-dimensional code or a one-dimensional code. Hereinafter, in this embodiment, an example using a matrix type two-dimensional code will be described.
The patient confirms the consent form and signs the consent form in the consent form. The consent form is kept by the contributor.
The poster terminal 15 transmits a written consent form signed by facsimile to the information sharing server 11.
The information sharing server 11 confirms the matrix type two-dimensional code of the consent form and displays a confirmation screen of the consent form on the poster terminal 15.
This completes the permission method using the facsimile.

In step S206, an example of a permission method using a mobile phone will be described as a case registration permission method.
When a mobile phone is selected as the case registration permission method, a patient name input screen is displayed on the contributor terminal 15.
When the contributor inputs the patient's medical record number, name, and patient's mobile phone number to the contributor terminal 15, the consent form is displayed on the contributor terminal 15, and the contributor confirms the contents of the consent form to the patient.
When the confirmation is completed, a printing method selection method is displayed on the poster terminal 15. The poster terminal 15 selects printing or facsimile on the poster's printer.
The information sharing server 11 creates and transmits a consent form format including a matrix type two-dimensional code representing poster information, patient chart number, name, and mobile phone number. The contributor's printer or facsimile outputs a consent format.
The patient confirms the consent form and signs the consent form in the consent form. The consent form is kept by the contributor.
The poster terminal 15 transmits the approval to the information sharing server 11.
The information sharing server 11 calls the patient's mobile phone, and requests to press a designated key (for example, 1, #) when accepting the patient's response.
The patient presses the specified key. After confirming that the designated key has been pressed, the information sharing server 11 displays an acceptance confirmation screen on the contributor terminal 15.
This completes the permission method using the mobile phone.

In step S206, an example of a permission method using email as a case registration permission method will be described.
When electronic mail is selected as the case registration permission method, a patient name input screen is displayed on the poster terminal 15.
When the contributor terminal 15 inputs the patient's medical record number, name, and patient's e-mail address, the consent form is displayed on the contributor terminal 15, and the contributor confirms the contents of the consent form to the patient.
When the confirmation is completed, a printing method selection method is displayed on the poster terminal 15. The poster terminal 15 selects printing or facsimile on the poster's printer.
The information sharing server 11 creates and transmits a consent form including the poster information, patient chart number, name, and e-mail address. The contributor's printer or facsimile outputs a consent format. Here, the poster information, the patient chart number, and the name may be encoded into a matrix type two-dimensional code or a one-dimensional code.
The patient confirms the consent form and signs the consent form in the consent form. The consent form is kept by the contributor.
The poster terminal 15 transmits the approval to the information sharing server 11.
The information sharing server 11 transmits an e-mail to the patient's mobile phone. The patient opens the received e-mail, accesses a designated URI (Uniform Resource Identifier), and presses the accept button.
After confirming the patient's consent, the information sharing server 11 displays a confirmation screen for consent.
This completes the permission method using electronic mail.

(Embodiment 9)
In this embodiment, an example of registering a chart at the time of registering a case will be described. The case registration is preferably linked to the patient's electronic medical record. In the case of a patient who does not have an electronic medical record, it is preferable to register the electronic medical record in the information sharing server 11. In creating the electronic medical record, data may be input again, but it is preferable to digitize the paper medical record as it is in order to prevent an input error. In the present embodiment, a method for registering a paper chart as an electronic chart in the information sharing server 11 will be described.

(Method of storing image data)
A method for storing image data is shown in FIG.
First, the transparent case 100 is prepared in advance. A code 101 indicating the attribute information of the document 200 and characters 102 are attached to the transparent case 100, and then the document 200 is stored in the transparent case 100. In the electronic medical record system, the transparent case 100 is a clear file, the document 200 is a handwritten medical record, the code 101 is a matrix type two-dimensional code, and the attribute information includes the patient's name and its pseudonym, and the patient's name. Patient information such as date of birth. The transparent case 100 does not need to be prepared every time the document 200 is updated, and may be prepared at the first registration of the document 200.

  The document 200 is stored in the transparent case 100. In the electronic medical record system, the doctor or nurse puts the handwritten medical record in the clear file so that the patient information indicated by the characters 102 matches the patient information in the document 200 (step P1). Next, the document 200 stored in the transparent case 100 is set in the scanner 300. In the electronic medical chart system, a doctor or a nurse sets a handwritten medical chart sandwiched between clear files on the scanner 300 (step P2). Finally, the doctor or nurse presses the scan start button (step P3). The doctor or nurse may perform the processing up to Step P3 and may not perform the subsequent processing.

  The scanner 300 acquires a scan start instruction (step P4). Next, in the image conversion step, the scanner 300 converts the document 200 and the code 101 into image data in a state where the document 200 is stored in the transparent case 100 to which the code 101 indicating the attribute information of the document 200 is attached. In the electronic medical chart system, the scanner 300 converts the handwritten medical chart and the matrix type two-dimensional code into the electronic medical chart in a state where the handwritten medical chart is sandwiched between the clear files with the matrix type two-dimensional code indicating the patient information of the handwritten medical chart. To do. Next, the scanner 300 transmits the image data of the document 200 and the code 101 to the computer 400 (step P5). Next, the computer 400 executes authentication using an ID or a password for the authentication server 500 that approves storage of the image data of the document 200, and if the authentication is successful, transmits the image data of the document 200 and the code 101. (Step P6).

  In the attribute information setting step, the authentication server 500 identifies the image of the code 101 from the image data of the document 200 and the code 101, extracts the attribute information of the document 200 from the identified image of the code 101, and extracts the attribute of the extracted document 200 Information is set as attribute information of image data of the document 200. In the electronic medical record system, the authentication server 500 identifies the image of the matrix type two-dimensional code from the electronic medical record, extracts the patient information of the handwritten medical record from the identified image of the matrix type two-dimensional code (step P7), and extracts the handwritten data The patient information of the medical chart is set as the patient information of the electronic medical chart (Step P8).

  In the storage authentication step, the authentication server 500 approves storage of the image data of the document 200 when the attribute information set in the image data of the document 200 matches the attribute information of the document 200. In the electronic medical record system, the authentication server 500 approves storage of the electronic medical record (step P10) when the patient information set in the electronic medical record matches the patient information of the handwritten medical record (step P9). Specifically, the authentication server 500 confirms with the computer 400 whether these pieces of patient information match. Then, the computer 400 responds to the authentication server 500 as to whether or not the patient information matches in accordance with an instruction from a doctor having registration authority.

  In the document addition step, the authentication server 500 searches the image data of the document 200 before update based on the attribute information set in the image data of the document 200, and the image data of the document 200 after update is the document before update. Add to 200 image data. In the electronic medical record system, the authentication server 500 searches the electronic medical record before the update based on the patient information set in the electronic medical record, and adds the updated electronic medical record to the electronic medical record before the update (step P11).

  For the same patient, the same clear file is reused each time the handwritten medical chart is updated, so an electronic medical chart in which the same attribute information is set is generated. Therefore, the authentication server 500 can search the electronic medical record before the update based on the attribute information set in the electronic medical record after the update. The authentication server 500 can also add an updated electronic medical record in addition to the electronic medical record before updating as an additional form of the electronic medical record, and stores the updated electronic medical record instead of the electronic medical record before updating. It is also possible to create a new file and register the electronic medical record in a new file when registering for the first time.

  In the image conversion step and the attribute information setting step, it is only necessary to give a scan start instruction to the scanner 300 with the document 200 stored in the transparent case 100 and the document 200 stored in the transparent case 100. Therefore, it is not necessary to input the file name of the image data when converting the document 200 to the image data. In the storage authentication step, it is possible to store the image data after confirming whether or not the document 200 is stored in the transparent case 100 with the attribute information matched. In the document addition step, by using the automatic processing of the authentication server 500, the user does not need to search for the document 200 before update and add the updated document 200 to the document 200 before update.

  The transparent case 100 need only be prepared once and can be reused any number of times, and there is no need to attach the code 101 to the document 200 each time the document 200 is updated. Here, if the code 101 is attached to the document 200, the position of the code 101 is changed every time the document is updated, but the code 101 is attached to the transparent case 100. The position is not changed each time the document is updated. Therefore, the image of the code 101 can be automatically identified, and the recognition rate of the code 101 can be increased. Furthermore, even the document 200 created by hand or the document 200 created before introducing the document storage method can be easily digitized using the document storage method. .

(Configuration of authentication server)
The configuration of the authentication server 500 is shown in FIG. The authentication server 500 includes a content storage unit 501, a data communication unit 502, a code extraction unit 503, an attribute information setting unit 504, a content storage authentication unit 505, and a content storage addition unit 506. The content storage unit 501 stores image data and may be disposed in the authentication server 500 or may be disposed in a device other than the authentication server 500. The data communication unit 502 serves as an interface between the computer 400 and the authentication server 500 for authentication using ID or password and transmission of image data in step P6 and confirmation of attribute information match in step P9.

  The code extraction unit 503 identifies the image of the code 101 from the document 200 and the image data of the code 101 created in a state where the document 200 is stored in the transparent case 100 to which the code 101 indicating the attribute information of the document 200 is attached. Then, the attribute information of the document 200 is extracted from the identified image of the code 101. In the electronic medical record system, the code extraction unit 503 uses a matrix type two-dimensional code from an electronic medical record created with the handwritten medical record sandwiched between clear files to which a matrix type two-dimensional code indicating patient information of the handwritten medical record is attached. The patient information of the handwritten medical chart is extracted from the identified matrix type two-dimensional code image (step P7). The attribute information setting unit 504 sets the extracted attribute information of the document 200 as the attribute information of the image data of the document 200. In the electronic medical record system, the attribute information setting unit 504 sets the extracted patient information of the handwritten medical record as the patient information of the electronic medical record (step P8).

  The content storage authentication unit 505 approves storage of the image data of the document 200 when the attribute information set in the image data of the document 200 matches the attribute information of the document 200. In the electronic medical record system, the content storage authentication unit 505 approves the storage of the electronic medical record when the patient information set in the electronic medical record matches the patient information of the handwritten medical record (steps P9 and P10). The content storage / addition unit 506 searches the image data of the document 200 before the update based on the attribute information set in the image data of the document 200, and the image data of the document 200 before the update is searched for the image data of the document 200 after the update. Append to data. In the electronic medical record system, the content storage adding unit 506 searches the electronic medical record before update based on the patient information set in the electronic medical record, and adds the updated electronic medical record to the electronic medical record before updating (step P11). ).

  In the present embodiment, the code 101 indicating the attribute information of the document 200 is attached to the transparent case 100. However, in another embodiment, the code 101 indicating the attribute information that is changed each time the document 200 is updated is It may be attached to the document 200. The transparent case 100 is reused for each update, but the document 200 is created for each update. Therefore, the code 101 indicating the attribute information that is changed each time the document 200 is updated is not the transparent case 100 but the document. It is attached to 200. As attribute information that is changed each time the document 200 is updated, information on the date of update and the changed contents can be given.

  In the image conversion step, the scanner 300 converts the document 200 and the code 101 into image data in a state where the code 101 indicating the attribute information that is changed each time the document 200 is updated is attached to the document 200. The code extraction unit 503 identifies the image of the code 101 from the document 200 and the image data of the code 101 created with the code 101 indicating the attribute information changed every time the document 200 is updated. Then, the attribute information of the document 200 is extracted from the identified image of the code 101.

  The image data to be stored may be image data of only the document 200, or may be image data of both the document 200 and the code 101. When the image data of only the document 200 is stored, the image data of the code 101 is deleted from the image data of the document 200 and the code 101, and the image data of only the document 200 can be browsed. When both the image data of the document 200 and the code 101 are stored, the image data can be easily stored.

  In the present embodiment, the computer 400 performs authentication with the authentication server 500 using an ID or a password. However, in another embodiment, the mobile phone associated with the computer 400 transmits the ID or password to the authentication server 500. Authentication using a password or the like may be performed. The authentication server 500 associates the computer 400 and the mobile phone, and requests the mobile phone for authentication when the computer 400 requests permission to transmit image data. Since the mobile phone and the user are associated with each other on a one-to-one basis, the security of authentication can be enhanced when the mobile phone executes authentication with respect to the authentication server 500.

  The present invention is not limited to the medical industry and can be applied to an introduction system for collecting arbitrary advice and comments.

11: Information sharing server 12: Secretariat terminal 13: Advisor terminal 14: Coordinator terminal 15: Contributor terminal 16: Patient 21: Case registration unit 22: Coordinator notification unit 23: Advisor notification unit 24: Advisor registration unit 25: Comment writing Unit 27: Terminal registration unit 100: Transparent case 200: Document 300: Scanner 400: Computer 500: Authentication server 101: Code 102: Character 501: Content storage unit 502: Data communication unit 503: Code extraction unit 504: Attribute information setting unit 505: Content storage authentication unit 506: Content storage addition unit

Claims (5)

A case was registered in the information sharing server in a state where the electronic medical record and the link of the patient, and the contributor terminal for reading and writing of comments about the cases registered,
Set the period in which to comment on the registered cases of the projected draft terminal, select the Advisor terminal for the comment, and declare coordinator terminal the end of the comment,
Is selected from the coordinator terminal, and Advisor terminal for comment about the registered cases of the projected draft's terminal,
Accept the registration of the cases from the investment draft's terminal, along with the cases notified to the coordinator terminal or geographically close to the region matches the region of the post's terminal to the effect that has been registered, it is stored as a candidate of the Adviser terminal co over displayed on coordinator terminal with local of the terminal to extract your terminal, it notifies the coordinator selected terminal from the terminal of the displayed terminal, acceptance of terminals selected from the coordinator terminal the resulting terminal registered cases of Adviser terminal, Adviser terminal, disclose the coordinator terminal and period set the registered cases of projecting draft terminal to post terminal, Adviser terminal contributors terminal and discloses a comment written in the set period from the coordinator terminal advisor terminal, the projecting draft terminal and coordinator terminal, advice Terminal, when receiving the post terminal and comment-end declaration after the consent of the end of the comment by the coordinator terminal, and information sharing server to terminate Adviser terminal, cases of post terminal and the coordinator terminal reading and the writing of comments,
An information sharing system comprising: A case registration unit that accepts case registration from the poster terminal in a state linked to the patient's electronic medical record ;
When a case is registered in the case registration unit, a coordinator notifying unit for notifying a predetermined coordinator terminal in a region that matches or is geographically close to the region of the poster terminal , that the case has been registered,
The terminal stored as a candidate for the adviser of the case accepted by the case registration unit is extracted and displayed on the coordinator terminal together with the area of the terminal, and from the extracted terminal to the terminal selected by the coordinator terminal to the advisor An advisor notifying section for notifying that it has been selected,
An advisor registration unit for registering a terminal that has received consent among the terminals that have been notified that the advisor has been selected, to the advisor terminal of the case accepted by the case registration unit;
Adviser terminal, disclose the coordinator terminal and period set cases accepted the case registration unit to the post terminal, advisor terminal, the comments written in the set period from the coordinator terminal and contributor terminal wherein Join to Advisor terminal as of the accepted cases of comment cases registration unit, to disclose to the post's terminal and the coordinator terminal, Advisor terminal, after posted by terminal and comments of termination by the coordinator terminal consent comment Exit declaration from the coordinator terminal When receiving, a comment writing unit that terminates browsing of cases and writing of comments on the advisor terminal , the poster terminal and the coordinator terminal ,
An information sharing server comprising: The predetermined coordinator terminal in the coordinator notification unit is:
It is a terminal determined according to the priority order determined in advance for each coordinator terminal and the number of cases serving as the coordinator, or
The information sharing server according to claim 2, wherein the number of cases serving as a coordinator is a terminal having a predetermined number or less.   4. The information sharing server according to claim 2, wherein the advisor notifying unit extracts a terminal according to a priority order predetermined for each advisor terminal and the number of cases registered in the advisor terminal. 5. . An information sharing program executed by the information sharing server,
And case registration procedure that accepts the registration of the cases from the investment draft's terminal in a state where the electronic medical record and the link of the patient,
And the coordinator notification procedure for example diseases notified to the geographically close region of the coordinator terminal or matches the region of the post's terminal to the effect that has been registered,
And extracts the terminal which is stored as a candidate of cases advisors accepted in the previous SL patient registration procedure displays the coordinator terminal with local of the terminal, the extracted selected terminal from the coordinator terminal of the terminals, advisor An advisor notification procedure for notifying that it has been selected,
A terminal acceptance is obtained of the terminal which has received the notification of the selected Adviser, and Advisor registration procedure for registering the advisor terminal of said case,
Adviser terminal, disclose the coordinator terminal and set the case to the post terminal duration, advisor terminal, registered as the coordinator terminal and from author terminal the set period with the written comments Case Comments Advisor terminal, to disclose to the post's terminal and the coordinator terminal, Advisor terminal, and after the consent of the end of the comment by the author terminal and the coordinator terminal Ru received comments termination declaration from the coordinator terminal, Advisor terminal, contributor terminal and the coordinator terminal Comment writing procedure to finish browsing of cases and writing of comments,
Information sharing program for causing a computer to execute in order.

Images