Information processor, program, data processing method, data output system and server device

Abstract

To further reduce the burden of sending a document such as an invoice.SOLUTION: The present invention provides an information processor having a reception unit that accepts source data 11 containing a plurality of pieces of document data 7, a division unit that, based on dispatch destination identification information described in the document data, divides the source data into dispatch destination-specific data 13 having the dispatch destination identification information, and a transmission unit that transmits the dispatch destination-specific data divided by the division unit to an external entity 50.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing device, a program, a data processing method, a data output system, and a server device. [Background technology]

[0002] The task of sending documents such as invoices is well known. For example, in a facility (such as a nursing home) that issues invoices to users for service fees, the person in charge performs the document sending task using the following procedure. (1) Issue a separate invoice to each user. (2) Print and attach enclosures to the invoice, if necessary. (3) Fold the invoice, enclose it, and mail (or email) it.

[0003] As a conventional technology, a technology for improving the efficiency of billing operations using a computer network has been devised (see, for example, Patent Document 1). Patent Document 1 discloses a system that stores billing information for each biller and transmits billing data to a payer terminal based on the billing information. Summary of the Invention [Problem to be solved by the invention]

[0004] However, even with such conventional technology, there is a problem in that when a person in charge sends documents to a user, the person in charge has to take an enormous amount of time and effort to organize the documents by destination, and the burden on the person in charge of the document sending work as described above remains large. For example, if multiple document data for different destinations are mixed in one original data, the person in charge will have to print the original data and sort the documents by destination.

[0005] The present invention provides a technique for further reducing the burden of sending documents such as invoices. [Means for solving the problem]

[0006] The present invention provides an information processing device having a receiving unit that receives original data containing multiple document data, a dividing unit that divides the original data into destination-specific data having destination identification information based on the destination identification information of the document data described in the document data, and a transmitting unit that transmits the destination-specific data divided by the dividing unit to an external device. [Effects of the Invention]

[0007] This will further reduce the burden of sending documents such as invoices. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 2 is a diagram illustrating an outline of the operation of the data output system. [Figure 2] FIG. 1 is a diagram illustrating an example of a system configuration of a data output system. [Figure 3] FIG. 2 is a diagram illustrating a hardware configuration of an example of a terminal device. [Figure 4] FIG. 2 is a diagram illustrating a functional configuration of an example of a terminal device. [Figure 5] FIG. 4 is a diagram showing an example of shipping information registered in a shipping information storage unit. [Figure 6] FIG. 3 is a diagram illustrating an example of rules stored in a rule storage unit. [Figure 7] FIG. 10 is a diagram showing an example of document data of an invoice. [Figure 8] FIG. 10 is a diagram showing an example of document data of a receipt. [Figure 9] 10 is an example of a flowchart illustrating a flow from when the service processing unit creates an original file to when the user-specific file is sent to the delivery system. [Figure 10] FIG. 2 is a diagram illustrating a functional configuration of an example of a terminal device. [Figure 11] FIG. 3 is a diagram illustrating an example of rules stored in a rule storage unit. [Figure 12]10 is an example of a flowchart illustrating a flow from when the service processing unit creates an original file to when the user-specific file is sent to the delivery system. [Figure 13] FIG. 4 is a diagram showing an example of shipping information registered in a shipping information storage unit. [Figure 14] FIG. 10 is a diagram showing an example of enclosure selection information. [Figure 15] 10 is an example of a flowchart illustrating a flow from when the service processing unit creates an original file to when the user-specific file is sent to the delivery system. [Figure 16] FIG. 1 is a diagram illustrating an example of a system configuration of a data output system. [Figure 17] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal device and a server device. [Figure 18] 10 is an example of a sequence diagram illustrating a flow from when a terminal device creates an original file to when a server device transmits a user-specific file to a delivery system. DETAILED DESCRIPTION OF THE INVENTION

[0009] A data output system and a data processing method performed by the data output system will be described below as an example of an embodiment of the present invention.

[0010] [First embodiment] <Overview of operation> 1 is a diagram illustrating an outline of the operation of the data output system 100. In the following, as an example of an embodiment, a case will be described in which a person in charge of creating documents at a nursing care facility prepares document data such as invoices to be sent to users.

[0011] (1) At a nursing care facility, a staff member operates a terminal device 30 to create invoices, receipts, etc. The terminal device 30 runs business software 8 that supports billing processes for users of the nursing care facility. Because multiple users use the nursing care facility, the business software 8 compiles data on invoices, receipts, etc. for multiple users (hereinafter simply referred to as document data) and outputs them into one file (hereinafter referred to as original file 11). Therefore, the original file 11 contains multiple pieces of document data.

[0012] The business software 8 also allows the person in charge to select document data for individual users and print documents for each user (in this embodiment, create files), but if there are a large number of users, printing work and files will be generated for each user. For this reason, printing documents for each user may increase the workload.

[0013] (2) The terminal device 30 runs a service processing unit 9 and a file processing unit 6 suitable for shipping operations. The service processing unit 9 converts the document data 7 into an original file 11 (e.g., a PDF file) in response to an operation by a person in charge, and starts processing the original file 11. The service processing unit 9 acquires a user number for each piece of document data contained in the original file 11. Based on the user number, the service processing unit 9 divides the original file 11 into a single file for each user (hereinafter referred to as a user-specific file 13). The user-specific file 13 contains one or more document data. The service processing unit 9 also renames the user-specific file 13 based on predetermined rules.

[0014] (3) The file processing unit 6 determines whether enclosure data 12 is required for each user and combines the enclosure data 12 to be enclosed into the user-specific file 13. Therefore, some user-specific files 13 contain enclosure data 12, while others do not. In this way, even if the need for enclosure data 12 differs for each user, because the original file 11 is divided into user-specific files 13, it is possible to control whether or not to combine the enclosure data 12 for each user. (4) The file processing unit 6 transmits the user-specific file 13 of each user to a delivery system 50 in the cloud or the like.

[0015] (5) When the delivery system 50 receives the user-specific file 13, the sender prints the user-specific file 13, folds it, encloses it, and delivers it by mail or email.

[0016] In this way, the terminal device 30 of this embodiment divides the original file 11 into user-specific files 13, and the delivery system 50 can simply mail all of the printed copies of the user-specific files 13 to the same destination, thereby reducing the workload. Also, when sending by email, there is no need to manually divide the original file 11, determine whether or not the enclosure data 12 is needed, and then attach it; it is enough to send the user-specific files 13. Furthermore, because the terminal device 30 divides the original file 11 into user-specific files 13, the enclosure data 12 can be combined for each user.

[0017] <Terminology> Document data is electronic data related to documents such as invoices. Document data may include document data related to multiple users. Document data may also include different types of document data (invoices, receipts, etc.). A file containing document data related to multiple users may be called an original file (an example of original data). In principle, one page of document data is one document, but one document may span multiple pages.

[0018] The destination identification information is identification information for identifying the destination of the document data. In this embodiment, the destination identification information is explained using the term user number. The user number is identification information for the user of the service.

[0019] The data for each delivery destination is a file obtained by dividing the original file into only document data having the same delivery destination identification information. In this embodiment, the data for each delivery destination will be described using the term file for each user.

[0020] Dividing by page means that the data for each shipping destination is divided at the page break, and the original file is not divided in the middle of a page. However, even if the document changes in the middle of a page, the original file may be divided in the middle of the page as long as the change point is clear or detectable.

[0021] A service refers to something useful to a user, such as data processing, labor, or the provision of information. A service may include the transfer of an object. In this embodiment, a nursing care service is exemplified as an example of a service. A service may be provided by any facility, such as an educational institution, a government office, mail order, or information provision.

[0022] <System configuration example> 2 is an example of a system configuration diagram of the data output system 100. The data output system 100 includes a delivery system 50 and a terminal device 30. However, the delivery system 50 may be a company that undertakes delivery, and may not be included in the data output system 100.

[0023] The delivery system 50 and the terminal device 30 are communicatively connected via a wide-area network N1 such as the Internet. The delivery system 50 may be installed in a cloud or a data center, or may be installed on-premise. The delivery system 50 may be a web server that returns processing results to the terminal device 30 in response to a request from the terminal device 30. A server is a computer or software that performs the function of providing information and processing results in response to a request from a client.

[0024] The terminal device 30 is located in a facility such as a nursing home, and can be connected to the network N2. The network N2 may be any network that can communicate with the dispatch system 50, such as a LAN, Wi-Fi (registered trademark), Wide Area Ethernet (registered trademark), or a mobile phone network such as 4G, 5G, or 6G. When a facility staff member works remotely, the terminal device 30 may be used in the staff member's home, workspace, or the like.

[0025] The terminal device 30 is a general-purpose computer used by a care facility staff member. A native application or a web application called business software 8 for creating invoices and the like runs on the terminal device 30. The terminal device 30 also has a service processing unit 9 and a file processing unit 6. The service processing unit 9 may be realized by a printer driver that undertakes printing of the original file 11. The file processing unit 6 may be realized by, for example, an application, or may be realized by a printer driver. The service processing unit 9 and the file processing unit 6 are prepared in correspondence with the delivery system 50, and can send the user-specific file 13 to the delivery system 50 that has been registered in advance.

[0026] The terminal device 30 is, for example, a desktop PC, a notebook PC, a smartphone, a tablet terminal, etc. Alternatively, the terminal device 30 may be any device on which a web browser or a native application runs.

[0027] The delivery system 50 is one or more information processing devices that provide document delivery services. For example, a sender who performs delivery operations connects a user's PC to the delivery system 50, downloads a user-specific file, and prints it. The sender folds, encloses, and mails the document. Alternatively, the sender sends it by email. The delivery system 50 has a contract with a nursing care facility and holds the nursing care facility's delivery user information. The sender identifies the delivery destination (address, email address) based on the delivery user information and delivers the printed document. The delivery system 50 may also automatically print or email the document based on the delivery user information. Whether delivery is by mail or email is registered in the delivery user information.

[0028] The delivery system 50 may be compatible with cloud computing. Cloud computing refers to a form of use in which resources on a network are used without regard to specific hardware resources. Therefore, the delivery system 50 does not need to be housed in a single housing or provided as a single integrated device. The functions of the delivery system 50 may be distributed among multiple information processing devices, or multiple information processing devices may each have all of the functions and the information processing device that processes the data may be switched by load balancing or the like.

[0029] <Hardware configuration example> The hardware configuration of the terminal device 30 included in the data output system 100 according to this embodiment will be described with reference to FIG.

[0030] <<Terminal Device>> Fig. 3 is a diagram showing an example of the hardware configuration of the terminal device 30 according to this embodiment. As shown in Fig. 3, the terminal device 30 is constructed by a computer, and includes a CPU 501, a ROM 502, a RAM 503, an HD 504, an HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I / F (Interface) 508, a network I / F 509, a bus line 510, a keyboard 511, a pointing device 512, an optical drive 514, and a media I / F 516.

[0031] Of these, the CPU 501 controls the overall operation of the computer 500. The ROM 502 stores programs, such as an IPL, used to drive the CPU 501. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data, such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 under the control of the CPU 501. The display 506 displays various information, such as a cursor, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memories and printers. The network I / F 509 is an interface for data communication using the network N2. The bus line 510 is an address bus, a data bus, or the like, for electrically connecting the components, such as the CPU 501, shown in FIG. 3.

[0032] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The optical drive 514 controls reading and writing of various data from an optical storage medium 513, which is an example of a removable storage medium. The optical storage medium may be a CD, DVD, Blu-ray (registered trademark), etc. The media I / F 516 controls reading and writing (storing) of data from a storage medium 515, such as a flash memory.

[0033] <About the function> Next, the functional configuration of the data output system according to this embodiment will be described with reference to Fig. 4. Fig. 4 is a diagram showing the functional configuration of an example of the terminal device 30 according to this embodiment.

[0034] <<Terminal Device>> The terminal device 30 has business software 8, a service processing unit 9, and a file processing unit 6. Execution of the business software 8 realizes a display control unit 21, an operation reception unit 22, and a file creation request unit 23. The business software 8 has existing functions such as creating invoices, and a description of these functions will be omitted. The business software 8 is merely an example used in this embodiment to explain the shipping business of a nursing care facility, and the business software 8 may be any software that creates document data such as invoices. The service processing unit 9 and the file processing unit 6 may be integrated.

[0035] The service processing unit 9 also has a reception unit 24, a division unit 25, and a data naming unit 26. The file processing unit 6 also has a combination unit 27 and a transmission unit 28. That is, each of these functional units is a function or means realized by the CPU 501 executing instructions included in one or more programs installed in the terminal device 30.

[0036] The terminal device 30 also has a shipping information storage unit 31, a rule storage unit 32, and an enclosure data storage unit 33. Each of these storage units is created, for example, in the HD 504 or RAM 503 shown in Fig. 3. Note that one or more of the shipping information storage unit 31, the rule storage unit 32, and the enclosure data storage unit 33 may exist not in the terminal device 30, but on a network accessible by the terminal device 30.

[0037] The display control unit 21 displays an input screen for documents such as invoices, a print execution screen, and the like on the display 506. The operation reception unit 22 receives various operations by the person in charge on the various screens displayed on the display 506. For example, the person in charge can set which user's documents to print, which documents to print, and the like.

[0038] The file creation request unit 23 requests the service processing unit 9 to create a file containing document data in response to a file creation operation by the person in charge. The file creation operation is an operation to create a PDF file instead of paper when printing, so it can also be called a printing operation. This file is a multi-page original file 11 that compiles invoices, receipts, etc. for multiple users. However, the person in charge can also print only one document data for one user. The service processing unit 9 is called in response to a file creation request from the file creation request unit 23.

[0039] The reception unit 24 creates one file (original file 11) including multiple document data requested by the file creation request unit 23. Alternatively, the reception unit 24 can simply accept an already created original file 11. The original file 11 is in PDF format, but any file format is possible, such as a spreadsheet file, HTML file, or XML file.

[0040] In this embodiment, the reception unit 24 creates the original file 11. However, since the original file 11 is a normal file in PDF format or the like, the reception unit 24 may obtain the original file 11 from business software or a general-purpose printer driver, or may obtain the original file 11 created on another PC or the like.

[0041] The dividing unit 25 divides the original file 11 based on rules stored in the rule storage unit 32. For example, a dividing rule may be to divide by user number. Therefore, the dividing unit 25 divides the original file 11 into user-specific data having only the same user number based on the user number of the document data written in the document data. The person in charge can register rules. The dividing unit 25 determines which user the document data contained in the original file 11 belongs to for each page and divides it into user-specific files 13. The original file 11 contains document data addressed to multiple users, and the document data may include invoices, invoice copies, receipts, receipt copies, etc. In principle, copies are not included in the original file 11, but they may be included due to an operational error by the person in charge. In this embodiment, the dividing unit 25 obtains a user number for each piece of document data contained in the original file 11 (e.g., for each page) and divides the document data into one user-specific file 13 until the user number changes. Alternatively, the dividing unit 25 may search the document data for the user number registered in the shipping information storage unit 31 and extract the corresponding document data to divide it into user-specific files 13 .

[0042] The data naming unit 26 assigns file names to the user-specific files 13 divided by the dividing unit 25, the file names including character strings obtained from the user-specific files. The file names to be assigned are set in the rule storage unit 32. For example, a rule may be that the file name should be set using three items: "user number," "issue date," and "billing amount."

[0043] The combining unit 27 combines the enclosure data 12 with the destination-specific data for which enclosure data 12 is required, based on the shipping information in which the necessity of enclosure data is set in association with the user number. The enclosure data 12 is stored in the enclosure data storage unit 33. Enclosure means to combine, combine, or merge into one file. The necessity of enclosure for each user is registered in the shipping information storage unit 31.

[0044] The sending unit 28 sends the divided user-specific files 13 (some of which contain enclosure data and some of which do not) to the delivery system 50. The file processing unit 6 has pre-registered therein the IP address and URL of the delivery system 50, the ID and password of the care facility, etc.

[0045] When the delivery system 50 receives the user-specific file 13, it identifies the nursing care facility using the nursing care facility ID sent from the terminal device 30 (identifies the user information for delivery) and performs delivery operations. The delivery system 50 holds user information for delivery (shipping destination, whether by mail or email) for each nursing care facility. The delivery system 50 performs delivery operations in accordance with the details of the contract with the nursing care facility. The contract details include, for example, the deadline for delivery, the delivery method (if any) decided for the entire nursing care facility, the postage fee based on the number of sheets to be mailed, and the unit price for sending emails.

[0046] <<Shipping information registered in the shipping information storage unit>> Next, the shipping information used by the file processing unit 6 will be described with reference to Fig. 5. Fig. 5 shows an example of shipping information registered in the shipping information storage unit 31. The shipping information is information about the shipping method for each user. The shipping information includes information necessary for enclosing the enclosure data 12. The user number field contains the user's identification information that uniquely identifies the user at the nursing care facility. The user's identification information may be My Number, insured person number, telephone number, fax number, address, etc. The user name is set in the user name field. The "enclosure required" field indicates whether an enclosure is required when sending documents to the user (1 required, 0 not required). The reason for the "enclosure required" field is to accommodate the fact that, for example, if a care facility operator runs multiple care facilities, the information to be communicated may differ for each care facility to which the user belongs. For example, the information to be communicated may differ between a special nursing home and a residential care home. Also, in terms of individual users, if there are special instructions for a user, there may be information that is sent only to that user. The Enclosure 1 code field contains the identification information of the enclosure data. The Enclosure 2 code field contains the identification information of another enclosure data. In this example, there are two enclosure data items, but the number of enclosure data items is just an example. The email address field contains the email address to which the user or their family member is addressed. The address field contains the address of the user or their family.

[0047] It should be noted that the email address and address do not need to be registered in the file processing unit 6. The delivery system 50 has user information for delivery, and the delivery system 50 can obtain the email address, address, etc. using the user number assigned to the file name of the user-specific file 13 as a key.

[0048] The person in charge can operate the terminal device 30 to display the setting screen of the file processing unit 6, create shipping information, or display and edit already created shipping information.

[0049] <<Rules stored in the rule memory>> 6 shows an example of rules stored in the rule storage unit 32. The rules define how to perform each process included in a series of processes, such as when dividing a file and when renaming a file.

[0050] (1) For example, in Figure 6, a rule is defined that when dividing a file, "divide the file by 'user number'." The file may be divided not only by the user number, but also by any information that can uniquely identify the user and that is included in the document data. For example, the information used to divide the file may be name (assuming there are no other people with the same name), address, telephone number, fax number, email address, etc.

[0051] 6, a rule is defined that "invoices and receipts should be included in the user-specific file" when dividing files. This extraction rule allows the dividing unit 25 to prevent the inclusion of other document data in the user-specific file 13 even if the person in charge includes it in the original file 11.

[0052] 6, a rule is defined that "copies should not be included in the user-specific file" when dividing files. This exclusion rule allows the dividing unit 25 to exclude copies from being included in the user-specific file 13 even if the person in charge includes copies in the original file 11.

[0053] (2) For example, in Figure 6, a rule is defined that when assigning a file name, "User number" - "Issue date" - "Amount billed" should be set as the file name. Note that the date and time are automatically assigned to the file name of the user-specific file 13 immediately after it is created, and assigning a file name is simply renaming the file. However, if a new file name is assigned when the user-specific file 13 is divided, renaming is not necessary.

[0054] Also, including the "user number," "issue date," and "billing amount" in the file name is just an example, and only one of these may be used, or a different character string (which can be obtained from the user-specific file) may be added to the file name.In addition, information included in the shipping information may be used in the file name.

[0055] The person in charge can operate the terminal device 30 to display the setting screen of the file processing unit 6, create rules, or display and edit rules that have already been created.

[0056] <Example of document data> Next, an example of document data will be described with reference to Figures 7 and 8. Figure 7 is an example of document data for an invoice, and Figure 8 is an example of document data for a receipt. Both the invoice and the receipt contain the user's address 101, the recipient's name 102, the user's name 103, the user number 104, the issue date 105, and the amount 106. Since these are digital data, the service processing unit 9 and the file processing unit 6 can acquire each of these pieces of information.

[0057] When document data such as an invoice is in the form of image data, a method is known in which the service processing unit 9 performs OCR (Optical Character Recognition / Reader) processing on the image data to obtain character data. In this case, a scanner device scans the document (paper) and transmits the image data to the terminal device 30. The terminal device 30 performs character recognition on the image data and performs file division and other operations.

[0058] <Operations and Processing> Next, the flow of processing performed by the terminal device 30 will be described with reference to Fig. 9. Fig. 9 is a flowchart illustrating the flow from when the terminal device 30 creates the original file 11 to when it transmits the user-specific file 13 to the delivery system 50. The processing in Fig. 9 starts when, for example, a person in charge inputs a print operation for document data into the terminal device 30.

[0059] First, the file creation request unit 23 of the business software 8 requests the service processing unit 9 to create the original file 11 together with the document data (S11).

[0060] This request calls the service processing unit 9, and the reception unit 24 of the service processing unit 9 creates an original file 11 in, for example, PDF format from the document data received from the business software 8 (S12).

[0061] When the original file 11 is created, the division unit 25 of the service processing unit 9 refers to the rules and acquires the rules for dividing the file (S13). The rules are, for example, as follows:

[0062] 1-1 Divide files by "User Number" 1-2 Include "invoices" and "receipts" in user-specific file 13 1-3 Do not include copies in user file 13 The dividing unit 25 divides the original file 11 into user-specific files 13 for each user (S14). The dividing unit 25 acquires the user numbers from the first page of the original file 11 in order, and determines this user number as the user number of interest. The dividing unit 25 acquires pages that share the same user number of interest, determine whether the document name is "invoice" or "receipt," and do not contain the character "copy." The dividing unit 25 extracts pages with "invoice" or "receipt" until the user number changes, excludes pages containing "copy," and divides the document data of one or more pages acquired by these processes into one user-specific file 13. When division is complete for all user numbers, the original file 11 disappears.

[0063] The dividing unit 25 may determine whether there is a document containing the currently focused user number up to the last page of the original file 11. In this way, even if the original file 11 is not sorted by user number, document data containing the same user number can be divided into a single user-specific file 13.

[0064] The dividing unit 25 may also divide the original files 11 after sorting them in ascending or descending order of the user numbers.

[0065] When the dividing unit 25 divides all of the original files 11 into the individual user files 13, the data name assigning unit 26 refers to the rules and acquires the rules for renaming files (S15). The rules are, for example, as follows:

[0066] 2-1 Set the file name as "User Number"_"Issue Date"_"Billing Amount" The data name assigning unit 26 obtains the relevant character string from the user-specific file 13 based on the rules, and assigns a file name (an example of a name) using the character string to the user-specific file 13 (S16). The "user number," "issue date," and "billing amount" are all written on the invoice, so they can be obtained from the invoice. The data name assigning unit 26 may also obtain these character strings from a receipt. Note that the connector "_" connecting the "user number," "issue date," and "billing amount" is just an example, and "-," "~," "&," "#," etc. may also be used.

[0067] Once the file name is assigned, the combining unit 27 refers to the shipping information and determines whether or not an enclosure is required for each user-specific file 13 (S17). The combining unit 27 acquires the user number from the user-specific file 13, and acquires the enclosure requirement information associated with this user number from the shipping information storage unit 31.

[0068] If the determination in S17 is yes, the combining unit 27 retrieves the enclosure data 12 identified by the enclosure 1 code and the enclosure 2 code from the enclosure data storage unit 33 and combines them with the user-specific file 13 (S18). The combining method may be to add all pages of the enclosure data 12 to one of the user-specific files 13. For example, combining a user-specific file 13 with ...

[0069] If the enclosure is not required (No in S17), the process proceeds to step S19.

[0070] In step S19, the combining unit 27 determines whether or not the necessity of enclosure items has been determined for all user-specific files 13 (S19).

[0071] If the determination in step S19 is Yes, the process proceeds to step S20, and if No, the process returns to step S17.

[0072] In step S20, the transmission unit 28 transmits the user-specific files 13 to the delivery system 50 (S20). Note that the transmission unit 28 may transmit each user-specific file 13 to the delivery system 50 each time it is created, rather than waiting until all user-specific files 13 have been created.

[0073] The shipping system 50 receives the user-specific file 13, and the sender performs the shipping process manually, or the shipping system 50 performs the shipping process automatically. Whether the shipment is to be made by mail or by email may be determined by contract, or may be registered in the shipping user information for each user.

[0074] <Major Effects> In this embodiment, the terminal device 30 divides the original file 11 into user-specific files 13, and the delivery system 50 can mail all of the printed copies of the user-specific files 13 to the same destination, thereby reducing the workload. Also, when sending by email, there is no need to manually divide the original file 11, determine whether or not enclosure data 12 is required, and then attach it; the user-specific files 13 can be sent. Furthermore, because the terminal device 30 divides the original file 11 into user-specific files 13, enclosure data 12 can be enclosed for each user.

[0075] [Second embodiment] In this embodiment, a terminal device 30 will be described that does not necessarily divide the original file 11 by user. That is, in this embodiment, a terminal device 30 will be described that integrates multiple document data with the same shipping destination even if the document data has different user numbers.

[0076] <About the function> FIG. 10 is a diagram showing an example of the functional configuration of a terminal device 30 according to this embodiment. The explanation of FIG. 10 will mainly focus on the differences from FIG. 4. The file processing unit 6 of this embodiment has an integration unit 29. The integration unit 29 integrates multiple user-specific files 13 based on rules, for example, when users have the same address. This reduces the labor required for mailing.

[0077] <Rules stored in the rule memory> Fig. 11 shows an example of rules in this embodiment, in which a rule for recombining files is added. (3) When merging files 3-1 Merging user files 13 with the same "address" That is, the integration unit 29 refers to the addresses in the user-specific files 13 and combines the user-specific files 13 having the same address into one. For example, if a married couple resides in a nursing home, they may have the same address, which can reduce the labor required for mailing.

[0078] In the rule of FIG. 11, files are integrated by address, but the rule may also stipulate that user-specific files 13 with the same telephone number, fax number, or email address are integrated.

[0079] In addition, as a method for combining user-specific files 13 having the same address into one, there is also a method of not dividing document data of the same address even if the user number is different, that is, not dividing the data at the time of division. However, this method makes the process complicated if the original file 11 does not contain consecutive document data of users with the same address.

[0080] Since it is unclear how user-specific files 13 with the same "address" were created, when user-specific files 13 with the same "address" are integrated, they can be said to be "not split" regardless of internal processing.

[0081] <Operations and Processing> FIG. 12 is a flowchart illustrating the process from when the terminal device 30 creates the original file 11 to when the user-specific file 13 is sent to the delivery system 50. The explanation of FIG. 12 will mainly focus on the differences from FIG. 9. In FIG. 12, step S31 has been added. The processes other than step S31 may be the same as those in FIG. 9.

[0082] In step S31, the integration unit 29 of the file processing unit 6 integrates user-specific files 13 that have the same address (S31). That is, the integration unit 29 obtains the address from one user-specific file 13 and searches all other user-specific files 13 for a user-specific file 13 with the same address. The integration unit 29 performs this process for all user-specific files 13. If there are user-specific files 13 with the same address, the integration unit 29 integrates the multiple user-specific files 13 into one. The integration method may be to add all pages of one user-specific file 13 to another user-specific file 13; for example, integrating a user-specific file 13 with three pages and a user-specific file 13 with four pages results in a user-specific file 13 with seven pages.

[0083] As described above, the dividing unit 25 may divide the document data of users with the same address into one file 13 by using a method that does not divide the document data of users with the same address even if the user numbers are different.

[0084] It should be noted that when the delivery system 50 delivers the user-specific files 13 by email, it is not preferable to integrate user-specific files 13 with the same address. For this reason, the integration unit 29 should integrate user-specific files 13 with the same address only for users whose delivery method in the delivery system 50 is mail. In this case, it is assumed that the delivery method is set in the delivery information.

[0085] Furthermore, in the process of FIG. 12, when the delivery system 50 delivers the user-specific files 13 by email, the user-specific files 13 with the same email address may be integrated.

[0086] <Major Effects> According to this embodiment, in addition to the effects of the first embodiment, by integrating the user-specific files 13, it is possible to reduce the labor required for mailing.

[0087] [Third embodiment] In this embodiment, a terminal device 30 that determines whether or not an enclosure is required based on the attributes of the user will be described.

[0088] In this embodiment, the hardware configuration diagram of Fig. 3 and the functional block diagram of Fig. 4 described in the above embodiment can be used. In this embodiment, the shipping information stored in the shipping information storage unit 31 is different from that in the first embodiment.

[0089] <Shipping information stored in the shipping information storage unit> FIG. 13 shows an example of shipping information stored in the shipping information storage unit 31 of this embodiment. The explanation of FIG. 13 will mainly focus on the differences from FIG. 5. The shipping information in FIG. 13 does not have the field for whether enclosed items are required, and a new field for attributes has been added. The field for attributes is set to the type of nursing home the user is using. The type of nursing home the user is using is an attribute that indicates the user's health condition. The combining unit 27 of this embodiment identifies whether enclosed items are required and the enclosed item data 12 according to the user's attributes. In other words, the combining unit 27 combines the enclosed item data 12, which is previously associated with the user's attributes, into a user-specific file.

[0090] As shown in FIG. 14, in order to determine whether an enclosure is necessary and the enclosure data 12, enclosure selection information is stored in the enclosure data storage unit 33 of this embodiment. FIG. 14 shows the enclosure selection information. The enclosure selection information has an enclosure code associated with an attribute. In other words, an enclosure code is registered for each type of nursing home. The combining unit 27 of this embodiment determines the enclosure code according to the user's attribute based on the enclosure selection information. Note that if the attribute indicates that an enclosure is necessary, the enclosure code is a numeric value, and if the attribute indicates that an enclosure is not necessary, the enclosure code field is null or blank.

[0091] As in the first embodiment, if the shipping information includes an item for whether or not an enclosure is required, the person in charge must set whether or not an enclosure is required for each user. In contrast, in this embodiment, the necessity of whether or not an enclosure is required and the type of enclosure data are controlled according to attributes, thereby reducing the need for the person in charge to set whether or not an enclosure is required for each user.

[0092] 14 is the type of facility, but the user attributes may also be gender, age, family structure (whether married or not, whether or not there are children), contract details with the facility (grade of service, room size, whether or not nursing care is provided, etc.) In the enclosure selection information, enclosure codes are associated with these attributes.

[0093] <Operations and Processing> 15 is a flowchart illustrating the flow from creation of the terminal device 30 to transmission of the user-specific file 13 to the delivery system 50. The explanation of FIG. 15 will mainly focus on the differences from FIG. 9. The processing of steps S41 to S46 may be the same as steps S11 to S16 in FIG.

[0094] In step S47, the combining unit 27 refers to the shipping information and enclosure selection information and determines whether an enclosure is required for each user-specific file 13 (S47). The combining unit 27 obtains the user number from the user-specific file 13 and obtains the user attributes associated with this user number from the shipping information storage unit 31. From the enclosure selection information, the combining unit 27 determines whether an enclosure is required based on the enclosure code associated with the attribute (if the enclosure code is a number, then an enclosure is required), and if an enclosure is required, identifies the enclosure data.

[0095] If it is determined that an enclosure is necessary (Yes in S47), the combining unit 27 acquires the enclosure data 12 identified by the enclosure code from the enclosure data storage unit 33 and combines it with the user-specific file 13 (S48).

[0096] If it is determined that no enclosure is required (No in S47), the process proceeds to step S49.

[0097] In step S49, the combining unit 27 determines whether or not the necessity of enclosure items has been determined for all user-specific files 13 (S49).

[0098] If the determination in step S49 is Yes, the process proceeds to step S50, and if No, the process returns to step S47.

[0099] In step S50, the transmitting unit 28 of the file processing unit 6 transmits the user-specific files 13 to the delivery system 50 (S50). Note that the transmitting unit 28 may transmit each user-specific file 13 to the delivery system 50 each time it is created, rather than waiting until all user-specific files 13 have been created.

[0100] <Major Effects> According to this embodiment, in addition to the effects of the first embodiment, the terminal device 30 can enclose enclosed items according to the user's attributes in a user-specific file 13 and send the item, thereby reducing the need for the person in charge to set whether or not enclosed items are required for each user.

[0101] [Fourth embodiment] In this embodiment, a data output system will be described in which a server device performs the processing that was previously performed by a terminal device 30.

[0102] <System configuration example> Fig. 16 is an example of a system configuration diagram of the data output system 100. In the explanation of Fig. 16, differences from Fig. 2 will be mainly explained. As shown in Fig. 16, the data output system has a server device 60.

[0103] The server device 60 performs tasks such as dividing the original file 11, assigning file names, and combining the enclosure data 12. The server device 60 is realized by one or more information processing devices. The server device 60 can communicate with the terminal device 30 via networks N1 and N2. The server device 60 can also communicate with the delivery system 50 via network N1.

[0104] The server device 60 may be realized by cloud computing or by a single information processing device. Cloud computing refers to a usage mode in which resources on a network are used without being aware of specific hardware resources. The server device 60 may exist on the Internet or on-premise.

[0105] <About the function> 17 is a diagram showing an example of the functional configuration of the terminal device 30 and the server device 60 according to this embodiment. Note that the explanation of FIG. 17 will mainly focus on the differences from FIG.

[0106] <<Terminal Device>> In this embodiment, the terminal device 30 includes a communication unit 41, an operation reception unit 22, a display control unit 21, a file creation request unit 23, and a reception unit 24. Among these, the functions of the operation reception unit 22, the display control unit 21, the file creation request unit 23, and the reception unit 24 may be the same as those in FIG.

[0107] The communication unit 41 (an example of a first communication unit) transmits and receives various types of information to and from the server device 60. In this embodiment, the communication unit 41 transmits an original file 11 containing document data such as invoices for multiple users to the server device 60. Alternatively, when the terminal device 30 executes a Web application, the communication unit 41 receives various types of screen information and the like from the server device 60, and transmits to the server device 60 information (original file 11) set on the screen by a care facility staff member.

[0108] Assuming that the terminal device 30 communicates with the server device 60, the terminal device 30 may execute business software 8 provided as a web application. In this case, the person in charge can connect the terminal device 30 to the server device 60, download the web application, and create an invoice within this web application. Furthermore, the person in charge can execute printing within the web application or send the created document data to the server device 60, which can then divide the data into user-specific files 13 and send them to the delivery system 50. Therefore, the person in charge does not need to prepare business software 8 separately from the contract for using the server device 60.

[0109] A web app is an application that runs through cooperation between a program written in a programming language (e.g., JavaScript (registered trademark)) that runs on a web browser and a program on the web server (dispatch system 50) side. In contrast, an application that cannot be executed unless it is installed on the terminal device 30 is called a native app. In this embodiment, the application executed on the terminal device 30 may be either a web app or a native app.

[0110] <<Server device>> The server device 60 has a communication unit 42, a division unit 25, a data naming unit 26, a combination unit 27, and a transmission unit 28. Each function of the server device 60 is a function or means realized when any of the components shown in Fig. 3 operates in response to an instruction from the CPU 501 in accordance with a program loaded from the HD 504 onto the RAM 503. Of these, the functions of the division unit 25, the data naming unit 26, the combination unit 27, and the transmission unit 28 may be the same as those in Fig. 4.

[0111] The server device 60 also has a shipping information storage unit 31, a rule storage unit 32, and an enclosure data storage unit 33. Each of these storage units may exist on the network. The information stored in each of these storage units may be the same as that shown in FIG. 4.

[0112] The communication unit 42 (an example of a second communication unit) transmits and receives various types of information to and from the terminal device 30. In this embodiment, the communication unit 42 receives an original file 11 containing document data such as invoices for multiple users from the terminal device 30. When the terminal device 30 executes a web application, the communication unit 42 transmits various types of screen information and the like to the terminal device 30, and receives from the terminal device 30 information set on the screen by a care facility staff member.

[0113] <<Action or Processing>> 18 is a sequence diagram illustrating the flow from when the terminal device 30 creates the original file 11 until when the server device 60 transmits the user-specific file 13 to the delivery system 50. Note that the explanation of FIG. 18 may use the process described in FIG. 9.

[0114] S101: The reception unit 24 of the terminal device 30 creates the original file 11. That is, the terminal device 30 executes the processes of steps S11 and S12 in FIG.

[0115] S102: When the original file 11 is created, the communication unit 41 of the file processing unit 6 transmits the original file 11 to the server device 60.

[0116] S103: The communication unit 42 of the server device 60 receives the original file 11. The server device 60 divides the original file 11 into user-specific files 13, assigns file names, and combines the enclosure data 12. That is, the server device 60 executes the processes of steps S13 to S19 in FIG. 9.

[0117] S104: When the user-specific file 13 is created, the transmitting unit 28 of the server device 60 transmits the user-specific file 13 to the delivery system 50.

[0118] S105: The shipping system 50 receives the user-specific file 13. The sender performs the shipping process manually, or the shipping system 50 performs the shipping process automatically. Whether the shipping is performed by mail or email may be determined by contract, or may be registered in the shipping user information for each user.

[0119] 18, the server device 60 transmits the user-specific file 13 to the delivery system 50. However, the process may be such that the server device 60 transmits the user-specific file 13 to the terminal device 30, and the terminal device 30 transmits it to the delivery system 50.

[0120] Furthermore, although the processing in FIG. 18 is similar to that in the first embodiment, the server device 60 may execute the processing in the second and third embodiments.

[0121] <Major Effects> According to this embodiment, in addition to the effects of the first embodiment, the server device 60 can perform operations such as dividing the original file 11, so that the terminal device 30 can perform operations such as dividing the original file 11 by connecting to the server device 60.

[0122] [Other application examples] The best mode for carrying out the present invention has been described above using examples, but the present invention is not limited to these examples in any way, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention.

[0123] For example, in this embodiment, the service processing unit 9 divides the file, but the file division may be performed by application software. In the case of application software, it is sufficient to obtain the original file 11 created by a general-purpose printer driver.

[0124] Furthermore, the functions of the business software, the service processing unit 9, or the file processing unit 6 may be possessed by any of the business software, the service processing unit 9, or the file processing unit 6. Two or more of the business software, the service processing unit 9, and the file processing unit 6 may be integrated.

[0125] In this embodiment, the terminal device 30 sends the user-specific files to the shipping system, but the terminal device 30 may also print the user-specific files on a printing device in the care facility. In this case, the terminal device 30 also sends the user-specific files 13 to the printing device. The user-specific files 13 are compiled by user using the finisher of the printing device, making the process easy.

[0126] In addition, the configuration examples shown in Fig. 4 and the like are divided according to main functions to make it easier to understand the processing by the terminal device 30. The method of dividing the processing units and their names do not limit the present invention. The processing by the terminal device 30 can be divided into even more processing units depending on the processing content. Furthermore, it can also be divided so that one processing unit includes even more processing.

[0127] Additionally, the devices described in the examples are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, server device 60 includes multiple computing devices, such as a server cluster, configured to communicate with each other via any type of communications link, including a network, shared memory, etc., and to perform the processes disclosed herein.

[0128] Furthermore, the server device 60 can be configured to share the processing steps disclosed in this embodiment, such as those shown in FIG. 18, in various combinations. For example, a process executed by a specific unit can be executed by multiple information processing devices included in the server device 60. Furthermore, the server device 60 may be integrated into a single server device, or may be divided into multiple devices.

[0129] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and conventional circuit modules designed to perform each of the above-described functions.

[0130] <Aspect> [Claim 1] a reception unit that receives original data including a plurality of document data; a dividing unit that divides the original data into data for each delivery destination, each having delivery destination identification information, based on delivery destination identification information of the document data described in the document data; a transmission unit that transmits the data by destination divided by the division unit to an external device; An information processing device having the above. [Claim 2] a data name assigning unit that assigns a name including a character string acquired from the data by destination to the data by destination divided by the dividing unit, The transmission unit transmits the named data by destination to the outside. 2. The information processing device according to claim 1, comprising: [Claim 3] a combining unit that combines the enclosure data with the destination-specific data for which the enclosure data is required, based on shipping information in which the necessity of enclosure data is set in association with the destination identification information; The transmission unit transmits the destination-specific data combined with the enclosure data to the outside. 3. The information processing device according to claim 1 or 2. [Claim 4] If the necessity of the enclosure data associated with the shipping destination identification information is "necessary," The shipping information includes identification information of the enclosure data associated with the shipping destination identification information, the combining unit combines the enclosure data identified by the identification information of the enclosure data with the delivery destination data. The information processing device according to claim 3. [Claim 5] a rule for dividing the original data into the data by delivery destination is registered in advance by the dividing unit; The rule defines the shipping destination identification information to be referenced in the original data in order for the dividing unit to divide the same shipping destination identification information into one of the shipping destination-specific data. 5. The information processing device according to claim 1. [Claim 6] The document data is sent to the user of the service, The shipping destination identification information is the identification information of the user. 6. The information processing device according to claim 1. [Claim 7] The rule defines document names to be extracted from the original data into the delivery destination data, among the document data that may be included in the original data; the dividing unit divides only the document data of the document name defined in the rule from the original data into the data by delivery destination. The information processing device according to claim 5. [Claim 8] The rule defines document names that should not be divided into the data by delivery destination by excluding them from the original data, among documents that may be included in the original data; the dividing unit does not divide the document data of the original data having the document name that should not be divided as defined in the rule into the data by delivery destination; The information processing device according to claim 5. [Claim 9] character strings to be included in the names are registered in advance as rules for the data name assigning unit to assign the names to the delivery destination data, the data name assigning unit assigns a name to the delivery destination data, the name including the character string defined in the rule, acquired from the delivery destination data; The information processing device according to claim 2. [Claim 10] a rule for dividing the original data into the data by delivery destination is registered in advance by the dividing unit; The rules include a rule for integrating data for a plurality of shipping destinations, and an integration unit that integrates the plurality of pieces of shipping destination data based on the rule; The information processing device according to claim 6. [Claim 11] The rule for integrating the data by shipping destination specifies that the data by shipping destination is integrated if the addresses of the users of the service are the same; The integration unit integrates two or more pieces of shipping destination data having the same address acquired from the shipping destination data. The information processing device according to claim 10. [Claim 12] The document data is sent to the user of the service, Identifying the attributes of the user based on shipping information in which the attributes of the user are set in association with the shipping destination identification information; a combining unit that combines enclosure data that is previously associated with the attributes of the user with the data by delivery destination, The transmission unit transmits the destination-specific data combined with the enclosure data to the outside. 3. The information processing device according to claim 1 or 2. [Claim 13] the receiving unit receives the original data created by the information processing device or the original data from an external source; 13. The information processing device according to claim 1. [Explanation of symbols]

[0131] 8. Business Software 9 Service Processing Department 30 Terminal Equipment 50 Shipping System [Prior art documents] [Patent documents]

[0132] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-183322

Claims

1. a reception unit that receives original data including a plurality of document data; a dividing unit that divides the original data into data for each delivery destination, each having delivery destination identification information, based on delivery destination identification information of the document data described in the document data; a transmission unit that transmits the data by destination divided by the division unit to an external device; An information processing device having the above.

2. a data name assigning unit that assigns a name including a character string acquired from the data by destination to the data by destination divided by the dividing unit, The transmission unit transmits the named data by destination to the outside. The information processing device according to claim 1 ,

3. a combining unit that combines the enclosure data with the destination-specific data for which the enclosure data is required, based on shipping information in which the necessity of enclosure data is set in association with the destination identification information; The transmission unit transmits the destination-specific data combined with the enclosure data to the outside.

3. The information processing device according to claim 1 or 2.

4. If the necessity of the enclosure data associated with the shipping destination identification information is "necessary," The shipping information includes identification information of the enclosure data associated with the shipping destination identification information, the combining unit combines the enclosure data identified by the identification information of the enclosure data with the delivery destination data. The information processing device according to claim 3 .

5. a rule for dividing the original data into the data by delivery destination is registered in advance by the dividing unit; The rule defines the shipping destination identification information to be referenced in the original data in order for the division unit to divide the same shipping destination identification information into one of the shipping destination-specific data. The information processing device according to claim 1 .

6. The document data is sent to the user of the service, The shipping destination identification information is the identification information of the user. The information processing device according to claim 1 .

7. The rule defines document names to be extracted from the original data into the delivery destination data, among the document data that may be included in the original data; the dividing unit divides only document data of the document name defined in the rule from the original data into the data by delivery destination. The information processing device according to claim 5 .

8. The rule defines document names that should not be divided into the data by delivery destination by excluding them from the original data, among documents that may be included in the original data; the dividing unit does not divide the document data of the original data having the document name that should not be divided as defined in the rule into the data by delivery destination; The information processing device according to claim 5 .

9. character strings to be included in the names are registered in advance as rules for the data name assigning unit to assign the names to the delivery destination data, the data name assigning unit assigns a name to the delivery destination data, the name including the character string defined in the rule, acquired from the delivery destination data; The information processing device according to claim 2 .

10. a rule for dividing the original data into the data by delivery destination is registered in advance by the dividing unit; The rules include a rule for integrating data for a plurality of shipping destinations, and an integration unit that integrates the plurality of pieces of shipping destination data based on the rule; The information processing device according to claim 6 .

11. The rule for integrating the data by shipping destination specifies that the data by shipping destination is integrated if the addresses of the users of the service are the same; The integration unit integrates two or more pieces of shipping destination data having the same address acquired from the shipping destination data. The information processing device according to claim 10.

12. The document data is sent to the user of the service, Identifying the attributes of the user based on shipping information in which the attributes of the user are set in association with the shipping destination identification information; a combining unit that combines enclosure data that is previously associated with the attributes of the user with the data by delivery destination, The transmission unit transmits the destination-specific data combined with the enclosure data to the outside.

3. The information processing device according to claim 1 or 2.

13. the receiving unit receives the original data created by the information processing device or the original data from an external source; The information processing device according to claim 1 .

14. An information processing device a reception unit that receives original data including a plurality of document data; a dividing unit that divides the original data into data for each delivery destination, each having delivery destination identification information, based on delivery destination identification information of the document data described in the document data; a transmission unit that transmits the data by delivery destination divided by the division unit to an external device; A program to function as a

15. A data processing method performed by an information processing device, A process in which an accepting unit accepts original data including a plurality of document data; a process in which a dividing unit divides the original data into data for each delivery destination having the delivery destination identification information based on the delivery destination identification information of the document data described in the document data; A process in which a transmission unit transmits the data by destination divided by the division unit to an external device; Data processing methods.

16. A data output system in which a terminal device and a server device can communicate with each other, The terminal device a reception unit that receives original data including a plurality of document data; a first communication unit that transmits the original data to the server device; The server device a second communication unit that receives the original data; a dividing unit that divides the original data into data for each delivery destination, each having delivery destination identification information, based on delivery destination identification information of the document data described in the document data; a transmission unit that transmits the data by destination divided by the division unit to an external device; A data output system having:

17. a reception unit that receives original data including a plurality of document data; a first communication unit that transmits the original data to the server device; and a server device that can communicate with the terminal device, the server device comprising: a second communication unit that receives the original data; a dividing unit that divides the original data into data for each delivery destination, each having delivery destination identification information, based on delivery destination identification information of the document data described in the document data; a transmission unit that transmits the data by destination divided by the division unit to an external device; A server device having the above configuration.

18. A data processing method performed by a data output system capable of communicating between a terminal device and a server device, comprising: The terminal device A process of accepting original data containing multiple document data; transmitting the original data to the server device; The server device receiving the original data; A process of dividing the original data into data for each delivery destination, each data having only the delivery destination identification information, based on the delivery destination identification information of the document data described in the document data; A process of transmitting the divided data by destination to an external device; Data processing methods.

19. a reception unit that receives original data including a plurality of document data; a server device capable of communicating with a terminal device having a first communication unit that transmits the original data to the server device; a second communication unit that receives the original data; a dividing unit that divides the original data into data for each delivery destination, each having delivery destination identification information, based on delivery destination identification information of the document data described in the document data; a transmission unit that transmits the data by delivery destination divided by the division unit to an external device; A program to function as a

Images