File transfer program, file transfer method and information processing device

Abstract

To improve usability in file transmission.SOLUTION: A file transfer program causes a computer to execute the processing to: receive input of a file related to a care plan or care results to be transmitted from a first business operator associated with care (for example, a home care support business office) to another business operator associated with care (for example, a care service business office); extract identification information on the business operator at the transmission destination from the file name of the file; manage the file while linking the file to the extracted identification information on the business operator at the transmission destination; and transmit the file linked to the identification information on the transmission destination to a second business operator corresponding to the identification information on the transmission destination when the identification information on the transmission destination is already stored in a storage part which stores pieces of identification information on respective business operators.SELECTED DRAWING: Figure 16

Description

[Technical field]

[0001] The present invention relates to a file transfer program, a file transfer method, and an information processing device. [Background technology]

[0002] In home care support, in order to enable users (those receiving care) to live their daily lives at home as independently as possible, care managers employed at home care support offices create home service plans (care plans) for each person receiving care. In addition, implementers (physiotherapists, occupational therapists, helpers, etc.) employed at the care service offices provide care services to the people receiving care based on the care plans created by the care managers, and report information on the results of these services to the home care support office.

[0003] At home care support offices, service delivery slips (plans) are created based on the care plan, and at care service offices, service delivery slips (actual results) are created based on the actual results of providing care services. Conventionally, these service delivery slips were handwritten or created on a PC and printed out, and therefore had to be exchanged between offices by fax or mail. In response to this, a method has recently become known for exchanging service delivery slip files (data) between offices using a care plan data linkage system established by the Ministry of Health, Labor and Welfare (see, for example, Non-Patent Document 1, etc.). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] “About the Care Plan Data Linkage System” [online], January 24, 2023, Nursing Care Insurance Division, National Health Insurance Association, [Searched August 24, 2023], Internet<URL:https: / / www.mhlw.go.jp / content / 12300000 / 001047111.pdf> Summary of the Invention [Problem to be solved by the invention]

[0005] However, when exchanging files between establishments using the care plan data linkage system of Non-Patent Document 1, if the destination establishment is not registered in the system, the file exchange will result in an error. For this reason, for example, it is not possible to send a file in advance (before registration) to an unregistered establishment, which is inconvenient.

[0006] In one aspect, the present invention aims to provide a file transfer program, a file transfer method, and an information processing device that can improve usability when transmitting files. [Means for solving the problem]

[0007] In one aspect, the file transfer program is a program that causes a computer to execute a process of accepting input of a file related to a care plan or care results to be sent from a first care-related business to another care-related business, extracting identification information of the destination business from the file name of the file, managing the file by linking it to the extracted identification information of the destination business, and referring to a memory unit that stores the identification information of each business, sending the file linked to the destination identification information to a second business corresponding to the destination identification information. Effect of the Invention

[0008] This can improve usability when sending files. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating a schematic configuration of a home care support system according to an embodiment. [Diagram 2]Figure 2(a) is a diagram showing the flow of care services provided to care recipients by a home care support facility and a care service facility, and Figure 2(b) is a diagram showing the processing executed in the server, the care support facility terminal, and the service facility terminal. [Diagram 3] FIG. 3(a) is a diagram showing the hardware configuration of a server, and FIG. 3(b) is a diagram showing the hardware configuration of a care support establishment terminal and a service establishment terminal. [Figure 4] FIG. 4 is a functional block diagram of the server. [Diagram 5] FIG. 5 is a diagram showing an example of a data structure of the transmission information DB. [Figure 6] FIG. 6 is a diagram showing an example of the data structure of the attachment file information DB. [Figure 7] FIG. 7 is a diagram showing an example of the data structure of the management information DB. [Figure 8] FIG. 8 is a diagram illustrating an example of a data structure of the establishment DB. [Figure 9] FIG. 9 is a flowchart showing the flow of a file transmission process by the server. [Figure 10] FIG. 10 is a diagram showing an example of a file to be uploaded. [Figure 11] 11(a) to 11(c) are diagrams for explaining information stored in the management information DB. [Figure 12] FIG. 12 is a diagram (part 1) showing the batch transmission screen. [Figure 13] FIG. 13 is a diagram (part 2) showing the batch transmission screen. [Figure 14] FIG. 14 is a flow chart showing the flow of processing performed by the server when downloading a file. [Figure 15] FIG. 15 is a flowchart showing the flow of file management processing by the server. [Figure 16] FIG. 16 is a diagram showing an overview of one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, one embodiment of the home care support system will be described in detail with reference to Figs.

[0011] Fig. 1 shows a schematic configuration of a home care support system 100 according to an embodiment. As shown in Fig. 1, the home care support system 100 includes a server 10 as an information processing device, a care support office terminal 60, and a service office terminal 70. The server 10, the care support office terminal 60, and the service office terminal 70 are connected to a network 80 such as the Internet.

[0012] Here, a home care support facility that possesses a care support facility terminal 60 and a care service facility that possesses a care support facility terminal 60 provide care services to a person receiving care (a person requiring care) in the manner shown in FIG. 2(a). (1) Home care support offices accept requests for the provision of home care support services from care recipients and their families (hereinafter referred to as "care recipients, etc."). (2) With the consent of the person receiving care, etc., the home care support facility will coordinate with the care service facility regarding the provision of services and prepare a "home care service plan" (hereinafter referred to as the "care plan"). (3) Based on the created care plan, the home care support facility will prepare a "Service Delivery Form (Planned)" and a "Home Service Plan" and send them to the care service facility. A "Service Delivery Form (Planned)" means a service delivery form with a plan for care services written in it. A "Home Service Plan" is a document that specifically describes the type, content, and frequency of services necessary to achieve the long-term and short-term goals of the person receiving care. (4) Upon receiving the service provision form (planned), the care service provider will provide services to the care recipient based on the service provision form (planned). (5) The nursing care service provider prepares a "Service Delivery Record (Results)" based on the services provided and transmits it to the home nursing care support provider. "Service Delivery Record (Results)" means a service delivery record in which the details of nursing care services provided to the care recipient for one month (Results) are entered. (6) The home care support facility shall prepare a "Benefits Management Form" based on the "Service Provision Form (Performance)" and send it to the National Health Insurance Association of each prefecture together with invoices for the cost of creating the care plan, etc.

[0013] FIG. 2(b) shows a schematic diagram of the processes executed in the server 10, the care support establishment terminal 60, and the service establishment terminal .

[0014] The home care support office creates the above (2) service delivery slip (plan) and home service plan using the care support office terminal 60. The home care support office also creates the above (6) benefit management slip using the care support office terminal 60. The care service office also creates the above (5) service delivery slip (actual results) using the service office terminal 70.

[0015] Meanwhile, the server 10 executes a process to transmit a file (data) of a service delivery slip (plan) created in the care support office terminal 60 to the service office terminal 70. The server 10 also executes a process to transmit a file of a service delivery slip (actual results) created in the service office terminal 70 to the care support office terminal 60. In other words, the server 10 has a function of mediating the exchange of service delivery slip files between the home care support office and the care service office.

[0016] FIG. 3(a) shows a schematic diagram of the hardware configuration of the server 10. As shown in FIG. 3(a), the server 10 includes a CPU (Central Processing Unit) 90, a ROM (Read Only Memory) 92, a RAM (Random Access Memory) 94, a storage (here, an SSD (Solid State Drive) or an HDD (Hard Disk Drive)) 96, a network interface 97, and a portable storage medium drive 99. These components of the server 10 are connected to a bus 98. In the server 10, the CPU 90 executes a program (including a file transfer program) stored in the ROM 92 or the HDD 96, or a program read by the portable storage medium drive 99 from the portable storage medium 91, thereby realizing the functions of the components shown in FIG. 4. The functions of the components in FIG. 4 may be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). Details of the components in FIG. 4 will be described later.

[0017] Fig. 3(b) shows a schematic diagram of the hardware configuration of the care support office terminal 60 and the service office terminal 70. The care support office terminal 60 and the service office terminal 70 are information processing devices such as PCs (Personal Computers). As shown in Fig. 3(b), the care support office terminal 60 and the service office terminal 70 include a CPU 190, a ROM 192, a RAM 194, a storage 196, a network interface 197, a display unit 193, an input unit 195, and a portable storage medium drive 199. The components of the care support office terminal 60 and the service office terminal 70 are connected to a bus 98.

[0018] (About Server 10 functions) Fig. 4 is a functional block diagram of the server 10. In the server 10, the CPU 90 as a processing unit executes a program to realize the functions of each unit shown in Fig. 4. Specifically, the server 10 functions as a file import unit 20, a transmission information extraction unit 22, an attachment file information creation unit 24, a transmission / reception management information creation unit 26, a screen display unit 28, a download request acceptance unit 40, a file acquisition unit 42, a file transmission unit 44, and a file management unit 46 shown in Fig. 4.

[0019] When a file (service delivery slip (plan), (actual results), or home service plan file) created at the care support business terminal 60 or the service business terminal 70 is uploaded, the file import unit 20 executes a process to import the file. The file import unit 20 stores the imported file in the file storage unit 30. Here, it is assumed that the uploaded file is a CSV file.

[0020] The transmission information extraction unit 22 refers to the file name of the imported file, extracts various information, and stores it in the transmission information DB 32. Here, the file name is given according to the rules set by the Ministry of Health, Labor and Welfare. For example, in the case of a service delivery slip (plan), it is "UP6KYO_target year and month (YYYYMM)_sender's business number (10 digits)_destination's business number (10 digits)_creation date and time (YYYYMMDDHHMMSS).csv". In addition, in the case of a home service plan, it is "UPSKYU_target year and month (YYYYMM)_sender's business number (10 digits)_destination's business number (10 digits)_creation date and time (YYYYMMDDHHMMSS).csv". In addition, in the case of a service delivery slip (actual results), it is "UP6JSK_target year and month (YYYYMM)_sender's business number (10 digits)_destination's business number (10 digits)_creation date and time (YYYYMMDDHHMMSS).csv".

[0021] Therefore, the transmission information extraction unit 22 can obtain the creation date, target date, sender's establishment number, and destination establishment number from the file name, and stores this information for each file in the transmission information DB 32. Here, the transmission information DB 32 has a data structure as shown in FIG. 5. Specifically, the transmission information DB 32 stores information extracted from the file name ("creation date", "target date", "sender's establishment", "destination establishment"). The transmission information DB 32 also stores file identification information ("management number") that is automatically assigned to each file, and a "transmission status" that indicates whether the file has been transmitted or not.

[0022] The attachment information creation unit 24 stores information on the files imported by the file import unit 20 in the attachment information DB 34. Here, the attachment information DB 34 has a data structure as shown in FIG. 6. Specifically, the attachment information DB 34 stores information on the "source establishment," "destination establishment," "management number," "serial number," "file name," and "storage path" for each file in association with each other. The home care support business simultaneously transmits a file of the service delivery slip (plan) and a file of the home service plan to the same destination. In this case, the serial number "1" is assigned to one file, and the serial number "2" is assigned to the other file. The "storage path" indicates the storage destination of the files in the file storage unit 30 of FIG. 4.

[0023] When a request to send an uploaded file is input from the care support business terminal 60 or the service business terminal 70, the transmission / reception management information creation unit 26 changes the "transmission status" of the transmission information DB 32 from "not yet" to "done". In addition, the transmission / reception management information creation unit 26 stores information on the file for which a batch transmission request has been made in the management information DB 36. Here, the management information DB 36 stores "schedule creation business", "management number (schedule)", "result creation business", and "management number (result)" in association with "No.". For example, assume that there is a request to send a file with management number "487010000100000000001". In this case, the transmission / reception management information creation unit 26 refers to the transmission information DB 32 and acquires the number "4870100001" of the source business and the number "4869011111" of the destination business corresponding to the management number "487010000100000000001". Then, the transmission / reception management information creation unit 26 registers the source establishment number "4870100001", the management number "48701000010000000001", and the destination establishment number "4869011111" in the "Schedule creation establishment", "Management number (scheduled)", and "Actual establishment" columns of the same row in the management information DB 36.

[0024] Here, there may be cases where the combination of the source establishment number and destination establishment number of the file to be sent matches the combination of the actual result creation establishment number and schedule creation establishment number already registered in the management information DB 36. In this case, the transmission / reception management information creation unit 26 registers the management number of the file to be sent in the "Management Number (Actual Results)" column of that row in the management information DB 36.

[0025] Returning to Fig. 4, the screen display unit 28 creates a screen for operation and transmits it to the care support establishment terminal 60 or the service establishment terminal 70. At this time, the screen display unit 28 may create the screen by referring to the transmission information DB 32 or the management information DB 36.

[0026] When a file download request is received from the care support establishment terminal 60 or the service establishment terminal 70, the download request receiving unit 40 receives the request and transmits the name of the file requested to be downloaded to the file acquisition unit .

[0027] The file acquisition unit 42 acquires the file for which a download request has been made from the file storage unit 30, creates a zip file including the script, and transmits the zip file to the file transmission unit 44.

[0028] The file transmission unit 44 transmits the zip file created by the file acquisition unit 42 to the terminal that has requested the download. The terminal that has received the zip file unzips the zip file and executes a script to store the file in a specified location within the terminal.

[0029] The file management unit 46 manages the files stored in the file storage unit 30 by referring to the business DB 38, the transmission information DB 32, and the attachment file information DB 34. FIG. 8 shows the data structure of the business DB 38 as a storage unit. As shown in FIG. 8, the business DB 38 stores the names of the business that registered to use the home care support system 100 in association with their business numbers. The file management unit 46 refers to the transmission information DB 32 to identify files of which the numbers of the destination business are not registered in the business DB 38. The file management unit 46 also refers to the transmission information DB 32 to identify files of which a predetermined period has elapsed since the creation date (or the target date) among the identified files. Then, the file management unit 46 reads the storage path of the identified file from the attachment file information DB 34, and deletes the file of the read storage path in the file storage unit 30.

[0030] (Regarding Server 10 processing) Next, the processing of the server 10 will be described in detail with reference to the flowcharts of FIGS. 9, 14 and 15, and other drawings as appropriate.

[0031] (File transmission process) FIG. 9 is a flowchart showing the flow of a file transmission process by the server 10.

[0032] 9 is started, first, in step S10, the screen display unit 28 waits until there is a request to display the upload screen. The upload screen is a screen for specifying a file to be sent and uploading it. When there is a display request from the care support business terminal 60 or the service business terminal 70 (hereinafter simply referred to as "terminal"), the screen display unit 28 proceeds to step S12.

[0033] In step S12, screen display section 28 transmits an upload screen to the terminal that transmitted the display request, and displays it on display section 193 of the terminal.

[0034] Next, in step S14, the file import unit 20 waits until the files are uploaded all at once. For example, assume that a user of the care support office terminal 60 selects multiple files as shown in Fig. 10 and inputs an upload request. In this case, the determination in step S14 is affirmative, and the process proceeds to step S16.

[0035] In step S16, the file import unit 20 imports the uploaded file and stores it in the file storage unit 30.

[0036] Next, in step S18, the transmission information extraction unit 22 extracts transmission information from the file name of each file and stores it in the transmission information DB 32 (FIG. 5). Specifically, the transmission information extraction unit 22 extracts information such as "creation date," "target date," "sender's establishment," and "destination establishment" from the file name of each file, and stores it in the transmission information DB 32. Note that at this stage, the "transmission status" column of the transmission information stored in the transmission information DB 32 is set to "not yet."

[0037] Next, in step S20, the attachment information creation unit 24 creates attachment information and stores it in the attachment information DB 34 (FIG. 6). At this time, there may be multiple files with the same combination of source and destination establishments. In this case, the attachment information creation unit 24 assigns different serial numbers to these multiple files.

[0038] Next, in step S22, the transmission / reception management information creation unit 26 creates transmission / reception management information and stores it in the management information DB 36. For example, when a file shown in FIG. 10 is uploaded as a file to be transmitted from the care support business terminal 60 to the service business terminal 70, information as shown in FIG. 11(a) is stored in the management information DB 36. On the other hand, assume that a file as shown in FIG. 11(b) is uploaded as a file to be transmitted from the service business terminal 70 to the care support business terminal 60 while the data in FIG. 11(a) is stored in the management information DB 36. In this case, the transmission / reception management information creation unit 26 checks whether the combination of the sender's business number "4869011111" and the destination's business number "4870100001" matches any of the combinations of the number of the record creation business and the number of the schedule creation business in the management information DB 36. In the example of Fig. 11(b), the combination of the sender's business number "4869011111" and the recipient's business number "4870100001" matches the combination of the actual result creation business number and the schedule creation business number in row No. 1 in Fig. 11(a). At this time, the transmission / reception management information creation unit 26 stores the management number of the uploaded file (=486901111110000000001) in the "Management Number (Actual Results)" column in row No. 1 of the management information DB 36, as shown in Fig. 11(c).

[0039] Next, in step S24, the screen display unit 28 creates a batch transmission screen and transmits it to the terminal, thereby displaying the batch transmission screen on the display unit 193 of the terminal. For example, when the file shown in FIG. 10 is uploaded as a file to be transmitted from the care support business terminal 60 to the service business terminal 70, a list transmission screen as shown in FIG. 12 is displayed. The batch transmission screen in FIG. 12 is a screen that displays information of the file to be transmitted to other business. The screen display unit 28 creates the batch transmission screen by referring to the transmission information DB 32, the management information DB 36, the business DB 38, etc. The user of the terminal can press the "Batch Transmission" button on the screen in FIG. 12. The screen when transmitting the files of the service provision slip (achievement) in a batch from the service business terminal 70 to the care support business terminal 60 is a screen as shown in FIG. 13. As shown in the first line of the screen in FIG. 13, the "Status" column to the right of "Service Business" is "Not Transmitted".

[0040] Next, in step S26, the transmission / reception management information creation unit 26 waits until a request for batch transmission of files is input from the terminal. When the "Batch Transmission" button is pressed on the screen of Figure 12 or Figure 13, the determination in step S26 becomes positive, and the process proceeds to step S28.

[0041] In step S28, the transmission / reception management information creating section 26 changes the "transmission status" of the transmission information DB 32 to "transmitted" for the files that were "not transmitted" on the screens of FIG. 12 and FIG.

[0042] With this, the processing in FIG. 9 ends.

[0043] (File download process) FIG. 14 is a flowchart showing the flow of processing by the server 10 when a file is downloaded to a terminal.

[0044] When the process of Fig. 14 is started, first, in step S50, the download request receiving unit 40 waits until a display request for a download screen is received from any terminal. When the display request is received from a terminal of any establishment registered in the establishment DB 38, the download request receiving unit 40 proceeds to step S52. Note that if the display request is received from a terminal of an establishment not registered in the establishment DB 38, the download request receiving unit 40 displays an error message or the like and ends the process of Fig. 14.

[0045] In step S52, the screen display unit 28 refers to the transmission information DB 32, creates a download screen displaying a list of files with the establishment that requested the display as the "destination establishment", and transmits the download screen to the terminal. Note that the download screen is provided with a "bulk download" button.

[0046] Next, in step S54, the download request receiving unit 40 waits until the "Bulk download" button is pressed. When the "Bulk download" button is pressed on the terminal, the process proceeds to step S56, and the file acquisition unit 42 and the file transmission unit 44 execute the file download process. Specifically, the file acquisition unit 42 acquires the file for which a download request has been made from the file storage unit 30, creates a zip file including the script, and transmits it to the file transmission unit 44. Then, the file transmission unit 44 transmits the zip file created by the file acquisition unit 42 to the terminal for which the download request has been made.

[0047] With this, the processing in FIG. 14 ends.

[0048] (File management processing) Fig. 15 is a flowchart showing the flow of file management processing by the server 10. The processing in Fig. 15 is executed, for example, once a month.

[0049] When the process of FIG. 15 is started, first, in step S80, the file management unit 46 identifies a file in the transmission information DB 32 that has an establishment not registered in the establishment DB 38 as the destination establishment.

[0050] Next, in step S82, the file management unit 46 deletes, among the identified files, files for which a predetermined period has passed since the creation date. The predetermined period can be, for example, three months. For example, if the process of FIG. 15 was executed in September 2023, among the files identified in step S80, files whose creation date is "2023 / 06" are to be deleted. Note that, in step S82, files for which a predetermined period has passed since the target date may be deleted. Then, the file management unit 46 reads out the storage path of the file to be deleted from the attachment file information DB 34, and deletes the file of the read storage path from the file storage unit 30. Note that, in the server 10, information related to the file deleted by the file management unit 46 may be deleted from the transmission information DB 32, the attachment file information DB 34, and the management information DB 36.

[0051] In this way, by deleting files sent to unregistered business establishments after a predetermined period of time has passed, unnecessary files can be deleted from the file storage unit 30. Furthermore, by managing files as described above, even if a file is sent to an unregistered business establishment, an error does not occur at the sending stage. This makes it possible to send files to unregistered business establishments in advance, improving usability when sending files.

[0052] With this, the processing in FIG. 15 ends.

[0053] FIG. 16 shows an outline of this embodiment. The step numbers in FIG. 16 correspond to those in FIG. 9 and FIG. 14. As shown in FIG. 16, according to this embodiment, when a file to be transmitted from a home care support business (or a care service business) to another business is input (uploaded), the server 10 retrieves the file (S16). The server 10 also extracts the business number of the transmission destination from the file name of the uploaded file (S18). The server 10 also manages the file in the attachment file information DB34 by linking it with the extracted business number of the transmission destination (S20). Then, in response to a request from a business whose business number is stored in the business DB38, the server 10 transmits a file linked to the business number of the business (S50 to S56). That is, the server 10 automatically extracts the business number of the transmission destination from the file name and transmits the file using the business number of the transmission destination, so that the transmission source business can transmit the file without separately specifying or inputting the transmission destination. In addition, in this embodiment, when the attachment information creation unit 24 manages a file in the attachment information DB 34, the file is managed even if the business number of the destination is not registered in the business DB 38. As a result, an error does not occur even if the business number of the destination is not registered in the business DB 38, so that a file can be sent in advance to an unregistered business. This improves usability when sending a file. In addition, in this embodiment, a file sent to an business not registered in the business DB 38 is deleted after a predetermined period of time has passed, so that unnecessary files can be deleted from the file storage unit 30 at an appropriate time, and the amount of data in the server 10 can be reduced.

[0054] In this embodiment, the management information DB36 manages the business number of the sender of the file, the business number of the destination, and the management number of the file in association with each other. If the combination of the business number of the sender of the file and the business number of the destination matches the combination of the business number of the destination and the business number of the sender included in a row of the management information DB36, the management number of the file is managed in that row. This makes it possible to easily create a batch transmission screen by using the management information DB36. Also, by looking at the management information DB36 of FIG. 7 or a screen created based on the management information DB36, the home care support business can easily check whether the service delivery slip (actual results) corresponding to each service delivery slip (planned) has been returned from the care service business.

[0055] In the above embodiment, a "Send all" button is provided on the screens of Figures 12 and 13, but this is not limited thereto, and a "Send selected" button for sending only selected files may be provided.

[0056] The above processing functions can be realized by a computer. In that case, a program is provided that describes the processing contents of the functions that the processing device should have. The above processing functions are realized on the computer by executing the program on the computer. The program that describes the processing contents can be recorded on a computer-readable recording medium (excluding carrier waves).

[0057] When a program is distributed, it is sold in the form of a portable recording medium on which the program is recorded, such as a DVD (Digital Versatile Disc), a CD-ROM (Compact Disc Read Only Memory), etc. The program can also be stored in a storage device of a server computer and transferred from the server computer to other computers via a network.

[0058] A computer that executes a program stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. The computer then reads the program from its own storage device and executes processing in accordance with the program. The computer can also read the program directly from a portable recording medium and execute processing in accordance with that program. The computer can also execute processing in accordance with the received program each time a program is transferred from the server computer.

[0059] The above-described embodiment is a preferred example of the present invention, but the present invention is not limited to this embodiment and can be modified in various ways without departing from the scope of the present invention.

[0060] In addition, the following supplementary notes are disclosed in relation to the above-described embodiment. (Appendix 1) Accepting input of a file related to a care plan or care record to be transmitted from a first care-related business to another care-related business, Extracting the identification information of the destination business operator from the file name of the file; managing the file in association with the extracted identification information of the destination business operator; When the identification information of the destination is stored in a storage unit that stores identification information of each business, the file associated with the identification information of the destination is transmitted to a second business corresponding to the identification information of the destination. A file transfer program that causes a computer to execute a process. (Appendix 2) The file transfer program according to appendix 1, wherein in the management process, the file is managed in association with identification information of the destination operator even if the extracted identification information of the destination is not stored in the memory unit. (Appendix 3) The file transfer program according to Appendix 2, characterized in that the computer is caused to execute a process of deleting files linked to identification information that is not stored in the memory unit after a predetermined period of time has elapsed. (Appendix 4) A file transfer program as described in any one of Appendices 1 to 3, characterized in that the computer is caused to execute a process of generating management information that links and manages identification information of a provider that sends the file, identification information of a provider that receives the file, and identification information of the file. (Appendix 5) A file transfer program as described in Appendix 4, characterized in that if a combination of identification information of the sender operator and the destination operator of the file matches a combination of identification information of the destination operator and the sender operator contained in specified management information, the identification information of the file is managed in the specified management information. (Supplementary Note 6) The file transfer program according to any one of Supplementary Notes 1 to 5, wherein the process of transmitting the file includes a process of displaying the file on a terminal of the second business so as to be downloadable. (Appendix 7) Accepting input of a file related to a care plan or care performance to be transmitted from a first care-related business to another care-related business; Extracting the identification information of the destination business operator from the file name of the file; managing the file in association with the extracted identification information of the destination business operator; When the identification information of the destination is stored in a storage unit that stores identification information of each business, the file associated with the identification information of the destination is transmitted to a second business corresponding to the identification information of the destination. A file transfer method, characterized in that processing is executed by a computer. (Appendix 8) Accepting input of a file related to a care plan or care performance to be transmitted from a first care-related business to another care-related business; Extracting the identification information of the destination business operator from the file name of the file; managing the file in association with the extracted identification information of the destination business operator; When the identification information of the destination is stored in a storage unit that stores identification information of each business, the file associated with the identification information of the destination is transmitted to a second business corresponding to the identification information of the destination. An information processing device including a processing unit that executes processing. [Explanation of symbols]

[0061] 10 Server (information processing device) 20 File Import Section 22 Transmission information extraction unit 24 Attachment information creation section 26 Transmission and Reception Management Information Creation Department 28 Screen display section 30 File Storage 32 Transmission information DB 34 Attachment information DB 36 Management information DB 38 Office DB (Storage Department) 40 Download request reception section 42 File Acquisition Section 44 File transmission section 46 File Management Section 60 Nursing care support office terminal 70 Service business terminal 90 CPU (processing unit)

Claims

1. Accepting input of a file related to a care plan or care record to be transmitted from a first care-related business to another care-related business; Extracting the identification information of the destination business operator from the file name of the file; managing the file in association with the extracted identification information of the destination business operator; When the identification information of the destination is stored in a storage unit that stores identification information of each business, the file associated with the identification information of the destination is transmitted to a second business corresponding to the identification information of the destination. A file transfer program that causes a computer to execute a process.

2. 2. The file transfer program according to claim 1, wherein in the management process, the file is managed in association with identification information of a business of the destination even if the extracted identification information of the destination is not stored in the storage unit.

3. 3. The file transfer program according to claim 2, further comprising a step of causing the computer to execute a process of deleting a file associated with identification information that is not stored in the storage unit after a predetermined period of time has elapsed.

4. The file transfer program according to claim 1, characterized in that the computer is caused to execute a process of generating management information that links and manages identification information of the operator that sent the file, identification information of the operator that is the destination of the file, and identification information of the file.

5. The file transfer program according to claim 4, characterized in that if a combination of identification information of the sender operator and the destination operator of the file matches a combination of identification information of the destination operator and the sender operator contained in specified management information, the identification information of the file is managed in the specified management information.

6. The file transfer program according to claim 1 , wherein the process of transmitting the file includes a process of displaying the file on the terminal of the second business operator so as to be downloadable.

7. Accepting input of a file related to a care plan or care record to be transmitted from a first care-related business to another care-related business; Extracting the identification information of the destination business operator from the file name of the file; managing the file in association with the extracted identification information of the destination business operator; When the identification information of the destination is stored in a storage unit that stores identification information of each business, the file associated with the identification information of the destination is transmitted to a second business corresponding to the identification information of the destination. A file transfer method, characterized in that processing is executed by a computer.

8. Accepting input of a file related to a care plan or care record to be transmitted from a first care-related business to another care-related business; Extracting the identification information of the destination business operator from the file name of the file; managing the file in association with the extracted identification information of the destination business operator; When the identification information of the destination is stored in a storage unit that stores identification information of each business, the file associated with the identification information of the destination is transmitted to a second business corresponding to the identification information of the destination. An information processing device including a processing unit that executes processing.

Images