Information provision program, information provision device, and in-vehicle device

Abstract

To enable effective individualized medical care during mobile clinic visits. [Solution] The server controller of the embodiment receives a request for medical treatment at the patient's home and determines whether the vehicle will visit the patient's home based on information about the destination, information about the vehicle, and information about the patient that has been set in advance for the vehicle. If the controller determines that it will visit the patient's home, it notifies the in-vehicle device installed in the vehicle of the location of the patient's home.

Description

Technical Field

[0001] The present invention relates to an information providing program, an information providing apparatus, and an in-vehicle apparatus.

Background Art

[0002] Recently, vehicles equipped with medical equipment have been dispatched to locations other than hospitals such as community centers, and mobile medical services have been carried out where multiple patients receive medical examinations in the vehicle on a rotational basis.

[0003] In addition, as a technology related to mobile medical services, there is a technology for changing the schedule when an interrupt reservation is possible in a system for determining a schedule for visiting the homes of patients who wish to receive home medical care (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the conventional technology, effective individual medical examinations during mobile medical services may not be achievable in some cases.

[0006] For example, in mobile medical services, although multiple patients can be examined at one location at a time, the medical examination schedule is determined in advance, and it is not possible to respond, for example, to a request for home medical examination from a patient who cannot go to a community center.

[0007] In addition, in response to such a request for a home visit, an interrupt reservation can be made using the technology of Patent Document 1, but depending on the medical equipment mounted on the vehicle, it may not be possible to perform treatment and examination suitable for the patient at the visit destination.

[0008] This invention has been made in view of the above, and aims to realize effective individualized medical care during mobile clinic visits. [Means for solving the problem]

[0009] The information provision program according to the present invention causes the controller of the information provision device to execute processing. The information provision program receives a request for medical treatment at the patient's home and, based on information about the destination, information about the vehicle, and information about the patient that has been set in advance for the vehicle, executes processing to determine whether or not the vehicle will visit the patient's home. If the information provision program determines that it will visit the patient's home, it executes processing to notify the in-vehicle device installed in the vehicle of the location of the patient's home. [Effects of the Invention]

[0010] Even if a route and schedule for a home visit are determined when a patient requests a home visit during a mobile clinic visit, effective treatment cannot be provided if the medical services that can be performed using the vehicle do not match the patient's symptoms. In contrast, the present invention can support the planning of a medical service that considers not only the route and schedule, but also the matching of patient information with vehicle information. As a result, according to the present invention, effective individualized medical care can be realized during mobile clinic visits. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 shows an example of the configuration of a medical support system according to an embodiment. [Figure 2] Figure 2 shows an example of a server hardware configuration. [Figure 3] Figure 3 shows an example of the functional configuration of a server controller. [Figure 4] Figure 4 shows an example of the hardware configuration of an in-vehicle device. [Figure 5] Figure 5 shows an example of the functional configuration of a controller for an in-vehicle device. [Figure 6] FIG. 6 is a diagram showing an example of a vehicle table. [Figure 7] FIG. 7 is a diagram showing an example of a patient table. [Figure 8] FIG. 8 is a diagram showing an example of a home image. [Figure 9] FIG. 9 is a flowchart showing the processing flow of the server. [Figure 10] FIG. 10 is a diagram showing an example of a reservation screen for home visits. [Figure 11] FIG. 11 is a diagram showing an example of a reservation screen for individual medical treatments. [Figure 12] FIG. 12 is a flowchart showing the processing flow of the in-vehicle device. [Figure 13] FIG. 13 is a diagram showing an example of a map with information superimposed.

Embodiments for Carrying Out the Invention

[0012] [[ID=3G]]Hereinafter, embodiments of the information providing program, information providing apparatus, and in-vehicle device disclosed in the present application will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited by the embodiments shown below.

[0013] The medical support system according to the embodiment will be described using FIG. 1. FIG. 1 is a diagram showing a configuration example of the medical support system according to the embodiment. The medical support system 1 is a system for supporting home visits using a vehicle.

[0014] In home visits, a vehicle equipped with medical equipment and carrying staff (doctors, nurses, etc.) visits a specific place (such as a community center) where a plurality of patients gather. Then, the staff performs medical treatments (examinations, treatments, etc.) using the medical equipment at the visited place.

[0015] As shown in FIG. 1, the medical support system 1 includes a server 10, a terminal 20, a medical database 30, a vehicle 40, an in-vehicle device 50, terminals 60_1, 60_2, and 60_3.

[0016] The terminal 20 is used by an operator. The terminals 60_1, 60_2, and 60_3 are used by a user. The user is a person related to the patient himself or his family members such as the patient's family. The terminals 60_1, 60_2, and 60_3 may be referred to as the terminal 60 without distinction. Also, the number of terminals is not limited to that shown in FIG. 1.

[0017] The medical database 30 is a database provided in a server external to the server 10. Also, the medical database 30 may be provided inside the server 10. The server 10 is an example of an information providing device.

[0018] The server 10, the in-vehicle device 50, and the terminal 60 are connected via the network N. The network N is, for example, the Internet.

[0019] FIG. 2 is a diagram showing an example of the hardware configuration of the server. As shown in FIG. 2, the server 10 has an interface 11, a controller 12, and a memory 13.

[0020] The interface 11 performs input / output of data with other devices. For example, the interface 11 communicates with the in-vehicle device 50 and the terminal 60 via the network N.

[0021] The controller 12 reads and executes a program stored in the memory 13. The controller 12 is a CPU (Central Processing Unit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), a SoC (System on a Chip), etc.

[0022] The controller 12 may be a single processor. The controller 12 may have a multi-processor configuration. Also, the controller 12 may have a multi-core configuration in which a plurality of cores are provided in a single chip connected by a single socket.

[0023] Figure 3 shows an example of the functional configuration of the server controller. As shown in Figure 3, the controller 12 has a providing unit 121, a determination unit 122, and a notification unit 123.

[0024] The provision unit 121 provides information regarding mobile medical services. The provision unit 121 provides the terminal 60 with an input screen for requesting medical services. The provision unit 121 can accept requests for mobile medical services and individual medical services through the input screen.

[0025] Mobile medical services involve a vehicle equipped with medical equipment and staff (doctors, nurses, etc.) visiting specific locations (such as community centers) where multiple patients gather, and the staff providing medical care (examinations, treatments, etc.) using the medical equipment at those locations. Individual medical care involves staff providing medical care (examinations, treatments, etc.) using medical equipment at the patient's home.

[0026] The determination unit 122 determines whether or not vehicle 40 will visit the patient's home based on information about the destination pre-set for vehicle 40, information about vehicle 40, and information about the patient. Here, the destination pre-set for vehicle 40 is a specific place where multiple patients gather, i.e., a place where mobile medical services are conducted.

[0027] The notification unit 123 notifies the vehicle-mounted device 50 of the determination result. For example, the notification unit 123 notifies the vehicle-mounted device 50 to add the home of a patient who is the target of individual medical treatment as a waypoint to the route for mobile medical services.

[0028] Figure 4 shows an example of the hardware configuration of an in-vehicle device. As shown in Figure 4, the in-vehicle device 50 has an interface 51, a controller 52, a memory 53, and a display unit 54. The in-vehicle device 50 is, for example, a car navigation system.

[0029] Interface 51 performs data input and output with other devices. For example, interface 51 communicates with server 10 via network N. Interface 51 can also communicate with the ECU of vehicle 40 via wired or wireless communication.

[0030] The controller 52 reads and executes the program stored in memory 53. The controller 52 can be a CPU, DSP, FPGA, GPU, SoC, etc.

[0031] The controller 52 may be a single processor. The controller 52 may be a multi-processor configuration. Alternatively, the controller 52 may be a multi-core configuration having multiple cores within a single chip connected by a single socket.

[0032] Figure 5 shows an example of the functional configuration of a controller for an in-vehicle device. As shown in Figure 5, the controller 52 has a setting unit 521 and an output control unit 522.

[0033] The setting unit 521 sets the route according to the destination and waypoints. The output control unit 522 outputs information for moving the vehicle 40 according to the route. In other words, the setting unit 521 and the output control unit 522 realize the functions of a car navigation system.

[0034] The aforementioned medical database 30 stores a vehicle table and a patient table as data used in the processing of the server 10. The vehicle table contains information about vehicles used for medical treatment. The patient table contains information about patients who are the subjects of medical treatment.

[0035] Figure 6 shows an example of a vehicle table. As shown in Figure 6, the vehicle table 31 has columns for "Vehicle", "Doctor", "Specialty", "Nurse", "Medical Equipment", "Wheelchair Space", "Destination", "Date and Time of Consultation", "Departure Time", "Return Time", "Appointed Patient Name", and "Areas Where Visits are Possible".

[0036] The "Vehicle" column stores information identifying the vehicle. The "Doctor" column stores information identifying the doctor in the vehicle (e.g., name). The "Specialty" column stores the specialties the doctor is able to treat (e.g., surgery, internal medicine, etc.). The "Nurse" column stores information identifying the nurse in the vehicle (e.g., name). The "Medical Equipment" column stores information about the medical equipment installed in the vehicle. The "Wheelchair Space" column stores whether or not there is a wheelchair space in the vehicle. The "Destination" column stores information identifying the destination of the mobile clinic. The "Date and Time of Consultation" column stores the date and time of the mobile clinic. The "Departure Time" column stores the departure time of the mobile clinic. The "Return Time" column stores the return time of the mobile clinic. For example, in a mobile clinic, the vehicle departs from the hospital, visits the destination, and returns to the hospital after the consultation at the destination is completed. The "Appointed Patient Name" column stores information identifying the patient who has booked the mobile clinic. The "Areas where visits are possible" column stores information that identifies the areas where individual consultations are possible during mobile clinic visits.

[0037] Figure 6 shows that vehicle 40 is identified as "Z Wagon," and that it carries a doctor named "○○" who is capable of handling "internal medicine" as medical staff, and a nurse named "△△," and is equipped with "stethoscope, blood pressure monitor, and thermometer" as medical equipment, and has a wheelchair space. Figure 6 also shows that the destination of vehicle 40's mobile clinic on "2024 / 10 / 25" is "Y Community Center," the departure time is "9:00," the return time is "16:00," and the scheduled patients are "A, B, C, D."

[0038] Figure 6 also shows that the area where visitors can stop is "(x1, y1) ~ (x2, y2)". Here, the area where visitors can stop is represented by a rectangle with the coordinates of a specific point in the area (e.g., latitude and longitude) as its diagonal vertices. The area where visitors can stop is not limited to a rectangle; it may also be represented by a figure formed by curves. Furthermore, the coordinates of the specific points in the area may be three or more points, and a figure may be formed by straight lines or curves with each of these as vertices. In addition, the area where visitors can stop may be specified by a place name.

[0039] Figure 7 shows an example of a patient table. As shown in Figure 7, the patient table 32 has columns for "Address", "Name", "Age", "Doctor", "Disease / Medical Record / Prescription", "Date and Time of Visit", "Location of Visit", "Route", and "Photo of Front of Home".

[0040] The "Address" column stores the patient's address. The "Name" column stores the patient's name. The "Age" column stores the patient's age. The "Doctor" column stores the name of the doctor in charge of the patient. The "Disease / Medical Record / Prescription" column stores information describing the patient's symptoms. The "Date and Time of Visit" column stores the date and time of the last individual consultation for the patient. The "Visit Location" column stores information identifying the location of the individual consultation (the patient's home). The "Route" column stores the route to visit the patient's home. The "Image in Front of Home" column stores information to identify an image of the patient's home.

[0041] Figure 7 shows that patient "E"'s address is "G town, F city", their age is "90", their doctor is "XX", and their symptoms are "a cold". Figure 7 also shows that the date and time of the visit to patient "E" was "2024 / 9 / 25", the location of the visit was "G town, F city", the route was "P1→P2→P3", and the file for the image of the front of their house is "XXX.JPEG".

[0042] Here, an example of an image taken in front of a house is shown in Figure 8. Figure 8 is a diagram showing an example of an image taken in front of a house. For example, image 322 is captured by a camera mounted on vehicle 40 during individual medical consultations. Processing using image 322 will be described later.

[0043] Figure 9 will be used to explain the processing performed by the controller 12 of the server 10. Figure 9 is a flowchart showing the processing flow of the server.

[0044] As shown in Figure 9, first, the controller 12 starts the application for subsequent processing (step S101). Next, the controller 12 accepts the mobile clinic reservation and sets the schedule (step S102).

[0045] To accept reservations for mobile medical services, the controller 12 displays the reservation screen 811 shown in Figure 10 on the terminal 60 in response to a request from the terminal 60. Figure 10 is a diagram showing an example of a mobile medical service reservation screen. Note that each screen, including the reservation screen 811 provided by the controller 12, is, for example, a web page.

[0046] The controller 12 displays the date, time, location, etc. of the mobile medical service on the reservation screen 811 based on the vehicle table 31. When a specific operation (for example, pressing the reservation button) is performed on the reservation screen 811, the controller 12 transitions the screen to the reservation screen 812. The reservation screen 812 is where information of the patient who wishes to receive the mobile medical service is entered. The controller 12 stores the information entered on the reservation screen 812 in, for example, the "Patient Name" column of the vehicle table 31.

[0047] Returning to Figure 9, the controller 12 instructs the vehicle-mounted device 50 to set a route for mobile medical services (step S103).

[0048] Next, the controller 12 accepts reservations for individual consultations (step S104). Reservations for individual consultations may be accepted before the start of the mobile consultations by the vehicle 40, or during the mobile consultations by the vehicle 40 (for example, on the same day).

[0049] To accept individual consultation reservations, the controller 12 displays the reservation screen 821 shown in Figure 11 on the terminal 60 in response to a request from the terminal 60. Figure 11 is a diagram showing an example of an individual consultation reservation screen.

[0050] When a specific operation (for example, pressing the reservation button) is performed on the reservation screen 821, the controller 12 transitions the screen to the reservation screen 822. The reservation screen 822 is where information of patients who wish to receive individual medical treatment is entered. The controller 12 stores the information entered on the reservation screen 822 in the patient table 32.

[0051] Returning to Figure 9, the controller 12 determines whether the day of the mobile clinic and the desired date for the individual consultation are the same (step S105). If the day of the mobile clinic and the desired date for the individual consultation are not the same (step S105; No), the controller 12 proceeds to step S110.

[0052] If the day of the mobile clinic and the desired date for the individual consultation are the same (Step S105; Yes), the controller 12 displays the mobile clinic information and the individual consultation information on the map (Step S106). Specifically, the controller 12 displays an image of the map on the terminal 20 with the mobile clinic information and the individual consultation information superimposed.

[0053] Then, the controller 12 determines whether or not to stop by the patient's home in order to provide individualized medical care (step S107). At this time, the controller 12 determines whether or not the vehicle 40 will visit the patient's home based on the destination information pre-set for the vehicle 40, the information about the vehicle 40, and the information about the patient. For example, the controller 12 makes this determination by referring to information from both the vehicle table 31 and the patient table 32.

[0054] Thus, the controller 12 does not simply make a decision based on the time required if a stop is made, but rather refers to information from both the vehicle table 31 and the patient table 32 to match the patient with the vehicle 40 and then decide whether or not to make a stop. As a result, the server 10 can not only provide individualized medical care tailored to the patient, but also streamline mobile medical care by avoiding unnecessary individualized medical care, and ensure that individualized medical care is provided only when truly necessary. Consequently, according to this embodiment, effective individualized medical care can be achieved during mobile medical care.

[0055] If the controller 12 does not determine that a stop is to be made (step S108; No), the process proceeds to step S110. If the controller 12 determines that a stop is to be made (step S108; Yes), it instructs the in-vehicle device 50 to make a stop for individual medical treatment (step S109). At this time, if the controller 12 determines that a stop is to be made, that is, that it determines that it will visit the patient's home, it notifies the in-vehicle device 50 of the location of the patient's home.

[0056] If reservation acceptance has not yet ended (step S110; No), controller 12 returns to step S102 and continues to accept reservations. If reservation acceptance has ended (step S110; Yes), controller 12 terminates the process. Reservation acceptance is terminated if there is an explicit operation from terminal 60, or if the reservation period has expired.

[0057] Figure 12 will be used to explain the processing performed by the controller 52 of the in-vehicle device 50. Figure 12 is a flowchart showing the processing flow of the in-vehicle device.

[0058] As shown in Figure 12, first, the controller 52 starts the application for subsequent processing (step S201). Next, the controller 52 sets the route for the mobile medical service (step S202). The route for the mobile medical service is instructed to the in-vehicle device 50 from the server 10 in step S103 of Figure 9.

[0059] The controller 52 provides route guidance according to the set route (step S203). The controller 52 can provide voice or image navigation. For example, the controller 52 displays an image showing a map and route on the display unit 54.

[0060] Here, the controller 52 checks for instructions to make a stop (step S204). The controller 52 may also query the server 10 at regular intervals to check for instructions to make a stop. If there are no instructions to make a stop (step S205; No), the controller 52 proceeds to step S207.

[0061] If an instruction to make a stop is given (Step S205; Yes), the controller 52 readjusts the route to take the stop into consideration (Step S206) and then determines whether the guidance is complete. If an instruction to make a stop is given, the controller 52 adds the home of the patient who is the subject of individual medical treatment as a waypoint to the route.

[0062] If the guidance is not yet complete (step S207; No), the controller 52 returns to step S203 and continues to provide route guidance. If the guidance is complete (step S207; Yes), the controller 52 terminates processing. The guidance is terminated if there is an explicit operation on the in-vehicle device 50, or when the vehicle 40 arrives at its destination.

[0063] [Examples] A specific implementation of the medical support system 1 described above will now be explained. It is assumed that the controller 12 has already created the data for the vehicle table 31 as shown in Figure 6, based on the acceptance of the mobile medical service.

[0064] The controller 12 receives individual consultation requests and creates data for the patient table 32 as shown in Figure 7. Here, an example of the map that the controller 12 displays in step S106 in Figure 9 is shown in Figure 13. Figure 13 is a diagram showing an example of a map with information superimposed.

[0065] As shown in Figure 13, the controller 12 provides an image of a map 84 in which the destination, the location of the patient's home, information about the vehicle 40, and information about the patient are superimposed. The information displayed on the map 84 will be described below.

[0066] As shown in Figure 13, the controller 12 displays shapes on the map 84 indicating locations 841, 842, and 843. Location 841 is "X Hospital," which is both the starting and ending point of the mobile clinic. Location 842 is "Y Community Center," which is the destination of the mobile clinic. Location 843 is the home of the patient receiving individual medical treatment.

[0067] Furthermore, the controller 12 displays area 844 on the map 84 that shows information related to mobile medical services, and area 845 that shows information related to individual medical services. Area 844 displays, for example, information related to the vehicle 40. Area 845 displays, for example, information related to the patient.

[0068] The controller 12 displays the current location of the vehicle 40 on the map 84. The controller 12 also displays a figure 847 on the map 84 indicating areas that can be visited, based on the value in the "Places to Visit" column of the vehicle table 31. At this time, the controller 12 may also display a figure 847 on the map 84 indicating areas where the increase in travel time due to a visit is within a certain amount of time (for example, 1 hour).

[0069] In this way, by displaying not only route information but also various other information on the map, server 10 can provide a wealth of information in an intuitive manner. Furthermore, when an operator decides whether or not to provide individualized medical care, server 10 can streamline the operator's thought process.

[0070] Area 845 displays the estimated travel time if vehicle 40 visits the patient's home. "10 minutes for individual travel + 30 minutes for consultation" represents the additional travel time if vehicle 40 stops at point 843 for individual consultation. This streamlines the operator's thought process, especially when deciding whether or not to provide individual consultation.

[0071] Furthermore, the controller 12 displays a home front image 322 near the location 843 of the patient's home, which is the subject of the individualized medical treatment. This allows, for example, the operator to communicate to the driver of the vehicle 40, based on the image 322, that caution is needed because the parking space is narrow, thereby making the individualized medical treatment more efficient. In addition, by saving the patient's home front image 322 in the medical database 30, useful information can be provided when individualized medical treatment is performed again in the future.

[0072] The controller 12 determines whether vehicle 40 will visit the patient's home for individualized medical treatment, based on pre-set destination information for vehicle 40, information about vehicle 40, and information about the patient. For example, vehicle table 31 includes information about the destination and the vehicle. Also, for example, patient table 32 includes information about the patient.

[0073] Furthermore, the decision of whether or not vehicle 40 will visit the patient's home for individual medical treatment may be made by an operator instead of the controller 12. The operator can make this decision by referring to the map 84 displayed on terminal 20. In this case, the controller 12 can support the operator's decision by displaying the route 846 if the vehicle visits the patient's home, and by highlighting the shape of point 843 with a flashing display or the like.

[0074] For example, the controller 12 determines that if the medical treatment that can be performed by the medical equipment installed in the vehicle 40 corresponds to the patient's symptoms, the vehicle 40 should visit the patient's home.

[0075] Controller 12 retrieves the patient's symptoms from the "Disease / Medical Record / Prescription" column in the patient table 32. Controller 12 also retrieves information about the medical devices installed in the vehicle 40 from the "Medical Devices" column in the vehicle table 31.

[0076] The controller 12 determines that if the medical equipment installed in the vehicle 40 matches the patient's symptoms, the vehicle 40 should visit the patient's home.

[0077] For example, let's assume that a "thermometer" is predetermined as a medical device that matches the symptom "cold." Therefore, in the examples in Figures 6 and 7, the controller 12 determines that the vehicle 40 will visit the patient's home.

[0078] Let's assume that the patient's symptoms are "fracture," and that a "cast" is predetermined as a medical device that matches the symptom "fracture." In this case, since vehicle 40 does not have a "cast" installed, the controller 12 determines that vehicle 40 will not visit the patient's home.

[0079] Furthermore, the controller 12 determines that if the medical treatment that the staff assigned to the vehicle 40 can perform corresponds to the patient's symptoms, then the vehicle 40 should visit the patient's home.

[0080] Controller 12 retrieves the patient's symptoms from the "Disease / Medical Record / Prescription" column in the patient table 32. Controller 12 also retrieves information about the specialty of the doctor in vehicle 40 from the "Specialty" column in the vehicle table 31.

[0081] The controller 12 determines that if the medical specialty of the doctor in vehicle 40 matches the patient's symptoms, then vehicle 40 should visit the patient's home.

[0082] For example, let's assume that "internal medicine" is predetermined as the medical specialty that matches the symptom "cold." Therefore, in the examples in Figures 6 and 7, the controller 12 determines that the vehicle 40 will visit the patient's home.

[0083] Let's assume that the patient's symptoms are "fracture," and that "orthopedics" is predetermined as the specialty that matches the symptom "fracture." In this case, since the doctor in vehicle 40 does not specialize in "orthopedics," the controller 12 determines that vehicle 40 will not visit the patient's home.

[0084] In this way, the controller 12 can prevent wasteful situations such as when vehicle 40 visits a patient's home but is unable to provide medical treatment, by matching information from vehicle 40 with patient information.

[0085] The controller 12 determines that vehicle 40 will visit the patient's home if the travel time, when the patient's home is added as a waypoint to the route via the destination, is below a threshold. For example, the controller 12 determines that vehicle 40 will visit the patient's home if the patient's home is located within the shape 847 in Figure 13. In this way, the controller 12 can provide a more practical determination result by matching patient information with vehicle 40 information and making a determination based on the required travel time.

[0086] Furthermore, the processes described so far as being performed by the server 10 may also be performed by the in-vehicle device 50. In that case, the in-vehicle device 50 will accept the request for medical treatment at the patient's home, and if the medical treatment that can be performed by the medical device corresponds to the patient's symptoms, it will add the location of the patient's home as a waypoint to a pre-set route and display the route.

[0087] Further effects and modifications can be readily derived by those skilled in the art. Therefore, broader aspects of the present invention are not limited to the specific details and representative embodiments expressed and described above. Accordingly, various modifications are possible without departing from the spirit or scope of the overall concept of the invention as defined by the appended claims and equivalents. [Explanation of Symbols]

[0088] 1. Medical Support System 10 servers 11, 51 Interfaces 12, 52 controllers 13.53 memory Terminals 20, 60, 60_1, 60_2, 60_3 30 Medical Databases 31 Vehicle Table 32 patient tables 40 vehicles 50 Onboard equipment 84 Map 121 Provision Department 122 Judgment section 123 Notification Department 322 images 521 Settings Section 522 Output Control Unit 811, 812, 821, 822 Reservation screen 841, 842, 843 points 844, 845 area Route 846 847 Shapes

Claims

1. We accept applications for medical consultations at the patient's home. Based on information about a destination pre-set for the vehicle, information about the vehicle, and information about the patient, it is determined whether or not the vehicle will visit the patient's home. If it is determined that the vehicle will visit the patient's home, the vehicle will notify the onboard device installed in the vehicle of the location of the patient's home. An information provision program that instructs the controller of the information provision device to perform the processing.

2. The information relating to the vehicle includes information relating to medical devices installed in the vehicle. The aforementioned determination process determines that if the medical treatment that can be performed by the medical equipment installed in the vehicle corresponds to the patient's symptoms, the vehicle should visit the patient's home. The information provision program according to claim 1.

3. The information relating to the vehicle includes information relating to the staff associated with the vehicle. The process of making the determination involves determining that if the medical treatment that the staff assigned to the vehicle can provide corresponds to the patient's symptoms, the vehicle will visit the patient's home. An information providing program according to claim 1 that causes processing to be executed.

4. The process for making the determination described above determines that the vehicle will visit the patient's home if the travel time when the patient's home is added as a waypoint to the route passing through the destination is less than or equal to a threshold. An information providing program according to claim 1 that causes processing to be executed.

5. The present invention provides a map image in which the destination, the location of the patient's home, information about the vehicle, and information about the patient are superimposed. The information providing program according to claim 1, which causes the controller to perform further processing.

6. The process provided above provides an image of the map in which the time required for the vehicle to visit the patient's home is further superimposed. The information provision program according to claim 5.

7. The process provided above provides the map image in which the image of the patient's home is further superimposed. The information provision program according to claim 5.

8. It has a controller that performs processing related to mobile medical services using a vehicle, The aforementioned controller, We accept applications for medical consultations at the patient's home. Based on information about a destination pre-set for the vehicle, information about the vehicle, and information about the patient, it is determined whether or not the vehicle will visit the patient's home. If it is determined that the vehicle will visit the patient's home, the vehicle will notify the onboard device installed in the vehicle of the location of the patient's home. Information provision device.

9. An in-vehicle device for route navigation installed in a vehicle equipped with medical equipment, We accept applications for medical consultations at the patient's home. If the medical treatment that can be performed by the aforementioned medical device corresponds to the patient's symptoms, The location of the patient's home is added as a waypoint to the pre-set route. Display the aforementioned route In-vehicle device.

Images