Program, method, and device

Abstract

To improve convenience when transmitting a replacement file from a transmission source to a transmission destination.SOLUTION: A program causes a computer to perform the following processing. The processing includes transmitting a cancellation request of registration at the destination of a first file transmitted to the destination to the destination, obtaining a second file for replacement of the first file, and transmitting the second file to the destination in response to receiving a notification of completion of cancellation processing in response to the cancellation request.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to a program, a method, and an apparatus. [Background technology]

[0002] A transmission service that supports the transmission of files from a source terminal to a destination system is known. The system receives the file from the transmission service, performs a reception process including checking the format of the file, and notifies the terminal of the reception result via the transmission service once the reception is complete.

[0003] The reception system has a mechanism for eliminating duplicate file reception, and when multiple files with the same identification information are received, the reception system notifies the terminal of an error during the reception process for the second or subsequent files received among the multiple files.

[0004] By eliminating duplicate acceptance in this way, if there is an error in a transmitted file, for example, the terminal sends a request to cancel that file to the receiving system via the transmission service and waits to receive a completion response indicating that the file cancellation process is complete. Upon receiving the completion response from the receiving system, the terminal transmits the replacement file with the error corrected to the receiving system via the transmission service, and receives an acceptance result from the receiving system indicating that acceptance of the replacement file has been completed, thereby completing the file replacement. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-097545 Summary of the Invention [Problem to be solved by the invention]

[0006] As described above, the reception system will not be able to accept a replacement file until the file cancellation process is complete.

[0007] Therefore, the terminal cannot transmit the replacement file to the receiving system via the transmission service until it receives a cancellation processing completion response from the receiving system, which is inconvenient. If the terminal transmits the replacement file without waiting to receive the completion response from the receiving system, an error will occur in the receiving system's reception processing of the file, and the replacement may fail.

[0008] In one aspect, an object of the present invention is to improve convenience when transmitting a replacement file from a sender to a destination. [Means for solving the problem]

[0009] In one aspect, the program A device capable of communicating with both the source and destination terminals The computer may be caused to perform the following process: The aforementioned Sending to the destination a request to cancel registration at the destination of the first file sent to the destination; From the terminal The method may include a process of obtaining a second file to replace the first file, and transmitting the second file to the destination in response to receiving a notification of completion of the cancellation process in response to the cancellation request. [Effects of the Invention]

[0010] In one aspect, the present invention can improve the convenience when transmitting a replacement file from a sender to a destination. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 10 is a diagram illustrating an example of the operation of the nursing care claim system. [Figure 2] 1 is a block diagram illustrating an example of the configuration of a care claim system according to an embodiment. [Figure 3] FIG. 10 is a diagram for explaining an example of a replacement process in the care claim system according to an embodiment. [Figure 4] FIG. 2 is a block diagram showing an example of the hardware (HW) configuration of a computer that realizes the functions of the transmission system. [Figure 5] 1 is a block diagram illustrating an example of a functional configuration of a care claim system according to an embodiment. [Figure 6] FIG. 10 is a diagram illustrating an example of a care claim screen. [Figure 7] FIG. 10 is a diagram illustrating an example of transmission information. [Figure 8] FIG. 10 is a sequence diagram illustrating a first operation example of a replacement process according to an embodiment. [Figure 9] FIG. 10 is a diagram showing a care claim screen in the first operation example. [Figure 10] 10A and 10B are diagrams illustrating changes in transmission information in the first and second operation examples. [Figure 11] FIG. 10 is a sequence diagram illustrating a second operation example of the replacement process according to an embodiment. [Figure 12] FIG. 10 is a diagram showing a care request screen in the second operation example. [Figure 13] FIG. 10 is a sequence diagram illustrating a third operation example of the replacement process according to an embodiment. [Figure 14] FIG. 10 is a diagram showing a care claim screen in the third and fourth operation examples. [Figure 15] FIG. 10 is a diagram illustrating changes in transmission information in the third operation example. [Figure 16] FIG. 10 is a sequence diagram illustrating a fourth operation example of the replacement process according to an embodiment. [Figure 17] FIG. 10 is a diagram showing changes in transmission information in the fourth operation example. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the embodiments described below are merely examples, and are not intended to exclude various modifications or application of techniques not explicitly described below. For example, the present embodiment can be implemented with various modifications within the scope of the spirit thereof. In the drawings used in the following description, parts with the same reference numerals represent the same or similar parts unless otherwise specified.

[0013] [1] One embodiment [1-1] An example of a transmission service Below, we will explain the nursing care claim transmission service, which supports nursing care claims, as an example of a transmission service. The nursing care claim transmission service (hereinafter simply referred to as the "transmission service") provides an environment for businesses and other operators to submit nursing care claims to the National Federation of National Health Insurance Organizations (hereinafter referred to as the "NHI Federation").

[0014] For example, a business that provides nursing care insurance services to a user submits a nursing care claim to the National Health Insurance Federation within a specified period. Hereinafter, "nursing care claim" refers to a claim for a portion (e.g., 80% or 90%) of the cost of the nursing care insurance services provided by the business to the user. As one method of nursing care claim processing, the National Health Insurance Federation provides an API (Application Programming Interface) that accepts files in a specified format containing nursing care benefit claim forms and nursing care benefit details from businesses via the Internet.

[0015] For example, the transmission service provides a transmission environment for transmitting files in a specified format from a business operator's terminal to the National Health Insurance Association's API via the Internet.

[0016] 1 is a diagram showing an example of the operation of a nursing care claim system 100. The nursing care claim system 100 is a system for making a nursing care claim by transmitting a file (data) from a terminal 121 of a business operator 120 to a reception system 131 of a National Health Insurance Association 130 via a transmission system 110. The transmission system 110 is a system that provides a transmission service.

[0017] In the example of Fig. 1, a user of the business operator 120 transmits a file 140 in a predetermined format for making a nursing care claim from the terminal 121 to the reception system 131 via the transmission system 110. The reception system 131 executes reception processing 131a, which includes checking the format of the file 140.

[0018] For example, if there is an error in a transmitted file 140, the user operates the terminal 121 to transmit a cancellation request 150 for the file 140 to the reception system 131 via the transmission system 110. The user also transmits a replacement file 160 from the terminal 121 to the reception system 131 via the transmission system 110.

[0019] Here, in order to prevent duplicate reception of files relating to the same care claim, the reception system 131 notifies the terminal of an error in the reception process for, for example, a file received later among files relating to the same care claim. In the example of Fig. 1, the file 160 transmitted immediately after operation 121a results in a reception error in the reception system 131.

[0020] For example, after receiving the cancellation request 150, the reception system 131 notifies the terminal 121 of a cancellation completion response, thereby becoming able to receive the replacement file 160 (see reference numeral 131b). Note that, after receiving the cancellation request 150, the National Health Insurance Association 130 may take several tens of minutes, for example, about 30 to 90 minutes, before sending the cancellation completion response.

[0021] When the user confirms the receipt of the cancellation completion response by operating 121 b on the terminal 121 , the user transmits the replacement file 160 to the reception system 131 via the transmission system 110 by operating 121 c on the terminal 121 .

[0022] The reception system 131 executes reception (replacement) processing for the replacement file 160, and after a processing time, for example, about 60 minutes, notifies the terminal 121 that the file 160 has arrived.

[0023] The user confirms that the replacement of the file 140 for the care claim has been completed normally by operating the terminal 121 d to confirm the receipt of the notification of the completion of arrival.

[0024] As such, there is a time lag (30 to 90 minutes in the example of Figure 1) between when terminal 121 sends the cancellation request and when it receives notification of cancellation completion from reception system 131, so the user will have to postpone sending file 160 until they receive notification of cancellation completion.

[0025] Furthermore, if the user sends file 160 before receiving notification of the completion of cancellation, as in the case of sending file 160 immediately after operation 121a (see Figure 1), the file 160 may result in a reception error and may not be registered in the reception system 131.

[0026] As described above, in the transmission system 110, when the replacement file 160 is transmitted from the business operator 120 to the National Health Insurance Association 130, convenience may be reduced.

[0027] Furthermore, if the file 160 results in a reception error in the receiving system 131, the file 160 will be transmitted multiple times over the transmission system 110 until the replacement of the file 160 is completed. This increases the communication load and processing load of the transmission system 110, as well as the processing load of the terminal 121 and the receiving system 131.

[0028] Therefore, in one embodiment, as an example of a transmission service, a nursing care claim transmission service that can improve the convenience when transmitting a replacement file from a business operator to the National Health Insurance Association will be described.

[0029] [1-2] Example of the configuration of a nursing care claim system according to one embodiment Figure 2 is a block diagram showing an example of the configuration of a nursing care claim system 1 according to one embodiment. The nursing care claim system 1 is a system that allows users of businesses such as offices to submit nursing care claims to the National Health Insurance Federation. As shown in Figure 2, the nursing care claim system 1 may, for example, include a transmission system (nursing care claim transmission system) 2 that transmits files for nursing care claims, one or more (multiple in the example of Figure 2) terminals 3 used by users of the business, and a reception system 4 that allows the National Health Insurance Federation to accept files.

[0030] The transmission system 2 and each of the one or more terminals 3 may be connected to each other via a network 1a so that they can communicate with each other. The transmission system 2 and the receiving system 4 may be connected to each other via a network 1b so that they can communicate with each other. Each of the networks 1a and 1b may include one or both of the Internet and a LAN (Local Area Network).

[0031] The transmission system 2 is connected to one or more terminals 3 and the receiving system 4 so as to be able to communicate with each other, and performs various communications relating to the transmission of files between the terminals 3 and the receiving system 4.

[0032] As an example, the transmission system 2 may provide the terminal 3 with a web service for registering (uploading) a file, replacing a file, checking the file transmission status, etc. Furthermore, for example, the transmission system 2 may transmit a file registered or replaced by the terminal 3 to the reception system 4 via the API of the reception system 4.

[0033] The transmission system 2 may include, for example, one or more servers, and these servers may work together to realize the functions of the transmission system 2. The server is an example of a computer or an information processing device. Furthermore, at least some of the functions of the transmission system 2 may be provided as a cloud service.

[0034] The terminal 3 is an example of a computer or information processing device, and may be, for example, various information processing terminals used by a user, such as a PC (Personal Computer), a smartphone, a tablet terminal, etc. The terminal 3 may have the same configuration as the terminal 121 shown in FIG.

[0035] The terminal 3 may be capable of executing an application program for creating a file for a nursing care claim and transmitting the file to the reception system 4 via a web service provided by the transmission system 2. The terminal 3 may transmit and receive various information related to the transmission of files to and from the transmission system 2 by executing the application program.

[0036] The application program may be, for example, a program such as a web browser that can display the screen of a web service (web page) provided by the transmission system 2. The application program may include a program for processing at least a part of the web service on the terminal 3 side.

[0037] The reception system 4 is an example of a file destination, and executes reception processing including format checks of files received from the transmission system 2, and upon completion of reception, notifies the terminal 3 of the reception result via the transmission system 2. In addition, in order to eliminate duplicate reception of files relating to the same care claim, the reception system 4 notifies the terminal of an error in the reception processing for, for example, files relating to the same care claim that are received later.

[0038] The receiving system 4 may include, for example, one or more servers, and the functions of the receiving system 4 may be realized by cooperation of these servers. The server is an example of a computer or an information processing device. The receiving system 4 may also provide the transmission system 2 with an API for communication related to file transmission. The receiving system 4 may have, for example, the same configuration as the receiving system 131 shown in FIG. 1.

[0039] 3 is a diagram illustrating an example of a replacement process in the nursing care claim system 1 according to an embodiment. As shown in FIG. 3, the transmission system 2 receives a replacement file 310 uploaded by a user operation 301a. The transmission system 2 transmits a cancellation request 320 for the replacement file 310 to the reception system 4, and stores the replacement file 310 in a storage area of ​​the transmission system 2.

[0040] The "original file to be replaced" is an example of a first file, and the "replacement file" is an example of a second file. The original file 310 to be replaced and the replacement file 310 may each contain details of nursing care benefit expenses related to the same nursing care claim.

[0041] The transmission system 2 transmits the replacement file 310 to the receiving system 4 when the receiving system 4 becomes able to accept the replacement file 310, for example, 30 to 90 minutes later. For example, the transmission system 2 may transmit the replacement file 310 to the receiving system 4 in response to receiving (catching) a notification of cancellation completion from the receiving system 4.

[0042] The reception system 4 executes reception (replacement) processing for the replacement file 310, and after a processing time, for example, about 60 minutes, notifies the terminal 3 that the file 310 has arrived.

[0043] The user confirms that the file replacement for the care claim has been completed normally by operating the terminal 3 (301b) and confirming that the notification of arrival has been received.

[0044] In this way, the transmission system 2 sends a request to the receiving system 4 to cancel the registration at the receiving system 4 for the file that was sent to the receiving system 4, obtains a file to replace the file, and sends the replacement file to the receiving system 4 in response to receiving a notification that the cancellation process for the cancellation request has been completed.

[0045] As a result, according to the transmission system 2 of one embodiment, the user can complete the operations related to the registration and transmission of the replacement file 310 without waiting for a cancellation completion notification from the reception system 4. In other words, the transmission system 2 allows the user to complete the operations related to the replacement process with a single operation 301a related to the registration of the replacement file 310, instead of the three operations indicated by reference numerals 121a to 121c in Fig. 1.

[0046] This prevents the user from forgetting to resend the replacement file 310 after the cancellation is complete, and from forgetting to make a request due to duplicate transmission during the cancellation. Also, the user can effectively use the time from when the cancellation request 150 is made to when the replacement file 160 is resent in the example of Figure 1 for other tasks.

[0047] As described above, the transmission system 2 can improve the convenience of transmitting the replacement file 310 from the business operator to the National Health Insurance Association. Furthermore, since unnecessary transmission of the file 310 from the transmission system 2 to the reception system 4 can be suppressed, an increase in the communication load and processing load of the transmission system 2, as well as the processing load of the terminal 3 and the reception system 4, can be suppressed.

[0048] [1-3] Hardware configuration example The HW (hardware) that realizes the transmission system 2 according to an embodiment may be a virtual server (VM) or a physical server. The functions of the transmission system 2 may be realized by one computer or two or more computers. Furthermore, at least some of the functions of the transmission system 2 may be realized using HW resources and NW (Network) resources provided by a cloud environment.

[0049] 4 is a block diagram showing an example of a hardware (HW) configuration of a computer 10 that realizes the functions of the transmission system 2. When multiple computers are used as HW resources that realize the functions of the transmission system 2, each computer may have the HW configuration exemplified in FIG.

[0050] As shown in FIG. 4, the computer 10 may include, as a HW configuration, a processor 10a, a memory 10b, a storage unit 10c, an IF (Interface) unit 10d, an IO (Input / Output) unit 10e, and a reading unit 10f, for example.

[0051] The processor 10a is an example of a processing unit that performs various controls and calculations. The processor 10a may be connected to each block in the computer 10 via a bus 10i so that they can communicate with each other. The processor 10a may be a multiprocessor including multiple processors, a multi-core processor having multiple processor cores, or a configuration having multiple multi-core processors.

[0052] The processor 10a may be, for example, an integrated circuit (IC) such as a CPU, MPU, GPU, APU, DSP, ASIC, or FPGA. Note that the processor 10a may be a combination of two or more of these integrated circuits. CPU is an abbreviation for Central Processing Unit, MPU is an abbreviation for Micro Processing Unit, GPU is an abbreviation for Graphics Processing Unit, and APU is an abbreviation for Accelerated Processing Unit. DSP is an abbreviation for Digital Signal Processor, ASIC is an abbreviation for Application Specific IC, and FPGA is an abbreviation for Field-Programmable Gate Array.

[0053] The memory 10b is an example of HW that stores various types of data, programs, and other information. Examples of the memory 10b include a volatile memory such as a dynamic random access memory (DRAM) and / or a non-volatile memory such as a persistent memory (PM).

[0054] The storage unit 10c is an example of HW that stores various types of data, programs, and other information. Examples of the storage unit 10c include various storage devices such as a magnetic disk device such as a hard disk drive (HDD), a semiconductor drive device such as a solid state drive (SSD), and a nonvolatile memory. Examples of nonvolatile memory include a flash memory, a storage class memory (SCM), and a read-only memory (ROM).

[0055] The storage unit 10c may store a program 10g (transmission control program) that realizes all or part of the various functions of the computer 10.

[0056] For example, the processor 10a of the computer 10 can realize the functions of the transmission system 2 illustrated in FIG. 3 and the control unit 27 illustrated in FIG. 5 by expanding and executing the program 10g stored in the storage unit 10c in the memory 10b.

[0057] The IF unit 10d is an example of a communication IF that controls connections and communications with various networks including the networks 1a and 1b. For example, the IF unit 10d may include an adapter that complies with a LAN such as Ethernet (registered trademark) or optical communications such as FC (Fibre Channel). The adapter may support either or both of wireless and wired communication methods.

[0058] For example, the computer 10 that realizes the functions of the transmission system 2 may be connected to one or more terminals 3 via the IF unit 10d and the network 1a so that they can communicate with each other. The computer 10 may also be connected to the reception system 4 via the IF unit 10d and the network 1b so that they can communicate with each other. The program 10g may be downloaded to the computer 10 from the network 1a or 1b or another network via the communication IF and stored in the storage unit 10c.

[0059] The IO unit 10e may include one or both of an input device and an output device. Examples of input devices include a keyboard, a mouse, and a touch panel. Examples of output devices include a monitor, a projector, and a printer. The IO unit 10e may also include a touch panel that combines an input device and a display device.

[0060] The reading unit 10f is an example of a reader that reads data and program information recorded on the recording medium 10h. The reading unit 10f may include a connection terminal or device to which the recording medium 10h can be connected or inserted. Examples of the reading unit 10f include an adapter that complies with USB (Universal Serial Bus) or the like, a drive device that accesses a recording disk, and a card reader that accesses a flash memory such as an SD card. Note that the recording medium 10h may store the program 10g, and the reading unit 10f may read the program 10g from the recording medium 10h and store it in the memory unit 10c.

[0061] Examples of the recording medium 10h include non-transitory computer-readable recording media such as magnetic / optical disks and flash memories. Examples of magnetic / optical disks include flexible disks, CDs (Compact Discs), DVDs (Digital Versatile Discs), Blu-ray Discs, and HVDs (Holographic Versatile Discs). Examples of flash memories include semiconductor memories such as USB memories and SD cards.

[0062] The above-described hardware configuration of the computer 10 is an example. Therefore, the hardware in the computer 10 may be increased or decreased (for example, adding or deleting any block), divided, integrated in any combination, or buses may be added or deleted as appropriate.

[0063] Furthermore, each of the one or more terminals 3 shown in FIG. 2 and each of the one or more servers that realize the functions of the reception system 4 may have the same hardware configuration as the computer 10 described above.

[0064] [1-4] Example of functional configuration Fig. 5 is a block diagram showing an example of a functional configuration of a care claim system 1 according to an embodiment. As shown in Fig. 5, the transmission system 2 in the care claim system 1 may illustratively include a DB (Database) unit 21, an input control unit 22, an output control unit 23, a DB access unit 24, a transmission / reception processing unit 25, and a replacement control unit 26. These functional blocks 22 to 26 are an example of a control unit 27. Note that the control unit 27 may be, for example, at least a part of the functions of a program 10g shown in Fig. 4.

[0065] The DB unit 21 is an example of a storage area or a storage device, and stores various data used by the transmission system 2. As shown in Fig. 5, the DB unit 21 may be capable of storing, for example, transmission information 21a and one or more (plural in Fig. 5) files 21b.

[0066] The input control unit 22 controls the input of various information to the transmission system 2. As an example, the input control unit 22 may accept input of input information from the terminal 3. The "reception" of the input of input information may include, for example, outputting the acquired input information to at least one of the function blocks 23 to 26 or the DB unit 21. The output to the DB unit 21 may include, for example, working in cooperation with the DB access unit 24 to store the input information in transmission information 21a or to store it in the DB unit 21 as file 21b.

[0067] The input control unit 22 may receive input information via, for example, the IF unit 10d shown in Fig. 4. Note that the reception of input information via the IF unit 10d may include, for example, the reception of a request or a response from an application program such as a web browser of the terminal 3.

[0068] The output control unit 23 controls various outputs to the terminal 3. For example, the output control unit 23 may control the output based on information or instructions input from at least one of the functional blocks 22, 24 to 26. The output control may include generating and transmitting display information to the terminal 3. The display information may be, for example, screen information such as a web page. For example, the output control unit 23 may transmit the display information to the terminal 3 via the network 1a. The transmission of the display information may include, for example, transmitting a response in response to a request from a web browser of the terminal 3.

[0069] Fig. 6 is a diagram showing an example of a care claim screen 30. As shown in Fig. 6, the output control unit 23 may generate, as screen information, for example, the care claim screen 30 to be displayed on a web browser on the display device of the terminal 3 (for example, the IO unit 10e in Fig. 4). The care claim screen 30 is a screen for registering, replacing, and deleting files 21b for care claims, and for checking the reception status of the files 21b at the reception system 4. The care claim screen 30 is an example of screen information that associates one or more files 21b transmitted to the reception system 4 with the reception status of the one or more files 21b at the reception system 4.

[0070] The care request screen 30 may include buttons 31 to 34 and a display area 35, as shown in FIG.

[0071] The button 31 is a button for selecting the file 21b to be transmitted, and pressing the button 31 may display a screen (not shown) for registering (uploading) the file. The button 31 is an example of a second operation area for transmitting at least one file 21b to the reception system 4.

[0072] The button 32 is a button for sending (transmitting) to the reception system 4 the file 21b registered by the button 31 or a button 37a described later.

[0073] The button 33 is a button for canceling the transmission of the file 21b transmitted by the button 32, in other words, for deleting the file 21b from the receiving system 4.

[0074] The button 34 is a button for displaying a screen (not shown) showing a list of errors related to the processing in response to pressing of the button 32 or 33, for example, a list of errors notified from the reception system 4.

[0075] The display area 35 is an area for displaying information for each file 21b, and may include a check box 36 and areas 37-39.

[0076] Checkbox 36 is an area for selecting one or more files 21b, and for example, a process is performed on the file 21b corresponding to the checked checkbox 36 in response to pressing button 32 or 33. Checkbox 36 and button 33 are an example of a third operation area for individually canceling one or more files 21b.

[0077] Area 37 is an area showing the current status of each file 21b, and may include items such as business name, status, and error code.

[0078] Area 38 is an area showing the contents of each file 21b, for example, information on the number of nursing care benefit claim forms and nursing care benefit details, amounts, etc. Area 38 may include the file name of file 21b.

[0079] Area 39 is an area showing information such as the arrival number for each file 21b, which is notified from the receiving system 4 that has received the file 21b.

[0080] As shown in FIG. 6, the display area 35, for example, an area 37, may display a replacement button 37a (indicated as "Replace").

[0081] The replace button 37a is a button for replacing the file 21b for which the transmission process has been performed with another file 21b. The replace button 37a may be displayed in an entry for a file 21b for which the replacement process according to one embodiment can be executed. The replace button 37a is an example of a first operation area for registering a replacement file 21b in association with each replaceable file 21b among the one or more files 21b.

[0082] In one embodiment, various conditions can be exemplified for the file 21b for which replacement processing can be executed. In the example of Fig. 6, a replace button 37a is displayed for each entry of a file 21b for which reception processing has been completed in the reception system 4 and a file 21b that was not accepted in the reception processing due to a format error. Note that in the display area 35, an entry of a file 21b for which transmission processing is performed by pressing the replace button 37a may be displayed in a "waiting for replacement" state.

[0083] In this way, the output control unit 23 may generate the care claim screen 30 based on the transmission information 21a of the DB unit 21 via the DB access unit 24. Furthermore, the input control unit 22 may store input information input from the terminal 3 through the user's operation of the care claim screen 30 in the DB unit 21 via the DB access unit 24.

[0084] 5, the DB access unit 24 accesses the DB unit 21. For example, the DB access unit 24 may update the transmission information 21a and register or delete the file 21b in the transmission information 21a.

[0085] Fig. 7 is a diagram showing an example of the transmission information 21a. Note that, for convenience, Fig. 7 shows the transmission information 21a in a table format, but this is not limiting. The transmission information 21a may be stored in the DB unit 21 in various formats, such as a DB format or an array format. Also, Fig. 7 shows the transmission information 21a as information in one table, but this is not limiting, and the transmission information 21a may be information that combines multiple tables.

[0086] 7, the transmission information 21a may include, for example, the following items: "establishment number," "file name," "transmission management number," "sent date and time," "arrival code," "arrival name," "cancellation status," "arrival number," "cancellation status flag," "error code," "error content," and "cancellation flag." In addition to the information shown in FIG. 7, the transmission information 21a may also include various information displayed in the display area 35 of the care claim screen 30 shown in FIG. 6.

[0087] The "establishment number" is an example of identification information of the establishment (business) to which the terminal 3 belongs. The "file name" is the name of the file 21b registered in the transmission system 2 via the care claim screen 30 for transmission (new transmission or replacement transmission) to the reception system 4. The "file name" may include information indicating the storage location of the file 21b in the DB section 21, such as a file path.

[0088] The "transmission management number" is a number used to manage the transmission of the file 21b or request (request) in the transmission system 2, and is an example of identification information for the transmitted data on the transmission system 2 side. As illustrated in FIG. 7, the transmission management number may include the business number. The "transmission date and time" is an example of the date and time (timestamp) when the file 21b or request is transmitted. The "arrival code" and "arrival name" are a code (identification information) indicating the status of the transmitted file 21b or request in the receiving system 4, and a status name linked to the code.

[0089] The "cancellation status" indicates the status of the cancellation process in the receiving system 4 in response to the cancellation request for file 21b. For example, the cancellation status may be set to "Null" or "0" if the cancellation request has not been sent or the cancellation process has not been completed in the receiving system 4, and may be set to "cancellation completed" or "1" if the cancellation process has been completed.

[0090] The "arrival number" is a number used to manage the arrival of the file 21b or request in the receiving system 4, and is an example of identification information for the received data on the side of the receiving system 4. The "error code" and "error content" indicate the code (identification information) of an error that occurred in the receiving system 4 during the reception process for the arrived file 21b or request, and the content of the error.

[0091] The "cancellation flag" is a flag indicating whether the file 21b of the entry is a file 21b to be cancelled or a replacement file 21b; for example, "1" may indicate that the file 21b is a file 21b to be cancelled, and "2" may indicate that the file 21b is a replacement file 21b. In one embodiment, the uploaded replacement file 21b (stored in the DB unit 21) is held in the DB unit 21 until it becomes available for acceptance by the reception system 4. Therefore, setting the cancellation flag to "2" may mean that a replacement transmission is scheduled.

[0092] The transmission / reception processing unit 25 performs transmission / reception processing for the receiving system 4. For example, the transmission / reception processing unit 25 may transmit a file 21b or a request to the API of the receiving system 4, and may receive a message or a response from the API of the receiving system 4. In the transmission / reception processing, the transmission / reception processing unit 25 may update the transmission information 21a via the DB access unit 24.

[0093] The replacement control unit 26 performs replacement control in response to pressing of the replacement button 37a. For example, the replacement control unit 26 may control the transmission / reception processing unit 25 based on the transmission information 21a so as to transmit the replacement file 21b after the cancellation process of the replacement source file 21b is completed in the reception system 4.

[0094] Incidentally, the transmission system 2 may realize each processing function by, for example, having a plurality of devices (for example, servers) linked to one another via a network.

[0095] For example, the DB unit 21 may be one or more DB servers, and the input control unit 22, the output control unit 23, and the DB access unit 24 may be one or more Web servers and / or one or more application servers. The transmission / reception processing unit 25 and the replacement control unit 26 may be one or more application servers (for example, transmission servers having a transmission (communication) function).

[0096] In the following explanation, as illustrated in Figures 8 and onwards, the input control unit 22, output control unit 23 and DB access unit 24 are realized by the AP server 5, the DB unit 21 is realized by the DB server 6, and the transmission / reception processing unit 25 and replacement control unit 26 are realized by the transmission server 7.

[0097] [1-5] Example of replacement process Next, a detailed operation example of the replacement process by the transmission system 2 will be described. The replacement process according to an embodiment may be realized in any of a number of ways. First to fourth operation examples will be described below as detailed operation examples of the replacement process.

[0098] [1-5-1] First operation example Fig. 8 is a sequence diagram for explaining a first operation example of the replacement process according to an embodiment, and Fig. 9 is a diagram showing the care claim screen 30 in the first operation example. Fig. 10 is a diagram showing changes in the transmission information 21a in the first and second operation examples.

[0099] As illustrated in Figure 8, the AP server 5 refers to the transmission information 21a of the transmission system 2, obtains a list of files 21b to be transmitted related to the business to which the terminal 3 connected to the transmission system 2 belongs (process P1), and transmits a care claim screen 30 including the list to the terminal 3.

[0100] The terminal 3 displays the received care claim screen 30 (see FIG. 9) on the display device (process P2). For example, when the user presses the replacement button 37a of the third entry in the area 35 of FIG. 9 and selects the replacement file 21b on the selection screen (not shown) for the file 21b, the terminal 3 uploads the file 21b (process P3).

[0101] The AP server 5 writes a cancellation request to the transmission information 21a of the DB server 6 based on the entry of the pressed replacement button 37a and the uploaded file 21b, and confirms the transmission of the cancellation request (process P4). For example, the AP server 5 updates the entry of the file 21b to be canceled in the transmission information 21a and creates an entry for the cancellation request. The AP server 5 also stores the replacement file 21b in the DB server 6.

[0102] 10, symbol A indicates an entry for the original file 21b (file name "AAAAA.csv"), and symbol B indicates an entry for a request to cancel the original file 21b. For example, the AP server 5 creates a cancellation request entry (symbol B) that does not include a file name, and sets the cancellation flag of the entry for the original file 21b (symbol A) to "1."

[0103] When the transmission server 7 detects an entry to be canceled in which the cancellation flag is set to "1" from the transmission information 21a, it sends the contents of the entry of the cancellation request to the reception system 4 (API) by specifying the arrival number of the file 21b to be canceled (process P5). The reception system 4 executes the reception process of the cancellation request (process P6). The reception system 4 issues an arrival number related to the arrival number of the file 21b to be canceled (for example, by adding "1" to the end) to the cancellation request. When the transmission server 7 receives the arrival number of the reception request from the reception system 4, it sets the arrival number in the entry marked B in the transmission information 21a.

[0104] Furthermore, the terminal 3 may acquire information such as the number of items and the amount based on the replacement file 21b and transmit it to the AP server 5 (process P7). The AP server 5 creates an entry (record) for the replacement file 21b in the transmission information 21a based on the information acquired by the terminal 3 (or information acquired by itself from the file 21b) (process P8). Note that processes P4 and P8 may be executed in parallel (almost simultaneously).

[0105] 10, symbol C indicates an entry of the replacement file 21b (file name "BBBBB.csv"). For example, the AP server 5 sets the cancellation flag of the entry (symbol C) of the replacement file 21b to "2", which indicates a replacement transmission reservation.

[0106] When the transmission server 7 receives a completion notification of the cancellation request from the reception system 4 a predetermined time later (for example, about one hour) after sending the cancellation request, the transmission server 7 writes the cancellation result to the transmission information 21a (process P9). For example, as shown by symbol E in FIG. 10, the transmission server 7 may set "reception completed" to the arrival name of the entry of the cancellation request that matches the arrival number indicated in the completion notification. Also, as shown by symbol D in FIG. 10, the transmission server 7 may set "cancellation completed" or "1" to the cancellation status of the entry to be canceled that is associated with the arrival number indicated in the completion notification. The transmission server 7 may also notify the terminal 3 of the completion of the cancellation process by a method such as email (process P10).

[0107] In response to receiving the notification of completion of the cancellation request, the transmission server 7 transmits the replacement file 21b stored in the DB server 6 to the receiving system 4 (process P11). The receiving system 4 executes the reception process for the replacement file 21b (process P12). For example, as shown by symbol F in FIG. 10, the transmission server 7 may confirm the transmission of the replacement file 21b with the cancellation flag set to "2" and transmit it to the receiving system 4. The receiving system 4 issues a delivery number for the replacement file 21b. When the transmission server 7 receives the delivery number from the receiving system 4, it sets the delivery number in the entry for symbol F in the transmission information 21a.

[0108] When the transmission server 7 receives a notification of completion of the reception process for the replacement file 21b from the reception system 4, it may notify the terminal 3 of the completion of the reception process by a method such as email (process P13). The transmission server 7 may also write the reception result in the transmission information 21a. For example, as shown by symbol G in Figure 10, the transmission server 7 may set the arrival code and arrival name of the entry in file 21b that matches the arrival number indicated in the completion notification to "5C05" and "reception completed", respectively, and clear the deletion flag (or set it to "0").

[0109] As described above, in the first operation example, in response to the user's designation of the replacement file 21b for the original file 21b, the transmission system 2 issues a cancellation request for the original file 21b to the receiving system 4 and reserves the transmission of the replacement file 21b. After the cancellation process by the receiving system 4 is completed, the transmission system 2 transmits the replacement file 21b to the receiving system 4 (without going through the user).

[0110] This allows the user to complete the replacement of file 21b simply by specifying the file 21b to be cancelled and each replacement file 21b (for example, by pressing the replace button 37a for each file 21b to upload the replacement file 21b). Therefore, the user is freed from being tied up in the time from when he or she made a cancellation request until the replacement file 160 is sent after notification of the completion of the cancellation process as shown in FIG. 1.

[0111] In addition, the user can detect the completion of the acceptance process for the replacement file 21b through a notification such as an email from the transmission system 2, which reduces the time the user is required to spend at the business premises and prevents errors or missed billing for the replacement file 21b.

[0112] [1-5-2] Second operation example FIG. 11 is a sequence diagram for explaining a second operation example of the replacement process according to an embodiment, and FIG. 12 is a diagram showing the care claim screen 30 in the second operation example.

[0113] The second operation example differs from the first operation example in that the transmission system 2 enables replacement of the file 21b for which a normal cancellation request has been made. For example, as shown in Fig. 12, the AP server 5 may display a replacement button 37a on the second entry whose status is being cancelled, thereby enabling replacement processing of the file 21b of that entry.

[0114] A second operation example of the replacement process will be described below with reference to Fig. 11. In the example of Fig. 11, the processes denoted by the same reference numerals as in Fig. 8 are the same as the processes already described with reference to Fig. 8. In addition, in the process shown in Fig. 11, the change in the transmission information 21a is the same as the change described with reference to Fig. 10.

[0115] In process P2, when the care claim screen 30 (see Figure 12) is displayed on the terminal 3, the user requests cancellation of the file 21b of the second entry, for example, by selecting the check box 36 of the second entry and pressing the button 33 (process P21).

[0116] Based on the cancellation request of the second entry, the AP server 5 writes the cancellation request to the transmission information 21a of the DB server 6 and confirms the transmission of the cancellation request (process P22). For example, the AP server 5 updates the entry of the file 21b to be canceled in the transmission information 21a (for example, by setting the cancellation flag to "1") and creates an entry for the cancellation request.

[0117] When the transmission server 7 detects an entry to be cancelled, in which the cancellation flag is set to "1", from the transmission information 21a, it sends the contents of the entry of the cancellation request to the receiving system 4 (API) by specifying the arrival number of the file 21b to be cancelled (process P23). The receiving system 4 executes the acceptance process of the cancellation request (process P24). Processes P21 to P24 may be regarded as the normal cancellation process of the file 21b.

[0118] After issuing the cancellation request, when the user presses the replacement button 37a of the second entry and selects the replacement file 21b on the file 21b selection screen (not shown), the terminal 3 uploads the file 21b (process P25). The AP server 5 stores the replacement file 21b in the DB server 6 based on the entry of the pressed replacement button 37a and the uploaded file 21b.

[0119] Furthermore, the terminal 3 may acquire information such as the number of items and the amount based on the replacement file 21b and transmit it to the AP server 5 (process P26). The AP server 5 creates an entry (record) for the replacement file 21b in the transmission information 21a based on the information acquired by the terminal 3 (or information acquired by itself from the file 21b) (process P27).

[0120] As described above, the second operation example can achieve the same effect as the first operation example, and the transmission system 2 can also accept the specification of a replacement file 21b for the original file 21b for which a cancellation request has been made earlier by the user.

[0121] Furthermore, since the cancellation process for the original file 21b is already underway when the user uploads the replacement file 21b, the time required for the replacement file 21b to be sent to the reception system 4 after notification of the completion of the cancellation process can be made shorter than in the first operation example.

[0122] [1-5-3] Third operation example Fig. 13 is a sequence diagram for explaining a third operation example of the replacement process according to an embodiment, and Fig. 14 is a diagram showing the care claim screen 30 in the third and fourth operation examples. Fig. 15 is a diagram showing changes in the transmission information 21a in the third operation example.

[0123] The third operation example differs from the first or second operation example (the second operation example in Figure 13) in that the transmission system 2 enables one or more files 21b to be uploaded without the user being aware of the replacement.

[0124] 14, the user can issue a request to cancel one or more files 21b by selecting a check box 36 and pressing a button 33. The user can also select one or more replacement files 21b as files 21b to be uploaded by using a file 21b selection screen (not shown) that is displayed by pressing a button 31, or by dragging the file 21b onto the care claim screen 30, for example.

[0125] In such an operation, if the file 21b to be uploaded is a file 21b intended to replace the file 21b for which a cancellation request has been issued, in the example of Figure 1, the file 160 to be uploaded will result in a delivery error and will fail to be transmitted to the receiving system 131.

[0126] In the third operation example, when a file 21b to replace the file 21b for which a cancellation request has been issued is selected as the file to be uploaded, the transmission system 2 reserves the transmission of the file 21b to be uploaded in response to an arrival error response from the receiving system 4. This allows the user to issue a cancellation request and perform an operation to upload the replacement file 21b, and enables the replacement file 21b to be transmitted to the receiving system 4 without the user being aware of the replacement.

[0127] In the third operation example, as shown in FIG. 14, the replacement button 37a (see FIGS. 9 and 12) displayed on the care request screen 30 in the first and second operation examples may be omitted.

[0128] A third operation example of the replacement process will be described below with reference to Fig. 13. In the example of Fig. 13, processes with the same reference numerals as in Fig. 11 are the same as the processes already described with reference to Fig. 11. In addition, in the example of Fig. 15, entries with the same reference numerals as in Fig. 10 are the same as the entries already described with reference to Fig. 10.

[0129] After a request to cancel one or more files 21b is issued in processes P21 to P24, the terminal 3 uploads the one or more files 21b, for example, by selecting one or more files 21b including a replacement file 21b and pressing button 32 (process P31).

[0130] Furthermore, the terminal 3 may acquire information such as the number of items and the amount based on the replacement file 21b and transmit it to the AP server 5 (process P32). The AP server 5 creates an entry (record) for the replacement file 21b in the transmission information 21a based on the information acquired by the terminal 3 (or information acquired by itself from the file 21b) (process P33).

[0131] 15, the transmission server 7 transmits the replacement file 21b stored in the DB server 6 to the receiving system 4 (process P34). The receiving system 4 executes a receiving process for the replacement file 21b (process P35).

[0132] However, because the cancellation process for the replacement file 21b has not been completed, the transmission server 7 receives an arrival error from the receiving system 4 (process P36). The arrival error includes, for example, the error code "ZZZZZ" indicating that the replacement file 21b has already been claimed with the arrival number "YYYYY0" (see symbol A), as shown by symbol I in Fig. 15.

[0133] In this case, the transmission server 7 identifies the arrival number "YYYYY0" of the file 21b in which the arrival error occurred based on the error content, and determines whether the arrival number is the file 21b for which a cancellation request is being made (process P37).

[0134] If the arrival number "YYYYY0" is not the file 21b for which a cancellation request is being made (NO in process P37), the transmission server 7 notifies the terminal 3 of information including the error code and error content of the arrival error, for example, by a method such as email (process P38). In this case, the user issues a cancellation request based on the notification. That is, in the nursing care claim system 1, the processes from process P21 onwards are executed.

[0135] If the arrival number "YYYYY0" is the file 21b for which a cancellation request is being made (YES in process P37), the transmission server 7 executes a replacement creation process (process P39). In the replacement creation process, the transmission server 7 creates an entry for the replacement file 21b in the transmission information 21a based on the notification of the arrival error, and reserves the transmission of the file 21b. In the example of Figure 15, the transmission server 7 creates a new entry for the replacement file 21b, as shown by symbol J, and sets a new transmission management number and a cancellation flag "2" in the entry.

[0136] Furthermore, the transmission server 7 may notify the terminal 3 that the replacement creation process has been executed, for example, by email or other means (process P40). As an example, the transmission server 7 may send a message to the terminal 3 such as "The replacement file is being sent during the cancellation request. The replacement file will be automatically sent after the cancellation is complete."

[0137] When the transmission server 7 receives the processing result of the cancellation request acceptance processing in the processing P24, it executes the processing from the processing P9 onwards based on the information of the entry created in the replacement creation processing.

[0138] For example, the transmission server 7 writes the cancellation result in the transmission information 21a (process P9; see symbols D and E in FIG. 15), and notifies the terminal 3 of the completion of the cancellation process by e-mail or other means (process P10).

[0139] Furthermore, in response to receiving the notification of completion of the cancellation request, the transmission server 7 transmits the replacement file 21b stored in the DB server 6 to the receiving system 4 (process P11). The receiving system 4 executes a reception process for the replacement file 21b (process P12). For example, as shown by symbol K in FIG. 15, the transmission server 7 may confirm the transmission of the replacement file 21b corresponding to the entry created in the replacement creation process (the entry for which the cancellation flag "2" is set), and transmit it to the receiving system 4. The receiving system 4 issues a delivery number for the replacement file 21b. Upon receiving the delivery number from the receiving system 4, the transmission server 7 sets the delivery number (for example, "YYYYY3") in the entry of the transmission information 21a.

[0140] When the transmission server 7 receives a notification of completion of the reception process for the replacement file 21b from the reception system 4, it may notify the terminal 3 of the completion of the reception process by a method such as email (process P13). The transmission server 7 may also write the reception result in the transmission information 21a. For example, as shown by symbol L in Figure 15, the transmission server 7 may set the arrival code and arrival name of the entry in file 21b that matches the arrival number "YYYYY3" indicated in the completion notification to "5C05" and "Reception Completed", respectively, and clear the deletion flag (or set it to "0").

[0141] As described above, in the third operation example, the transmission system 2 transmits a group of files uploaded from the terminal 3 to the reception system 4, and when an arrival error is received from the reception system 4, the transmission system 2 identifies (detects) the original and replacement files 21b based on the arrival error. Then, the transmission system 2 reserves the identified replacement file 21b for transmission, and transmits the replacement file 21b after completing the cancellation process for the identified original file 21b.

[0142] As a result, in the third operation example, the same effects as those of the first and second operation examples can be achieved, and the user can omit the task of associating the original file 21b with the replacement file 21b, and can replace multiple files 21b at once.

[0143] In addition, the reception system 4 associates the original file 21b with the replacement file 21b based on the logic of the reception process, and notifies the transmission server 7 of the association result as an arrival error, thereby reducing the risk of mistaking the file 21b to be replaced.

[0144] [1-5-4] Fourth operation example FIG. 16 is a sequence diagram for explaining a fourth operation example of the replacement process according to an embodiment, and FIG. 17 is a diagram showing changes in the transmission information 21a in the fourth operation example.

[0145] The fourth operation example differs from the first or second operation example in that the transmission system 2 allows the user to replace multiple files 21b at once.

[0146] For example, as shown in FIG. 14, the user can select one or more replacement files 21b as files 21b to be uploaded by pressing a button 31 or the like.

[0147] In the first to third operation examples, the transmission system 2 detects, from among the files 21b to be uploaded, the files 21b that are being cancelled by receiving a notification of an arrival error from the receiving system 4.

[0148] On the other hand, the fourth operation example is premised on the assumption that the determination logic of the reception process in the reception system 4 is disclosed to the transmission system 2. For example, the transmission system 2 determines, based on the uploaded file 21b, whether the file 21b is a file 21b for normal registration or a file 21b for replacement. If the uploaded file 21b is a file 21b for replacement, the transmission system 2 requests the cancellation of the original file 21b and suspends and reserves the transmission of the replacement file 21b.

[0149] This allows a plurality of files 21b to be replaced at once without the user being aware of the cancellation request and replacement.

[0150] A fourth operation example of the replacement process will be described below with reference to Fig. 16. In the example of Fig. 16, processes with the same reference numerals as in Fig. 13 are the same as the processes already described with reference to Fig. 13. In addition, in the example of Fig. 17, entries with the same reference numerals as in Fig. 15 are the same as the entries already described with reference to Fig. 15.

[0151] On the care claim screen 30, the terminal 3 selects one or more files 21b including the replacement file 21b and presses the button 32, thereby uploading the one or more files 21b to the AP server 5 (process P41).

[0152] In addition, the terminal 3 obtains information such as the number of items and the amount based on each of the one or more files 21b, creates an entry for each file 21b in the transmission information 21a via the AP server 5 (process P42), and confirms the transmission (process P43; see symbol M in Figure 17).

[0153] The AP server 5 checks whether each of the one or more files 21b whose transmission has been confirmed by the terminal 3 is a file 21b to be replaced based on the transmission information 21a (process P44). For example, the AP server 5 may read detailed information about the files 21b and write information about the relationship between the files 21b into the transmission information 21a. Examples of information about the relationship between the files 21b include information such as "date of claim," "business number," "date of service provision," "data type," "insurer number," "insured person number," "arrival number," and "cancellation status."

[0154] The AP server 5 determines whether or not an entry with the same information about the relationship between the files 21b already exists in the transmission information 21a for each of the one or more files 21b (process P45). For example, the AP server 5 may determine whether or not an entry with the same "business establishment number," "billing year / month," and "data type" already exists in the transmission information 21a for each of the one or more files 21b.

[0155] If the entry does not exist in the transmission information 21a (NO in process P45), the transmission server 7 transmits the uploaded file 21b to the receiving system 4 as a normal transmission based on the transmission information 21a (process P46). The receiving system 4 executes the reception process for the file 21b (process P47). Processes P41 to P43, P46, and P47 may be considered as normal transmission processes for the file 21b.

[0156] If an entry exists in the transmission information 21a in process P45 (YES in process P45), the AP server 5 creates a cancellation request based on the entry and the uploaded file 21b (process P46; see symbol N in Figure 17) and stores the entry in the transmission information 21a.

[0157] When the transmission server 7 detects an entry to be canceled in which the cancellation flag is set to "1" from the transmission information 21a, it transmits the contents of the entry of the cancellation request, specifying the arrival number of the file 21b to be canceled, to the reception system 4 (process P49). The reception system 4 executes reception processing of the cancellation request (process P50). Based on the transmission information 21a updated by the transmission server 7, the AP server 5 may display the status "canceling" in the entry of the file 21b to be canceled on the nursing care claim screen 30.

[0158] Furthermore, the AP server 5 confirms the transmission of the replacement file 21b, of the uploaded files 21b, for which an entry exists in the transmission information 21a (process P51).

[0159] The transmission server 7 updates the entry for the replacement file 21b in the transmission information 21a to reserve the transmission of the file 21b (process P52; see symbol O in FIG. 17). Based on the transmission information 21a updated by the transmission server 7, the AP server 5 may display the status "waiting for replacement" in the entry for the replacement file 21b on the care claim screen 30.

[0160] When the transmission server 7 receives the processing result of the cancellation request acceptance processing in the processing P50, it executes the processing from the processing P9 onwards based on the information of the entry updated in the processing P52.

[0161] For example, the transmission server 7 writes the cancellation result in the transmission information 21a (process P9; see symbols D and E in FIG. 17), and notifies the terminal 3 of the completion of the cancellation process by e-mail or other means (process P10).

[0162] Furthermore, in response to receiving the notification of completion of the cancellation request, the transmission server 7 transmits the replacement file 21b stored in the DB server 6 to the receiving system 4 (process P11). The receiving system 4 executes a reception process for the replacement file 21b (process P12). For example, as shown by symbol P in FIG. 17, the transmission server 7 may confirm the transmission of the replacement file 21b corresponding to the entry updated in process P52 (the entry for which the cancellation flag "2" is set), and transmit the replacement file 21b to the receiving system 4. The receiving system 4 issues a delivery number for the replacement file 21b. Upon receiving the delivery number from the receiving system 4, the transmission server 7 sets the delivery number (for example, "YYYYY2") in the entry of the transmission information 21a.

[0163] When the transmission server 7 receives a notification of completion of the reception process for the replacement file 21b from the reception system 4, it may notify the terminal 3 of the completion of the reception process by a method such as email (process P13). The transmission server 7 may also write the reception result in the transmission information 21a. For example, as shown by symbol Q in Figure 17, the transmission server 7 may set the arrival code and arrival name of the entry in file 21b that matches the arrival number "YYYYY2" indicated in the completion notification to "5C05" and "Reception Completed", respectively, and clear the deletion flag (or set it to "0").

[0164] As described above, in the fourth operation example, when the file 21b is uploaded from the terminal 3, the transmission system 2 checks whether the contents of the file 21b match those sent to the receiving system 4. If they match, the transmission system 2 executes a cancellation process for the file 21b sent to the receiving system 4, and after the cancellation is complete, sends the uploaded file 21b as a replacement.

[0165] In this way, in the fourth operation example, it is possible to eliminate the need for the user to perform an operation to cancel the file 21b, thereby improving user convenience.

[0166] In the fourth operation example, the files 21b that are the subject of a cancellation request determined by the transmission system 2 (process P45) may be limited to, for example, files 21b for which an error such as "format error exists" has been notified by the receiving system 4. This reduces the risk that, for example, a file 21b that has been normally accepted by the receiving system 4 will be canceled due to erroneous duplicate transmission.

[0167] [2] Other The technology according to the embodiment described above can be implemented with the following modifications and variations.

[0168] For example, the functional blocks 22 to 26 included in the transmission system 2 shown in FIG. 5 may be merged in any combination, or may be divided into individual blocks.

[0169] Furthermore, the above-described first to fourth operation examples may be executed in appropriate combination. For example, the first or second operation example may be combined with the third or fourth operation example, or the first or second operation example may be combined with both the third and fourth operation examples.

[0170] Furthermore, in one embodiment, an example has been described in which the transmission system 2 is applied to a nursing care claim system 1, but this is not limited to this, and the transmission system 2 may be applied to various systems in which reception processing is performed at the transmission destination.

[0171] [3] Supplementary Note The following additional notes are provided regarding the above-described embodiments.

[0172] (Appendix 1) Sending to the destination a request to cancel registration at the destination of the first file sent to the destination; obtaining a second file to replace the first file; transmitting the second file to the destination in response to receiving a notification of completion of the cancellation process in response to the cancellation request; A program that causes a computer to perform a process.

[0173] (Appendix 2) outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; causing the computer to execute a process; the output process includes a process of including, in the screen information, a first operation area for registering a replacement file in association with each replaceable file among the one or more files; the process of transmitting the cancellation request includes a process of transmitting the cancellation request related to the first file identified based on the operation input to the first operation area to the destination; the acquiring process includes a process of acquiring the second file based on an operation input to the first operation area. The program described in Appendix 1.

[0174] (Appendix 3) outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; causing the computer to execute a process; the output process includes a process of including in the screen information a second operation area for transmitting at least one file to the destination and a third operation area for individually canceling the one or more files; the process of transmitting the cancellation request includes a process of transmitting the cancellation request related to the first file identified based on the operation input to the third operation area to the destination; the acquiring process includes a process of identifying the second file based on an error response related to acceptance of the file transmitted to the destination in response to the operation input in the second operation area; 1. A program according to claim 1 or 2.

[0175] (Appendix 4) outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; causing the computer to execute a process; the outputting process includes a process of including a second operation area for transmitting at least one file to the destination in the screen information; the process of transmitting the cancellation request includes a process of identifying the first file based on information of the one or more files transmitted to the destination and an operation input to the second operation area; the acquiring process includes a process of identifying the second file based on an operation input to the second operation area. The program according to any one of Supplementary Notes 1 to 3.

[0176] (Appendix 5) each of the first file and the second file includes details of nursing care benefit expenses relating to the same nursing care claim; The second file is a file for replacing the first file sent to the destination, which eliminates duplicate reception of files related to the same nursing care claim. The program according to any one of Supplementary Notes 1 to 4.

[0177] (Appendix 6) Sending to the destination a request to cancel registration at the destination of the first file sent to the destination; obtaining a second file to replace the first file; transmitting the second file to the destination in response to receiving a notification of completion of the cancellation process in response to the cancellation request; A method in which processing is performed by a computer.

[0178] (Appendix 7) outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; The processing is executed by the computer, the output process includes a process of including, in the screen information, a first operation area for registering a replacement file in association with each replaceable file among the one or more files; the process of transmitting the cancellation request includes a process of transmitting the cancellation request related to the first file identified based on the operation input to the first operation area to the destination; the acquiring process includes a process of acquiring the second file based on an operation input to the first operation area. The method described in Appendix 6.

[0179] (Appendix 8) outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; The processing is executed by the computer, the output process includes a process of including in the screen information a second operation area for transmitting at least one file to the destination and a third operation area for individually canceling the one or more files; the process of transmitting the cancellation request includes a process of transmitting the cancellation request related to the first file identified based on the operation input to the third operation area to the destination; the acquiring process includes a process of identifying the second file based on an error response related to acceptance of the file transmitted to the destination in response to the operation input in the second operation area; 8. The method according to claim 6 or 7.

[0180] (Appendix 9) outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; The processing is executed by the computer, the outputting process includes a process of including a second operation area for transmitting at least one file to the destination in the screen information; the process of transmitting the cancellation request includes a process of identifying the first file based on information of the one or more files transmitted to the destination and an operation input to the second operation area; the acquiring process includes a process of identifying the second file based on an operation input to the second operation area. The method according to any one of Supplementary Notes 6 to 8.

[0181] (Appendix 10) each of the first file and the second file includes details of nursing care benefit expenses relating to the same nursing care claim; The second file is a file for replacing the first file sent to the destination, which eliminates duplicate reception of files related to the same nursing care claim. The method according to any one of Supplementary Notes 6 to 9.

[0182] (Appendix 11) Sending to the destination a request to cancel registration at the destination of the first file sent to the destination; obtaining a second file to replace the first file; transmitting the second file to the destination in response to receiving a notification of completion of the cancellation process in response to the cancellation request; An apparatus comprising a control unit.

[0183] (Appendix 12) The control unit outputting screen information that associates the one or more files transmitted to the destination with the reception status of the one or more files at the destination; In the output process, the screen information includes a first operation area for registering a replacement file in association with each replaceable file among the one or more files, In the process of transmitting the cancellation request, the cancellation request related to the first file identified based on the operation input to the first operation area is transmitted to the transmission destination; In the acquiring process, the second file is acquired based on an operation input to the first operation area. 12. The apparatus of claim 11.

[0184] (Appendix 13) The control unit outputting screen information that associates the one or more files transmitted to the destination with the reception status of the one or more files at the destination; In the output process, the screen information includes a second operation area for transmitting at least one file to the destination and a third operation area for individually canceling the one or more files; In the process of transmitting the cancellation request, the cancellation request related to the first file identified based on the operation input to the third operation area is transmitted to the transmission destination; In the acquiring process, the second file is identified based on an error response related to the acceptance of the file transmitted to the destination in response to the operation input to the second operation area. 13. The apparatus of claim 11 or 12.

[0185] (Appendix 14) The control unit outputting screen information that associates the one or more files transmitted to the destination with the reception status of the one or more files at the destination; In the output process, a second operation area for transmitting at least one file to the destination is included in the screen information; In the process of transmitting the cancellation request, the first file is identified based on information of the one or more files transmitted to the transmission destination and an operation input to the second operation area; In the acquiring process, the second file is identified based on an operation input to the second operation area. The device according to any one of Supplementary Notes 11 to 13.

[0186] (Appendix 15) each of the first file and the second file includes details of nursing care benefit expenses relating to the same nursing care claim; The second file is a file for replacing the first file sent to the destination, which eliminates duplicate reception of files related to the same nursing care claim. The device according to any one of Supplementary Notes 11 to 14. [Explanation of symbols]

[0187] 1. Nursing care billing system 1a, 1b network 10. Computers 2 Transmission System 21 DB Department 21a Transmission Information 21b file 22 Input control section 23 Output control section 24 DB Access Section 25 Transmission and reception processing section 26 Replacement control section 27 Control Unit 3. Terminal 4. Reception system 5. AP Server 6 DB Server 7 Transmission Server

Claims

1. A computer that can communicate with both a source terminal and a destination terminal, Sending to the destination a request to cancel registration at the destination of the first file sent to the destination; obtaining a second file to replace the first file from the terminal; transmitting the second file to the destination in response to receiving a notification of completion of the cancellation process in response to the cancellation request; A program that executes a process.

2. outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; causing the computer to execute a process; the output process includes a process of including, in the screen information, a first operation area for registering a replacement file in association with each replaceable file among the one or more files; the process of transmitting the cancellation request includes a process of transmitting the cancellation request related to the first file identified based on the operation input to the first operation area to the destination; the acquiring process includes a process of acquiring the second file from the terminal based on an operation input to the first operation area. The program according to claim 1.

3. outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; causing the computer to execute a process; the output process includes a process of including in the screen information a second operation area for transmitting at least one file to the destination and a third operation area for individually canceling the one or more files; the process of transmitting the cancellation request includes a process of transmitting the cancellation request related to the first file identified based on the operation input to the third operation area to the destination; the acquiring process includes a process of identifying the second file based on an error response related to acceptance of the file transmitted to the destination in response to the operation input in the second operation area. The program according to claim 1 or 2.

4. outputting screen information in which the one or more files transmitted to the destination are associated with the reception status of the one or more files at the destination; causing the computer to execute a process; the output process includes a process of including a second operation area for transmitting at least one file to the destination in the screen information; the process of transmitting the cancellation request includes a process of identifying the first file based on information of the one or more files transmitted to the destination and an operation input to the second operation area; the acquiring process includes a process of identifying the second file based on an operation input to the second operation area. The program according to any one of claims 1 to 3.

5. each of the first file and the second file includes details of nursing care benefit expenses relating to the same nursing care claim; The second file is a file for replacing the first file sent to the destination, which eliminates duplicate reception of files related to the same care claim. The program according to any one of claims 1 to 4.

6. A computer capable of communicating with both a source terminal and a destination terminal, Sending to the destination a request to cancel registration at the destination of the first file sent to the destination; obtaining a second file to replace the first file from the terminal; transmitting the second file to the destination in response to receiving a notification of completion of the cancellation process in response to the cancellation request; A method for performing a process.

7. A device capable of communicating with each of a source terminal and a destination terminal, Sending to the destination a request to cancel registration at the destination of the first file sent to the destination; obtaining a second file to replace the first file from the terminal; transmitting the second file to the destination in response to receiving a notification of completion of the cancellation process in response to the cancellation request; An apparatus comprising a control unit.

Images