Medical service management system

Abstract

We provide a healthcare service management system that allows for accurate management of the use of healthcare services through SaMD (Savings on Medical Devices). [Solution] The medical service management system of this disclosure is a medical service management system that manages the use of medical services by SaMD (Software as a Medical Service), wherein display information indicating the results of examinations performed by the medical service is output to a first terminal on which the medical service application is installed, the output display information is read by a second terminal that can be linked with an electronic medical record, and the examination results are registered in the electronic medical record based on the reading results.

Description

Technical Field

[0001] The present disclosure relates to a medical service management system for managing the use of medical services.

Background Art

[0002] Medical systems have been developed that provide applications (hereinafter referred to as apps) for processing output data from medical devices such as X-ray CT devices and magnetic resonance diagnostic devices. In such medical systems, billing is performed according to the use of the app.

[0003] As a technique for accurately billing the amount, there is a technique disclosed in Patent Document 1. Patent Document 1 discloses that the diagnostic effectiveness of the used app is judged and billing is performed according to the effectiveness.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In recent years, the use of medical services utilizing SaMD (Software as a Medical Device) has been expanding in the medical field. SaMD is software with complex medical functions. Doctors can access SaMD services on the cloud using general-purpose terminal devices such as tablet devices and smartphones, and utilize various SaMD-based medical services on these terminal devices. According to SaMD, diverse data obtained from various tests can be processed quickly and accurately, facilitating various medical procedures such as diagnosis and treatment. Furthermore, because SaMD can be used on relatively small, portable computers such as tablet devices and smartphones, medical procedures can be performed regardless of location.

[0006] To improve usability in medical settings, it is desirable that the general-purpose terminal device for using SaMD be operable by an unspecified number of people. Examples of such unspecified people include nurses and patients, in addition to doctors.

[0007] To reduce the risk of sensitive information such as patient data being leaked, it is desirable to separate terminal devices that can be operated by an unspecified number of people from the electronic medical record system that handles patient information.

[0008] However, separating the terminal device used for SaMD from the electronic medical record system in this way can lead to the following disadvantages. Specifically, it becomes difficult to automatically reflect medical information obtained through the SaMD service into the electronic medical record on the terminal device. As a result, physicians will need to manually reflect the medical information obtained through the SaMD service into the electronic medical record, increasing their workload.

[0009] Furthermore, information regarding the usage history of the SaMD service is managed separately by the server device providing the SaMD service and the electronic medical record system. Because the server device and the electronic medical record system are independent of each other, inconsistencies may occur in the SaMD service usage history between the two systems. In such cases, it becomes difficult to calculate the correct usage fee for the SaMD service.

[0010] This disclosure aims to provide a healthcare service management system that can accurately manage the use of healthcare services by SaMDs. [Means for solving the problem]

[0011] A medical service management system according to one aspect of this disclosure is a medical service management system for managing the use of medical services by SaMD (Software as a Medical Service), wherein display information indicating the results of examinations performed by the medical service is output to a first terminal on which the application for the medical service is installed, the outputted display information is read by a second terminal that can be linked with an electronic medical record, and the examination results are registered in the electronic medical record based on the reading results. [Effects of the Invention]

[0012] According to this disclosure, it is possible to accurately manage the use of healthcare services by SaMDs. [Brief explanation of the drawing]

[0013] [Figure 1] A diagram showing an example of the configuration of a medical service management system in the first embodiment of this disclosure. [Figure 2] Block diagram showing an example of the functional configuration of a terminal device for SaMD in the first embodiment. [Figure 3] Block diagram showing an example of the functional configuration of an electronic medical record terminal device in the first embodiment. [Figure 4]Sequence diagram for explaining an operation example of a medical service management system in the first embodiment [Figure 5] Diagram showing an example of the configuration of a medical service management system in the second embodiment of the present disclosure [Figure 6] Block diagram showing an example of the functional configuration of a verification server device in the second embodiment [Figure 7] Flowchart for explaining an operation example during the verification process of a verification server device in the second embodiment

Modes for Carrying Out the Invention

[0014] Hereinafter, each embodiment of the present disclosure will be described in detail with reference to the drawings. However, detailed descriptions that are more detailed than necessary, for example, detailed descriptions of well-known matters and duplicate descriptions of substantially the same configurations, may be omitted. However, the scope of the present disclosure is not limited to those described in the following embodiments and drawings.

[0015] (First Embodiment) Hereinafter, the first embodiment of the present disclosure will be described.

[0016] <Overall Configuration> FIG. 1 is a diagram showing an example of the configuration of a medical service management system 100 in the first embodiment of the present disclosure. In the first embodiment, the medical service management system 100 includes a SaMD service providing system 10 and an electronic medical record system 20.

[0017] The SaMD service providing system 10 and the electronic medical record system 20 are connected via a network (for example, the Internet) 30.

[0018] The SaMD service providing system 10 is a system that provides various medical services using SaMD to medical staff such as doctors. The SaMD service providing system 10 is introduced into a medical institution such as a hospital, for example.

[0019] In the present disclosure, as a medical service by SaMD, a service for outputting examination results performed on a patient is assumed. As a specific example of the medical service by SaMD in the present disclosure, there is a dementia examination service that examines whether the patient has dementia based on the patient's voice or the like and provides the results of the examination. A doctor can suitably diagnose a patient by utilizing the examination results provided by the medical service by SaMD.

[0020] The SaMD service providing system 10 is composed of a SaMD terminal device 11 and a SaMD service providing server device 12.

[0021] The SaMD terminal device 11 is a terminal device for medical personnel such as doctors to use the medical service by SaMD. In the present disclosure, examples of the SaMD terminal device 11 include portable computers such as tablet terminals, smartphones, notebook PCs (Personal Computers), or stationary computers such as desktop PCs.

[0022] The SaMD service providing server device 12 is a server device that provides a medical service by SaMD to the SaMD terminal device 11. Examples of the SaMD service providing server device 12 include a physical server composed of a stationary computer, or a cloud server composed of virtualized one or more server functions arranged in a cloud environment.

[0023] The SaMD terminal device 11 and the SaMD service provision server device 12 are connected to each other so that they can communicate with one another. When a medical professional, such as a doctor, performs an operation to use SaMD-based medical services via the SaMD terminal device 11, the SaMD terminal device 11 requests service provision from the SaMD service provision server device 12. The SaMD service provision server device 12 transmits various information for service provision to the SaMD terminal device 11, enabling the medical professional to use SaMD-based medical services on the SaMD terminal device 11.

[0024] The electronic medical record system 20 is a system that centrally manages various types of information generated when a doctor examines a patient, as an electronic medical record. Examples of the various types of information generated when a doctor examines a patient include the patient's personal information, the results of tests performed on the patient, test images, the doctor's test results based on the test results and examination, prescription orders, and accounting information. The electronic medical record system 20, like the SaMD service provision system 10, is installed in medical institutions such as hospitals.

[0025] The electronic medical record system 20 consists of an electronic medical record terminal device 21, an electronic medical record server device 22, and a firewall 23. The electronic medical record server device 22 is a server device that manages the electronic medical records of multiple patients. The electronic medical record terminal device 21 is a terminal device that can access the electronic medical record server device 22. In this disclosure, examples of the electronic medical record terminal device 21 include, for example, portable computers such as tablet terminals, smartphones, and notebook PCs, or stationary computers such as desktop PCs. Examples of the electronic medical record server device 22 include, for example, a physical server composed of stationary computers, or a cloud server composed of one or more virtualized server functions deployed in a cloud environment. When a physician inputs the results of a patient diagnosis (hereinafter referred to as "examination results") via the electronic medical record terminal device 21, the examination results are reflected in the electronic medical record managed by the electronic medical record server device 22.

[0026] The firewall 23 restricts communication connections inside and outside the electronic medical record system 20. It can reduce the risk of leakage of sensitive information (such as patient personal information and information regarding examination results) handled inside the electronic medical record system 20 to the outside of the electronic medical record system 20. In particular, in the example shown in FIG. 1, the firewall 23 restricts communication between the SaMD service providing system 10 and the electronic medical record system 20.

[0027] <Terminal device 11 for SaMD> FIG. 2 is a block diagram showing an example of the functional configuration of the terminal device 11 for SaMD in the first embodiment. As shown in FIG. 2, the terminal device 11 for SaMD includes an operation unit 111, a voice reception unit 112, a display unit 113, an examination result acquisition unit 114, an examination result character display unit 115, a doctor approval reception unit 116, a patient approval reception unit 117, a code display permission unit 118, and an examination result code display unit 119.

[0028] The operation unit 111 receives the operations of the person using the terminal device 11 for SaMD. The persons using the terminal device 11 for SaMD include at least doctors. Also, the persons using the terminal device 11 for SaMD may include nurses or various technicians who are medical staff other than doctors, or the patient himself / herself. The operation unit 111 is constituted by, for example, various buttons, keys, switches, touch pads, and the like.

[0029] The voice reception unit 112 receives the voice of the patient. The voice reception unit 112 is constituted by, for example, a microphone or the like. The voice of the patient received by the voice reception unit 112 is transmitted to the SaMD service providing server device 12.

[0030] The display unit 113 displays various types of information handled by the SaMD terminal device 11. The display unit 113 is a display device such as a liquid crystal display or an organic EL (Electro Luminescence) display. If the operation unit 111 is configured as a touch pad, the operation unit 111 may be superimposed on the display unit 113 to form a so-called touch panel.

[0031] The test result acquisition unit 114 acquires the test results generated by the SaMD service provision server device 12 based on the patient's voice. If the medical service provided by the SaMD service provision system 10 is a dementia testing service, the test results acquired by the test result acquisition unit 114 are test results indicating whether or not the patient has dementia.

[0032] The test result text display unit 115 displays the test results acquired by the test result acquisition unit 114 in text format on the display unit 113. This allows the person using the SaMD terminal device 11 to accurately understand the test results.

[0033] The physician approval reception unit 116 accepts physician approval for the test results acquired by the test result acquisition unit 114. The physician approval reception unit 116 should recognize that it has received physician approval when a physician performs the approval operation via the operation unit 111. Note that physician approval for a patient's test results means that the physician approves that the test results may be reflected in the patient's electronic medical record.

[0034] The patient approval reception unit 117 accepts patient approval for the test results obtained by the test result acquisition unit 114. The physician approval reception unit 116 should recognize that patient approval has been received when the patient performs the approval operation via the operation unit 111. Patient approval for a patient's test results means that the patient is satisfied with those test results.

[0035] The inspection result code display unit 119 displays the inspection results acquired by the inspection result acquisition unit 114 in barcode format on the display unit 113. In this disclosure, the barcode includes at least one-dimensional barcodes and two-dimensional codes. An example of a two-dimensional code is the QR (Quick Response) code (a registered trademark of DENSO WAVE INCORPORATED).

[0036] The barcode-format test results displayed on the display unit 113 by the test result code display unit 119 are read by the electronic medical record terminal device 21. As a result, the test results obtained from the medical services provided by the SaMD service provision system 10 are automatically and accurately received by the electronic medical record system 20.

[0037] Furthermore, in the display unit 113, the inspection result in character format displayed by the inspection result character display unit 115 and the inspection result in barcode format displayed by the inspection result code display unit 119 may be displayed simultaneously and side by side. Alternatively, in the display unit 113, the inspection result in character format may be displayed by the inspection result character display unit 115, and then the inspection result in barcode format may be displayed by the inspection result code display unit 119.

[0038] The code display authorization unit 118 authorizes the display of test results in barcode format by the test result code display unit 119, provided that approval has been received from the physician and the patient by the physician approval reception unit 116 and the patient approval reception unit 117.

[0039] <Electronic medical record terminal device 21> Figure 3 is a block diagram showing an example of the functional configuration of the electronic medical record terminal device 21 in the first embodiment. As shown in Figure 3, the electronic medical record terminal device 21 includes an operation unit 211, a display unit 212, an examination result code reading unit 213, and an electronic medical record registration unit 214.

[0040] The control unit 211 receives input from a physician using the electronic medical record terminal device 21. The control unit 211 is composed of various buttons, keys, switches, touchpads, etc.

[0041] The display unit 212 displays various types of information handled by the electronic medical record terminal device 21. The display unit 212 is a display device such as a liquid crystal display or an organic EL display. If the operation unit 211 is configured as a touch pad, the operation unit 211 may be superimposed on the display unit 212 to form a so-called touch panel.

[0042] The inspection result code reading unit 213 reads the barcode-formatted inspection result displayed on the display unit 113 by the inspection result code display unit 119 of the SaMD terminal device 11. The inspection result code reading unit 213 has, for example, a barcode reader function and reads the barcode displayed on the display unit 113 by binarizing it.

[0043] The electronic medical record registration unit 214 registers the test results in the electronic medical record managed by the electronic medical record server device 22 by transmitting the contents of the test results read by the test result code reading unit 213 to the electronic medical record server device 22. In addition to the above processing, the electronic medical record registration unit 214 may also perform the process of registering information entered by a physician into the electronic medical record to the electronic medical record server device 22 by transmitting the information to the electronic medical record server device 22. Examples of information to be registered in the electronic medical record include patient information and diagnostic information.

[0044] <Example of operation of Medical Service Management System 100> Referring to Figure 4, an example of the operation of the medical service management system 100 in the first embodiment will be described. Figure 4 is a sequence diagram illustrating an example of the operation of the medical service management system 100 according to the first embodiment. The arrows between each device shown in Figure 4 indicate that some kind of information is being exchanged.

[0045] In the following description, a dementia screening service using SaMD is assumed to be one of the medical services provided by the SaMD service delivery system 10. The dementia screening service is a service that tests whether or not a patient has dementia based on the patient's voice and provides the test results.

[0046] Medical professionals such as doctors or nurses can initiate the use of the dementia screening service via SaMD by operating the SaMD service provision system 10. In step S1, the SaMD terminal device 11 receives the patient's voice to be used for the dementia screening service, either by the medical professional or the patient themselves. The patient's voice received by the SaMD terminal device 11 in step S1 is transmitted to the SaMD service provision server device 12.

[0047] In step S2, the SaMD service provider server device 12 acquires the patient's voice transmitted from the SaMD terminal device 11.

[0048] In step S3, the SaMD service provider server device 12 uses the patient's voice acquired in step S2 to perform a test to determine whether or not the patient has dementia. This test can be performed, for example, using a trained model that outputs an index value indicating the degree of dementia in the patient when the patient's voice is input. In this case, the test result is either the index value itself, or the presence or absence of dementia determined based on the index value.

[0049] In step S4, the SaMD service provider server device 12 registers the test results obtained from the test performed in step S3. Note that registering the test results means that the SaMD service provider server device 12 does not store information about the patient who underwent the test, but only stores information about the date and time the test was performed and information indicating the content of the test results. Examples of information about the patient who underwent the test include the patient's name, gender, age, and address. This ensures that sensitive patient information is not stored in the SaMD service provider server device 12. Therefore, the risk of sensitive patient information being leaked to the outside via the SaMD service provider server device 12 through the use of the SaMD service is reduced.

[0050] In step S5, the SaMD terminal device 11 acquires the test results transmitted from the SaMD service provision server device 12.

[0051] In step S6, the SaMD terminal device 11 displays the test results obtained in step S5 in text format. This allows the person using the SaMD terminal device 11 to understand the patient's test results.

[0052] In step S7, the SaMD terminal device 11 obtains patient approval. Patient approval means that the patient accepts the contents of the test results displayed in step S6. If patient approval is not obtained in step S7, the process in step S7 may be repeated until patient approval is obtained, or the process may be returned to step S1 and the test may be restarted from the process of receiving the patient's voice.

[0053] In step S8, the SaMD terminal device 11 obtains approval from the physician. Physician approval means that the physician acknowledges that the test results displayed in step S6 are official test results that can be recorded in the electronic medical record. If physician approval is not obtained in step S8, the process in step S8 may be repeated until physician approval is obtained, or the process may be returned to step S1 and the test restarted from the process of receiving the patient's voice. After obtaining physician approval in step S8, the SaMD terminal device 11 transmits approval information to the SaMD service provider server device 12 indicating that physician approval has been obtained.

[0054] In step S9, the SaMD service provider server device 12 registers the approval information transmitted from the SaMD terminal device 11 in association with the test results registered in step S4. This makes it clear that the test results registered in the SaMD service provider server device 12 have been approved by a physician.

[0055] In step S10, the SaMD terminal device 11 is authorized to display the test results obtained in step S5 in barcode format, triggered by the physician's approval in step S8.

[0056] In step S11, the SaMD terminal device 11, upon receiving permission in step S10, displays the inspection results obtained in step S5 in barcode format. As described above, the inspection results in text format displayed in step S6 and the inspection results in barcode format displayed in step S11 may be displayed simultaneously on the same display unit, side by side. Alternatively, after the inspection results in text format are displayed in step S6, the display of the inspection results in text format may be stopped, and then the inspection results in barcode format may be displayed again in step S11.

[0057] In step S12, the electronic medical record terminal 21 reads the test result code displayed in step S9. The reading of the test result code in step S12 is not achieved by any information being transmitted from the SaMD terminal 11 to the electronic medical record terminal 21, and is therefore shown by a dashed arrow in Figure 4. The electronic medical record terminal 21 transmits the test result obtained from the test result code read in step S12 to the electronic medical record server 22.

[0058] In step S13, the electronic medical record server device 22 registers the test results transmitted from the electronic medical record terminal device 21 into the electronic medical record. This ensures that test results obtained using SaMD medical services are automatically registered into the electronic medical record. This eliminates the need for doctors to expend considerable effort, such as operating the electronic medical record terminal device 21 based on test results displayed in text format on the SaMD terminal device 11, when registering test results obtained using SaMD medical services into the electronic medical record.

[0059] <Effects> Based on the example of operation of the medical service management system 100 shown in Figure 4, the effects obtained by the medical service management system 100 will be explained in detail.

[0060] As described above, the SaMD terminal device 11 for using SaMD is designed to be usable by an unspecified number of people, including medical professionals other than doctors and the patients themselves. This allows for flexible use of medical services (dementia screening services in the example in Figure 4) provided to the SaMD terminal device 11 by the SaMD service provision server device 12, according to the situation in the medical setting. For example, a doctor or nurse can use the SaMD terminal device 11 to explain to a patient the medical services they will be using. Furthermore, the acquisition of the patient's voice using the SaMD terminal device 11, which is necessary for the provision of medical services, can be done by the patient themselves by operating the SaMD terminal device 11, or by a doctor or nurse operating the SaMD terminal device 11.

[0061] On the other hand, the SaMD service provision system 10, which includes the SaMD terminal device 11 that can be used by an unspecified number of people, has its communication with the electronic medical record server device 22 restricted by the firewall 23 of the electronic medical record system 20. This reduces the risk of sensitive information, such as patients' personal information and test results, handled within the electronic medical record system 20, being leaked to the outside via the SaMD terminal device 11.

[0062] Then, as shown in step S6 of Figure 4, the SaMD terminal device 11 displays the test results obtained from the SaMD service provision server device 12 in text format. This allows the person using the SaMD terminal device 11 to understand the content of the test results. Therefore, in steps S7 and S8, the patient and the doctor can fully understand the content of the test results and approve them.

[0063] Furthermore, as shown in step S9 of Figure 4, after patient and physician approval in steps S7 and S8, the SaMD terminal device 11 displays the test results obtained from the SaMD service provision server device 12 in barcode format. The electronic medical record terminal device 21 then reads the test results displayed in barcode format using its barcode reader function. This allows for accurate transmission of test results from the SaMD terminal device 11 to the electronic medical record terminal device 21 without direct communication between the two devices. Physicians and others do not need to manually input the contents of the test results displayed on the SaMD terminal device 11 into the electronic medical record terminal device 21 using the operation unit 211 or the like; the contents of the test results obtained through medical services can be accurately reflected in the electronic medical record. This reduces the workload for physicians when registering test results obtained through SaMD medical services into the electronic medical record.

[0064] After patient and physician approval in steps S7 and S8, the reading in step S12 is performed, allowing the results of medical service tests performed by SaMD to be reflected in the electronic medical record only if approved by the patient and physician. This prevents situations where test results are reflected in the electronic medical record without prior approval.

[0065] Furthermore, each time a medical service is used via the SaMD terminal device 11, the test results are registered in both the SaMD service provision server device 12 and the electronic medical record server device 22 (see steps S4 and S13 in Figure 4). In this way, by keeping a record of medical service usage on both the SaMD service provision system 10 and the electronic medical record system 20, medical service providers can bill for accurate usage fees that reflect actual usage. Also, for medical facilities using medical services, since the usage history is kept on the electronic medical record system 20, they can verify whether the usage fees billed by medical service providers are accurate. For this reason, the medical service management system 100 according to the first embodiment allows for accurate management of medical service usage.

[0066] (Modified version of the first embodiment) The first embodiment described above may include the following modifications.

[0067] <First variation> In the example of operation of the medical service management system 100 according to the first embodiment shown in Figure 4, the test results are displayed in text format in step S6, and after patient and physician approval is obtained in steps S7 and S8, the test results are displayed in barcode format in step S11. This allows patients and physicians to fully understand the content of the test results before giving approval. Furthermore, the test results are transmitted from the SaMD terminal device 11 to the electronic medical record terminal device 21 only after patient and physician approval has been obtained. This prevents situations where test results are reflected in the electronic medical record without prior approval.

[0068] In this disclosure, patient and physician approval does not necessarily have to be obtained before permission is granted to display the test results in barcode format. That is, the SaMD terminal device 11 may obtain patient and physician approval while the test results are displayed in both text and barcode formats. In this case, it is desirable to configure the system so that the test results displayed in barcode format before patient and physician approval are not reflected in the electronic medical record. Specifically, the SaMD service provider server device 12 should register the test results in the electronic medical record managed by the electronic medical record server device 22 after patient and physician approval has been obtained.

[0069] Furthermore, in some cases, patient approval may be omitted. For example, if the results of a dementia screening service performed on a patient indicate that the patient's level of dementia is below a predetermined level, the SaMD terminal device 11 may allow the display of the screening results in barcode format, regardless of whether or not the patient has given their approval.

[0070] <Second variation> The SaMD terminal device 11 may further have a function to print the test results displayed on the display unit 113 in text format or barcode format. In this case, the SaMD terminal device 11 has a printing function and may print and output at least one of the test results in text format or barcode format. Alternatively, the SaMD terminal device 11 may transmit the test results in text format or barcode format to an external printer device with a printing function and have the printer device print them. This makes it possible to save the test results in paper format in the medical setting.

[0071] The SaMD terminal device 11 may further have a function to save the display content of the display unit 113 as an image file. In this case, it is preferable because the test result information can be saved on the SaMD terminal device 11, which is used for general purposes in medical settings.

[0072] <Third variation> In the medical service management system 100 according to the first embodiment described above, the SaMD terminal device 11 transmits the patient's voice acquired by the SaMD to the SaMD service provision server device 12, and the SaMD service provision server device 12 performs the examination using the patient's voice. The disclosure is not limited thereto, and for example, the SaMD terminal device 11 may perform the examination itself without transmitting the patient's voice to the SaMD service provision server device 12. In this case, the medical service management system only needs to have the function of the SaMD terminal device providing medical services by SaMD. In this case, the medical service management system does not need to have a SaMD service provision server device.

[0073] (Second Embodiment) A second embodiment of the present disclosure will be described below. In the second embodiment, components similar to those in the first embodiment will be denoted by the same reference numerals as in the first embodiment, and detailed descriptions may be omitted. Figure 5 is a diagram showing an example of the configuration of the medical service management system 100A in the second embodiment of the present disclosure. The medical service management system 100A according to the second embodiment differs from the medical service management system 100 described in the first embodiment in that it has a matching server device 40.

[0074] The matching server device 40 is located between the SaMD service provision system 10 and the electronic medical record system 20. In the example shown in Figure 5, the matching server device 40 is located between the network 30 and the SaMD service provision system 10, but the disclosure is not limited to this. The matching server device of this disclosure may be located, for example, between the network and the electronic medical record system 20.

[0075] The verification server device 40 manages accurate medical service usage records by verifying the medical service usage history managed on the SaMD service provision system 10 side with the medical service usage history managed on the electronic medical record system 20 side. Examples of the verification server device 40 include, for example, a physical server consisting of a stationary computer, or a cloud server consisting of one or more virtualized server functions deployed in a cloud environment.

[0076] Figure 6 is a block diagram showing an example of the functional configuration of the matching server device 40 in the second embodiment. As shown in Figure 6, the matching server device 40 includes a SaMD examination history acquisition unit, an electronic medical record examination history acquisition unit 42, and a matching unit 43.

[0077] The SaMD examination history acquisition unit 41 acquires the usage history of medical services managed by the SaMD service provision system 10. More specifically, the SaMD examination history acquisition unit 41 acquires the usage history from the SaMD terminal device 11 each time a medical service is used by the SaMD terminal device 11. Alternatively, the SaMD examination history acquisition unit 41 may acquire the usage history of multiple medical services over a certain period of time, which are registered in the SaMD service provision server device 12, from the SaMD service provision server device 12.

[0078] The electronic medical record examination history acquisition unit 42 acquires the usage history of medical services managed by the electronic medical record system 20. More specifically, the electronic medical record examination history acquisition unit 42 acquires the usage history of medical services registered in the electronic medical record managed by the electronic medical record server device 22 from the electronic medical record server device 22.

[0079] The matching unit 43 compares the medical service usage history managed by the SaMD service provision system 10, which was acquired by the SaMD examination history acquisition unit 41, with the medical service usage history managed by the electronic medical record system 20, which was acquired by the electronic medical record examination history acquisition unit 42. This allows confirmation that there are no inconsistencies in the medical service usage history managed by the SaMD service provision system 10 and the electronic medical record system 20, respectively.

[0080] If the verification by the verification unit 43 reveals an inconsistency, the notification unit 44 notifies the SaMD service provision system 10 and the electronic medical record system 20 that an inconsistency has occurred. This allows healthcare professionals in the medical field and businesses providing medical services to quickly recognize the inconsistency. This enables the use history of medical services managed by the SaMD service provision system 10 to be synchronized with the use history of medical services managed by the electronic medical record system 20.

[0081] Figure 7 is a flowchart illustrating an example of the operation of the matching server device 40 during the matching process in the second embodiment. The matching process shown in Figure 7 may be automatically executed by the matching server device 40 at regular intervals, for example.

[0082] In step S21, the matching server device 40 obtains the usage history of medical services managed by the SaMD service provision system 10 from the SaMD service provision system 10.

[0083] In step S22, the matching server device 40 obtains the usage history of medical services managed by the electronic medical record system 20 from the electronic medical record system 20.

[0084] In the example shown in Figure 7, the processing in step S21 is performed before the processing in step S22. The disclosure is not limited thereto, and the processing in step S22 may be performed before step S21. Alternatively, the processing in steps S21 and S22 may be performed in parallel and approximately simultaneously.

[0085] In step S23, the matching server device 40 compares the usage history managed by the SaMD service provision system 10, which was acquired in step S21, with the usage history managed by the electronic medical record system 20, which was acquired in step S22.

[0086] If the verification results in step S23 show that the inspection histories are consistent (step S24:Y), the verification server device 40 terminates the process. If the inspection results do not show consistency (step S24:N), the verification server device 40 proceeds to step S25.

[0087] In step S25, the matching server device 40 notifies that there is an inconsistency between the usage history managed by the SaMD service provision system 10 and the usage history managed by the electronic medical record system 20. This notification only needs to be sent to the SaMD service provision system 10 and the electronic medical record system 20. As a result, for example, a healthcare professional using the SaMD service provision system 10 can become aware that there is an inconsistency between the usage history managed by the SaMD service provision system 10 and the usage history managed by the electronic medical record system 20. Similarly, for example, an administrator of the electronic medical record system 20 can become aware that there is an inconsistency between the usage history managed by the SaMD service provision system 10 and the usage history managed by the electronic medical record system 20. This allows at least one of the SaMD service provision system 10 and the electronic medical record system 20 to start processing to resolve the inconsistency.

[0088] According to the medical service management system 100A of the second embodiment, it is possible to compare the usage history managed on the SaMD service provision system 10 side with the usage history managed on the electronic medical record system 20 side. If there is a discrepancy, a notification can be issued. This prevents medical service providers from billing for medical service usage fees that do not reflect actual usage. Therefore, according to the medical service management system 100A of the first embodiment, the use of medical services can be accurately managed. [Industrial applicability]

[0089] This disclosure is useful for healthcare service management systems that manage the use of healthcare services by SaMDs. [Explanation of Symbols]

[0090] 100,100A Medical Service Management System 10 SaMD Service Delivery System 11. Terminal device for SaMD 111 Operation section 112 Voice Reception Department 113 Display section 114 Inspection Result Acquisition Department 115 Inspection Result Text Display Section 116 Physician Approval Reception Department 117 Patient Approval Reception Department 118 Code Display Permission Section 119 Inspection Result Code Display Unit 12 SaMD Service Provider Server Device 20 Electronic Medical Record System 21 Electronic medical record terminal device 211 Operation section 212 Display section 213 Inspection Result Code Reading Unit 214 Electronic Medical Record Registration Department 22 Electronic medical record server device 23 Firewall 30 Networks 40. Verification Server Device 41 SaMD Test History Acquisition Department 42 Electronic Medical Record Examination History Acquisition Department 43 Verification section 44 Notification Department

Claims

1. A medical service management system for managing the use of medical services through SaMD (Software as a Medical Service), Display information showing the test results from the aforementioned medical service is output to the first terminal on which the application for the aforementioned medical service is installed. The outputted display information is read by a second terminal that can be linked with the electronic medical record system. Based on the reading results, the test results are registered in the electronic medical record. Medical service management system.

2. The first terminal receives the physician's approval of the aforementioned test results. Upon receiving approval from the aforementioned physician, the output of the display information by the first terminal is permitted. A medical service management system according to claim 1.

3. The patient's approval of the aforementioned test results is received by the first terminal. Upon receiving approval from both the physician and the patient, the output of the display information from the first terminal is permitted. The medical service management system according to claim 2.

4. The aforementioned medical service is a service for making a diagnosis related to dementia based on the patient's voice, and after playing back the patient's voice used for the diagnosis, the service obtains approval from the patient. The medical service management system according to claim 3.

5. The medical service includes determining the degree of dementia in the patient, and if the degree of dementia is below a predetermined level, it permits the output of the display information by the first terminal, regardless of whether the patient has given their consent. The medical service management system according to claim 4.

6. The output of the display information by the first terminal is performed by displaying the display information on the display unit provided by the first terminal. A medical service management system according to claim 1.

7. The output of the display information by the first terminal is performed by having a printing device that can cooperate with the first terminal print the display information. A medical service management system according to claim 1.

8. The display information output by the first terminal is converted into an image and stored in the first terminal as an inspection result image. A medical service management system according to claim 1.

9. The use of the medical service is managed by comparing the first history information relating to the use history of the medical service generated at the first terminal with the second history information generated based on the test results registered in the electronic medical record. A medical service management system according to claim 1.

10. The first history information relating to multiple usage histories is managed by a SaMD service provision server device that provides the medical service function to the first terminal. The second history information based on multiple aforementioned test results is managed by an electronic medical record server device that provides the electronic medical record function to the second terminal. The comparison between the first history information obtained from the SaMD service provision server device and the second history information obtained from the electronic medical record server device is performed by a comparison server device independent of the SaMD service provision server device and the electronic medical record server device. The medical service management system according to claim 9.

11. The display information is output to the first terminal in barcode format indicating the inspection result, and the display information in barcode format is read by the second terminal. A medical service management system according to any one of claims 1 to 10.

Images