JP7779127B2 - Program, method, and device - Google Patents

Description

The present invention relates to a program, a method, and an apparatus.

Transmission services are known that support the transmission of files from a source terminal to a destination system. The system performs a reception process, including format checks, on files received from the transmission service, and once reception is complete, notifies the terminal of the reception result via the transmission service.

The reception system has a mechanism for eliminating duplicate file reception, so if multiple files with the same identification information are received, the terminal will be notified of an error during the reception process for any files received after the second of those multiple files.

By eliminating duplicate acceptance in this way, if a terminal finds an error in a transmitted file, for example, it 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 via the transmission service to the receiving system, and completes the file replacement by receiving an acceptance result from the receiving system indicating that the replacement file has been accepted.

Japanese Patent Application Laid-Open No. 2013-097545

As mentioned above, the reception system will not be able to accept replacement files until the file cancellation process is complete.

As a result, the terminal cannot transmit the replacement file to the reception system via the transmission service until it receives a cancellation completion response from the reception system, which is inconvenient. Furthermore, if the terminal transmits the replacement file without waiting to receive a completion response from the reception system, an error will occur in the reception system's acceptance process for that file, and the replacement may fail.

In one aspect, the present invention aims to improve convenience when transmitting replacement files from a sender to a destination.

In one aspect, the program may cause a computer capable of communicating with both a source terminal and a destination terminal to execute the following processes: The processes may include sending to the destination a request to cancel registration at the destination of a first file transmitted to the destination, obtaining from the destination 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 for the cancellation request.

In one aspect, the present invention can improve the convenience of transmitting replacement files from a sender to a destination.

FIG. 10 is a diagram illustrating an example of the operation of the nursing care claim system. 1 is a block diagram illustrating an example of the configuration of a care claim system according to an embodiment. FIG. 10 is a diagram for explaining an example of a replacement process in the care claim system according to an embodiment. 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. 1 is a block diagram illustrating an example of a functional configuration of a care claim system according to an embodiment. FIG. 10 is a diagram illustrating an example of a care claim screen. FIG. 10 is a diagram illustrating an example of transmission information. FIG. 10 is a sequence diagram illustrating a first operation example of a replacement process according to an embodiment. FIG. 10 is a diagram showing a care claim screen in the first operation example. 10A and 10B are diagrams illustrating changes in transmission information in the first and second operation examples. FIG. 10 is a sequence diagram illustrating a second operation example of the replacement process according to an embodiment. FIG. 10 is a diagram showing a care claim screen in the second operation example. FIG. 10 is a sequence diagram illustrating a third operation example of the replacement process according to an embodiment. FIG. 10 is a diagram showing a care claim screen in the third and fourth operation examples. FIG. 10 is a diagram showing changes in transmission information in the third operation example. FIG. 10 is a sequence diagram illustrating a fourth operation example of the replacement process according to an embodiment. FIG. 10 is a diagram showing changes in transmission information in the fourth operation example.

Embodiments of the present invention will be described below with reference to the drawings. However, the embodiments described below are merely examples, and are not intended to exclude various modifications or technological applications not explicitly stated below. For example, this embodiment can be implemented with various modifications without departing from its spirit. In the drawings used in the following description, parts with the same reference numerals represent the same or similar parts unless otherwise specified.

[1] One embodiment [1-1] An example of a transmission service The following describes a transmission service using as an example a nursing care claim transmission service that supports nursing care claims. 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 Health Insurance Association (hereinafter referred to as the "NHI Association").

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 detail sheets from businesses via the Internet.

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.

Figure 1 shows an example of the operation of the nursing care claim system 100. The nursing care claim system 100 is a system that submits nursing care claims by transmitting a file (data) from a terminal 121 of a business operator 120 to a reception system 131 of the National Health Insurance Association 130 via a transmission system 110. The transmission system 110 is a system that provides transmission services.

In the example of Figure 1, a user of the business operator 120 transmits a file 140 in a predetermined format for submitting 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.

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.

Here, in order to prevent duplicate reception of files related to the same care claim, the reception system 131 notifies the terminal of an error in the reception process for files related to the same care claim that are received later. In the example of Figure 1, file 160 transmitted immediately after operation 121a results in a reception error in the reception system 131.

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 accept the replacement file 160 (see reference symbol 131b). Note that it may take several tens of minutes, for example, 30 to 90 minutes, for the National Health Insurance Association 130 to send a cancellation completion response after receiving the cancellation request 150.

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

The reception system 131 executes the reception (replacement) process for the replacement file 160, and after the processing time, for example, approximately 60 minutes, has elapsed, notifies the terminal 121 that the file 160 has arrived.

The user confirms that the replacement of the file 140 for the care claim has been completed successfully by operating 121d on the terminal 121 to confirm receipt of the notification of completion of delivery.

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.

Furthermore, if the user sends file 160 before receiving notification that cancellation is complete, 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.

As described above, the transmission system 110 may experience reduced convenience when transmitting a replacement file 160 from the business operator 120 to the National Health Insurance Association 130.

Furthermore, if a file 160 encounters a reception error in the reception system 131, the file 160 will be transmitted multiple times over the transmission system 110 until the replacement of the file 160 is complete. This will increase the communication load and processing load on the transmission system 110, as well as the processing load on the terminal 121 and the reception system 131.

In one embodiment, as an example of a transmission service, we will describe a nursing care claim transmission service that can improve convenience when transmitting replacement files from a business operator to the National Health Insurance Association.

[1-2] Example of the Configuration of a Nursing Care Claim System According to an Embodiment Figure 2 is a block diagram showing an example of the configuration of a nursing care claim system 1 according to an 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 through which the National Health Insurance Federation accepts files.

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

The transmission system 2 is connected to one or more terminals 3 and the reception system 4 so that they can communicate with each other, and performs various communications related to the transmission of files between the terminals 3 and the reception system 4.

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

Transmission system 2 may include, for example, one or more servers, and the functions of transmission system 2 may be realized by these servers working together. A server is an example of a computer or information processing device. Furthermore, at least some of the functions of transmission system 2 may be provided as a cloud service.

Terminal 3 is an example of a computer or information processing device, and may be, for example, any of a variety of information processing terminals used by a user, such as a personal computer (PC), a smartphone, or a tablet terminal. Terminal 3 may have a configuration similar to that of terminal 121 shown in FIG. 1, for example.

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. By executing the application program, the terminal 3 may send and receive various information related to the transmission of files to and from the transmission system 2.

The application program may be, for example, a program such as a web browser capable of displaying the screen of a web service (web page) provided by the transmission system 2. The application program may also include a program for processing at least a portion of the web service on the terminal 3 side.

Reception system 4 is an example of a file destination, and performs reception processing including format checks on files received from transmission system 2. Once reception is complete, it notifies terminal 3 of the reception result via transmission system 2. Furthermore, in order to prevent duplicate reception of files related to the same care claim, reception system 4 notifies the terminal of an error in the reception processing for files related to the same care claim that are received later, for example.

The reception system 4 may include, for example, one or more servers, and the functions of the reception system 4 may be realized by these servers working together. A server is an example of a computer or information processing device. The reception system 4 may also provide the transmission system 2 with an API for communicating regarding file transmission. The reception system 4 may have a configuration similar to that of the reception system 131 shown in FIG. 1, for example.

Figure 3 is a diagram illustrating an example of replacement processing in a nursing care claim system 1 according to one embodiment. As shown in Figure 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 original file 310 to be replaced to the reception system 4, and stores the replacement file 310 in a storage area of the transmission system 2.

Note that 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.

The transmission system 2 transmits the replacement file 310 to the reception system 4 when the reception system 4 is ready 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 reception system 4 in response to receiving (catching) a cancellation completion notification from the reception system 4.

The reception system 4 executes the reception (replacement) process for the replacement file 310, and after the processing time, for example, approximately 60 minutes, has elapsed, notifies the terminal 3 that the file 310 has arrived.

The user confirms that the file replacement for the care claim has been completed successfully by operating terminal 3 (301b) to confirm receipt of the notification of completion of delivery.

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

As a result, with the transmission system 2 according to one embodiment, the user can complete 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 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.

This prevents users from forgetting to resend the replacement file 310 after the cancellation is complete, and from forgetting to make a request due to duplicate transmissions during the cancellation process. Furthermore, in the example of Figure 1, the user can effectively use the time between making the cancellation request 150 and resending the replacement file 160 for other tasks.

As described above, transmission system 2 improves convenience when transmitting replacement files 310 from businesses to the National Health Insurance Association. Furthermore, unnecessary transmission of files 310 from transmission system 2 to reception system 4 can be reduced, thereby reducing the communication load and processing load on transmission system 2, as well as the processing load on terminal 3 and reception system 4.

[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. Furthermore, 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.

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

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

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

Examples of the processor 10a include integrated circuits (ICs) such as a CPU, MPU, GPU, APU, DSP, ASIC, and FPGA. Note that a combination of two or more of these integrated circuits may be used as the processor 10a. 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.

Memory 10b is an example of HW that stores various data, programs, and other information. Examples of memory 10b include volatile memory such as DRAM (Dynamic Random Access Memory) and/or non-volatile memory such as PM (Persistent Memory).

The storage unit 10c is an example of HW that stores various types of data, programs, and other information. Examples of storage unit 10c include various storage devices such as magnetic disk devices such as HDDs (Hard Disk Drives), semiconductor drive devices such as SSDs (Solid State Drives), and non-volatile memory. Examples of non-volatile memory include flash memory, SCM (Storage Class Memory), and ROM (Read Only Memory).

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

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

IF unit 10d is an example of a communication IF that controls connections and communications between various networks, including networks 1a and 1b. For example, 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 wireless and wired communication methods.

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 memory unit 10c.

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

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

Examples of the recording medium 10h include non-transitory computer-readable recording media such as magnetic/optical disks and flash memory. 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 memory include semiconductor memory such as USB memory and SD cards.

Note that the HW configuration of the computer 10 described above is an example. Therefore, the HW within the computer 10 may be increased or decreased (for example, adding or deleting any blocks), divided, integrated in any combination, or buses may be added or deleted as appropriate.

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 a hardware configuration similar to that of the computer 10 described above.

[1-4] Functional Configuration Example Fig. 5 is a block diagram showing an example of the functional configuration of a nursing care claim system 1 according to one embodiment. As shown in Fig. 5, the transmission system 2 in the nursing 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 examples of a control unit 27. Note that the control unit 27 may be, for example, at least a part of the functions of the program 10g shown in Fig. 4.

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

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 information from the terminal 3. "Accepting" the input of input information may include, for example, outputting the acquired input information to at least one of the function blocks 23-26 or the DB unit 21. Output to the DB unit 21 may include, for example, working with the DB access unit 24 to store the input information in transmission information 21a, or storing it in the DB unit 21 as file 21b.

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

The output control unit 23 controls various outputs to the terminal 3. As an example, the output control unit 23 may control output based on information or instructions input from at least one of the functional blocks 22, 24-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. As an 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 on the terminal 3.

Figure 6 is a diagram showing an example of a care claim screen 30. As shown in Figure 6, the output control unit 23 may generate, as screen information, for example, a care claim screen 30 to be displayed in a web browser on the display device of the terminal 3 (for example, the IO unit 10e in Figure 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 sent to the reception system 4 with the reception status of the one or more files 21b at the reception system 4.

The care claim screen 30 may include buttons 31 to 34 and a display area 35, as illustrated in FIG. 6.

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

Button 32 is a button for sending (transmitting) file 21b registered using button 31 or button 37a (described below) to reception system 4.

Button 33 is a button for canceling the transmission of file 21b sent by button 32; in other words, for deleting file 21b from the reception system 4.

Button 34 is a button for displaying a screen (not shown) showing a list of errors related to processing in response to pressing button 32 or 33, for example, a list of errors notified by reception system 4.

Display area 35 is an area for displaying information for each file 21b, and may include check boxes 36 and areas 37 to 39.

Checkbox 36 is an area for selecting one or more files 21b. For example, when button 32 or 33 is pressed, processing is performed on the files 21b corresponding to the checked checkbox 36. Checkbox 36 and button 33 are an example of a third operation area for individually canceling one or more files 21b.

Area 37 shows the current status of each file 21b and may include fields for the business name, status, and error code.

Area 38 shows the contents of each file 21b, such as the number and amount of nursing care benefit claim forms and nursing care benefit statement documents. Area 38 may also include the file name of file 21b.

Area 39 shows information such as the arrival number for each file 21b, which is notified by the reception system 4 that accepted the file 21b.

Furthermore, as shown in FIG. 6, a replacement button 37a (labeled "Replace") may be displayed in the display area 35, for example, in area 37.

The replace button 37a is a button for replacing the file 21b for which transmission processing has been performed with another file 21b. The replace button 37a may be displayed in the entry for a file 21b for which replacement processing can be performed in one embodiment. 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 one or more files 21b.

In one embodiment, the conditions for a file 21b that can be replaced can take various forms. In the example of Figure 6, a replace button 37a is displayed for each entry of a file 21b for which the reception process has been completed in the reception system 4, and a file 21b that was not accepted during the reception process due to a format error. Note that in the display area 35, the entry of a file 21b for which transmission processing will be performed when the replace button 37a is pressed may be displayed in a "waiting for replacement" state.

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. In addition, 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.

Returning to the explanation of Figure 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.

Figure 7 is a diagram showing an example of transmission information 21a. Note that, for convenience, Figure 7 shows transmission information 21a in table format, but this is not limited to this. Transmission information 21a may be stored in DB unit 21 in various formats, such as DB format or array format. Also, Figure 7 shows transmission information 21a as information in a single table, but this is not limited to this, and transmission information 21a may be information combining multiple tables.

As shown in FIG. 7, the transmission information 21a may, for example, include 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.

The "establishment number" is an example of identification information for 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 unit 21, such as a file path.

The "transmission control number" is a number used to manage the transmission of file 21b or a 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 shown in Figure 7, the transmission control number may also 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 codes (identification information) that indicate the status of the transmitted file 21b or request in the reception system 4, and the status name associated with the code.

The "Cancellation Status" indicates the status of the cancellation process in the reception 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 reception system 4, and may be set to "Cancellation Completed" or "1" if the cancellation process has been completed.

The "Arrival Number" is a number used by the Reception System 4 to manage the arrival of file 21b or a request, and is an example of identification information for received data on the Reception System 4 side. The "Error Code" and "Error Details" indicate the code (identification information) of an error that occurred in the Reception System 4 during the reception process for the arrived file 21b or request, and the details of that error.

The "cancellation flag" is a flag that indicates whether the file 21b of the entry in question is to be cancelled or a replacement file 21b; for example, "1" may indicate that the file 21b is to be cancelled, and "2" may indicate that it 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.

The transmission/reception processing unit 25 performs transmission/reception processing for the reception system 4. For example, the transmission/reception processing unit 25 may send files 21b or requests to the API of the reception system 4, and receive messages or responses from the API of the reception system 4. During the transmission/reception processing, the transmission/reception processing unit 25 may update the transmission information 21a via the DB access unit 24.

The replacement control unit 26 controls replacement 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 to transmit the replacement file 21b after the cancellation process for the replacement source file 21b has been completed in the reception system 4.

Incidentally, the transmission system 2 may realize each processing function by, for example, multiple devices (e.g., servers) cooperating with each other via a network.

As an example, the DB unit 21 may be one or more DB servers, and the input control unit 22, output control unit 23, and 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 replacement control unit 26 may be one or more application servers (e.g., transmission servers with transmission (communication) functions).

In the following explanation, as illustrated in Figure 8 and subsequent figures, 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 by the DB server 6, and the transmission/reception processing unit 25 and replacement control unit 26 by the transmission server 7.

[1-5] Operational Examples of Replacement Processing Next, detailed operational examples of the replacement processing by the transmission system 2 will be described. The replacement processing according to one embodiment may be realized in any of a number of ways. Below, first to fourth operational examples will be described as detailed operational examples of the replacement processing.

[1-5-1] First Operation Example Fig. 8 is a sequence diagram for explaining a first operation example of the replacement process according to one 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.

As illustrated in Figure 8, the AP server 5 references 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.

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

Based on the entry for the pressed replacement button 37a and the uploaded file 21b, the AP server 5 writes a cancellation request to the transmission information 21a of the DB server 6 and confirms the transmission of the cancellation request (process P4). For example, the AP server 5 updates the entry for 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.

In the entries of the transmission information 21a shown in Figure 10, symbol A indicates the entry for the original file 21b (file name "AAAAA.csv"), and symbol B indicates the entry for the cancellation request for the original file 21b. For example, the AP server 5 creates a cancellation request entry (symbol B) that does not include the file name, and sets the cancellation flag for the entry for the original file 21b (symbol A) to "1."

When the transmission server 7 detects an entry to be canceled in the transmission information 21a, with the cancellation flag set to "1," it sends the contents of the cancellation request entry, specifying the arrival number of the file 21b to be canceled, to the reception system 4 (API) (process P5). The reception system 4 executes the cancellation request reception process (process P6). The reception system 4 issues a reception number for the cancellation request that is related to the arrival number of the file 21b to be canceled (for example, by adding "1" to the end). 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.

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

In Figure 10, symbol C indicates an entry in replacement file 21b (file name "BBBBB.csv"). For example, AP server 5 sets the cancellation flag in the entry (symbol C) in replacement file 21b to "2," indicating a replacement transmission reservation.

When the transmission server 7 receives a cancellation request completion notification from the reception system 4 a predetermined time later (e.g., about one hour) after sending the cancellation request, it 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 cancellation request entry that matches the arrival number indicated in the completion notification. Furthermore, 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 email or other means (process P10).

In response to receiving the cancellation request completion notification, the transmission server 7 transmits the replacement file 21b stored in the DB server 6 to the reception system 4 (process P11). The reception system 4 executes reception processing for the replacement file 21b (process P12). For example, as shown by symbol F in Figure 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 reception system 4. The reception system 4 issues a delivery number for the replacement file 21b. Upon receiving the delivery number from the reception system 4, the transmission server 7 sets the delivery number in the entry marked F in the transmission information 21a.

When the transmission server 7 receives a notification from the reception system 4 that the reception process for the replacement file 21b has been completed, it may notify the terminal 3 of the completion of the reception process by email or other means (process P13). The transmission server 7 may also write the reception results to 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").

In this way, in the first operation example, in response to the user's designation of a replacement file 21b for the original file 21b, the transmission system 2 issues a cancellation request for the original file 21b to the reception system 4 and reserves the transmission of the replacement file 21b. After the cancellation process by the reception system 4 is completed, the transmission system 2 transmits the replacement file 21b to the reception system 4 (without going through the user).

This allows the user to complete the replacement of file 21b simply by specifying the file 21b to be canceled and each replacement file 21b (for example, by pressing the replacement button 37a for each file 21b and uploading the replacement file 21b). Therefore, the user is freed from being tied up in the time between making a cancellation request and sending the replacement file 160 after receiving notification of the completion of the cancellation process, as shown in Figure 1.

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, thereby reducing the time the user spends at the business premises and preventing errors or missed billing for the replacement file 21b.

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

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 for the second entry whose status is being cancelled, enabling replacement processing of the file 21b for that entry.

A second operational example of the replacement process will now be described with reference to Figure 11. Note that in the example of Figure 11, processes with the same reference numerals as in Figure 8 are the same as the processes already described with reference to Figure 8. Furthermore, in the process shown in Figure 11, the changes in the transmission information 21a are the same as the changes described with reference to Figure 10.

When the care claim screen 30 (see Figure 12) is displayed on the terminal 3 in process P2, the user selects the check box 36 for the second entry, for example, and presses button 33 to request the cancellation of the file 21b for the second entry (process P21).

Based on the cancellation request for the second entry, the AP server 5 writes a 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 for the file 21b to be canceled in the transmission information 21a (e.g., by setting the cancellation flag to "1") and creates an entry for the cancellation request.

When the transmission server 7 detects an entry to be canceled with the cancellation flag set to "1" from the transmission information 21a, it sends the contents of the cancellation request entry to the reception system 4 (API) by specifying the arrival number of the file 21b to be canceled (process P23). The reception system 4 then executes the cancellation request reception process (process P24). Processes P21 to P24 may be considered the normal cancellation process for file 21b.

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

In addition, terminal 3 may obtain information such as the number of items and the amount based on replacement file 21b and send it to AP server 5 (process P26). Based on the information obtained by terminal 3 (or information obtained by the AP server 5 itself from file 21b), AP server 5 creates an entry (record) for replacement file 21b in the transmission information 21a (process P27).

As described above, the second operation example can achieve the same effects 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.

In addition, since the cancellation process for the original file 21b is already underway when the user uploads the replacement file 21b, the time it takes for the replacement file 21b to be sent to the reception system 4 after notification of the completion of the cancellation process can be shortened compared to the first operation example.

[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.

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 allows the user to upload one or more files 21b without making the user aware of the replacement.

For example, as shown in FIG. 14, the user can issue a request to cancel one or more files 21b by selecting checkbox 36 and pressing button 33. The user can also select one or more replacement files 21b as files 21b to be uploaded by using the file 21b selection screen (not shown) displayed by pressing button 31, or by dragging the file 21b onto the care claim screen 30.

In such an operation, if the file 21b to be uploaded is a replacement file 21b for the file 21b for which a cancellation request has been issued, in the example of Figure 1, a delivery error occurs for the file 160 to be uploaded, and transmission to the reception system 131 fails.

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

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

A third operational example of the replacement process will be described below with reference to Figure 13. Note that in the example of Figure 13, processes with the same reference numerals as in Figure 11 are the same as the processes already described with reference to Figure 11. Also, in the example of Figure 15, entries with the same reference numerals as in Figure 10 are the same as the entries already described with reference to Figure 10.

After a request to cancel one or more files 21b is issued in processes P21 to P24, the terminal 3 uploads 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).

In addition, terminal 3 may obtain information such as the number of items and the amount based on replacement file 21b and send it to AP server 5 (process P32). Based on the information obtained by terminal 3 (or information obtained by the AP server 5 itself from file 21b), AP server 5 creates an entry (record) for replacement file 21b in the transmission information 21a (process P33).

As shown by symbol H in Figure 15, the transmission server 7 transmits the replacement file 21b stored in the DB server 6 to the reception system 4 (process P34). The reception system 4 executes the reception process for the replacement file 21b (process P35).

However, because the cancellation process for the replacement file 21b has not been completed, the transmission server 7 receives an arrival error from the reception system 4 (process P36). The arrival error includes, for example, the error code "ZZZZZ," which indicates that the replacement file 21b has already been requested using the arrival number "YYYYY0" (see symbol A), as shown by symbol I in Figure 15.

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

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, for example by email, of information including the error code and details of the arrival error (process P38). In this case, the user issues a cancellation request based on the notification. That is, the nursing care claim system 1 executes process P21 and subsequent processes.

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 arrival error notification and schedules the transmission of that file 21b. In the example in 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 cancellation flag of "2" in that entry.

The transmission server 7 may also 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."

When the transmission server 7 receives the processing result of the cancellation request acceptance process in process P24, it executes process P9 and subsequent processes based on the information in the entry created in the replacement creation process.

For example, the transmission server 7 writes the cancellation result to the transmission information 21a (process P9; see symbols D and E in Figure 15), and notifies the terminal 3 of the completion of the cancellation process by email or other means (process P10).

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 reception system 4 (process P11). The reception system 4 executes the reception process for the replacement file 21b (process P12). For example, as shown by symbol K in Figure 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 reception system 4. The reception system 4 issues a delivery number for the replacement file 21b. Upon receiving the delivery number from the reception system 4, the transmission server 7 sets the delivery number (e.g., "YYYYY3") in the entry of the transmission information 21a.

When the transmission server 7 receives a notification from the reception system 4 that the reception process for the replacement file 21b has been completed, it may notify the terminal 3 of the completion of the reception process by email or other means (process P13). The transmission server 7 may also write the reception results to 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").

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, it identifies (detects) the original and replacement files 21b based on the arrival error. The transmission system 2 then schedules the identified replacement file 21b for transmission, and transmits the replacement file 21b after completing the cancellation process for the identified original file 21b.

As a result, the third operation example can achieve the same effects as the first and second operation examples, and also allows the user to omit the task of associating the original file 21b with the replacement file 21b, allowing multiple files 21b to be replaced at once.

In addition, the reception system 4 associates the original file 21b with the replacement file 21b based on the reception processing logic, and notifies the transmission server 7 of the association result as a delivery error, thereby reducing the risk of mistaking the file 21b to be replaced.

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

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.

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 button 31, etc.

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

On the other hand, the fourth operation example assumes that the judgment 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 normal registration file 21b or a replacement file 21b. If the uploaded file 21b is a replacement file 21b, the transmission system 2 requests the cancellation of the original replacement file 21b and suspends and schedules the transmission of the replacement file 21b.

This allows multiple files 21b to be replaced at once without the user having to be aware of the cancellation request and replacement.

A fourth operational example of the replacement process will be described below with reference to Figure 16. Note that in the example of Figure 16, processes with the same reference numerals as in Figure 13 are the same as the processes already described with reference to Figure 13. Also, in the example of Figure 17, entries with the same reference numerals as in Figure 15 are the same as the entries already described with reference to Figure 15.

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

The terminal 3 also acquires 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).

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

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

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 reception system 4 as a normal transmission based on the transmission information 21a (process P46). The reception system 4 executes the reception process for file 21b (process P47). Processes P41 to P43, P46, and P47 may be considered normal transmission processes for file 21b.

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.

When the transmission server 7 detects an entry to be canceled with the cancellation flag set to "1" from the transmission information 21a, it sends the contents of the cancellation request entry, specifying the arrival number of the file 21b to be canceled, to the reception system 4 (process P49). The reception system 4 executes the cancellation request reception process (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 for the file 21b to be canceled on the care claim screen 30.

The AP server 5 also confirms the transmission of the replacement file 21b, among the uploaded files 21b, for which an entry exists in the transmission information 21a (process P51).

The transmission server 7 updates the entry for the replacement file 21b in the transmission information 21a to schedule the transmission of the file 21b (process P52; see symbol O in Figure 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.

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

For example, the transmission server 7 writes the cancellation result to the transmission information 21a (process P9; see symbols D and E in Figure 17), and notifies the terminal 3 of the completion of the cancellation process by email or other means (process P10).

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 reception system 4 (process P11). The reception system 4 executes the reception process for the replacement file 21b (process P12). For example, as shown by symbol P in Figure 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 it to the reception system 4. The reception system 4 issues a delivery number for the replacement file 21b. Upon receiving the delivery number from the reception system 4, the transmission server 7 sets the delivery number (e.g., "YYYYY2") in the entry of the transmission information 21a.

When the transmission server 7 receives a notification from the reception system 4 that the reception process for the replacement file 21b has been completed, it may notify the terminal 3 of the completion of the reception process by email or other means (process P13). The transmission server 7 may also write the reception results to the transmission information 21a. For example, as shown by symbol Q in FIG. 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").

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

In this way, the fourth operation example eliminates the need for the user to perform an operation to cancel file 21b, thereby improving user convenience.

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

[2] Others The technology according to the embodiment described above can be implemented with the following modifications and changes.

For example, the functional blocks 22 to 26 provided in the transmission system 2 shown in Figure 5 may be merged in any combination, or may be separated.

The first to fourth operation examples described above may be executed in combination as appropriate. 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.

Furthermore, in one embodiment, an example was described in which the transmission system 2 is applied to the 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.

[3] Supplementary Notes The following supplementary notes are further disclosed regarding the above-described embodiments.

(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.

(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.
10. The program according to claim 1.

(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.
10. The program according to claim 1 or 2.

(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 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 appendix 1 to appendix 3.

(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 care claim.
The program according to any one of appendix 1 to appendix 4.

(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.

(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.

(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 of claim 6 or 7.

(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 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.
9. The method of any one of claims 6 to 8.

(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 care claim.
10. The method of any one of claims 6 to 9.

(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.

(Appendix 12)
The control unit
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;
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.

(Appendix 13)
The control unit
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;
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 in the second operation area.
13. The device of claim 11 or 12.

(Appendix 14)
The control unit
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;
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.
14. The device of any one of claims 11 to 13.

(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 care claim.
15. The device of any one of claims 11 to 14.

REFERENCE SIGNS LIST 1 nursing care claim system 1a, 1b network 10 computer 2 transmission system 21 DB section 21a transmission information 21b file 22 input control section 23 output control section 24 DB access section 25 transmission/reception processing section 26 replacement control section 27 control section 3 terminal 4 reception system 5 AP server 6 DB server 7 transmission server

Claims (7)

A computer that can communicate with both the source terminal and the 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. 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. 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. 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. 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. 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 method for performing a process. 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.