Medical support method and medical support device
The medical support method and device address the compensation gap in medical consultation systems by calculating compensation based on usage status, enhancing the quality of medical care through incentivizing specialist participation and transparent payment mechanisms.
Patent Information
- Application Number
- PCT/JP2024/020491
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-07-12
- Filing Date
- 2024-06-05
- Publication Date
- 2025-01-16
AI Technical Summary
Conventional systems for medical consultation between attending physicians and specialists lack an effective mechanism for compensating specialists, which hinders the widespread use of specialist knowledge and thereby affects the quality of medical care.
A medical support method and device that provide a consultation environment between attending physicians and specialists, calculating and managing compensation based on usage status, allowing for transparent payment systems that incentivize specialist participation.
The solution promotes the widespread use of specialist knowledge, improving the quality of medical care by ensuring fair compensation and efficient consultation processes.
Smart Images

Figure JP2024020491_16012025_PF_FP_ABST
Abstract
Description
Medical support method and medical support device
[0001] The present invention relates to a medical support method and a medical support device, and more particularly to a medical support method and a medical support device that support the transmission of consultation details from a primary care physician to a specialist.
[0002] There are cases where a patient's doctor is required to provide medical care in a field other than his or her specialty, and in such cases, the doctor may need the advice of a specialist.
[0003] Regarding the above-mentioned situation, Japanese Patent Laid-Open Publication No. 2022-040689 (Patent Document 1) discloses a system for a non-specialist attending physician to seek advice from an external specialist. In this system, a chat room is opened for use in consultations. The attending physician uses the chat room via a server to send the consultation content to the specialist. In response, the specialist uses the chat room via the server to send a response to the consultation content to the attending physician. This allows the attending physician to refer to the response from the specialist and perform treatment or consideration.
[0004] Japanese Patent Application Laid-Open No. 2022-040689
[0005] In the above-mentioned system, the compensation paid to specialists needs to be transparent because it is a payment for medical care. However, in conventional technology, the payment mechanism for specialists has not been fully considered. Establishing a payment mechanism is expected to increase the incentive for specialists to participate in the above-mentioned system and promote their participation in the system. Promoting the participation of specialists in the above-mentioned system is expected to encourage the widespread use of specialist knowledge, which is expected to lead to an improvement in the quality of medical care provided.
[0006] The present disclosure has been devised in light of the above-mentioned circumstances, and its purpose is to provide technology that promotes widespread use of the knowledge of specialists, thereby improving the quality of medical care.
[0007] A medical support method according to one aspect of the present disclosure is a medical support method executed by a computer capable of communicating with a primary physician terminal and multiple specialist physician terminals, and includes the steps of providing a consultation environment between the primary physician and the specialist physician, and calculating a fee to be paid to the specialist physician depending on the usage status of the consultation environment.
[0008] A medical support device according to one aspect of the present disclosure includes a communication interface, a processor capable of communicating with a first terminal operated by a primary physician and a second terminal operated by a specialist via the communication interface, and a memory for storing a program, and the program, when executed by the processor, causes the processor to perform the steps of providing a consultation environment between the primary physician and the specialist, and calculating a fee to be paid to the specialist depending on the usage status of the consultation environment.
[0009] According to one aspect of the present disclosure, a technique is provided for promoting widespread use of specialist knowledge, thereby improving the quality of medical care.
[0010] 6 is a diagram illustrating a schematic configuration of a medical support system 1 according to an embodiment of the present disclosure. FIG. 7 is a diagram illustrating a hardware configuration of a server 20. FIG. 8 is a diagram illustrating an example of the data structure of a user database. FIG. 9 is a diagram illustrating an example of the data structure of a specialist database. FIG. 10 is a diagram illustrating an example of the data structure of a consultation database. FIG. 11 is a diagram illustrating an example of a consultation screen. FIG. 12 is a diagram illustrating an example of the screen of FIG. 6 with consultation details entered. FIG. 13 is a flowchart of a main routine performed by a system operation company 200. FIG. 14 is a flowchart of a subroutine for medical collaboration (step S2). FIG. 15 is a flowchart of a subroutine for point allocation (step S3). FIG. 16 is a flowchart of a subroutine for payment (step S4).
[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and description thereof will not be repeated.
[0012] 1 is a diagram schematically illustrating a configuration of a medical support system 1 according to an embodiment of the present disclosure. The medical support system 1 supports a primary care physician 101 in consulting with a specialist 300 regarding the diagnosis and / or treatment of a patient.
[0013] More specifically, in the medical support system 1, a consultation regarding a patient's medical examination and / or treatment from a primary care physician 101 in a medical institution 100 is transferred to a specialist 300 via a system operation company 200. The consultation content may be transferred as is or may be processed before being transferred. A disease suffering from the patient may be predicted using a disease prediction model based on the consultation content, and the predicted disease and the consultation content may be transferred together to the specialist. The specialist 300 provides the primary care physician 101 with a response to the consultation content via the system operation company 200 or directly. The system operation company 200 provides the primary care physician 101 and the specialist 300 with the mechanisms of the medical support system 1, thereby providing a consultation environment between the primary care physician 101 and the specialist 300. The consultation environment may be one that allows direct communication, such as a chat room.
[0014] The number of medical institutions 100, attending physicians 101, and specialists 300 included in the medical support system 1 is not limited to those shown in Fig. 1. There may be one or more medical institutions 100, attending physicians 101, and specialists 300.
[0015] The system operation company 200 receives payment of the system usage fee from the medical institution 100 and grants a given amount of points to the medical institution 100. The attending physician 101 transmits the details of the consultation with the specialist 300 to the system operation company 200. The system operation company 200 forwards the details of the consultation to the specialist 300. The system operation company 200 subtracts an amount of points according to the details of the consultation from the points owned by the medical institution 100 to which the attending physician 101 belongs, and pays compensation (consultation fees) to the specialist 300. The system operation company 200 forwards the response to the above consultation details from the specialist 300 to the attending physician 101.
[0016] The medical institution 100 may purchase points in advance from the system operation company 200, and the attending physician 101 of the medical institution 100 may use the points to transmit consultation contents to the system operation company 200. Since the number of specialists registered as specialists 300 in the medical support system 1 is finite, the number of answers that can be provided in the medical support system 1 within a certain period of time is also finite. By limiting the upper limit of the number of points that can be sold within a certain period of time to correspond to the number of answers that can be provided within the certain period of time, the medical support system 1 can guarantee that the attending physician 101 will transmit the amount of consultation contents that corresponds to the number of points granted to the medical institution 100 to which the attending physician 101 belongs.
[0017] In the medical support system 1, the amount of compensation and working hours (available days and times) of the specialist 300 are managed by the system operation company 200. Furthermore, regarding participation in the medical support system 1, the system operation company 200 only needs to enter into a contract with the specialist 300, and the medical institution 100 does not need to enter into a direct contract with the specialist 300. As a result, by using the medical support system 1, the medical institution 100 can connect the attending physician 101 belonging to the medical institution 100 with the specialist 300 without having to manage various aspects of the specialist 300 or enter into a direct contract with the specialist 300.
[0018] In one implementation example, the transfer of consultation details, management of points for the medical institution 100, and payment of fees to the specialist 300 are performed by a server 20 of a system operation company 200. The server 20 is an example of a medical support device.
[0019] 2 is a diagram showing the hardware configuration of the server 20. The server 20 includes an input / output I / F (interface) 21, a CPU (central processing unit) 22, a RAM (random access memory) 23, a ROM (read-only memory) 24, and a storage device 25. The input / output I / F 21, the CPU 22, the RAM 23, the ROM 24, and the storage device 25 are connected to a bus 26.
[0020] The input / output I / F 21 is realized by, for example, a network interface, and functions as a communication interface for communication between the server 20 and external devices (a terminal operated by the attending physician 101 and a terminal operated by the specialist physician 300).
[0021] The CPU 22 executes a given program stored non-temporarily in the storage device 25 on the RAM 23. This allows the server 20 (system operation company 200) to perform the processes described herein. The programs executed by the CPU 22 may be stored in the ROM 24.
[0022] An operation unit 27 and a display unit 28 are connected to the bus 26. The operation unit 27 is an input interface such as a keyboard and / or a mouse. The display unit 28 is a display device such as a monitor.
[0023] The storage device 25 stores various data used in the medical support system 1. The stored data includes a user database, a specialist database, and a consultation database. The data structure of each database will be described below.
[0024] [User Database] Fig. 3 is a diagram showing an example of the data structure of the user database. The user database includes data related to the medical institution 100. More specifically, as shown in Fig. 3, the user database includes five items ("medical institution," "prefecture," "points," "user ID," and "password"). In the user database, the data in each row is associated with each other.
[0025] "Medical institution" represents information that identifies each medical institution. In Fig. 3, "H01" is an example of an ID that represents a certain medical institution.
[0026] "Prefecture" represents the prefecture with which each medical institution is associated. In Figure 3, "Kyoto" is an example of a prefecture with which the medical institution identified by ID "H01" is associated. In one implementation example, each medical institution is associated with the prefecture in which the medical institution is located.
[0027] "Points" represents the amount of points granted to each medical institution. In this embodiment, when the attending physician transmits the consultation details to the system operation company 200, the attending physician consumes the medical institution to which the attending physician belongs. In this sense, the amount of points granted to the medical institution is an example of the amount of points granted to the attending physician.
[0028] The "user ID" represents an ID assigned to each of one or more attending physicians belonging to each medical institution. In Fig. 3, a user ID "1001" assigned to one attending physician 101 and a user ID "1002" assigned to another attending physician 101 are shown.
[0029] The "password" indicates the password registered for each user ID. The attending physician 101 uses the user ID assigned to the attending physician 101 and the password registered for the attending physician 101 to use the medical support system 1.
[0030] [Specialist Database] Figure 4 is a diagram showing an example of the data structure of the specialist database. The specialist database includes data related to specialists 300. More specifically, as shown in Figure 4, the specialist database includes 12 items ("Specialty," "Specialist ID," "Remittance Information," "Name," "Affiliation," "Prefecture," "Available Days and Times," "Subspecialty," "Comments," "Compensation Information," "Shortest Response Period," and "Earned Points"). In the specialist database, the data in each row is associated with each other.
[0031] "Specialty" indicates the type of specialist. In FIG. 4, "infectious diseases (specialist)" is shown as an example of the type of specialist.
[0032] The "specialist ID" indicates the ID assigned to each specialist 300. In FIG. 4, two specialists (a specialist assigned with a specialist ID "0001" and a specialist assigned with a specialist ID "0002") are shown.
[0033] "Remittance information" indicates information (for example, a bank account number) used to remit money to each specialist 300. In Figure 4, the account number "BA01" is shown as the remittance information for specialist ID "0001," and the account number "BA02" is shown as the remittance information for specialist ID "0002."
[0034] "Name" indicates the name of each specialist 300. In Fig. 4, "AAA" is shown as the name of specialist ID "0001", and "BBB" is shown as the name of specialist ID "0002".
[0035] "Affiliation" indicates the organization to which each specialist 300 belongs. The organization may be, for example, a medical institution or a medical association.
[0036] "Prefecture" represents the prefecture associated with each specialist 300. In one implementation example, the prefecture designated by each specialist 300 is registered as the "Prefecture."
[0037] The "available days and times" indicate the days and times when each specialist 300 is available to provide medical care as a specialist within the medical support system 1. In one implementation example, the information registered as the "available days and times" of each specialist 300 is specified by each specialist 300.
[0038] The "subspecialty" represents the field of expertise of each specialist 300. In one implementation example, the "subspecialty" includes the medical department of each specialist 300 and is provided to the attending physician 101 along with the type of specialist indicated as the "specialty."
[0039] "Comments" indicates comments about the consultation registered by each specialist 300. "Compensation information" indicates the amount of compensation required for each specialist 300 to respond to one consultation. The amount of compensation required may be specified by the specialist 300, or may be specified by a person in charge of the medical support system 1, or may be updated to increase according to the number of times the specialist 300 has responded to consultations in the medical support system 1 (number of experiences).
[0040] As the amount of compensation required, multiple amounts may be registered according to the period required for the response. More specifically, as shown for the specialist ID "0002" in Figure 4, if the response period is "within one day," the amount of compensation required may be 200 P (points), if the response period is "within five days," the amount of compensation required may be 100 P, and if the response period is "within seven days," the amount of compensation required may be 70 P.
[0041] The "shortest response time" represents the shortest time required for each specialist 300 to respond to the consultation content after receiving the consultation content. In one implementation example, the "shortest response time" is specified by each specialist 300.
[0042] "Earned points" indicates the points that will be given to each specialist 300 by answering the consultation content or by receiving the consultation content transferred to him / her.
[0043] [Consultation Database] Fig. 5 is a diagram showing an example of the data structure of the consultation database. The consultation database includes data related to the content of consultations handled in the medical support system 1. More specifically, as shown in Fig. 5, the consultation database includes five items ("Consultation ID", "Consultation Date and Time", "Points", "Consultant", and "Specialist"). In the consultation database, the data in each row are associated with each other.
[0044] "Consultation ID" represents the ID assigned to each consultation content. "Consultation date and time" represents the date and time when the system operation company 200 (server 20) received the consultation content from the attending physician 101. "Points" represents the amount of points required for the consultation content. "Consultant" represents the ID of the attending physician 101 who sent the consultation content. "Specialist" represents the ID of the specialist physician 300 to whom the consultation content will be transferred.
[0045] Figure 5 shows an example in which the consultation content assigned with the consultation ID "C01" was sent from the attending physician 101 with user ID "1008" to the system operation company 200 at 10:05 on June 1, 2023, and then sent from the system operation company 200 to the specialist 300 with specialist ID "0007."
[0046] [Screen Display] Fig. 6 is a diagram showing an example of a consultation screen. A screen 600 in Fig. 6 is displayed on the display of a terminal operated by the attending physician 101.
[0047] 6 includes an area 610 and an area 620. The area 610 mainly displays information used for inputting consultation details. The area 620 mainly displays information related to the specialist 300.
[0048] More specifically, area 610 includes columns 611 to 616. In column 611, text about the consultation is entered. In column 612, the patient's medical record information is entered. In column 613, the first candidate for the patient's suspected disease name is entered. In column 614, a comment about the disease name entered in column 613 is entered. In column 615, the second candidate for the patient's suspected disease name is entered. In column 616, a comment about the disease name entered in column 615 is entered.
[0049] Area 620 includes tabs 621 and 622. Each of tabs 621 and 622 represents information about one specialist 300. When information about multiple specialists 300 is provided to the attending physician 101, the area 620 displays as many tabs as the number of specialists 300. That is, in the example of FIG. 6 , information about two specialists 300 is provided.
[0050] Each of the tabs 621 and 622 includes a field 621X, 622X that displays the name of the tab. The name of the tab is configured by the name and affiliation of the specialist 300 to which the tab corresponds. More specifically, the field 621X of the tab 621 displays the name "AAA" and the affiliation "aaa." This means that the tab 621 provides information on the specialist 300 identified by the name "AAA." The field 622X of the tab 622 displays the name "BBB" and the affiliation "bbb." This means that the tab 622 provides information on the specialist 300 identified by the name "BBB."
[0051] In the area 620, one of the tabs is selected, and the information included in the selected tab (detailed information about the specialist 300) is displayed.
[0052] 6, the tab 622 is selected. The tab 622 includes columns 622A, 622B, and 622C in addition to a column 622X.
[0053] Column 622A displays the amount of compensation specified by the specialist 300's "compensation information." Column 622A provides the attending physician 101 with compensation information. In the medical support system 1, the amount of compensation does not need to be set for each specialist 300, but may be set in other ways, such as for each consultation content. Column 622B displays information specified by the specialist 300's "available days and times." Column 622C displays information registered as the specialist 300's "comments."
[0054] Tab 622 may further display other types of information (such as "Specialty," "Specialist ID," "Name," "Affiliation," "Prefecture," "Subspecialty," "Compensation Information," and / or "Shortest Response Period") registered in the specialist database (Figure 4) in addition to "Remittance Information" and "Earned Points."
[0055] When tab 621 is selected, tab 621 displays information about specialist "AAA" that has one or more items that are the same as the items included in the information about specialist "BBB" displayed in tab 622 in Figure 6.
[0056] Area 620 further includes a field 623. Field 623 is used to specify a response period. In one implementation, field 623 specifies the response period in a pull-down menu.
[0057] The screen 600 further includes a button 630. By operating the button 630, the attending physician 101 transmits the consultation details input on the screen 600 to the specialist 300 via the system operation company 200.
[0058] Fig. 7 is a diagram showing an example of the screen of Fig. 6 in which the consultation content has been input. In the response period of Fig. 7, compared to the screen 600 of Fig. 6, the consultation content has been input in a field 611, and medical record information has been input in a field 612.
[0059] The attending physician 101 inputs the consultation content in field 611. The attending physician 101 may further input the patient's medical record information in field 612, and may also input information in each of fields 613 to 616. The attending physician 101 selects one of one or more tabs displayed in area 620 to select one specialist 300 as the destination of the consultation content. The attending physician 101 specifies a response period in field 623. When button 630 is operated in this state, the system operation company 200 transfers the information entered in area 610, including field 611, to the specialist 300 selected in area 620. At this time, the response period specified in field 623 is also transferred to the specialist 300.
[0060] In the medical support system 1, the attending physician 101 can select multiple specialists 300 as destinations for the consultation content. In this case, the system operation company 200 transfers the consultation content to all selected destinations.
[0061] [Processing Flow] (Main Routine) Next, a description will be given of the processing carried out by the system operation company 200. FIG.
[0062] The process of Fig. 8 is performed by the server 20. More specifically, the CPU 21 executes a given program (for example, a system management program), causing the server 20 to perform the process shown in Fig. 8 as a process corresponding to the given program. In one implementation example, the server 20 starts the process upon startup.
[0063] 8, in step S1, server 20 determines whether or not there has been access from an external terminal (a terminal operated by attending physician 101 or a terminal operated by specialist 300). If server 20 determines that there has been access (YES in step S1), it proceeds to step S2; otherwise, it proceeds to step S3.
[0064] In step S2, the server 20 performs medical cooperation, the details of which will be described later with reference to the flowchart of the subroutine in FIG.
[0065] In step S3, the server 20 awards points. Details of the points awarding process will be described later with reference to the flowchart of the subroutine in FIG.
[0066] In step S4, the server 20 performs the payment. Details of the payment will be described later with reference to the subroutine flowchart in Figure 11. After that, the server 20 returns control to step S1.
[0067] (Access to Server 20) As described above, the terminal operated by the attending physician 101 accesses the server 20, and the terminal operated by the specialist physician 300 also accesses the server 20. Specific situations of each access will be described.
[0068] When the attending physician 101 needs a response to a consultation, the attending physician 101 uses a terminal to access the server 20. In one implementation example, the attending physician 101 uses the terminal to browse a consultation website provided by the server 20. To input the consultation content, the attending physician 101 enters a user ID and password into the consultation website and operates the "Send" button on the consultation website. This causes the user ID and password to be sent to the server 20. The server 20 recognizes access using the user ID and password implemented in this manner as "access for consultation."
[0069] The specialist 300 accesses the server 20 to send a response to the consultation content to the attending physician 101. In one implementation example, the server 20 may attach a URL to which the response will be sent when transferring the consultation content to a terminal operated by the specialist 300. The specialist 300 accesses the URL using the terminal. The server 20 recognizes this type of access as an "access for response."
[0070] (Medical Cooperation) Fig. 9 is a flowchart of the subroutine of medical cooperation (step S2). The details of medical cooperation in step S2 will be described with reference to Fig. 9.
[0071] In step S200, server 20 determines whether the access detected in step S1 (FIG. 8) is an access for consultation. If server 20 determines that the access detected in step S1 is an access for consultation (YES in step S200), control proceeds to step S202; otherwise (NO in step S200), control proceeds to step S218.
[0072] In step S202, the server 20 checks the pair of user ID and password included in the access detected in step S1 against pairs of user ID and password registered in the user database (FIG. 3).
[0073] In step S204, the server 20 identifies, as the target medical institution, the medical institution located in the same row as the user ID and password pair included in the access detected in step S1 in the user database (FIG. 3).
[0074] In step S206, the server 20 displays a consultation screen on the consultation website on the terminal (terminal of the attending physician 101) from which the access detected in step S1 occurred. As described with reference to Figures 6 and 7, the attending physician 101 inputs the consultation content into the consultation screen and transmits the consultation content to the server 20 (system operation company 200).
[0075] In step S208, the server 20 acquires the consultation content from the attending physician 101. In step S210, the server 20 specifies the number of points required for the consultation content acquired in step S208.
[0076] In one implementation example, the server 20 identifies a specialist selected in the acquired consultation content, and then identifies the number of points registered as "compensation information" for the identified specialist in the specialist database as the number of points required for the consultation content.
[0077] In another implementation example, the server 20 identifies the amount of points required for the consultation content as the amount of points from among two or more types of points registered as the "compensation information" for the identified specialist, which corresponds to the response period specified for the consultation content. For example, in the specialist database of FIG. 4, three types of amounts (200 P for response period "within 1 day," 100 P for response period "within 5 days," and 70 P for response period "within 7 days") are registered for specialist "0002." In this case, if the specified response period is "within 5 days," the identified amount of points is 100 P. Also, if the specified response period is "within 3 days," the identified amount of points is 200 P.
[0078] In yet another implementation example, the server 20 specifies the number of points required for a consultation content as the number of points that is uniformly set for each consultation content in the medical support system 1.
[0079] In step S212, the server 20 adjusts the points of both the medical institution and the specialist according to the amount specified in step S210. More specifically, the server 20 subtracts the amount specified in step S210 from the number of points in the user database for the target medical institution specified in step S204. In addition, the server 20 adds the amount specified in step S210 to the earned points in the specialist database for the specialist 300 specified in the consultation content acquired in step S208.
[0080] In step S214, the server 20 transfers the consultation content acquired in step S208 to the specialist 300 selected for the consultation content.
[0081] In step S216, the server 20 generates consultation information corresponding to the transfer in step S214 and registers the consultation information in the consultation database. In one implementation example, the server 20 generates a new consultation ID for the transferred consultation content and generates the consultation information by associating the consultation ID with the date and time when the consultation content was received from the attending physician 101, the amount of points identified in step S210, the user ID of the attending physician 101 who sent the consultation content, and the specialist ID of the specialist 300 selected as the destination of the consultation content. Thereafter, the server 20 returns control to FIG. 8.
[0082] On the other hand, if the access detected in step S1 (FIG. 8) is a reply access, the server 20 advances the control from step S200 to step S218.
[0083] In step S218, the server 20 identifies the consultation ID corresponding to the access for answer detected in step S1. In one implementation example, the server 20 generates a URL in association with the consultation content. The URL may include information identifying the consultation ID associated with the consultation content. The server 20 then transfers the consultation content to the specialist 300 and transmits the URL. The specialist 300 enters an answer on a screen displayed by accessing the URL. The server 20 identifies the consultation ID from the URL to which the answer was entered.
[0084] In step S220, the server 20 refers to the consultation database (FIG. 5) to identify the ID of the "client" associated with the consultation ID identified in step S218.
[0085] In step S222, the server 20 transfers the answer included in the access for answer detected in step S1 (i.e., the answer from the specialist 300) to the client whose ID was identified in step S220 (i.e., the attending physician 101 who sent the consultation content). In one implementation example, the user database (FIG. 3) may register forwarding destination information (e.g., email address) for each user ID. The server 20 may transfer the answer to the forwarding destination information of the client by referring to the user database. Thereafter, the server 20 returns control to FIG. 8.
[0086] (Point Assignment) Fig. 10 is a flowchart of the subroutine for point assignment (step S3). The content of point assignment in step S3 will be described with reference to Fig. 10.
[0087] In step S300, the server 20 determines whether or not input of information for point allocation has been received. In the medical support system 1, when the system usage fee is paid from the medical institution 100 to the system operation company 200, information for point allocation is input to the server 20. One example of this input is input by an employee of the system operation company 200 using the operation unit 27. The worker inputs, for example, information identifying the medical institution that paid the system usage fee and the amount of the system usage fee paid. Another example of the above input is a notification from a financial institution that a deposit has been made to the system operation company 200.
[0088] In step S302, the server 20 identifies the medical institutions eligible for point allocation. More specifically, the server 20 identifies the IDs of the medical institutions that have paid the system usage fee. The server 20 may store information that associates each medical institution with the ID of the medical institution, and the server 20 may identify the IDs of the eligible medical institutions by referring to the information.
[0089] In step S304, the server 20 identifies the number of points (amount of points) to be awarded. The server 20 may store information correlating the amount of the system usage fee with the number of points to be awarded. By referring to the information, the server 20 may identify the number of points associated with the amount paid by the medical institution as the number of points to be awarded.
[0090] The number of points awarded in step S304 may be adjusted according to a given upper limit. More specifically, in the medical support system 1, an upper limit may be set on the number of points that can be awarded within a certain period of time throughout the entire medical support system 1, and the number of points awarded may be adjusted so as not to exceed this upper limit. The upper limit may be limited by the number of answers that can be provided within the certain period by all specialists registered in the medical support system 1.
[0091] In step S306, the server 20 updates the user database (FIG. 3) so that the points of the medical institution identified in step S302 are increased by the number of points identified in step S304. Thereafter, the server 20 returns control to FIG. 8.
[0092] (Payment) Fig. 11 is a flowchart of the subroutine for payment (step S4). The content of the payment in step S4 will be described with reference to Fig. 11.
[0093] In step S400, the server 20 determines whether the time has come to pay the consultation fee to the specialist 300. In one implementation example, in step S400, it is determined whether a specific day (e.g., the 5th of each month) in a specific period has arrived. If the server 20 determines that the time has come to pay (YES in step S400), the server 20 proceeds to step S402; otherwise (NO in step S400), the server 20 returns the control to FIG. 8 .
[0094] In step S402, the server 20 identifies the amount to be remitted to each specialist 300. In one implementation example, information correlating the number of earned points with the amount is stored in the server 20. The server 20 may refer to the information to identify the amount to be remitted based on the earned points of each specialist 300 in the specialist database.
[0095] In step S404, the server 20 uses the remittance information in the specialist database to remit the amount specified in step S402 to each specialist 300. Thereafter, the server 20 returns control.
[0096] 8 to 11, the response from the specialist 300 is transferred to the attending physician 101 via the server 20 of the system operation company 200. The response from the specialist 300 may also be sent to the attending physician 101 without going through the server 20. For example, when the consultation content is transferred, contact information for the attending physician 101, such as a telephone number, may be sent to the specialist 300. The specialist 300 may directly contact the attending physician 101 and convey the response.
[0097] In the above process, points of the medical institution 100 to which the attending physician 101 belongs are deducted in accordance with the transfer of the consultation content (step S212). Thus, the control of step S212 constitutes an example of a payment process for the fee corresponding to the consultation content.
[0098] The settlement process does not have to be performed for each transfer of consultation content. Similar to the payment (step S4) described with reference to FIG. 11, the settlement process may be realized as a lump-sum settlement by deducting the amount of points corresponding to the consultation content within a given period all at once. Furthermore, each medical institution 100 may select whether to deduct points for each transfer of consultation content or for each given period.
[0099] In the above process, points purchased in advance by paying the system usage fee are used as payment. The payment may be cash. The payment does not need to be paid in advance by the system operation company 200, but may be paid from the medical institution 100 to the system operation company 200 when the consultation content is transferred or when payment for the consultation content within the given period is made.
[0100] In the above process, as explained mainly with reference to Fig. 11, payment to the specialist 300 is made in a lump sum for each specific period. Payment to the specialist 300 may also be made for each transfer of consultation content. Payment to the specialist 300 may also be made on the condition that a response to the consultation content has been provided.
[0101] The server 20 may select one or more specialists 300 to be displayed in the area 620 of the screen 600 or the screen 700 from among the specialists 300 registered in the medical support system 1 .
[0102] An example of the selection criteria is the field of specialty. For example, the server 20 receives a designation of the type of specialist from the attending physician 101. The server 20 refers to the "Specialty" item in the specialist database and selects specialists of the designated type as one or more specialists 300 to be displayed in the area 620.
[0103] Another example of the selection criteria is region. For example, when a certain attending physician 101 accesses the server 20 for consultation, the server 20 selects, as one or more specialists 300 to be displayed in the area 620, specialists associated with the same "prefecture" as the "prefecture" registered for the medical institution to which the attending physician 101 belongs.
[0104] Another example of a selection criterion is a response period. For example, on the screen 600, the attending physician 101 can switch the response period specified in the field 623 before operating the button 630. In response to switching the response period specified in the field 623, the server 20 selects, as one or more specialists 300 to be displayed in the area 620, specialists who can provide a response within the response period.
[0105] An example of information used for the selection based on the response period is the "shortest response period" in the specialist database. Specialists whose "shortest response period" is registered as a response period equal to or shorter than the specified response period are selected as one or more specialists 300 to be displayed in area 620.
[0106] Another example of information used for the selection is the "available days and times" in the specialist database. For example, consider a situation in which the screen 600 is displayed at 10:00 AM on Monday and the response period is specified as "within one day." In FIG. 4 , for specialist ID "0002," Tuesday, the day after Monday, is included in the "available days and times." However, for specialist ID "0001," Tuesday, the day after Monday, is not included in the "available days and times." Therefore, in this situation, specialist ID "0002" is selected as one or more specialists 300 to be displayed in area 620, but specialist ID "0001" is not selected as one or more specialists 300 to be displayed in area 620.
[0107] Aspects It will be understood by those skilled in the art that the exemplary embodiments described above are examples of the following aspects.
[0108] (Section 1) A medical support method according to one aspect is a medical support method executed by a computer capable of communicating with a primary physician terminal and multiple specialist physician terminals, and may include the steps of providing a consultation environment between the primary physician and the specialist physician, and calculating a fee to be paid to the specialist physician depending on the usage status of the consultation environment.
[0109] According to the medical support method described in paragraph 1, a technique is provided for promoting widespread use of specialist knowledge, thereby improving the quality of medical care.
[0110] (Clause 2) In the medical support method described in paragraph 1, the step of providing the consultation environment may include a step of receiving the consultation content from the attending physician, and may further include a step of providing information about the compensation to the attending physician before the step of receiving the consultation content.
[0111] According to the medical support method described in paragraph 2, the attending physician can obtain information about the fee when transmitting the consultation content.
[0112] (Clause 3) In the medical support method described in Clause 2, the information on the compensation may specify an amount of compensation that differs depending on a response period for the consultation content.
[0113] According to the medical support method described in paragraph 3, the burden required for responding can be reflected in the amount of compensation. (paragraph 4) In the medical support method described in any one of paragraphs 1 to 3, the step of providing a consultation environment includes a step of receiving consultation details from the attending physician, and may further include a step of providing information on one or more specialists to the attending physician before the step of receiving consultation details, and the step of receiving consultation details may include receiving information for selecting the specialist from the one or more specialists.
[0114] According to the medical support method described in Section 4, a specialist can be selected so that an answer appropriate to the consultation content of the attending physician can be provided more reliably.
[0115] (Clause 5) In the medical support method described in Clause 4, the information on the one or more specialists may include providing information on the amount of compensation required for each of the one or more specialists.
[0116] According to the medical support method described in Section 5, the amount of compensation paid to the specialist can be adjusted according to the characteristics of the specialist.
[0117] (Clause 6) In the medical support method described in Clause 5, the amount of the required compensation may be set for each of two or more types of response periods for the consultation content.
[0118] According to the medical support method described in paragraph 6, the burden required for the response can be reflected in the amount of compensation. (Clause 7) In the medical support method described in paragraph 4, the step of providing information on one or more specialists may include receiving, from the attending physician, designation of a response period for the consultation content, and selecting, as the one or more specialists, specialists who can respond within the response period.
[0119] According to the medical support method described in Section 7, it is possible to more easily connect a primary care physician with a specialist who can provide an answer within the response period desired by the primary care physician.
[0120] (Clause 8) The medical support method described in any one of clauses 1 to 7 further includes a step of performing a payment process for the consideration to the attending physician, and the payment process may include subtracting the value of an amount corresponding to the consideration from the value of an amount previously granted to the attending physician.
[0121] According to the medical support method described in Section 8, by limiting the amount of value to be pre-assigned according to the amount of answers that can be provided to the attending physician, it is possible to ensure that the attending physician receives an amount of answers corresponding to the amount of value pre-assigned.
[0122] (Clause 9) The medical support method described in any one of clauses 1 to 8 further includes a step of performing a payment process for the fee to the attending physician, and the payment process may include paying the fees corresponding to multiple consultation contents from the attending physician in one lump sum to the attending physician.
[0123] According to the medical support method described in paragraph 9, the number of settlement processes can be minimized. (paragraph 10) The medical support method described in any one of paragraphs 1 to 9 further comprises a step of performing a payment process to pay the specialist the consideration, and the payment process may pay the specialist the consideration corresponding to multiple consultation contents from the attending physician in one lump sum.
[0124] According to the medical support method described in paragraph 10, the number of payment processes is minimized. (paragraph 11) A medical support device according to one aspect includes a communication interface, a processor capable of communicating with a first terminal operated by a primary care physician and a second terminal operated by a specialist physician via the communication interface, and a memory for storing a program, wherein the program, when executed by the processor, causes the processor to perform the steps of providing a consultation environment between the primary care physician and the specialist physician, and calculating a fee to be paid to the specialist physician depending on the usage status of the consultation environment.
[0125] The medical support device described in item 11 provides a technique for promoting widespread use of specialist knowledge, thereby improving the quality of medical care.
[0126] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is defined by the claims, not by the description of the above-described embodiments, and is intended to include all modifications within the meaning and scope of the claims. Furthermore, it is intended that each technique in the embodiments can be implemented alone or, if necessary, in combination with other techniques in the embodiments to the extent possible.
[0127] 1 Medical support system, 20 Server, 25 Storage device, 100 Medical institution, 101 Attending doctor, 200 System operation company, 300, ID specialist, 600, 700 Screen, 610, 620 Area, 621, 622 Tab, 630 Button.
Claims
1. A medical support method executed by a computer capable of communicating with a primary physician terminal and multiple specialist physician terminals, comprising: a step of providing a consultation environment between the primary physician and a specialist physician; and a step of calculating a fee to be paid to the specialist physician depending on the usage status of the consultation environment.
2. The medical support method according to claim 1, wherein the step of providing a consultation environment includes a step of receiving consultation details from the attending physician, and further includes a step of providing information regarding the compensation to the attending physician prior to the step of receiving consultation details.
3. The medical support method according to claim 2, wherein the compensation information specifies different amounts of compensation according to a response period for the consultation content.
4. The medical support method of claim 1, wherein the step of providing a consultation environment includes a step of receiving consultation contents from the attending physician, and further includes a step of providing information on one or more specialists to the attending physician before the step of receiving the consultation contents, and the step of receiving the consultation contents includes receiving information on selecting the specialist from the one or more specialists.
5. The medical support method according to claim 4, wherein the information on the one or more specialists includes providing information on the amount of compensation required for each of the one or more specialists.
6. The medical support method according to claim 5, wherein the amount of the required compensation is set for each of two or more types of response periods for the consultation content.
7. The medical support method according to claim 4, wherein the step of providing information on the one or more specialists includes: receiving from the attending physician a response period for the consultation content; and selecting, as the one or more specialists, specialists who can respond within the response period.
8. The medical support method of claim 1, further comprising a step of executing a payment process for the compensation to the attending physician, the payment process including subtracting the value of an amount corresponding to the compensation from the value of an amount previously granted to the attending physician.
9. The medical support method according to claim 1, further comprising a step of carrying out a payment process for the fee to the attending physician, the payment process comprising making a lump-sum payment to the attending physician for the fees corresponding to multiple consultation contents from the attending physician.
10. The medical support method according to claim 1, further comprising a step of carrying out a payment process for paying the fee to the specialist, the payment process paying a lump sum of fees corresponding to multiple consultation contents from the attending physician to the specialist.
11. A medical support device comprising: a communications interface; a processor capable of communicating with a first terminal operated by a primary physician and a second terminal operated by a specialist via the communications interface; and a memory for storing a program, which, when executed by the processor, causes the processor to perform the steps of: providing a consultation environment between the primary physician and the specialist; and calculating a fee to be paid to the specialist depending on the usage status of the consultation environment.
Citation Information
Patent Citations
System for performing switching and storage of rare disease counseling information
JP2012177975A
Device and method for consultation between doctors, and program therefor
JP2022040689A
Remote medical examination / advice system for animal patients
WO2021250881A1
