Information processing system, information processing method, and information processing program

Abstract

To provide an information processing system, an information processing method, and an information processing program that easily select a document form.SOLUTION: An information processing system includes: a document form storage unit that stores, for each application specified in a hierarchical structure consisting of a plurality of hierarchical layers including a top layer and a bottom layer, one or more document forms that define the document form in association with the application; an application selection reception unit that accepts selection of an application from the top layer to the bottom layer in order to accept a selection of the application; and a selection unit that selects one or more document forms corresponding to the selected application as a document form for generating one or more document form data suitable for the selected application.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to a technique for selecting a form. [Background technology]

[0002] Conventionally, an information output device (see Patent Document 1) has been proposed that includes an input receiving unit that receives a selection of a template into which user information is to be embedded, a judgment unit that judges whether the information output device is connected to a network in order to obtain the user information, a reading unit that reads the user information from a recording medium on which the user information is recorded if it is determined that the device is not connected to the network, an embedding processing unit that embeds the read user information in a specified area of ​​the selected template, and an output unit that outputs the template in which the user information is embedded.

[0003] In addition, in an administrative system, when an applicant's life event and registration information corresponding to the life event are input, a device has been proposed (see Patent Document 2) that refers to a memory unit that stores the correspondence between the life event and one or more procedures related to it, identifies the procedure associated with the inputted applicant's life event, and transmits the inputted registration information of the applicant to a processing device that processes the identified procedure.

[0004] Also, an electronic document system has been proposed (see Patent Document 3) in which a main menu screen and various sub-menu screens for selecting a document are displayed, and when the desired document is selected using the menu screen and various sub-menu screens and printing is instructed, a print command for the selected document is sent to a management computer and printing data for the document is obtained from the management computer, thereby performing the printing process for the document.

[0005] Furthermore, a device has been proposed (see Patent Document 4) that, when it receives the application type of an applicant's application procedure, refers to an other application procedure memory unit that stores other application procedures that the applicant should perform for the application type based on the received application type, and determines other application procedures that the applicant should perform. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2017-98690 A [Patent Document 2] JP 2015-46129 A [Patent Document 3] JP 2010-213206 A [Patent Document 4] JP 2017-41138 A Summary of the Invention [Problem to be solved by the invention]

[0007] Conventionally, report forms (report templates) are provided for various types of reports. A user selects the report (report form) to be used depending on what he or she wants to do (purpose), and creates the desired report based on the selected report form. However, there are cases where it is not easy for a user to select all the reports (report forms) required for what he or she wants to do (purpose).

[0008] In view of the above problems, an object of the present disclosure is to easily select a form. [Means for solving the problem]

[0009] One example of the present disclosure is an information processing system including: a form storage means for storing, for each purpose specified in a hierarchical structure consisting of multiple layers including a top layer and a bottom layer, one or more form forms that define the format of the form in association with the purpose; a purpose selection receiving means for receiving a selection of purpose elements from the top layer to the bottom layer in order, and a selection means for selecting the one or more form forms corresponding to the selected purpose as form forms for generating one or more form data suitable for the selected purpose.

[0010] The present disclosure can be understood as an information processing device, a system, a method executed by a computer, or a program executed by a computer. The present disclosure can also be understood as a program recorded on a recording medium readable by a computer or other device, machine, etc. Here, a recording medium readable by a computer, etc. refers to a recording medium that stores information such as data and programs by electrical, magnetic, optical, mechanical, or chemical action and can be read by a computer, etc. Effect of the Invention

[0011] According to the present disclosure, it becomes possible to easily select a form. [Brief description of the drawings]

[0012] [Figure 1] 1 is a schematic diagram showing a configuration of a system according to an embodiment. [Diagram 2] 1 is a diagram illustrating an outline of the functional configuration of an information processing device and a reading device according to an embodiment. [Diagram 3] FIG. 11 is a diagram showing an example of a description condition according to the embodiment. [Figure 4] FIG. 13 is a diagram showing an example of a medium definition according to the embodiment. [Diagram 5] FIG. 11 is a diagram showing an example of underlay data according to the embodiment; [Figure 6] FIG. 11 is a diagram showing an example of underlay data according to the embodiment; [Figure 7] 11 is a diagram for explaining a method of defining items using underlay data according to an embodiment (in the case of application by the person in question). FIG. [Figure 8] 13 is a diagram for explaining a method of defining items using underlying data according to an embodiment (in the case of application by a proxy). FIG. [Figure 9] 11 is a diagram for explaining a method of defining items using underlay data according to an embodiment (in the case of application by the person in question). FIG. [Figure 10]13 is a diagram for explaining a method of defining items using underlying data according to an embodiment (in the case of application by a proxy). FIG. [Figure 11] 13 is an example of a form generation screen according to the embodiment. [Figure 12] 5 is a diagram showing an example of item definitions of a form according to the embodiment; FIG. [Figure 13] FIG. 4 is a diagram illustrating an example of a form list according to the embodiment. [Figure 14] FIG. 13 is a diagram showing an example of a form list generation screen (category 1 generation screen) according to the embodiment. [Figure 15] FIG. 13 is a diagram showing an example of a form list generation screen (a generation screen for category 2) according to the embodiment. [Figure 16] FIG. 13 is a diagram showing an example of a form list generation screen (a form association screen) according to the embodiment. [Figure 17] FIG. 2 is a diagram showing an example of an outline of a form associated with a use according to the embodiment; [Figure 18] FIG. 13 is a diagram showing an example of a form selection screen (a use element (category 1) selection screen) according to the embodiment. [Figure 19] FIG. 13 is a diagram showing an example of a form selection screen (a use element (category 2) selection screen) according to the embodiment. [Figure 20] FIG. 11 is a diagram showing an example of read data for a read item according to the embodiment; [Figure 21] FIG. 11 is a diagram showing an example of data description (conversion example) according to the embodiment. [Figure 22] FIG. 13 is a diagram showing an example of an output image confirmation screen according to the embodiment. [Diagram 23] FIG. 11 is a diagram illustrating an example of CSV information according to the embodiment. [Figure 24] 1 is a flowchart showing an overview of the flow of a form generation process according to an embodiment. [Diagram 25] 10 is a flowchart showing an overview of the flow of a form list generation and association process according to the embodiment. [Figure 26]4 is a flowchart showing an outline of the flow of a form generation and output process according to the embodiment. [Figure 27] 11 is a flowchart showing an outline of the flow of a form generation and output process (with a back side reading instruction) according to the embodiment. [Figure 28] 11 is a flowchart showing an overview of the flow of a form selection process according to the embodiment. [Figure 29] 1 is a flowchart showing an overview of the flow of a form generation process according to the embodiment. [Diagram 30] 13 shows an example of a form (item definition) related to variations. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment of an information processing device, a system, a method, and a program according to the present disclosure will be described with reference to the drawings. However, the embodiment described below is an example of an embodiment, and the information processing device, a system, a method, and a program according to the present disclosure are not limited to the specific configuration described below. In carrying out the present disclosure, a specific configuration according to the embodiment may be appropriately adopted, and various improvements and modifications may be made.

[0014] In this embodiment, an information processing device, a system, a method, and a program according to the present disclosure will be described as being implemented in a system that generates a form (form data) using information on an identification card read by a card reader. However, the information processing device, a system, a method, and a program according to the present disclosure can be widely used in technologies for creating forms (form data), and the application of the present disclosure is not limited to the examples shown in the embodiment.

[0015] <System configuration> FIG. 1 is a schematic diagram showing the configuration of a system according to this embodiment. In the system according to this embodiment, an information processing device 1 is connected to a reading device 9 via a network or other communication means so that they can communicate with each other. In this embodiment, a mode of implementing the technology according to this disclosure in a system in which a card reader (reading device 9) equipped with a reading unit and an information processing device 1 connected to the card reader via a wired or wireless connection are connected will be described. However, the system according to this embodiment may be an information processing system in which a reading device 9 that reads information from a medium on which information related to a user is recorded is connected to an information processing device 1, and the technology according to this disclosure is also applicable to a system in which a scanner device and an information processing device 1 are connected, for example.

[0016] The information processing device 1 is a computer including a central processing unit (CPU) 11, a read only memory (ROM) 12, a random access memory (RAM) 13, a storage device 14 such as an electrically erasable and programmable read only memory (EEPROM) or a hard disk drive (HDD), an input device 15 such as a keyboard, a mouse, or a touch panel, an output device 16 such as a display, and a communication unit 17 such as a network interface card (NIC). However, the specific hardware configuration of the information processing device 1 can be omitted, replaced, or added as appropriate depending on the embodiment. In addition, the information processing device 1 is not limited to a device consisting of a single housing, and may be realized by multiple devices using so-called cloud or distributed computing technology. Therefore, for example, the function of generating a form (form definition) and the function of generating a form (form data) may be functions provided in different devices (systems). The information processing device 1 generates form data based on information recorded on a medium such as an identification card read by a reading device 9.

[0017] The reading device 9 is a computer including a reading unit 91, a camera (camera for photographing a face) 92, a CPU 93, a ROM 94, a RAM 95, a storage device 96, an input device 97 such as a touch panel, an output device 98 such as a display, and a communication unit 99. However, the specific hardware configuration of the reading device 9 can be omitted, replaced, or added as appropriate depending on the embodiment. Furthermore, the reading device 9 is not limited to a device consisting of a single housing, and may be realized by multiple devices using so-called cloud or distributed computing technology, etc.

[0018] The reading device 9 (reading unit 91) is a device that reads information from a medium (such as an identification card) on which information related to a user (such as a person who performs a procedure or a person who is the subject of a procedure) associated with a document is recorded (including "written" on the medium). Hereinafter, "information related to (related to) a user" is referred to as "user information". In addition, in this embodiment, an identification card (personal identification document) is exemplified as a medium on which user information is recorded. However, the medium may be a card or document other than an identification card as long as it is a medium on which user information is recorded. In addition, the medium on which user information is recorded is not limited to being in card format, and may be a medium having a size different from the card size. In addition, any information may be recorded on the medium. For example, the medium may record, as user information, a name, an address, a changed address, a date of birth, a number (such as a driver's license number or a passport number), a validity period (such as a driving expiration date or a passport expiration date), a facial photo, etc. In this embodiment, an embodiment in which form data is generated by reading user information from a medium on which the user information is recorded will be described, but the present disclosure also applies to an embodiment in which form data is generated based on information other than the user information read from the medium. Therefore, the information recorded on the medium may be information other than the user information.

[0019] In this embodiment, the reading device 9 is exemplified by a card reader that reads information on an identification card. The reading device 9 transmits the read information to the information processing device 1. The reading unit 91 is, for example, a camera (certificate photographing camera) that photographs an identification card (ID card face) and / or an IC reader that reads information recorded in an IC chip. The reading device 9 reads information written on the identification card by, for example, performing character recognition processing (OCR (Optical Character Recognition) processing) on ​​an image obtained by photographing the identification card with the certificate photographing camera. The reading device 9 also reads information recorded on the IC chip by, for example, reading an IC chip that is built into the identification card (IC card) and records user information. Note that the reading device 9 is not limited to a card reader, and may be a device that captures an image by photographing an identification card set by a user. For example, the target identification card may be photographed using a scanner, a digital camera, or a camera sensor built into a smartphone / tablet to obtain an image. In this case, the identification card information is read by performing OCR processing on the obtained image in the reading device 9. However, the OCR processing may be performed in the information processing device 1 instead of the reading device 9. In this case, the captured image is transmitted from the reading device 9 to the information processing device 1, and the information processing device 1 that receives the image performs OCR processing.

[0020] In this way, the reading device 9 according to this embodiment has a function of transmitting data read from a medium to the information processing device 1 via a network. The reading device 9 may further have a user interface such as a touch panel display or a keyboard for enabling character input / output and application selection, as well as a web browsing function and a server function. The communication means and hardware configuration of the reading device 9 capable of employing the method according to this embodiment are not limited to the examples in this embodiment.

[0021] 2 is a diagram showing an outline of the functional configuration of the information processing device and the reading device according to the present embodiment. The information processing device 1 includes a condition storage unit 21, a medium definition storage unit 22, a display control unit 23, a form generating unit 24, a form list generating unit 25, a form storage unit 26, a form form selecting unit 27, a data acquiring unit 28, a collation unit 29, a form generating unit 30, and an output unit 31, by a program recorded in a storage device 14 being read into a RAM 13 and executed by a CPU 11, and each hardware included in the information processing device 1 is controlled. Note that in this embodiment and other embodiments described later, each function included in the information processing device 1 is executed by the CPU 11, which is a general-purpose processor, but some or all of these functions may be executed by one or more dedicated processors.

[0022] The condition storage unit 21 stores one or more writing conditions (condition definitions that define writing conditions) that can be specified (defined) for each form item (type of item). In this embodiment, the writing conditions are conditions related to the item data of the form item. The writing conditions are, for example, conditions related to the expression method when writing item data based on acquired user information (input information that is included in the user information and is input data for the form item) and / or conditions for writing item data of the form item (conditions indicating whether or not to write item data). Hereinafter, "conditions related to the expression method when writing item data" will be referred to as "expression method conditions", and "conditions for writing item data of the form item" will be referred to as "conditions for writing". The conditions for writing are conditions related to the type of medium (identification) for writing item data of the form item and / or conditions related to the result of identity verification for writing item data of the form item. As will be described in detail later, the report form generation unit 24 generates a report form in which the writing conditions for each report item are defined (specified) by accepting the writing conditions selected (selected and input) by the user from the writing conditions stored in the condition memory unit 21 for each report item.

[0023] FIG. 3 is a diagram showing an example of the description conditions according to the present embodiment. As shown in FIG. 3, the condition storage unit 21 stores one or more definable description conditions for each document item (type of item), such as "name", "address", "preliminary address change (address after change)", "date of birth", "number", "expiration date", and "fixed characters". As shown in FIG. 3, the number of conditions stored as definable description conditions may differ for each document item. Below, an example of a definable description condition for each item is shown. However, the definable description conditions are not limited to the examples of the description conditions below, and may include other description conditions, or may not include some of the description conditions below. In addition, the document item (type of item) is not limited to the items exemplified in FIG. 3, and may be any item. Hereinafter, the types of items (document items), such as name, address, preliminary address change, date of birth, number, expiration date, and fixed characters, are referred to as "item types".

[0024] (Conditions for the form item "Name") In FIG. 3, the following description conditions are shown as examples of definable conditions for the form item "Name", including "No Condition", "Remove Space", "Fix Space", and "Alphabet". "Remove Space" is a condition indicating that if there is a space between the last name and the first name in the input data (input information) related to the form item "Name", this space is removed before the data is written. "Fix Space" is a condition indicating that for the form item "Name", the item data is written with a space of a specified size (such as one full-width space) between the last name and the first name. In other words, if there is no space between the last name and the first name in the input data (input information) related to the form item "Name", the data is written with a space of a specified size. "Alphabet" is a condition indicating that if the input data (input information) related to the form item "Name" is a character type other than the alphabet, the data is converted to the alphabet before being written. All of these three conditions fall under the expression method conditions described above.

[0025] (Conditions for the form item "Address") In FIG. 3, the following are examples of definable description conditions for the form item "Address", including "No condition", "Complete prefecture", "Complete street number", and "Background fill". "Complete prefecture" is a condition indicating that when the prefecture is omitted in the input data (input information) related to the form item "Address", prefecture information is supplemented (added) from postal code, city, town, and village information, and then the data is entered. This condition is defined (selected) in forms (application documents, etc.) in which prefecture information needs to be entered. "Complete street number" is a condition indicating that when the street number is expressed as a hyphen (e.g., "1-2") in the input data (input information) related to the form item "Address", the data is converted to an expression using kanji characters such as "number" and "number" (e.g., "1-2-gou"). This condition is defined in forms (application documents, etc.) in which street number information needs to be entered. "Background fill" is a condition indicating that the background of the area in which the item data of the form item "Address" is entered is filled. Note that "Complete prefecture" and "Complete address" correspond to the expression method conditions described above. The description conditions may include conditions related to the area in which the item data is written, such as the above-mentioned "background filling." The description conditions may also include conditions related to the contents to be written as the item data.

[0026] (Conditions for the form item "Preliminary address change") In FIG. 3, examples of possible writing conditions that can be defined for the form item "preliminary address change (field for writing changed address)" include "no condition," "write image," and "write OCR results." "write image" is a condition that indicates that an image of the location where the changed address is written (address field) is to be written as the item data for the form item "preliminary address change." "write OCR results" is a condition that indicates that the results of OCR processing of the image of the location where the changed address is written is to be written as the item data for the form item "preliminary address change." Note that these two conditions correspond to the expression method conditions described above.

[0027] (Conditions for the form item "Date of birth") In FIG. 3, possible writing conditions that can be defined for the form item "Date of Birth" are "No Condition", "Japanese Calendar", "Gregorian Calendar", and "Background Fill". "Japanese Calendar" is a condition that indicates that the item data for the form item "Date of Birth" is written in the Japanese calendar. "Gregorian Calendar" is a condition that indicates that the item data for the form item "Date of Birth" is written in the Gregorian calendar. "Background Fill" is a condition that indicates that the background of the area in which the item data for the form item "Date of Birth" is written is filled in. Note that "Japanese Calendar" and "Gregorian Calendar" fall under the expression method conditions described above.

[0028] (Conditions for the form item "Number") In FIG. 3, examples of definable description conditions for the form item "number" include "no condition" and "describe the security code on the My Number card." "describe the security code on the My Number card" is a condition indicating that if the type of identification determined by the reading unit 81 described below is a My Number card, the security code read from the My Number card is to be written. This condition is specified, for example, when it is inappropriate to write the My Number card on the application form because it is confidential information. Note that "describe the security code on the My Number card" corresponds to the expression method condition described above.

[0029] (Description conditions for the form item "Expiration date") In FIG. 3, for the form item "Expiration date", "No condition", "Japanese calendar", "Western calendar", "Notification of expiration", etc. are shown as definable description conditions. "Japanese calendar" is a condition indicating that the item data related to the form item "Expiration date" is written in the Japanese calendar. "Western calendar" is a condition indicating that the item data related to the form item "Expiration date" is written in the Western calendar. "Notification of expiration" is a condition indicating that if the target identification card is determined to be expired based on the input data (input information) related to the form item "Expiration date", the fact that it has expired is notified (a mark (such as an * mark) indicating expiration is written). Note that "Japanese calendar" and "Western calendar" correspond to the expression method conditions, and "Notification of expiration" corresponds to the condition for writing. However, the designation of the type of fixed character (such as an * mark) means that expiration is expressed with an * mark, and therefore corresponds to the expression method condition.

[0030] (Description conditions for the form item "Static text") In FIG. 3, the following conditions are shown as definable conditions for the form item "fixed characters": "no condition", "specific identification", "expired", and "identity verification is NG". The type of identification is specified for "specific identification". For example, a condition such as "my number card" is specified. For example, the condition "my number card" is specified as a condition indicating that a fixed character (e.g., a circle mark) is to be written only when the (type of) identification that has been read is a my number card. "expired" is specified as a condition indicating that a fixed character (e.g., a * mark) is to be written only when it is determined that the validity period has expired. "identity verification is NG" is specified as a condition indicating that a fixed character (e.g., a * mark) is to be written only when the result of identity verification based on the identification is NG. All of these three conditions correspond to the above-mentioned conditions for writing. However, with regard to the designation of the type of fixed characters, it means that being a My Number Card, that it has expired, and that identity verification has failed are expressed by a circle, an asterisk, and a letter, respectively, and therefore each of these meets the expression method conditions.

[0031] As described above, the expression method conditions may include at least one of conditions, for example, conditions regarding the type of characters (Kanji, alphabet, etc.), conditions regarding the expression format of the date (Gregorian calendar, Japanese calendar, etc.), conditions regarding the data format of the time, conditions regarding whether data needs to be supplemented when entering item data based on the input information (such as supplementing prefectures), conditions regarding whether some data of the input information needs to be deleted when entering item data based on the input information, conditions regarding whether the input information needs to be replaced (substituted) with other data when entering item data based on the input information, conditions specifying the data to be entered as an image, and conditions specifying the data to be entered as the result of character recognition.

[0032] The medium definition storage unit 22 stores a medium definition (certificate definition) that defines the expression method for each record item recorded on the medium for each type of medium. In an identification card, the type of characters for the information recorded, the location where the information is recorded, the degree of information recorded, etc. may differ depending on the type of identification card. Therefore, in the medium definition (medium definition information) according to this embodiment, the difference in the expression method for the record items in a plurality of identification cards is defined. More specifically, in the medium definition, the expression method in the identification card for each record item that is an item recorded on the identification card is stored for each type of identification card. In this embodiment, the expression method of the record item means how the data (information) of the record item is expressed (expression method) in the identification card. Examples of the expression method include the expression format (type of characters used, date and time format, degree of information recorded (for example, "only prefecture" for address), etc.) and the written surface of the information (front side, back side), and the expression method defined in the medium definition may be at least one of these expression methods. In addition to the expression method, the medium definition may define the type (meaning) of recorded information, such as the type (meaning) of a number or the type (meaning) of an expiration date.

[0033] FIG. 4 is a diagram showing an example of a medium definition according to the present embodiment. As shown in FIG. 4, the medium definition defines, for each identification card, the expression method of each item recorded (written) on the identification card. For example, as shown in FIG. 4, in the case of a My Number card, the expression methods of the record items "name", "address", "preliminary address change", "date of birth", and "number" are defined as "kanji (with external characters)", "blank", "front side (handwritten)", "Japanese calendar, Western calendar (for foreign nationality)", and "none (front side), My Number (back side)", respectively. In this case, "kanji (with external characters)" indicates that the name, which is a record item, is recorded in kanji (but with external characters). "Blank" indicates that a part of the address is written without omission. "Handwritten on front side" indicates that the record item, preliminary address change (changed address), is recorded (written) by hand on the front side of the My Number card (identification card). "Japanese calendar, Western calendar (for foreign nationals)" indicates that the date of birth, which is a record item, will be recorded in the Japanese calendar if the card holder is not a foreign national, and will be written in the Western calendar if the card holder is a foreign national. "None (front), My Number (back)" indicates that the number (My Number), which is a record item, will not be written on the front of the My Number card, but will be written on the back.

[0034] In addition, the media definition shown in Figure 4 defines the method of expressing each recorded item on the identification card, as well as the type of information (meaning), such as the type of number recorded on the identification card ("My Number," "Driver's license number," "Residence number," "Passport number," etc.) and the type of expiration date ("Expiration date," "Driver's expiration date," "Residence expiration date," "Passport expiration date," etc.).

[0035] As with the My Number Card, the expression method for various identification documents such as a driver's license, a residence card, and a passport is defined in the media definition (see FIG. 4). For example, as shown in FIG. 4, for a driver's license, the expression method for the record item "address" is defined as "the prefecture may be omitted." "The prefecture may be omitted" indicates that the prefecture may be omitted from the record item of the address. Also, for example, as shown in FIG. 4, for a passport, the expression method for the record item "name" is defined as "alphabet." "Alphabet" indicates that the record item of the name is recorded in alphabet. Also, as shown in FIG. 4, for a passport, the expression method for the record item "address" is defined as "prefecture only." "Prefecture only" indicates that only the prefecture is written from the record item of the address. Also, for example, as shown in FIG. 4, for a passport, the expression method for the record item "preliminary change of address" is defined as "not stated." "Not stated" indicates that the record item of the preliminary change of address (changed address) is not written on the passport. It should be noted that the record items are not limited to those shown in FIG. 4, and any items may be included.

[0036] The display control unit 23 displays various screens via the output device 16. For example, the display control unit 23 displays a form generation screen, a form list generation screen, a form selection screen (application selection screen), an output image confirmation screen, etc. Details of the various screens displayed by the display control unit 23 will be described later.

[0037] The form generating unit 24 generates one or more form forms that define the format of the form. The form generating unit 24 generates a form form that defines, for each of a plurality of form items in the form, the description position of the item data of the form item and the description conditions for the item data of the form item that is described at the description position. In this embodiment, the "form form (form definition (information))" is composed of information (form format information) that defines the form format of the form such as the appearance of the form and the form item definition, and information (output information) that defines the output method of the form and the operation at the time of output. However, depending on the embodiment, the form definition information may not include the output information. In this embodiment, a method of using underlay data (underlay image, etc.) is exemplified as a method of generating a form form (form layout). When underlay data is used, the user may create a form form by laying out ruled lines, fixed character strings, etc. along the underlay data, or the underlay data itself may be the output target. In this embodiment, as an example, the underlying data itself is the output target. That is, a method of generating a form (form layout) by simply defining items on the underlying data is illustrated. Below, an example of a form generation method using underlying data is illustrated. The form generation unit 24 includes an underlying data acquisition unit 241, an input acceptance unit 242, and a generation unit 243.

[0038] The underlying data acquisition unit 241 acquires underlying data that serves as an underlying (base of the form) for the layout of the form from a user (a form creator). The underlying data may be in any data format. The underlying data may be, for example, a form image (image data such as bitmap data or JPEG data) obtained by imaging a paper form, a Word file (data), an Excel file (data), a PDF file (data), or the like. The underlying data may also be an electronic file obtained by performing OCR processing on an image. For example, a scanned image obtained by scanning a paper application document used in a city hall or the like can be used as the underlying data.

[0039] 5 and 6 are diagrams showing an example of underlying data according to the present embodiment. FIG. 5 shows a scanned image obtained by scanning a resident registration application form consisting of one page (one sheet) as underlying data. FIG. 6 shows a scanned image obtained by scanning a resident registration application form consisting of two pages (two sheets) as underlying data. When such underlying data is displayed on the form generation screen by the display control unit 23, a user (form form creator) can easily create a form form just by defining items on the underlying data. Note that the form form generated by the form generation unit 24 may include multiple form forms in which different item definitions are combined with the same layout (appearance of the form). For example, as described later, it is possible to generate multiple form forms in which different item definitions are combined with the same underlying data as multiple form forms that correspond to multiple uses having the same use element in layers above the lowest layer of the hierarchical structure.

[0040] The input receiving unit 242 receives input (including selection input) from the user (form creator) regarding the item data writing position (writing area), item type (item name, etc.), and one or more writing conditions for each form item. In order to generate a form form for a desired form (define the form items), the user specifies the writing area for the item data of the form item, selects the item type, and selects (selects) one or more writing conditions for the form item in the underlying data. The user performs these operations for each form item. Note that the user performs the above operations, for example, with the underlying data displayed on the form form generation screen displayed by the display control unit 23.

[0041] FIG. 7 is a diagram for explaining a method of defining items using underlay data according to this embodiment (in the case of a personal application). As shown by the bold frame in FIG. 7, the user specifies the writing area in the form for each of the item types, such as "address", "name", "date of birth", "fixed characters (where the type of identification card is written)", and "number (where in parentheses)". When this operation is performed, the input receiving unit 242 receives the specification (input) of this writing area. Any method may be used to specify the writing area, and for example, a method of specifying a desired area on the underlay data by dragging the mouse or a method of specifying coordinates may be used. In addition, when the underlay data is an Excel file, a method of specifying a cell may be used to specify the area. The area enclosed by the dotted frame in FIG. 7 may be specified as, for example, an area where the address after the change is written (an area for a preliminary address change).

[0042] The user selects (selects and inputs) the item type and description condition for each of the form items for which the area is specified. For example, when a list including definable item types is displayed on the form form generation screen (item type selection screen), the user selects the item type to be defined from the list. The item types are, for example, name, address, address change reserve, date of birth, creation date and time, and fixed characters. Also, for example, when a list including one or more description conditions (see FIG. 3) that can be defined for a form item is displayed on the form form generation screen (description condition selection screen), the user selects the description condition to be defined from the list. Note that the number of description conditions selected (defined) for a form item may be one or more. Also, the number of description conditions selected (defined) may differ between form items. When the user selects the item type and description condition, the input receiving unit 242 receives these selections (selects and inputs).

[0043] As described above, multiple forms may be generated with different item definitions for the same underlying data. For example, Fig. 7 illustrates the area designation for an application by a person himself / herself, but in the case of an application by a proxy, the underlying data shown in Fig. 7 (the underlying data in Fig. 5) may have different item definitions from those in Fig. 7.

[0044] FIG. 8 is a diagram for explaining a method of defining items using underlying data according to this embodiment (in the case of an application by an agent). As in FIG. 7, writing areas are specified for each of the item types "Address", "Name", "Date of Birth", "Fixed Characters", and "Number". In FIG. 7, the areas for "Address", "Name", and "Date of Birth" are specified, which correspond to the field for application by the person himself (area written by the person himself), whereas in FIG. 8, the areas for "Address", "Name", and "Date of Birth" are specified, which correspond to the field for application by an agent (area written by the agent). In this way, multiple forms with different item definitions may be generated for the same underlying data.

[0045] FIG. 9 is a diagram for explaining a method for defining items using underlying data according to this embodiment (in the case of an application by the person himself / herself). FIG. 10 is a diagram for explaining a method for defining items using underlying data according to this embodiment (in the case of an application by an agent). In FIGS. 9 and 10, an item data writing area is specified for the underlying data of a two-page resident registration application form (underlying data in FIG. 6). In FIGS. 9 and 10, a writing area is specified for each of the item types "address," "name," "fixed characters," and "number."

[0046] Fig. 11 is an example of a form generation screen according to this embodiment. The form generation screen as shown in Fig. 11 is displayed by the display control unit 23. On this form generation screen, the user may perform item definition for each form item as described above. Fig. 11 shows a state in which each field (area) has been set and item attributes (e.g., item name, maximum font size, etc.) for the item type "name" have been defined.

[0047] The generating unit 243 generates a form by combining the underlay data acquired by the underlay data acquiring unit 241 with the writing positions, item types, and writing conditions accepted by the input accepting unit 242 .

[0048] FIG. 12 is a diagram showing an example of item definition of a form according to the present embodiment. FIG. 12 shows an item definition in which attributes of nine fields (form items) in a form are defined as an example. In the form form (item definition) shown in FIG. 12, an item type, a writing position (area), and a writing condition are defined for each field. In the area, area information of the area specified by the user (for example, the position in the form (X coordinate, Y coordinate) and the size of the area (width and height)) is defined. Note that the area information may be automatically extracted when the user specifies the area by dragging the mouse on the form form generation screen. Also, in FIG. 12, as an example of the writing conditions, a condition for writing item data of the form item (writing condition), a condition for the expression method when writing the item data (expression method condition), and a condition for the area in which the data of the form item is written are defined. Note that, in FIG. 12, the font type, font size, and the like are not defined as item attributes, but these attributes are also defined as necessary.

[0049] In FIG. 12, for example, for field 1, the following conditions are defined for writing: item type "name", area "x1, y1, w1, h1", writing condition "all", expression method condition "no condition", and area-related condition "none". The writing condition "all" indicates that the item data of the item type "name" can be written on any type of identification card. The expression method condition "no condition" indicates that there is no expression method condition for the item data of the item type "name". The area-related condition "none" indicates that the background of the area in which the item data of the item type "name" is written is not filled in. Also, for example, for field 7, the following conditions are defined: item type "static characters", area "x7, y7, w7, h7", writing condition "My Number Card", expression method condition "static characters: 〇", and area-related condition "none". The expression method condition "static characters: 〇" indicates that the item data of the item type "static characters" is set to the static character "〇". In addition, in the item type "Creation Date and Time" of field 5, the date and time when the identification card was read is entered as item data.

[0050] Although the above describes a method for generating a form using underlying data, the form may be generated without using underlying data. In this case, the user (form creator) can generate the layout (appearance) of the form by determining the lines and character strings to be written fixedly on the form.

[0051] The form list generating unit 25 generates a form list (purpose list) that defines the purpose of the form (the purpose (what the user who creates the form wants to do)). The form list is configured in a hierarchical structure consisting of multiple hierarchies including a top layer and a bottom layer, and each purpose included in the form list is specified (configured) in one or more hierarchies. In other words, each purpose is uniquely specified by the purpose element of each layer. In this embodiment, a form list configured in a hierarchical structure consisting of two layers (a hierarchical structure consisting of only a top layer and a bottom layer) is exemplified. Therefore, each purpose is specified in one or two layers. Hereinafter, the top layer is referred to as "category 1" and the bottom layer is referred to as "category 2". The number of layers is not limited to two, and may be three or more.

[0052] FIG. 13 is a diagram showing an example of a form list according to the present embodiment. FIG. 13 shows an example of a form list consisting of two hierarchical levels, and "resident's certificate application", "moving-in application", "seal certificate" and "renewal of My Number card" are shown as use elements of category 1. Uses related to resident's certificate applications are defined as uses consisting of two hierarchical levels (categories), and in the form list, "for the person" and "for the agent" are defined as use elements of category 2 linked to "resident's certificate application", which is a use element of category 1. That is, the use of a resident's certificate application by the person is defined (specified) by category 1 "resident's certificate application" and category 2 "for the person", and the use of a resident's certificate application by an agent is defined (specified) by category 1 "resident's certificate application" and category 2 "for the agent". Similarly, uses related to a moving-in application are defined as uses consisting of two hierarchical levels, and in the form list, "moving from outside the city", "moving from within the city", and "moving from overseas" are defined as use elements of category 2 linked to "moving-in application", which is a use element of category 1.

[0053] In addition, the use related to the seal certification is defined as a use consisting of one layer, and in the form list, the use element of category 2 linked to the use element of category 1, "seal certification", is not defined (omitted). Similarly, the use related to the renewal of the My Number card is defined as a use consisting of one layer, but "Do you have a My Number card?" is defined as a use element of category 2 for the use element of category 1, "Renewal of My Number card". This means that when there is only one use element of category 2 (category linked to the top layer) linked to category 1, a screen that prompts the user to pay attention (confirm) (for example, a screen that asks the user to confirm (agree) that it is okay to create a form for the use selected by the user) is displayed. In the example of FIG. 13, when the user selects "Renewal of My Number card" as the use element of category 1, a screen containing the message "Do you have a My Number card?" is displayed.

[0054] In this way, the hierarchical structure may include a layer of purpose elements indicating the type of procedure (application type such as "resident registration application" or "seal certification"), and a layer of purpose elements indicating attributes of the user (user performing the procedure or subject of the procedure) (such as "self", "agent", "moving from outside the city") located below the layer related to the type of procedure. However, the hierarchical structure is not limited to this example, and may be composed of layers of any type of purpose element. Furthermore, the purposes included in the form list may be any purpose. Furthermore, a user (such as a system installer) can change, add, or delete the form list and the purposes (purpose elements) held in the form list as necessary.

[0055] 13, one or more form forms are associated (linked) with each purpose. For example, two form forms, "Resident Certificate Application (Self)" and "Resident Certificate Application (Common Back Side)", are associated with the purpose of a resident certificate application by an individual, defined by category 1 "Resident Certificate Application" and category 2 "For Individual". Similarly, two form forms, "Resident Certificate Application (Agent)" and "Resident Certificate Application (Common Back Side)", are associated with the purpose of a resident certificate application by an agent, defined by category 1 "Resident Certificate Application" and category 2 "For Agent". In this way, multiple form forms may be associated with one purpose.

[0056] Also, for example, a form "Application for moving in (from outside the city)" is associated with the purpose of application for moving in (from outside the city) defined by category 1 "application for moving in" and category 2 "moving from outside the city". Also, one form "seal certificate" is associated with the purpose of seal certification defined by category 1 "seal certification". Also, one form "application for updating my number card" is associated with the purpose of updating my number card defined by category 1 "update my number card". In this way, the form storage unit 26 described later stores one or more form forms in association with each purpose (the purpose element at the lowest level of each purpose). Below, an example of a method for generating a form list and associating purposes with form forms will be described.

[0057] Fig. 14 is a diagram showing an example of a form list generation screen (a generation screen for category 1) according to this embodiment. Fig. 14 shows an example in which "resident registration application", "seal certificate", and "moving-in procedure" are generated as use elements for category 1. In this way, a user (such as a system installer) generates displays (such as buttons) corresponding to use elements for category 1 on the form list generation screen.

[0058] Fig. 15 is a diagram showing an example of a form list generation screen (a generation screen for category 2) according to this embodiment. Fig. 15 shows an example in which "application by applicant" and "application by proxy" are generated as use elements of category 2 for a use element of category 1, "application for resident's certificate". In this way, a user (such as a system installer) generates displays (such as buttons) corresponding to use elements of category 2 on the form list generation screen.

[0059] FIG. 16 is a diagram showing an example of a form list generation screen (form correspondence screen) according to the present embodiment. FIG. 16 shows a selection screen for a form (form definition) to be associated with a purpose defined (specified) by the purpose element "resident's certificate application" of category 1 and the purpose element "application by the applicant himself" of category 2. In the screen shown in FIG. 16, a user can select a form definition with a form definition name "resident's certificate application (self)" to associate a purpose specified by the purpose element "resident's certificate application" of category 1 and the purpose element "application by the applicant himself" of category 2 with a form form with a form definition name "resident's certificate application (self)". Note that, although FIG. 14 to FIG. 16 show an example of a case where the form list generation and correspondence processing are performed on the screen, the form list generation and correspondence processing may be performed without using a screen. For example, these processes may be performed by using an Excel file (table), a text file, or the like.

[0060] FIG. 17 is a diagram showing an example of a summary of a form associated with a use according to the present embodiment. In FIG. 17, when the use element of category 1 is "resident's certificate application", "for the person" and "for the agent" are exemplified as use elements of category 2 below it, but there is a difference in the form associated with the case where the person applies (for the person) and the case where the agent applies (for the agent). Specifically, the base data used for the front side of the resident's certificate application is the same for both, but there is a difference in the definition of items (the position of the name and address, and whether or not the person who came to the counter is written). In this way, it is possible to generate multiple form forms in which different item definitions are combined with the same base data as multiple form forms that correspond to multiple uses having the same use element (for example, "resident's certificate application") in the layers above the lowest layer of the hierarchical structure. Note that there is no difference in the form associated with the back side of the resident's certificate application between the case where the person applies and the case where the agent applies (the same form is associated).

[0061] In this way, by associating the lowest-level use element of the hierarchical use with a form suitable for that use, it is possible to select and present a form suitable for the user's use. Also, the user (user) can select what he or she wants to do hierarchically.

[0062] The form storage unit 26 stores the purpose of the form (purpose of the user) and one or more form forms. The form storage unit 26 includes a form form storage unit 261 and a form list storage unit 262. The form form storage unit 261 stores a form form (such as "Resident's Certificate Application (Person)" and "Resident's Certificate Application (Agent)") that is generated by the form generation unit 24 and defines the format of the form. The form form storage unit 261 may store a form form generated in an external device. The form list storage unit 262 stores a form list generated by the form list generation unit 25. The form storage unit 26 stores, for each purpose, a purpose (the purpose element at the lowest level) and one or more form forms suitable for that purpose in association with each other. As shown in Fig. 16, when a user selects a form to be associated with a purpose on the screen, the form name of the selected form may be stored (stored) in the form list in a form associated with the corresponding purpose (the lowest-level purpose element) (see Fig. 13). As another method, the user may create a table in which form names of form forms are associated with the form list as shown in Fig. 13, so that the purpose and the form are stored in association with each other.

[0063] The form selection unit 27 selects a form for generating a form (form data). The form selection unit 27 selects a form for generating a form from among form forms stored in the form storage unit 261 by receiving an input related to the selection of a form from a user. In this embodiment, the form selection unit 27 includes a purpose selection receiving unit 271 and a selection unit 272. The purpose selection receiving unit 271 receives a selection input of a purpose element from the user as an input related to the selection of a form. More specifically, the purpose selection receiving unit 271 receives a selection of a purpose element from the user from the top layer to the bottom layer in order, thereby receiving a purpose selection from the user. The purpose selection receiving unit 271 receives one or more purposes from the user. The selection unit 272 selects one or more form forms corresponding to the purpose (selected purpose) specified by the purpose elements selected by the user from the top layer to the bottom layer as form forms for generating one or more form data suitable for the user's purpose (selected purpose). The selection unit 272 selects one or more form forms corresponding to the user's purpose from among the form forms stored in the form storage unit 261.

[0064] FIG. 18 is a diagram showing an example of a form selection screen (a selection screen for a use element (category 1)) according to the present embodiment. In the form selection screen shown in FIG. 18, the user can select one or more application documents (use elements of category 1). In FIG. 18, buttons for all use elements of category 1, namely "resident's certificate application", "seal certificate", "moving-in procedure" and "moving-out procedure", are displayed (arranged). Note that FIG. 18 shows a state in which "resident's certificate application" and "seal certificate" have been selected by the user as use elements of category 1 (the use element of category 2 for "resident's certificate application" has also been selected). In this state, when the user presses the "moving-in procedure" button (a check mark is displayed accordingly), a screen (see FIG. 19) for selecting a use element of category 2 linked to the use element of category 1, "moving-in procedure", is displayed (the screen transitions).

[0065] FIG. 19 is a diagram showing an example of a form selection screen (a use element (category 2) selection screen) according to this embodiment. In the form selection screen shown in FIG. 19, the user can select one or more use elements of category 2. In FIG. 19, buttons for all use elements of category 2 for the use element "moving in procedure" of category 1, such as "moving from outside the city," "moving from another ward in the city," and "moving from abroad," are displayed (arranged). When the use element desired by the user is selected (a button is pressed) in the screen shown in FIG. 19 and the "Confirm" button is pressed, the use elements are selected from the top to the bottom, so that the screen transitions (returns) to a screen for selecting use elements of category 1 (see FIG. 18). In other words, when use elements for the desired use are selected from the top to the bottom, the user can select another use. When all uses desired by the user are selected, the user presses the "Next" button in the transitioned screen (see FIG. 18).

[0066] In this way, when the user selects the purpose, the purpose selection receiving unit 271 receives the user's selection input of the purpose. In addition, when the user finishes selecting the purpose, the selection unit 272 selects a form corresponding to the selected purpose. If the user selects multiple purposes (for example, a seal certificate, a moving procedure (moving from outside the city), and a resident registration application (for the person)), the selection unit 282 selects a form corresponding to each purpose. In other words, the selection unit 282 selects multiple form forms corresponding to the multiple selected purposes as multiple form forms for generating multiple form data suitable for the multiple purposes of the user. In this case, input data (input information) is placed in the multiple form forms, and multiple form data in which the input data is placed is generated. In this way, the user can select multiple purposes at the same time. In this embodiment, the reading process of the identification card by the reading unit 81 is started by pressing the "Next" button on the screen of FIG. 18.

[0067] In addition, for the display of the use element (such as "moving from outside the city") displayed on the form selection screen of Figures 18 and 19, the data of the use element (use element name) stored in the form list may be used as is, or data (element name) prepared for display may be used. In this case, the data of the use element (use element name) stored in the form list and the data (element name) prepared for display are stored in association with each other.

[0068] The data acquisition unit 28 acquires data (input data) to be written on the form. In this embodiment, the data acquisition unit 28 acquires, as input data, user information recorded on a medium to be read (identification card) on which the user information is recorded. The data acquisition unit 28 also acquires information indicating the type of medium to be read (information on medium type) and the result of identity verification. The data acquisition unit 28 receives (acquires) this information transmitted from a data transmission unit 83, which will be described later.

[0069] FIG. 20 is a diagram showing an example of read data for read items according to the present embodiment. In the example of FIG. 20, each column shows read data (read user information) for one identification card. In the example of FIG. 20, the data acquisition unit 28 acquires data such as "AA BB", "CCCCCCC", "DDDD year E month F day", "male", and "GGGGGG" for read items such as "name", "address", "date of birth", "gender", and "number", respectively. The format of the read data is not limited to the format shown in FIG. 20, and any format may be adopted. The data acquisition unit 28 acquires information indicating the type of identification card and the result of identity verification together with the user information shown in FIG. 20.

[0070] The collation unit 29 collates the description conditions for the form items defined in the form form with information related to the form items obtained based on the medium (identification card) to be read (hereinafter referred to as "medium information"). The collation unit 29 collates the description conditions with the medium information for each of the multiple form items in the form form selected by the form selection unit 27. The medium information and the collation method will be described in detail later together with the form generation method.

[0071] The form generation unit 30 generates one or more form data in which data (item data such as user information recorded on a medium and fixed characters) is written by arranging (embedding) the data in one or more form forms selected by the form form selection unit 27. In this embodiment, the form generation unit 30 varies the contents written at the writing position of the form item according to the collation result by the collation unit 29. Any method may be used to write (arrange) the data at the writing position, and for example, a method of arranging a text object related to the data in the underlay data (copied underlay data) or, in the case of Excel, a method of inputting data into a specified cell (area) may be used.

[0072] Here, in this embodiment, the following are exemplified as medium information to be compared with the description conditions: (1) information (user information) read from an identification card; (2) a method of expressing record items defined for the identified type of identification card; (3) the identified type of identification card; and (4) a result of identity verification obtained based on an identification card. Below, the matching method and the form generation method for each of the above (1) to (4) will be described. Below, an example will be given of a case where the selected form form is the form form (item definition) shown in FIG. 12, and the information read from the identification card is the information shown in FIG. 20. The above (1) to (4) correspond to cases 1 to 4 described below, respectively. Note that the above (1) to (4) are examples of medium information, and the medium information may include other information. Furthermore, cases 1 to 4 are examples of a method for comparing the writing conditions with medium information and a method for generating a report (a method for writing item data), and the method for comparing the writing conditions with medium information and the method for generating a report are not limited to the following cases 1 to 4.

[0073] (Case 1: Matching the conditions and user information) In case 1, the matching unit 29 matches the description conditions (expression method conditions) related to the form item with the user information (input information for the form item) read from the identification card. The description conditions to be matched are the expression method conditions defined in the form. The input information to be matched is information acquired by the data acquisition unit 28. By matching the expression method conditions with the input information, the matching unit 29 determines whether or not it is necessary to change the expression method of the input information to match the expression method conditions (such as converting the character type or supplementing data).

[0074] For example, the collation unit 29 compares the expression method condition for the item type "address" "complement prefecture" with the input information "CCCCCCC" related to the address. When the input information "CCCCCCC" is an address notation that omits prefecture information, the collation unit 29 determines that it is necessary to change the expression method of the input information (complement prefecture information). Also, for example, the collation unit 29 compares the expression method condition for the item type "date of birth" "Gregorian calendar" with the input information related to the date of birth "DDDD year E month F (Gregorian calendar notation)". In this case, since the input information related to the date of birth is expressed in the Gregorian calendar and satisfies the expression method condition, the collation unit 29 determines that it is not necessary to change the expression method of the input information. Also, the collation unit 29 compares the expression method condition for the item type "preliminary address change" "describe image" with the input information (image and / or OCR result of image) related to the preliminary address change (changed address). When an image of the address change portion is acquired as the input information, the expression method condition is satisfied, and therefore the collation unit 29 determines that it is not necessary to change the expression method of the input information. Note that, when the expression method condition for the item type "preliminary address change" is "record OCR results" and the input information is an image of the address change portion, the collation unit 29 determines that it is necessary to change the expression method of the input information (convert from image to OCR information). Note that, since the expression method condition for the item type "name" is "no condition", the collation unit 29 determines that it is not necessary to change the expression method of the input information related to "name" (the input information may be placed as it is as item data). Note that, in the case of the expression method condition for the above-mentioned item type "number", "the My Number card records a security code", when the read identification is a My Number card, the collation unit 29 compares the expression method condition with the input information related to the number. When the input information related to the number is a My Number card and a security code, the collation unit 29 determines that it is necessary to change the expression method of the input information (delete part of the data (My Number) of the input information). Furthermore, when the input information relating to the number is only the My Number, the collation unit 29 determines that it is necessary to change the way of expressing the input information (to replace (switch) it with other data (security code)).The collation unit 29 may collate the identified type of identification card with the condition, without comparing the expression method condition "The My Number Card has a security code written on it" with the input information related to the number, and may determine that the read security code is to be written when the identified type of identification card is a My Number Card. In this case, the form generation unit 30 writes the read security code in the position where the form item "number" is written.

[0075] When the collation unit 29 determines that it is necessary to change the expression method of the input information, the form generation unit 30 generates item data by changing the expression method of the input information for the form item so as to satisfy the description condition, and writes (places) the generated item data (input information whose expression method has been changed) at the description position of the form item. For example, the form generation unit 30 complements the input information related to an address with prefecture information, and writes (embeds) the input information with the complemented prefecture information at the description position of the form item "Address" (the area indicated by "x2, y2, w2, h2" in the case of FIG. 12). The form generation unit 30 performs the process for all input information whose expression method needs to be changed. Note that, for input information whose expression method does not need to be changed, the form generation unit 30 writes (places) it as item data at the description position of the corresponding form item without making any changes. The method of case 1 described above is a method that can be applied to the items of fields 1 to 4 and field 9 in the case of FIG. 12.

[0076] (Case 2: Matching the description conditions with the expression method of the recorded items (media definition)) In case 2, the collation unit 29 compares the description condition (representation method condition) related to the form item with the representation method of the record item defined for the type of the read identification. The description condition to be compared is the representation method condition defined in the form form. The representation method to be compared is the representation method for the record item (record item corresponding to the form item) defined in the medium definition for the type of the identified identification. The collation unit 29 compares the representation method condition related to the form item with the representation method for the record item corresponding to the form item to determine whether or not the representation method of the input information (user information) for the form item needs to be changed (such as converting the character type or supplementing data) in accordance with the representation method condition. The collation unit 29 may also issue an additional reading instruction (for example, an instruction to read the back side as well) to the reading unit 81 according to the collation result by comparing the representation method condition with the representation method. Below, an example of the collation method in the case of the medium definition shown in FIG. 4 will be described. Also, an example will be described in which the type of identification presented by the user is determined to be a "driver's license".

[0077] For example, the expression method condition for the item type "Address" "Complete prefecture" is compared with the expression method for the record item "Address" "Prefecture may be omitted." In this case, since the input information regarding the address may not include the prefecture, the comparison unit 29 determines that the expression method condition may not be satisfied. In this case, the comparison unit 29 determines whether the input information "CCCCCCC" is an address notation that omits prefecture information, and if it is an notation that omits prefecture information, determines that it is necessary to change the expression method of the input information (complement prefecture information). If the type of the identified identification card is "Passport," the expression method is defined as "Prefecture only" in the medium definition, and prefecture information is not omitted and recorded, so it is determined that it is not necessary to change the expression method of the input information (complement prefecture). In this case, only prefectures are entered in the form (city, town, village, etc. are left blank), but city, town, village, address information, etc. may be manually added by the user when generating the form.

[0078] Also, for example, the collation unit 29 collates the expression method condition "Gregorian calendar" for the item type "Date of birth" with the expression method "Japanese calendar" for the record item "Date of birth". In this case, since the expression method for the record item "Date of birth" does not satisfy the expression method condition, the collation unit 29 determines that it is necessary to change the expression method of the input information (convert to the Gregorian calendar (convert the expression format)).

[0079] Also, the expression method condition for the item type "preliminary address change" is "describe image" and the expression method for the record item "preliminary address change" is "reverse side (handwritten)". In this case, the collation unit 29 determines that an image related to the preliminary address change needs to be written on the document as a result of the collation, and therefore additional reading of the reverse side of the presented identification card (driver's license) is necessary. Then, the collation unit 29 issues an additional reading instruction (instruction to read the reverse side (instruction to obtain an image)) to the reading unit 81 for the identification card. Since the expression method condition for the item type "name" is "no condition", the collation unit 29 determines that there is no need to change the expression method for the input information related to "name" (the input information may be arranged as it is as item data). When the type of the identified identification card is "My Number Card", the expression method is defined as "front side (handwritten)" in the medium definition. In this case, since the front side has already been read, the collation unit 29 does not issue an additional read instruction, and the read image (image for the address change reserve field) is entered. In this way, it is possible to issue an instruction to read the back side according to the type of identification.

[0080] When the collation unit 29 determines that it is necessary to change the expression method of the input information, the form generation unit 30 generates item data by changing the expression method of the input information for the form item so as to satisfy the description condition, and writes (places) the generated item data (input information whose expression method has been changed) in the description position of the form item. Note that, for input information (including information obtained by an additional read instruction) whose expression method does not need to be changed, the form generation unit 30 writes (places) it as item data in the description position of the corresponding form item without making any changes. The method of case 2 described above is a method that can be applied to the items of fields 1 to 4 and field 9 in the case of FIG. 12.

[0081] As described above, in cases 1 and 2, the expression method condition is compared with the medium information to determine whether or not the expression method of the input information needs to be changed to match the expression method condition. If it is determined that a change is necessary, item data is generated by changing the expression method of the input information so as to satisfy the expression method condition, and report data containing the generated item data (input information with its expression method changed) is generated.

[0082] (Case 3: Matching the conditions stated with the type of identification) In case 3, the matching unit 29 matches the writing conditions (conditions for writing) related to the form items with the type of identification read from the identification. The writing conditions to be matched are the conditions for writing (conditions related to the type of identification (medium type conditions)) defined in the form. The type (information) of the identification to be matched is information acquired by the data acquisition unit 28. The matching unit 29 matches the conditions for writing with the type of identification to determine whether the acquired type of identification meets the conditions for writing.

[0083] For example, the identification card type information acquired by the data acquisition unit 28 is compared with "My Number Card", which is a condition for writing for the item type "fixed characters" for field 7 in Fig. 12. When the identification card type information indicates My Number Card, the comparison unit 29 determines that the acquired identification card type meets the condition for writing. On the other hand, when the identification card type information indicates something other than My Number Card, the comparison unit 29 determines that the acquired identification card type does not meet the condition for writing.

[0084] Also, for example, the condition for filling out the item type "number" for field 9 in Fig. 12, "driver's license, residence card", is compared with the type information of the identification card acquired by the data acquisition unit 28. When the type information of the identification card indicates a driver's license or residence card, the comparison unit 29 determines that the type of the identification card acquired meets the condition for filling out. On the other hand, when the type information of the identification card indicates anything other than a driver's license or residence card, the comparison unit 29 determines that the type of the identification card acquired does not meet the condition for filling out.

[0085] Only when the collation unit 29 determines that the type of the acquired identification card meets the conditions for writing, the form generation unit 30 writes (places) the item data at the writing position of the form item. In the case of field 7 in FIG. 12, since "fixed character: o" is defined as the expression method condition, when the type of the identified identification card is a My Number card, "o", which is the data defined by the expression method condition, is written (placed) at the writing position (x7, y7, w7, h7). In this way, writing corresponding to the read identification card can be performed. Note that although "o" is exemplified as a fixed character, the fixed character (fixed character string) may be a mark other than "o", a character, a symbol, a combination thereof, etc., and may also be the type of recorded information (for example, the type of number (for example, the characters of "resident number") or the type of expiration date, etc.) defined in the medium definition. 12, since "no condition" is defined as the expression method condition, if the type of identification identified is a driver's license or residence card, the input information related to the number is written (placed) in the writing position (x9, y9, w9, h9). The method of case 3 described above is a method that can be applied to the items of field 7 and field 9 in the case of FIG.

[0086] (Case 4: Matching the stated conditions with the identity verification results) In case 4, the matching unit 29 matches the writing conditions (conditions for writing) related to the form items with the result of identity verification obtained based on the identification card. The writing conditions to be matched are the conditions for writing (conditions related to the result of identity verification (identity verification conditions)) defined in the form. The result of identity verification to be matched (information indicating the result of identity verification) is information acquired by the data acquisition unit 28. The matching unit 29 matches the conditions for writing with the result of identity verification to determine whether the result of identity verification meets the conditions for writing.

[0087] For example, the condition for writing for the item type "static characters" for field 8 in Fig. 12, "identity verification is NG", is compared with the result of identity verification acquired by data acquisition unit 28. If the result of identity verification is NG, matching unit 29 determines that the result of identity verification meets the condition for writing. On the other hand, if the result of identity verification is OK (appropriate), matching unit 29 determines that the result of identity verification does not meet the condition for writing.

[0088] When the collation unit 29 determines that the result of the identity verification satisfies the conditions for writing, the form generation unit 30 writes (places) the item data (data defined in the expression method conditions) at the writing position of the form item. In the case of field 8 in FIG. 12, since "fixed character: *" is defined as the expression method condition, if the result of the identity verification is NG, "*", which is the data defined in the expression method conditions, is written (placed) at the writing position (x8, y8, w8, h8). Note that although "*" is exemplified as a fixed character, the fixed character (fixed character string) may be a mark other than "*", a character, a symbol, a combination thereof, etc. The method of case 4 described above is a method that can be applied to the item of field 8 in the case of FIG. 12.

[0089] As described above, in cases 3 and 4, the conditions for writing are compared with the medium information to determine whether the medium information satisfies the conditions for writing, and item data is written in the writing position of the target form item only when it is determined that the conditions are met. In this case, the item data written in the writing position may be at least one of predetermined information (character string, mark, etc.) specified in the form form and input information for the target form item included in the acquired user information. As described above, when the item data for each form item is written (arranged) by at least one of the methods of cases 1 to 4, for example, form data is generated.

[0090] FIG. 21 is a diagram showing an example of data description (conversion example) according to this embodiment. FIG. 21 shows how data is described on a form (data description example) for each identification card in accordance with the form definition (predetermined description conditions). As shown in FIG. 21 and described above, by defining the description conditions in the form definition, form data is generated in which data that satisfies the description conditions is automatically described (arranged) regardless of the type of identification card presented by the user, making it possible to easily create forms. In other words, it becomes possible to automatically align (convert) the expression method, etc. of information read from each identification card in accordance with the expression method (format, etc.) defined in the expression method condition.

[0091] The output unit 31 outputs the form data (including data-converted form data) generated by the form generating unit 30, and / or outputs (or instructs to output) a form based on the form data. Various methods may be used for outputting and instructing the form data or a form based on the form data. For example, the output unit 31 outputs (transmits) the form data (image data, PDF data, etc.) or the data-converted form data to an external device or an external system communicatively connected to the information processing device 1 via a network or other communication means. The data-converted form data is, for example, form data (CSV information, Text information, etc.) that has been subjected to CSV conversion or Text conversion. In addition, in an external device (for example, a database input system, etc.) that has acquired data such as CSV information, the acquired data may be visually confirmed by a user, and then the database may be updated based on the data. For example, when the CSV information includes information related to a change of address, the information stored in the database of the local government may be updated based on the address information after the change.

[0092] As another output method, for example, when the information processing device 1 has the output unit 31 as a printing function, the output unit 31 prints (outputs) a paper form based on the form data generated by the form generation unit 30. For example, when the information processing device 1 is connected to a printing device (printer) via a network or other communication means so that the two can communicate with each other, the output unit 31 transmits the form data to the printing device and then instructs the printing device to print a paper form based on the form data.

[0093] Fig. 22 is a diagram showing an example of an output image confirmation screen according to this embodiment. As shown in Fig. 22, input data (input information) is embedded (placed) in the form and displayed on the output image confirmation screen, allowing the user to confirm the output image (description) of the form. When multiple form data are generated, it is possible to confirm these multiple form data on the output image confirmation screen. By pressing the "Print" button on this screen, the form is output (printed, etc.) with the displayed output image.

[0094] Fig. 23 is a diagram showing an example of CSV information according to this embodiment. Fig. 23 shows an example of CSV information obtained by CSV conversion of the form data (the form data shown in Fig. 22) generated by the form generation unit 30. The output unit 31 may output (transmit) the CSV information shown in Fig. 23 to another device, system, etc.

[0095] Next, a functional configuration of the reading device 9 will be described. The reading device 9 is provided with a reading unit 81, an identity verification unit 82, and a data transmission unit 83, by a program recorded in a storage device 96 being read into a RAM 95 and executed by a CPU 93 to control each piece of hardware provided in the reading device 9. Note that in this embodiment and other embodiments described later, each function provided in the reading device 9 is executed by the CPU 93, which is a general-purpose processor, but some or all of these functions may be executed by one or more dedicated processors.

[0096] The reading unit 81 determines the type (category) of the medium on which the user information is recorded. In this embodiment, an identification card (personal identification document) is exemplified as the medium on which the user information is recorded, so the reading unit 81 determines (acquires) from the medium which the user information is recorded on (the type of identification card) among various identification cards such as a My Number card, a driver's license, a residence card, and a passport. Various methods may be used to determine the type of identification card. For example, a method may be used in which the type of identification card is determined by reading the identification card (medium) and analyzing the arrangement of characters, photographs, and the like written on the identification card. As another method, a method may be used in which an IC chip mounted on the identification card is read to acquire information indicating the type of identification card recorded on the IC chip (a method using an IC reader). As another method, an image of the identification card may be read and an OCR process may be performed on the image to obtain characters indicating the identification card (e.g., characters such as "driver's license") written on the identification card. Note that, in this embodiment, the reading unit 81 uses the identification card to determine (obtain) the type of the identification card, but the type of the medium to be read may be obtained by receiving an input of the type of the medium to be read from the user.

[0097] Furthermore, the reading unit 81 reads a medium (such as an identification card) to obtain user information recorded on the medium. Various methods may be used to obtain information recorded on the identification card (medium). For example, a method may be used in which information written (recorded) on the surface of the identification card is obtained by performing OCR processing on the identification card (image of the identification card). In this case, a reading process may be performed on information (items) corresponding to the format of the identified type of identification card. Another method may be used in which an IC chip mounted on the identification card is read to obtain user information recorded on the IC chip.

[0098] The identity verification unit 82 performs identity verification using the user information recorded on the medium. Various methods may be used for identity verification. For example, the identity verification unit 82 compares face photo data recorded on the identification card (IC chip) with a face photo of the user taken by the camera 92 of the reading device 9, and judges that "identity verification was not possible (identity verification is NG)" when, for example, the facial features obtained from each of these face photos are different. In addition, for example, when the IC chip and the information on the surface are compared and the two are not consistent (when the information (name and address) recorded on the IC chip of the identification card is different from the information (name and address) on the surface of the identification card, when the layout of the surface of the identification card is the layout of a driver's license but the identification card does not have an IC chip (normally, a driver's license has an IC chip), when the contents of the IC chip are a My Number card but the layout of the surface of the identification card is a driver's license, etc.), it may be judged that identity verification is NG. Also, if the obtained user age is less than the designated age, it may be determined that the identity verification is NG. Note that, in this embodiment, the reading device 9 includes the identity verification unit 82, and thus the identity verification process is performed in the reading device 9, but the information processing device 1 may also include the identity verification unit 82, and thus the identity verification process may be performed in the information processing device 1.

[0099] The data transmission unit 83 transmits various data (information) to the information processing device 1. Specifically, the data transmission unit 83 transmits to the information processing device 1 the type of medium (information related to the medium type) acquired (determined) by the reading unit 81, the user information read by the reading unit 81, and information indicating the result of identity verification by the identity verification unit 82.

[0100] Fig. 24 is a flowchart showing an outline of the flow of the form generation process according to this embodiment. The process shown in this flowchart is started when the information processing device 1 receives an instruction to create a form from a user (such as an installer (operator) of the form generation system). The process shown in this flowchart is executed for each form that the user wants to create. The process shown in this flowchart may be executed by the user performing various operations on the form generation screen (see Fig. 11) displayed by the display control unit 23.

[0101] In step S101, underlying data is acquired. The underlying data acquisition unit 241 acquires underlying data that is the base of the form. When underlying data (for example, a scanned image of a paper form) is input by a user, the underlying data acquisition unit 241 acquires the input underlying data (see FIG. 5). Then, the process proceeds to step S102.

[0102] In steps S102 to S104, the entry area, item type, and entry conditions of item data input (specified) for one form item are acquired from the user. In step S102, the input receiving unit 242 acquires the entry area of ​​the item data input (specified) by the user (see FIG. 7). After that, the process proceeds to step S103.

[0103] In step S103, the input receiving unit 242 acquires the item type input (selected) by the user. A list including item types (name, address, date of birth, gender, etc.) is displayed on the form generation screen, and the user selects a desired item type (for example, "name" or "static characters") from the list. For example, if the user selects the area to the right of the name in FIG. 7 in step S102, the user selects "name" as the item type. Also, for example, if the user selects the leading area of ​​the character string "Personal Number Card" in the personal identification field in FIG. 7 in step S102, the user selects "static characters" as the item type. Then, the process proceeds to step S104.

[0104] In step S104, the input receiving unit 242 acquires one or more description conditions input (selected) by the user. For example, a list including description conditions that can be defined for the item type acquired in step S103 among the description conditions (see FIG. 3) stored in the condition storage unit 21 may be displayed on the form screen. This allows the user to select a desired description condition from the list. For example, if the item type "name" is selected in step S103, a list including description conditions such as "blank removal" and "no condition" is displayed in step S104, and the user selects, for example, "blank removal". Also, for example, if the item type "static characters" is selected in step S103, a list including description conditions such as "my number card (only)" and "driver's license only" is displayed in step S104, and the user selects, for example, "my number card" or "〇 (static characters)". After that, the process proceeds to step S105.

[0105] In step S105, it is determined whether the definition of all form items (all fields) is complete. The form generation unit 24 determines whether the item definition (processing of steps S102 to S104) for all items required by the user is complete. For example, the form generation unit 24 determines that the definition of all items is complete when the user presses a completion button or the like on the form generation screen. If the definition of all items is not complete (No in step S105), the process returns to step S102, and the form items for which the item definition is not complete are defined (processing of steps S102 to S104). On the other hand, if the definition of all items is complete (Yes in step S105), the process proceeds to step S106.

[0106] In step S106, a form is generated. The generation unit 243 generates a form (form definition data) by combining the base data acquired in step S101 with the data (item definition) acquired in steps S102 to S104. After that, the process proceeds to step S107.

[0107] In step S107, the form is saved. The form storage unit 261 stores the form generated in step S106. After that, the process shown in this flowchart ends. Note that between step S104 and step S105, the user may input a label, so that the input receiving unit 242 receives the label input. The label is information (e.g., "application by the person" or "application by the agent") that is higher than the item type (form item name) of "name" or "address." By performing the label input process, it is possible to understand in more detail what information each form item indicates when the form data is converted into CSV information. For example, the information helps to understand whether "name" or "address" belongs to the person or to the agent. Any method may be used to input the label. For example, the position of characters located around the writing area (for example, the characters "Application by Self" or "Application by Agent" as shown in Figure 5) may be specified to obtain information about the characters as the label, or the user may directly input the label characters.

[0108] FIG. 25 is a flowchart showing an outline of the flow of the form list generation and association process according to this embodiment. The process shown in this flowchart is started when the information processing device 1 receives a form list generation and association instruction from a user (such as an installer (operator) of the form generation system). The process shown in this flowchart is premised on the form form being generated in advance. In addition, this flowchart illustrates an example in which the form list is configured in two hierarchical levels (applications are specified in a maximum of two hierarchical levels), but as described above, the form list may be configured in three or more hierarchical levels. The process shown in this flowchart may be executed by the user performing various operations on the form list generation screen (see FIGS. 14 to 16) displayed by the display control unit 23.

[0109] In step S201, a purpose element of category 1 is generated. The form list generation unit 25 generates a purpose element of category 1 (e.g., "Residence Certificate Application") by accepting the user's generation (selection) of a button of category 1 and input of a name into the button (editing input). For example, as shown in Fig. 14, buttons for "Residence Certificate Application", "Seal Certification", and "Moving-in Procedure" are generated on the form list generation screen. After that, the process proceeds to step S202.

[0110] In step S202, it is determined whether or not to generate a use element of category 2. The form list generating unit 25 determines whether or not to generate a use element of category 2 associated with the use element of category 1 (for example, "Resident's Certificate Application") generated in step S201 (whether the user desires to generate it). For example, when a button or the like for associating with a form is pressed on the form list generating screen, the form list generating unit 25 determines not to generate a use element of category 2. In this way, when it is determined not to generate a use element of category 2 (No in step S202), the process proceeds to step S203. Also, for example, when a button or the like for generating a use element of category 2 for the generated use element of category 1 is pressed on the form list generating screen, the form list generating unit 25 determines to generate a use element of category 2. In this way, when it is determined to generate a use element of category 2 (Yes in step S202), the process proceeds to step S204.

[0111] In step S203, the form is associated with the form (form name). The form list generating unit 25 associates the purpose element of category 1 generated in step S201 (purpose specified by the purpose element of category 1) with one or more forms (forms) required for the purpose. For example, one or more form forms required for performing the seal certification are associated with the purpose "seal certification" specified only by the purpose element "seal certification" of category 1. For example, when the user selects the button ("seal certification" button) generated in step S201 on the form list generating screen and then selects one or more form forms to be associated on a screen as shown in FIG. 16, the form list generating unit 25 associates the purpose (purpose element of the lowest layer (category 1)) with the one or more form forms. After that, the process proceeds to step S207.

[0112] In step S204, a purpose element of category 2 is generated. The form list generation unit 25 generates a purpose element of category 2 (for example, "Application by applicant himself / herself") by accepting the user's generation (selection) of a button of category 2 and input of a name into the button (editing input). Then, the process proceeds to step S205.

[0113] In step S205, the form is associated with the form (form name). The form list generating unit 25 associates the purpose element of category 2 generated in step S204 (purpose specified by the purpose element of category 1 generated in step S201 and the purpose element of category 2 generated in step S204) with one or more form forms required for the purpose. For example, for a purpose specified by the purpose element "application for resident's certificate" of category 1 and the purpose element "application by the applicant himself" of category 2, one or more form forms required for the applicant himself to apply for resident's certificate are associated. For example, when the user selects the button ("application by the applicant himself") generated in step S204 on the form list generating screen and then selects one or more form forms to be associated on a screen as shown in FIG. 16, the form list generating unit 25 associates the purpose (purpose element of the lowest layer (category 2)) with the one or more form forms. After that, the process proceeds to step S206.

[0114] In step S206, it is determined whether the generation of all the use elements of category 2 has been completed. The document list generating unit 25 determines whether all the use elements of category 2 to be linked to the use elements of category 1 generated in step S201 (for example, "Application for Resident's Certificate") have been generated. For example, on the document list generating screen, a button or the like for completing the generation of category 2 for the use elements of category 1 generated in step S201 is pressed, whereby the document list generating unit 25 determines that the generation of all the use elements of category 2 has been completed. In this way, when it is determined that the generation of all the use elements of category 2 has been completed (Yes in step S206), the process proceeds to step S207. Also, for example, on the document list generating screen, a button or the like for additionally generating use elements of category 2 for the use elements of category 1 generated in step S201 is pressed, whereby the document list generating unit 25 determines that the generation of all the use elements of category 2 has not been completed. In this way, if it is determined that generation of all purpose elements in category 2 has not been completed (No in step S206), the process returns to step S204, and purpose elements in category 2 that have not yet been generated (e.g., "Application by agent") are generated.

[0115] In step S207, it is determined whether the creation of the use elements of category 1 is completed. The document list generating unit 25 determines whether the creation of all the use elements of category 1 desired by the user is completed. For example, when a button for completing the creation of the document list is pressed on the document list generating screen, the document list generating unit 25 determines that the creation of all the use elements of category 1 is completed. In this way, when the generation of all the use elements of category 1 is completed (Yes in step S207), the document list is generated, and the process shown in this flowchart ends. Also, for example, when a button for additionally generating a use element of category 1 is pressed on the document list generating screen, the document list generating unit 25 determines that the generation of all the use elements of category 1 is not completed. In this way, when the generation of all the use elements of category 1 is not completed (No in step S207), the process returns to step S201, and a use element of category 1 that has not yet been generated (for example, "transfer procedure") is generated.

[0116] In this flowchart, a method for generating a form list is illustrated by generating a lower-layer use element linked to a top-layer use element each time the top-layer use element is created. However, the method for generating a form list is not limited to this example, and a form list may be generated by generating all use elements in the layer starting from the top layer.

[0117] 26 is a flowchart showing an outline of the flow of the form generation and output process according to this embodiment. The process shown in this flowchart is started when the information processing device 1 receives an instruction to create and output a form from a user (such as a user of the form generation system).

[0118] In step S301, a form is selected. The form selection unit 27 selects a form to be used for generating a form. Details of the form selection process will be described later with reference to Fig. 28. After that, the process proceeds to step S302.

[0119] In step S302, an instruction to set the identification card is given. The display control unit 23 displays on the screen a message instructing the user to set (present) the identification card in the reading device 9. Note that, instead of the display control unit 23, another functional unit of the information processing device 1 or the reading device 9 may instruct the user to set (present) the identification card. Note that the instruction may be given by a method other than a screen display, such as sending a sound or a message. By giving the instruction, the user sets the identification card in the reading device 9. In addition, when the identification card is set in the reading device 9, the identity verification unit 82 performs identity verification. As a result, the data acquisition unit 28 acquires information indicating the result of identity verification from the data transmission unit 83. Thereafter, the process proceeds to step S303.

[0120] In step S303, the type of the identification card is acquired. When the reading unit 81 determines (discriminates) the type of the identification card by reading the identification card set in step S302, the data acquisition unit 28 acquires the determined type of the identification card (type information) from the data transmission unit 83. For example, the data acquisition unit 28 acquires information indicating that the type of the identification card set in step S302 is a My Number card. Then, the process proceeds to step S304.

[0121] In step S304, user information (input information) is acquired from the identification card. When the reading unit 81 acquires the user information recorded on the identification card by reading the identification card set in step S302, the data acquisition unit 28 acquires this acquired information from the data transmission unit 83. For example, the data acquisition unit 28 acquires the user information shown in FIG. 20. Note that the data acquisition unit 28 may acquire the type information of the set identification card and the user information recorded on the identification card together from the data transmission unit 83. After that, the process proceeds to step S305.

[0122] In step S305, a form (form data) is generated. The form generation unit 30 generates the form (form data) by combining one or more form forms selected in step S301 with the user information (input information) acquired in step S304. Details of the form generation process will be described later with reference to FIG. 29. In addition, in step S305, the generated form data may be stored. After that, the process proceeds to step S306.

[0123] In step S306, the form is output. The output unit 31 outputs the form data generated in step S305 or a paper form based on the form data. After that, the process shown in this flowchart ends. Note that before executing the process of step S306, the form data generated in step S305 may be presented (displayed) to the user. In addition, the display control unit 23 may display the form data on an output image confirmation screen, allowing the user who has confirmed the form data to modify or add to the form data.

[0124] Fig. 27 is a flowchart showing an outline of the flow of the form generation and output process (with back side reading instruction) according to this embodiment. The flowchart shown in Fig. 27 is a flowchart in which a process for issuing a back side reading instruction has been added to the flowchart shown in Fig. 26. In other words, it is a flowchart including a process for issuing a back side reading instruction after a reading process for the front side has been executed according to a single side (front side) reading setting. Among the processes shown in Fig. 27, the processes given the same numbers as those in Fig. 26 are the same as those explained above, and therefore will not be explained again.

[0125] In step S1, it is determined whether or not reading of the back side of the identification card is necessary. For each document item defined in the document form selected in step S301, the collation unit 29 compares the expression method condition for the document item with the expression method for the record item corresponding to the document item defined for the type of identification card acquired in step S303. For example, the collation unit 29 compares the expression method condition "describe image" for "preliminary address change" with the expression method "back side (handwritten)" for "preliminary address change" defined for the type of identification card acquired in step S303 (e.g., driver's license). In this case, the collation unit 29 determines that additional reading of the back side of the presented identification card (reading of the back side) is necessary because an image related to the preliminary address change needs to be written on the document. In this way, if it is determined that reading of the back side is necessary (Yes in step S1), the process proceeds to step S2. On the other hand, if it is determined that reading of the back side is not necessary (No in step S1), the process proceeds to step S305.

[0126] In step S2, an instruction to read the back side of the identification card is issued. The collation unit 29 issues an additional reading instruction (an instruction to read the back side (an image acquisition instruction)) for the identification card to the reading unit 81. After that, the process returns to step S302.

[0127] Note that step S1 may be performed between steps S303 and S304. After the process of step S302 is performed after step S2, step S303 may be omitted and the process of step S304 may be performed. As described above, by checking the medium definition against the writing conditions, it is possible to give additional reading instructions when necessary information is written on the back side.

[0128] Fig. 28 is a flowchart showing an outline of the flow of the form selection process according to this embodiment. This flowchart is a flowchart showing the details of the process of step S301 shown in Fig. 26. The process shown in this flowchart is started when the information processing device 1 receives an instruction to create and output a form from a user (such as a user of the form generation system). The process shown in this flowchart may be executed by the user performing various operations on the form selection screen (see Figs. 18 and 19) displayed by the display control unit 23.

[0129] In step S401, a use element of category 1 of the form list is acquired. The display control unit 23 acquires all use elements stored for category 1 from the form list storage unit 262. After that, the process proceeds to step S402.

[0130] In step S402, the purpose elements of category 1 are displayed. The display control unit 23 displays all the purpose elements of category 1 acquired in step S401 on the form selection screen (see FIG. 18). After that, the process proceeds to step S403.

[0131] In step S403, a selection of a use element of category 1 is accepted. The use selection accepting unit 271 accepts the selection of a use element of category 1 by the user selecting one use element from the use elements of category 1 displayed in step S402. After that, the process proceeds to step S404.

[0132] In step S404, it is determined whether or not there is a use element of category 2 linked to the use element of category 1 selected in step S403. The display control unit 23 determines whether or not there is a use element of category 2 corresponding to the use element by referring to the form list stored in the form list storage unit 262 based on the use element of category 1 selected in step S403. If there is no corresponding use element of category 2 (No in step S404), the process proceeds to step S405. On the other hand, if there is a corresponding use element of category 2 (Yes in step S404), the process proceeds to step S406.

[0133] In step S405, a form is acquired (selected). The selection unit 272 acquires (selects) one or more form associated with the purpose element of category 1 selected in step S403. For example, in the data shown in FIG. 13 (data held by the form list storage unit 262), a form corresponding to the form name associated with the purpose element of category 1 is acquired from the form storage unit 261. For example, when the purpose element "seal certificate" of category 1 is selected in step S403, the selection unit 272 acquires the form "seal certificate" associated with the purpose element (see FIG. 13). Note that in step S405, a screen for selecting category 2 is not displayed, but as described above, a screen (message) prompting the user to confirm may be displayed. After that, the process proceeds to step S410.

[0134] In step S406, a use element of category 2 of the form list is acquired. The display control unit 23 acquires all use elements of category 2 linked to the use element of category 1 selected in step S403 from the form list storage unit 262. After that, the process proceeds to step S407.

[0135] In step S407, the purpose elements of category 2 are displayed. The display control unit 23 displays the purpose elements of category 2 acquired in step S406 on the form selection screen (see FIG. 19). After that, the process proceeds to step S408.

[0136] In step S408, the selection of a usage element of category 2 is accepted. The usage selection accepting unit 271 accepts the selection of the usage element of category 2 by the user selecting one or more usage elements from the usage elements of category 2 displayed in step S407. Then, the process proceeds to step S409.

[0137] In step S409, a form is acquired (selected). The selection unit 272 acquires (selects) one or more form forms associated with the use element of category 2 (lowest layer) selected in step S408. For example, in the data shown in FIG. 13, the selection unit 272 acquires from the form storage unit 261 a form corresponding to the form name associated with the use element of category 2. For example, when the use element "Application for Resident's Certificate" of category 1 is selected in step S403 and the use element "For the person" of category 2 is selected in step S408, the selection unit 272 acquires "Application for Resident's Certificate (Person)" and "Application for Resident's Certificate (Common Back)" which are form forms associated with the use elements (see FIG. 13). When the use element of category 2, which is the lowest layer, is selected, the screen transitions from the screen shown in FIG. 19 to the screen shown in FIG. 18. After that, the process proceeds to step S410.

[0138] In step S410, it is determined whether the selection of the purpose is complete. The form selection unit 27 determines whether all the purposes desired by the user (purposes that the user wants to use) have been selected. For example, when the "Next" button is pressed by the user on the form selection screen shown in FIG. 18, the form selection unit 27 determines that the selection of the purpose is complete. In this way, when it is determined that the selection of the purpose is complete (YES in step S410), the process shown in this flowchart ends. On the other hand, when it is determined that the selection of the purpose is not complete (No in step S410), the process returns to step S403, and the selection of the purpose that has not been selected is performed. Note that the form may be selected after all the purposes have been selected.

[0139] FIG. 29 is a flowchart showing an outline of the flow of the form generation process according to this embodiment. This flowchart is a flowchart showing the details of the process of step S305 shown in FIG. 26. The process shown in this flowchart is started when the process of step S304 shown in FIG. 26 ends. If multiple form forms are selected in step S301, the process shown in this flowchart is performed for each selected form. In the following explanation, one of the form forms selected in step S301 is described as form A. It is assumed that form A has the item definitions shown in FIG. 12.

[0140] In steps S501 and S502, area information and condition information for the form items defined in the form A are acquired. The collation unit 29 acquires area information for one of the form items defined in the form A (step S501), and acquires condition information for the form item (step S502). Here, for field 2 (item type "address"), an example is shown in which area information "x2, y2, w2, h2" and, as condition information, a filling condition of "all", a representation method condition of "complement prefecture", and an area condition of "none" are acquired. After that, the process proceeds to step S503.

[0141] In step S503, information (medium information) related to the form item is acquired. The collation unit 29 acquires medium information related to the form item related to the area information and condition information acquired in steps S501 and S502. For example, for the item types "name", "address", "preliminary address change" and "date of birth" (fields 1 to 4), the user information read for the record item corresponding to the item type (in the case of case 1) or the expression method of the record item corresponding to the form item defined for the type of the read identification card (in the case of case 2) is acquired as the medium information. For example, when the method of case 1 is used, the collation unit 29 acquires "CCCCCCC", which is the user information (input information) for the record item "address" acquired in step S304 of FIG. 26, as the medium information related (corresponding) to field 2 (item type "address") shown in FIG. 12. Also, for example, when the method of Case 2 is used, the expression method for "address" defined for the type of identification (for example, "passport") that has been read, "prefecture only", is acquired as the medium information.

[0142] For the item type "static characters" (field 7), the type of identification obtained in step S303 in FIG. 26 is acquired as the medium information. For the item type "static characters" (field 8), the result of the identity verification performed in step S302 in FIG. 26 is acquired as the medium information. For the item type "number" (field 9), the input information related to the number and the type of identification obtained in step S303 in FIG. 26 are acquired as the medium information. For the item type "static characters" (field 6), there is no condition for writing, and fixed characters are input, so no information is acquired in step S503. For the item type "creation date and time", the date and time information when the form was created is acquired instead of the medium information. After that, the process proceeds to step S504.

[0143] In step S504, it is determined whether a condition is specified. The collation unit 29 determines whether a condition is specified by referring to the condition information acquired in step S502. In this embodiment, when a condition is not specified in either the expression method condition or the description condition, it is determined that a condition is not specified. For example, when the description condition is "all (all identification cards)" in the condition information (description condition) and the expression method condition is "no condition", it is determined that a condition is not specified. In the example of FIG. 12, it is determined that a condition is not specified for the item type "name". When it is determined that a condition is not specified (No in step S504), the process proceeds to step S505. On the other hand, when it is determined that a condition is specified (Yes in step S504), the process proceeds to step S506.

[0144] In step S505, the information is written in the designated area. The form generating unit 30 writes (places) the input information (user information, etc.) for the form item acquired in step S304 as it is as item data in the designated area (area indicated by the area information acquired in step S501) of the underlay data (copied underlay data). In the above example, in the case of the item type "name", the input information "AA BB" for the item type "name" is written as it is in the writing area indicated by "x1, y1, w1, h1". For example, in the case of a My Number card or a driver's license, it is written as it is in kanji, and in the case of a residence card or a passport, it is written as it is in alphabet. In the case of a residence card, some kanji may be recorded, so in that case, the information is also written as it is. After that, the process proceeds to step S510.

[0145] In step S506, it is determined whether the conditions for writing are met. The collation unit 29 determines whether the conditions for writing are met by collating the condition information (conditions for writing) acquired in step S502 with the medium information acquired in step S503 (information indicating the type of identification acquired in step S303 of FIG. 26 and the result of the identity verification acquired in step S302) (Case 3 and Case 4 described above). For example, in the case of the item type "static characters" of the field 8 shown in FIG. 12, the condition for writing is "My Number Card", so if the identification read in step S302 is a My Number Card, it is determined that the writing condition is met, and if it is other than a My Number Card, it is determined that the writing condition is not met. In addition, if the condition for writing is "all", it is determined that the writing condition is met regardless of which identification is read.

[0146] Also, for example, in the case of the item type "number" of field 9 shown in FIG. 12, the condition for writing is "driver's license, residence card", so if the identification card read in step S302 is a driver's license or residence card, it is determined that the writing condition is met, and if it is other than a driver's license or residence card, it is determined that the writing condition is not met. Also, for example, in the case of the item type "static characters" of field 8 shown in FIG. 12, the condition for writing is "personal identification is NG", so if the personal identification result acquired in step S302 is NG, it is determined that the writing condition is met, and if the personal identification result is not NG, it is determined that the writing condition is not met. If it is determined that it is not met (No in step S506), the process proceeds to step S510. On the other hand, if it is determined that it is met (Yes in step S506), the process proceeds to step S507.

[0147] In step S507, it is determined whether or not the expression method of the input information (user information, etc.) for the form item needs to be changed. The collation unit 29 determines whether or not the expression method of the input information for the form item acquired in step S304 needs to be changed by collating the condition information (expression method condition) acquired in step S502 with the medium information acquired in step S503 (Case 1 and Case 2 described above).

[0148] As described above, the medium information to be compared with the expression method condition may be the read user information (Case 1) or the expression method of the record item corresponding to the form item defined for the type of the read identification card (Case 2). For example, when the method of Case 1 is adopted, the expression method condition "Complete prefecture" of the item type "Address" of Field 2 shown in FIG. 12 is compared with the user information "CCCCCCC" related to the read "Address". In this case, if it is determined that prefecture information is omitted in "CCCCCCC", it is determined that a change in the expression method (completion of prefecture information) is necessary. Also, for example, when the method of Case 2 is adopted, the expression method condition "Complete prefecture" of the item type "Address" of Field 2 shown in FIG. 12 is compared with the expression method "Prefecture only" for "Address" defined for the type of the read identification card (for example, "Passport"), and it is determined that a change in the expression method (completion of prefecture data) is not necessary.

[0149] If it is determined that the expression method needs to be changed (Yes in step S507), the process proceeds to step S508. On the other hand, if it is determined that the expression method does not need to be changed (No in step S507), the process proceeds to step S509. Note that in the case of form items that contain static characters (fields 6 to 8 in FIG. 12), it is clear from the item type and expression method conditions that these are items that contain static characters, so it is determined that the expression method of information does not need to be changed without performing the above-mentioned comparison, and the process proceeds to step S509.

[0150] In step S508, the expression method of the input information is changed (condition processing) and then written (placed) in the designated area. The form generation unit 30 changes the expression method of the input information for the form item acquired in step S304 to match the condition information (expression method condition) acquired in step S502. Then, the form generation unit 30 writes (places) the input information (item data) whose expression method has been changed in the designated area (area indicated by the area information acquired in step S501) of the underlying data (copied underlying data). Then, the process proceeds to step S510. For example, the input information of the item type "Address" is supplemented with prefecture information and then written in the designated area. Then, the process proceeds to step S510.

[0151] In step S509, the information is written in the designated area. The form generating unit 30 writes (places) the input information for the form item acquired in step S304 as it is as item data in the designated area (area indicated by the area information acquired in step S501) of the underlay data (copied underlay data). For example, in the above example, if the input information "CCCCCCC" for "Address" includes prefecture information, the input information "CCCCCCC" is written in the designated area without data complementation. In addition, in the case of a form item that writes static characters (fields 6 to 8 in FIG. 12), the static characters (for example, "◯" or "※") specified in the expression method condition are written in the designated area. After that, the process proceeds to step S510.

[0152] In step S510, it is determined whether the processing has been completed for all the form items. The collation unit 29 determines whether the processing of steps S501 to S509 has been completed for all the form items defined in the form A. If it is determined that the processing has not been completed for all the form items (No in step S510), the process returns to step S501, and processing is performed for form items for which processing has not yet been completed (form items in other fields). On the other hand, if it is determined that the processing has been completed for all the form items (Yes in step S510), the form generation unit 30 generates form data in which data is placed in each field, and the process shown in this flowchart ends. Note that, although the process shown in this flowchart does not mention the process using the condition related to the area, the form generation unit 30 may perform a process of filling in the background by referring to the condition related to the area in steps S505, S509, S510, etc.

[0153] As described above, according to this embodiment, by changing the description content at the description position of the form item depending on the result of comparing the description conditions defined in the form form with the medium information, it is possible to easily create a form without being aware of the type of medium. In other words, according to this embodiment, by defining the description conditions in the form form, even if there is a difference between the expression method in the identification card and the rules (conditions) regarding the expression method in the form, it is possible to automatically generate a form in which the content required for the form form (read information, etc.) is described in an appropriate expression method. Therefore, the user can easily create a form without being aware of the type of identification card to be read (presented). In other words, according to this embodiment, by defining the description conditions, it is possible to provide a form creation method that is compatible with a plurality of identification cards.

[0154] Furthermore, according to this embodiment, since it is possible to accommodate a plurality of identification cards by defining the description conditions in the form, it is possible to reduce the effort of modifying or adding the form to accommodate a plurality of identification cards. Therefore, even if there are differences in the types of recorded items (recorded matters) and the expression method between types of identification cards, it is possible to easily generate (set) the form. In other words, even a user who is not familiar with identification cards can easily generate a form without being aware of the type of identification card (the recorded matters and expression method for each identification card).

[0155] Furthermore, according to this embodiment, by comparing the description conditions with the expression method defined in the medium definition for the type of identification card read, it is possible to determine whether the expression method of the information read from the identification card should be changed before writing it on the form. This makes it easy to determine whether the expression method of the information needs to be changed to match the form (form).

[0156] According to the present embodiment, the information read from the identification card or the information read after the expression method has been changed is automatically transcribed onto a form, so that a completed form can be created, thereby reducing the effort required for the user to handwrite or manually input information onto the form. Also, since the information read from the identification card or the information read after the expression method has been changed is automatically transcribed onto a form, it is possible to prevent typos and omissions that occur when a user writes information onto a form by hand, and as a result, it is possible to reduce the effort required to check the created form.

[0157] Furthermore, according to this embodiment, it is possible to generate a report form by selecting the location (area) to be printed on the underlying data (such as a captured image of an application form), and selecting the information to be printed (type of item) and the writing conditions, making it possible to easily create and modify report forms.

[0158] According to the present embodiment, the purpose of the user is associated with a document (document form) required for the purpose, and when the selection of the purpose is received from the user, one or more document forms associated with the selected purpose are selected as document forms suitable for the purpose, making it possible to easily select a document form. That is, by associating a purpose with a document form required for the purpose, it becomes possible to easily select a document form. According to the present embodiment, all document forms required for the purpose are stored in association with the purpose, so that when the purpose is selected by the user, all document forms required for the purpose can be selected (provided) without omission. For example, if a certified copy of a family register is required at the city hall, but an application is made by an agent, a power of attorney may be required in addition to the application documents for the certified copy of the family register. In such a case, the document forms for the application form for the certified copy of the family register and the power of attorney are stored in association with the purpose of the agent making the certified copy of the family register. As a result, when the agent selects the relevant purpose, not only the form for the family register copy application will be selected, but also the form for the power of attorney. In this way, by associating what the user wants to do (purpose) with one or more forms (forms) that suit the purpose, the user can use (select) the form that suits the purpose.

[0159] In addition, in this embodiment, since the purpose (form list) is defined in a hierarchical structure, the user can select what he or she wants to do hierarchically, making it easier to select the purpose. Also, by making the purpose (form list) into a hierarchical structure including a layer of purpose elements indicating the type of procedure and a layer of purpose elements indicating user attributes (attributes of the user who performs the procedure or the target of the procedure) located below the layer related to the type of procedure, it becomes possible to select (provide) different form forms when the user attributes are different even if the type of procedure is the same.

[0160] Furthermore, according to this embodiment, when it is desired to change the report form associated with a purpose or when it is desired to add a report form associated with a purpose, it is only necessary to change the correspondence relationship between the purpose and the report form, making it possible to easily change or add a report form associated with a purpose.

[0161] Furthermore, according to this embodiment, the user can easily and instantly create a completed application form by simply selecting the purpose (application type, etc.) and setting the identification card in the reading device 9. Also, according to this embodiment, by selecting multiple purposes, multiple form data (multiple application forms) can be created collectively, which saves the user who wants to create a form the trouble of creating multiple forms individually.

[0162] [Variation 1] In the above embodiment, an embodiment in which a form is selected by the user selecting a purpose (purpose element) has been described, but any method may be used to select a form. In this variation, an embodiment in which a user directly selects a form (form) without selecting a purpose will be described.

[0163] The system configuration and the functional configuration of the information processing device 1 in this variation are roughly the same as those shown in Fig. 1 and Fig. 2, respectively, and therefore description thereof will be omitted. However, in this variation, since the user directly selects the form form to be used to create the desired form, the information processing device 1 does not necessarily need to create and store a form list, and similarly, does not necessarily need to associate the purpose with the form form. Therefore, when a method other than the method of selecting a form form by selecting a purpose is used, as in this variation, the information processing device 1 does not necessarily need to include the form list generation unit 25, the form list storage unit 262, and the purpose selection reception unit 271.

[0164] Moreover, the form generation process, the form generation / output process, and the form creation process according to this variation are roughly similar to the processes shown in Figs. 24, 26 (Fig. 27), and 29, respectively, and therefore will not be described. Moreover, in this variation, the process shown in Fig. 25 (form list generation / association process) is not performed. Moreover, in this variation, the process shown in Fig. 28 is not performed as the form selection process. In this variation, in step S301 in Fig. 26, when the form selection unit 27 (selection unit 272) receives a form selection input from the user, it selects the form related to the selection input from among the form stored in the form storage unit 261.

[0165] In addition to the method of selecting a report form directly by the user, a method of selecting a report form that corresponds to the purpose selected by the user by associating a purpose that is not structured in a hierarchical structure with a report form may also be adopted.

[0166] [Variation 2] In the above embodiment, an embodiment was described in which a report form (see FIG. 12) with defined writing conditions is generated and the report form is used to create a report, but any report form may be used. In this variation, an embodiment is described in which a report form (report item definition) with no defined writing conditions is used. In addition, since the writing conditions are not defined in this variation, the above-mentioned process of matching the writing conditions with the medium information is not performed.

[0167] The system configuration and the functional configuration of the information processing device 1 in this variation are roughly the same as those shown in Fig. 1 and Fig. 2, respectively, and therefore a description thereof will be omitted. However, in this variation, the description conditions are not defined in the form, and the process of matching the description conditions with the medium information is not performed. Therefore, the information processing device 1 does not necessarily have to include the condition storage unit 21, the medium definition storage unit 22, and the matching unit 29.

[0168] In addition, the form generation process, form list generation and matching process, form generation and output process, and form selection process according to this variation are roughly the same as those shown in FIG. 24, FIG. 25, FIG. 26 (FIG. 27), and FIG. 28, respectively, and therefore the description will be omitted. However, in this variation, since the description conditions are not defined in the form, the process of step S104 in FIG. 24 is not performed (omitted). In addition, in this variation, the process shown in FIG. 29 is not performed as the form generation process. In this variation, in step S305 in FIG. 26, the form generation unit 30 generates a form (form data) in which item data (user information acquired in step S304, etc.) for the form item in the form selected in step S301 is written in the description area defined in the form. An example of the form according to this variation is shown below, but any form form can be adopted in this variation.

[0169] Fig. 30 shows an example of a form (item definition) according to this variation. As shown in Fig. 30, the form in this variation does not define writing conditions. In the form shown in Fig. 30, writing areas (item data writing areas) corresponding to each of a plurality of identification documents are defined for each type of form item (item type). Even for the same form item (item type), the form may be defined so that the writing areas differ depending on the type of identification document read. [Explanation of symbols]

[0170] 1. Information processing device

Claims

1. A computer, a form storage means for storing a form that defines a form format and a purpose in association with the form; a use selection receiving means for receiving the selection of the use; a selection means for selecting a form corresponding to the selected purpose from among the form forms stored in the form storage means; a form generating unit that generates form data containing data by arranging the data in the selected form, The data entry position differs between multiple forms with different uses, the form generation means generates the form data in which the data is entered at the entry position according to the selected purpose using the form corresponding to the selected purpose. Information processing program.

2. causing the computer to further function as a data acquisition unit that acquires the data to be arranged on the form; the form generation means generates the form data by arranging the data in the selected form. The information processing program according to claim 1 .

3. the data acquisition means acquires, as the data, information relating to the user read by a reading means that reads a medium on which information relating to the user is recorded; The information processing program according to claim 2 .

4. the form storage means stores at least one of the uses in association with a plurality of the form formats; The information processing program according to claim 1 .

5. The application is configured in a hierarchical structure including a top layer and a bottom layer, the plurality of form sheets corresponding to a plurality of uses having common use elements in layers above the lowest layer of the hierarchical structure and different use elements in the lowest layer are configured so that the data is written at different positions on a common layout, Common underlying data is used as the common layout. The information processing program according to claim 1 .

6. the application is one of a plurality of applications, the purpose selection receiving means receives a selection of the plurality of purposes, the selection means selects a plurality of form sheets corresponding to the selected plurality of uses from among the form sheets stored in the form storage means; the form generation means generates a plurality of form data by arranging the data in the plurality of selected form forms; The information processing program according to claim 1 .

7. causing the computer to further function as a data acquisition unit that acquires the data to be arranged on the form; the form generation means generates the plurality of form data by arranging the data in the plurality of form forms corresponding to the plurality of selected uses. The information processing program according to claim 6.

8. The application is configured in a hierarchical structure including a top layer and a bottom layer, The hierarchical structure is a layer of usage elements that indicate the type of procedure; A layer of usage elements indicating attributes of a user who performs the procedure or a target of the procedure, located below the layer related to the type of procedure, The information processing program according to claim 1 .

9. the form defines, for each of a plurality of form items in the form, the position at which item data is to be written and a description condition for the item data to be written at the position; The computer is further caused to function as a comparison unit that compares the description conditions related to the form items defined in the selected form with medium information, which is information related to the form items and is obtained based on a medium to be read on which information is recorded; the form generation means generates the form data in which the item data is entered at the entry position of the form item based on the result of the collation. The information processing program according to claim 1 .

10. A computer having a form storage means for storing a form that defines a form format in association with an application, a use selection receiving step of receiving the selection of the use; a selection step of selecting a form corresponding to the selected purpose from among the form forms stored in the form storage means; a form generating step of generating form data containing the data by arranging the data in the selected form, The data entry position differs between multiple forms with different uses, In the form generation step, the form data is generated in which the data is written in the writing position corresponding to the selected purpose using the form corresponding to the purpose. Information processing methods.

11. A form storage means for storing a form that defines the format of a form in association with an application; a use selection receiving means for receiving the selection of the use; a selection means for selecting a form corresponding to the selected purpose from among the form forms stored in the form storage means; and form generation means for generating form data containing data by arranging the data in the selected form, The data entry position differs between multiple forms with different uses, the form generation means generates the form data in which the data is entered at the entry position according to the selected purpose using the form corresponding to the selected purpose. Information processing system.

Images