JP6441773B2 - ID management system and ID management method - Google Patents

Description

  The present invention relates to an ID management system and an ID management method, and more particularly to an ID management system and an ID management method suitable for enhancing security when handling a form related to My Number.

  My Number is a 12-digit personal number assigned by the government to each citizen for the purpose of improving the efficiency and transparency of the social security and tax system. Notification of numbers, My number is scheduled to be used from January 2016 (Non-patent Document 1).

  Regarding this My Number System (Common Number System), it is assumed that private companies are affected by personnel, labor and salary operations. Under the My Number System, you must add a new My Number to documents that you have submitted to tax offices, municipal offices, pension offices, etc., as well as health insurance, welfare pension insurance, employment My number will also be listed on documents that report the acquisition or loss of insurance qualifications.

  Therefore, in addition to the employee numbers that have been handled so far, companies must write personal numbers in the My Number system in the forms.

  A system for converting IDs between systems is disclosed in Non-Patent Document 2, for example.

Cabinet Office Minister's Secretariat Government Public Relations Office, “Government Gazette Online Special Feature >> Social Security / Tax Number System <My Number>”, [online], [Search July 24, 2015], Internet <URL: http: // www.gov-online.go.jp/tokusyu/mynumber/ ＞ Hitachi, Ltd., “Hitachi ID Conversion System: Overview of Functions”, [online], [Search July 24, 2015], Internet <URL: http://www.hitachi.co.jp/Prod/comp/ app / cimms / composition.html>

  The personal number in the base of the My Number system is a number that identifies the individual, so damage to the company, such as the loss of corporate credit when the company is leaked or stolen, etc. ,unfathomable. Under the My Number Act, businesses must take various safety measures to perform appropriate management without leaking, losing or damaging personal numbers and specific personal information. There are many types of penalties and the punishment is heavy.

  The most common safety measures are personal number encryption and access control. Even in the system of Non-Patent Document 2, the ID conversion table is encrypted and stored.

  Like the above prior art, a technique related to encryption of a personal number that should be kept secret is widely used. However, once the operation of the My Number system is started, each company will be obliged to store the form with the personal number for a legal period. Each form is often printed and used as a paper medium or its image, and is stored. In this case, the personal number stored as digital data itself is printed with high security. There is a high risk that the assigned personal number will be seen by people, and security will be greatly reduced from the viewpoint of protecting personal information. Prior to the enforcement of the conventional My Number system, companies did not handle the forms listed in their personal numbers, so it was not considered to deal with such a situation.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide an ID management system corresponding to the My Number system and having improved security when handling a form related to My Number.

In order to achieve the above object, the ID management system according to the present invention has a tamper resistance in an ID management system that outputs a form with a first ID (personal number). An ID management unit that stores a second ID (employee number) in association with the second ID (employee number) is provided. Then, the form data including the second ID and not including the first ID is received,
Using the second ID of the received form data, obtain the first ID associated with this from the ID management unit, and output the obtained first ID and the form including the first ID from the form data Then, a form ID (form number) is assigned to the form to be output, and the form ID and the first ID included in the output form are associated with each other and stored in an ID management unit having tamper resistance.

  The first ID (personal number) is encrypted and stored, and decrypted when referenced.

  Another configuration of the ID management system of the present invention is to assign a form ID (form number) to a form including the first ID in an ID management system that outputs a form with a first ID (personal number). , The output ID information stored in the ID management unit having tamper resistance by associating the form ID with the first ID, and the output not stored in the ID management unit other than the ID management unit The form information including the first ID is received, the form data related to the form creation request is obtained from the output form information, and the form ID related to the form data is used to obtain the form data. The first ID stored in association with the ID is acquired from the output ID information, and the form including the first ID is output from the acquired form data and the first ID. is there.

  According to the present invention, it is possible to provide an ID management system corresponding to the My Number system and having improved security when handling a form related to My Number.

It is a schematic diagram of the submitting company of the form which operates ID management system, and an external organization of a submitting destination. It is a data flow figure regarding a form of a form creation system, an ID management system, and a submission destination external organization. It is a functional block diagram of ID management system. It is a hardware block diagram of ID management system server. It is a figure which shows an example of a form information table. It is a figure which shows an example of a form. It is a figure which shows an example of an employee master table. It is a figure which shows an example of a person in charge table. It is a figure which shows an example of an employee number-personal number conversion table. It is a figure which shows an example of a form number-personal number conversion table. It is a figure which shows an example of ID log. FIG. 10 is a sequence diagram illustrating a process from creating a form including a personal number to submitting a form to a submission destination external organization. FIG. 10 is a sequence diagram for explaining processing from browsing a form including a personal number to resubmission to a destination external organization. FIG. 11 is a sequence diagram for explaining processing until a form that does not include a personal number is browsed.

  Hereinafter, an embodiment according to the present invention will be described with reference to FIGS.

  In the present embodiment, an example will be described in which a certain company creates a form relating to an employee and submits the form to a submission destination external organization. It is assumed that the form submitted to the external organization to be submitted contains the employee's personal number. For example, the company is a corporation such as a corporation with tax obligations, the personal number is the My Number in the My Number System, and the external organization to be submitted is a tax office.

  First, the configuration of an ID management system according to an embodiment of the present invention will be described with reference to FIGS. FIG. 1 is a schematic diagram of a form submitting company and a submitting external organization that operate an ID management system. FIG. 2 is a data flow diagram relating to a form creation system, an ID management system, and a form of a destination external organization. FIG. 3 is a functional configuration diagram of the ID management system. FIG. 4 is a hardware configuration diagram of the ID management system server.

  In the present embodiment, as shown in FIG. 1, an example will be described in which a form submitting company 1 submits a form including a personal number to a submitting external organization 800. The submitting company 1 includes a form creation system 300 and an ID management system 10, and includes an operation terminal 50 connected to the form creation system 300 and a printer 60 connected to the operation terminal 50.

  The form creation system 300 is a system for creating forms relating to business such as personnel, accounting, and product handling in a company. Here, it is assumed that the form 20 created by the form creation system 300 does not include a personal number.

  The ID management system 10 includes two components, a front-end system 100 and an ID management unit 20 ring. The ID management system 10 inputs a form 20 without a personal number created by the form creation system 300, and creates a form 30 including a personal number. Output. The front-end system 100 is a system that accepts the form 20 from the form creation system 300 and processes it. The ID management unit is a subroutine called from the form creation system 300 for processing related to the personal number, and manages information related to the personal number.

  The form creation system 300 and the ID management system may be realized by each hardware device connected via a network as shown in FIG. 1 or may be realized by a single hardware device.

  The submitting company 1 mails a paper form to the submission destination or submits the form 30 including the personal number to the submission destination external organization 800 as data stored in the storage medium. Further, if the data flowing through the communication path is encrypted and sufficient security strength is ensured, the form 30 including the personal number may be submitted via the network.

  Next, an example in which a form including a personal number is submitted to an external submitting organization will be described with reference to FIG.

  Here, the form creation system 300 of the submitting company 1 creates a form including the employee number, and the ID management system 10 adds the employee's personal number of the employee number to the external submission organization 800. Shall be submitted. When a form including an employee number is input to the front-end system 100 of the ID management system 10, the front-end system 100 inquires of the ID management unit 200 about the personal number corresponding to the employee number and obtains the personal number. Create a report that contains it. The ID management unit 200 holds the correspondence information between the encrypted employee number and personal number (details will be described later). When the front-end system 100 creates a form including a personal number, it issues a form number for managing the form, and the ID management unit 200 encrypts and holds the correspondence between the form number and the personal number ( Details will be described later). The correspondence between the form number and the personal number is used when a form including the personal number is viewed or resubmitted. In this model, all information including the personal number is encrypted, and the form including the personal number is not held as data, so security is ensured.

  Next, the functional configuration of the ID management unit will be described with reference to FIG.

  As illustrated in FIG. 3, the ID management unit 200 includes a front-end system 100 and an ID management unit 200 as functional configurations, each of which includes a processing calculation unit 110, a storage unit 120, a processing calculation unit 210, and a storage. Part 220.

  The processing operation unit 110 of the front-end system 100 is a part that realizes processing in the front-end system 100, and includes a form composition unit 112, an output unit 114, and an authentication unit 116. The form composition unit 112 is a part that creates a form to which a personal number is added. The output unit 114 is a part that outputs a form to the screen or prints it on the printer 60. The authentication unit 116 is a part that checks the access authority of the person in charge for the form and gives access permission.

  The storage unit 120 of the front-end system 100 stores various data related to the front-end system 100, that is, a form information table 122, an employee master table 124, a person-in-charge table 126, and an operation log 128. Each data will be described in detail later.

  The processing operation unit 210 of the ID management unit 200 is a part that realizes processing in the ID management unit 200, and includes an ID conversion unit 212, an encryption / decryption unit 214, and an ID log management unit 216. The ID conversion unit 212 is a part that mutually converts employee numbers and personal numbers. The encryption / decryption unit 214 is a part that encrypts / decrypts data related to the personal number. The ID log management unit 216 is a part that records or refers to an access log related to an ID.

  The storage unit 220 of the ID management unit 200 stores various data related to the ID management unit 200, that is, an employee number-personal number conversion table 222, a form number-personal number conversion table 224, and an ID log 226. Each data will be described in detail later.

  The employee number-personal number conversion table 222 and the form number-personal number conversion table 224, which are tables including personal numbers of the ID management unit 200, are encrypted and stored with tamper resistance. However, the form information table 122, the employee master table 124, the person-in-charge table 126, and the operation log 128 of the front-end system 100 are not necessarily encrypted, and the storage medium of the ID management unit 200 It is also possible to use another storage medium.

  Next, the hardware configuration of the ID management system will be described with reference to FIG.

  The ID management system is realized by an ID management system server 400 shown in FIG. As shown in FIG. 4, the hardware configuration of the ID management system server 400 includes a CPU (Central Processing Unit) 402, a main storage device 404, a network I / F 406, a display I / F 408, an input / output I / F 440, and an auxiliary storage. The I / F 412 is connected by a bus.

  The CPU 402 controls each unit of the ID management system server terminal 400 and loads and executes a necessary program in the main storage device 404. The main storage device 404 is generally composed of a volatile memory such as a RAM, and stores a program executed by the CPU 402 and data to be referred to. A network I / F 406 is an interface for connecting to a network. A display I / F 408 is an interface for connecting a display device 420 such as an LCD (Liquid Crystal Display).

  The input / output I / F 410 is an interface for connecting an input / output device. In the example of FIG. 4, a keyboard 430 and a pointing device mouse 432 are connected.

  The auxiliary storage I / F 412 is an interface for connecting an auxiliary storage device such as an HDD (Hard Disk Drive) 450 or an SSD (Solid State Drive).

  The HDD 450 has a large storage capacity, and stores a program for executing this embodiment and database tables. The HDD 450 may be connected on the array to form a disk array. In the ID management system server 400, a front end program 500 and an ID management program 600 are installed in the HDD 450.

  The front end program 500 includes a form synthesis module 512, an output module 514, and an authentication module 516 as subprograms. The form synthesis module 512, the output module 514, and the authentication module 516 are modules that implement the functions of the form synthesis unit 112, the output unit 114, and the authentication unit 116 described with reference to FIG.

  The ID management program 600 includes an ID conversion module 612, an encryption / decryption module 614, and an ID log management module 616 as subprograms. The ID conversion module 612, the encryption / decryption module 614, and the ID log management module 616 are executed by the CPU 402, and thereby the ID conversion unit 212, the encryption / decryption unit 214, and the ID log management unit 216 described with reference to FIG. It is a module that realizes the function.

  The HDD 450 stores a front-end system DB (Data Base) 520 accessed from the front-end program 500 and an ID management DB 620 accessed from the ID management program 600.

  The front-end system DB 520 holds a form information table 122, an employee master table 124, a person-in-charge table 126, and an operation log 128.

  The ID management DB 620 holds an employee number-personal number conversion table 222, a form number-personal number conversion table 224, and ID logs 226, 228.

  Next, a data structure used in the ID management system will be described with reference to FIGS. FIG. 5 is a diagram illustrating an example of a form information table. FIG. 6 is a diagram illustrating an example of a form. FIG. 7 is a diagram illustrating an example of the employee master table. FIG. 8 is a diagram illustrating an example of a person-in-charge table. FIG. 9 is a diagram illustrating an example of an employee number-personal number conversion table. FIG. 10 is a diagram showing an example of a form number-personal number conversion table. FIG. 11 is a diagram illustrating an example of an ID log.

  The form information table 122 is a table for holding information related to forms, and includes fields of form number 122a, form type 122b, form data 122c, and display / print template 122d, as shown in FIG.

  The form number 122a stores a unique number for identifying the form. The form type 122b stores the type of the form. In the example of FIG. 5, “withholding table” and “invoice” are stored as examples. The form data 122c stores data corresponding to the type of each form. Since the form data has a variable format depending on the type of form, a pointer to the data may be stored. The display / print template 122d stores information representing template data for display / printing.

  The form used in the present embodiment is, for example, a withholding table as shown in FIG. Here, FIG. 6A shows a form (form A) in which the personal number is not displayed, and FIG. 6B shows a form (form B) in which the personal number is displayed. .

  The employee master table 124 is a master table for storing information about employees. As shown in FIG. 7, the employee number 124a, name 124b, gender 124c, date of birth 124d, support 124f, affiliation 124g, job title Each field includes 124h and retirement date 124i.

  The employee number 124a stores a unique number for identifying the employee. In addition, as information on the employee, it may be necessary to include information on the dependent family for tax purposes, so information on the employee's family is included as well as those who have an employment relationship with the company. In this example, it is assumed that the employee number 124a is in the format of upper 5 digits + 3 digits, the lower 3 digits are branch numbers related to the family, and the person “000”, the spouse “001”, and the like are recorded. The name 124b, gender 124c, date of birth 124d, and address 124e store the name, gender, and date of birth of the employee, respectively. The date of birth 124d is assumed to be stored in the format of MM month DD day in YYYY (YYYY is the year of the year, MM is the month, DD is the date). The dependent 124 f stores a flag indicating the presence or absence of the dependent family. The affiliation 124g and the post 124h store the affiliation and post (if any) of the employee in the company. The retirement date 124i is the date when the employee retires, and is blank before retirement. The retirement date 124i is stored in the same format as the date of birth 124d.

  The retirement date 124i is determined by the company's internal regulations when the employee retires, for example, the employee's data (especially data associated with a personal number, employee number-personal number correspondence described later) within the retirement half year. It is referred to when a table etc. must be deleted.

  The person-in-charge table 126 is a table for storing information on persons in charge who access the form, and has fields of person-in-charge number 126a, person-in-charge name 126b, and access authority 126c as shown in FIG.

  The person-in-charge number 126a stores a unique number for identifying the person in charge who accesses the form. The name of the person in charge 126b stores the name of the person in charge. The access authority 126c stores access authority such as creation and browsing for each form of the person in charge. In the example shown in FIG. 8, the access authority of the person in charge with the person in charge number “004” and the person in charge name “□ ▽ ▽ husband” has the authority to “create concerning personnel and accounting forms”. Yes.

  The employee number-personal number conversion table 222 is a table showing correspondence between employee numbers and personal numbers, and has fields of an employee number 222a and a personal number 222b as shown in FIG.

  Since the employee number-personal number conversion table 222 includes a personal number, when the data is stored, it is encrypted and read by the encryption / decryption unit shown in FIG. Note that it is decrypted.

  The personal number 222b is a legal 12-digit number in the case of My Number.

  The form number-personal number conversion table 224 is a table showing correspondence between form numbers and personal numbers, and has fields of form number 224a and personal number 224b as shown in FIG.

  Since the form number-personal number conversion table 224 includes a personal number, when the data is stored, it is encrypted and read by the encryption / decryption unit 224 shown in FIG. Note that it is decrypted.

  When each form with a personal number is issued, the form number is issued and stored in the form number 112a field of the form information table 122 and the form number 224a field of the form number-personal number conversion table 224 (described later). .

  The ID log is an access record related to the personal number, and as shown in FIG. 11, there is a form creation ID log 226 and a browsing ID log 228.

  The form creation ID log 226 is an access record created when working on the personal number required for form creation. As shown in FIG. 11A, the employee number 226a, work type, 226b, work date and time 226c, and person-in-charge number 226d.

  The employee number 226a stores an employee number related to ID creation work. The work type 226b stores work types such as employee number and personal number registration, employee number and personal number discard, and employee ID to personal number ID conversion. The work date and time 226c stores the date and time when the work was performed. The person in charge number 226d stores the number of the person in charge who performed the work.

  The browsing ID log 228 is an access record created when browsing a form related to a personal number. As shown in FIG. 11B, each field of the form number 228a, the ID conversion date 228b, and the person-in-charge number 226d. Have

  In the form number 228a, a form number related to the viewed personal number is stored. The conversion date and time 228b stores the date and time when the personal number was converted from the form number. The person-in-charge number 226d stores the number of the person in charge who performed the browsing work.

  Next, processing of the ID management system according to an embodiment of the present invention will be described with reference to FIGS. FIG. 12 is a sequence diagram for explaining a process from creation of a form including a personal number to submission to a submission destination external organization. FIG. 13 is a sequence diagram illustrating a process from browsing a form including a personal number to resubmission to a submission destination external organization. FIG. 14 is a sequence diagram for explaining processing up to browsing a form that does not include a personal number.

  In the following explanation and figure notation, the form created by the form creation system without the personal number added is referred to as “form A”, and the personal number is added to the “form A” by the following predetermined operation. The form is “form B”.

  First, with reference to FIG. 12, a process for creating a form A, creating a form B based on the data, and submitting the form B to a destination external organization will be described.

  First, a form A is created by the form creation system (S01). This is, for example, a withholding table that does not include a personal number as shown in FIG.

  Next, in order to create the form B with the personal number added to the form A, the person in charge logs in from the operation terminal 50 (S02), and instructs the front end system 100 to create the form with the personal number. (A01).

  The front-end system 100 refers to the person-in-charge table 126 in FIG. 8, and when the person in charge has access authority to create a form (S03), the form information created by the form creation system 300 is accessed (A02). It takes in the form information table shown in FIG. 5 (A03).

  Then, the front-end system 100 inquires the personal number using the employee number as a key (A04). The ID management unit 200 refers to the employee number-personal number correspondence table 222 in FIG. 9 and returns the personal number to the front-end system 100 (A05).

  Next, the front end system 100 creates a form B to which the personal number is added based on the personal number, and transmits it to the operation terminal 50 (A06).

  The person in charge confirms the contents by displaying the form B on the display device or printing it on the printer 60 (S06), and if it is appropriate, instructs the front-end system 100 to output (A07). . When necessary, the form B is sent to the submission destination external organization 800 by means of mail or network transmission, and the submission destination external organization 800 performs reception processing (S09).

  When the form B is created, a form number corresponding to the form B is generated (S07), and the form number and a personal number related to the form B are transmitted to the ID management unit 200 (A09).

  The ID management unit 200 associates the form number with the personal number, encrypts it, and stores it in the form number-personal number correspondence table shown in FIG.

  In this series of sequences, it is noted that the form B to which the personal number is added is not stored in the system, and only the form number is saved.

  Next, a process for re-creating a form to which a personal number that has been previously submitted to the submission destination external organization and adding it to the submission destination external organization will be described with reference to FIG.

  First, the person in charge logs in from the operation terminal 50 (S10), and makes a browsing request to the front end system 100 using the form number as a key (A20).

  The front-end system 100 refers to the person-in-charge table 126 in FIG. 8, and when the person in charge has access authority to create a form (S11), the form information is accessed (S12) and the form number that has been transmitted Is used as a key (A21), and the ID management unit 200 is inquired for the personal number. The ID management unit 200 refers to the form number-personal number correspondence table 224 in FIG. 10 and returns the personal number to the front-end system 100 (A22).

  Next, the front end system 100 creates a form B to which the personal number is added based on the personal number, and transmits it to the operation terminal 50 (A23).

  The person in charge checks the contents by displaying the form B on the display device or printing it on the printer 60 (S15), and when it is determined to be appropriate, instructs the front-end system 100 to output it (A24). ).

  Then, the form B is sent to the submission destination external organization 800 by means of mail or network transmission, and the submission destination external organization 800 performs re-acceptance processing (S16).

  As described with reference to FIG. 12, in the ID management system of the present embodiment, the form B to which the personal number is added is not stored, so that the personal number is assigned using the form number as a key as described above. Search and recreate it. Since the table relating to the personal number is encrypted and stored, the security for the personal number can be improved by operating the system in this way.

  Next, processing until a person in charge who does not have access authority regarding a form including a personal number browses the form will be described with reference to FIG.

  The person in charge logs in from the operation terminal 50 (S30) and makes a browsing request to the front-end system 100 using the form number as a key (A01).

  In the front-end system 100, the person-in-charge table 126 in FIG. 8 is referred to, and the person in charge determines the access authority for creating the form (S03). When the person in charge does not have access authority for the form including the personal number, the front-end system 100 accesses the form information (S32), creates a form that does not include the personal number (S33), and performs the operation. The data is transmitted to the terminal 50 (A32), and the operation terminal 50 displays a form that does not include a personal number (A34).

  As described above, by providing the person in charge with the authority to access a form including a personal number, security for the personal number can be enhanced.

  In the above embodiment, when a form including a personal number such as My Number is handled by a company, the image file of the form including the personal number is not stored and is recreated as necessary. The personal number is stored in a tamper-resistant form by means such as encryption, so that the personal number can be prevented from leaking and security can be improved. In addition, when a form including a personal number is browsed and created, access to the person in charge can be granted to prevent unauthorized access to the personal number.

  Furthermore, since a personal number is not added to a log created when a form is viewed or created, the risk of personal information leaking from this log is also suppressed.

  1 ... Source company, 10 ID management system, 20 forms (no personal number), 30 forms (with personal number), 50 operation terminals, 60 printers, 100 front-end system, 200 ID management unit, 300 form creation system, 800 submission destination External agency.

Claims (10)

In an ID management system that outputs a form with a first ID,
An ID management unit having tamper resistance and storing the first ID and the second ID in association with each other;
Receiving the form data including the second ID and not including the first ID;
Using the second ID of the received form data, obtaining the first ID associated with the second ID from the ID management unit,
Based on the acquired first ID and the form data, a form including the first ID is output,
An ID management system, wherein the form ID of the form to be output and the first ID included in the form data to be output are associated with each other and stored in the ID management unit having tamper resistance. In claim 1,
An ID management system for storing form data that does not include the first ID with respect to the form to be output, together with the form ID, other than the ID management unit. In claim 1 or claim 2,
Accepting an instruction to create a form from the form data,
Obtain the form data and form ID for the instruction to create the form,
Obtaining the first ID stored in association with the form ID from the ID management unit;
An ID management system, wherein a form is created by attaching the first ID to the form data. In claims 1 to 3,
Accepting the ID of the requester who instructed to create the form, and determining the access authority of the requester;
If you have access to a form containing the first ID, output the form with the first ID,
An ID management system that outputs a form that does not include the first ID when the user does not have access authority to the form that includes the first ID. In any one of Claim 1 thru | or 4,
The ID management unit
The first ID is encrypted and stored, and when the ID associated with the first ID is input, the encrypted first ID is decrypted and output. ID management system. In claim 4 or claim 5,
An ID management system that creates and saves log information including an ID associated with the first ID without including the first ID when a form including the first ID is output. In an ID management system that outputs a form with a first ID,
An output ID information stored in a tamper-resistant ID management unit by assigning a form ID to the form including the first ID, associating the form ID with the first ID,
Output form information that stores a form that does not include the first ID other than the ID management unit;
With
Accept a request to create a form including the first ID,
Obtain the form data related to the form creation request from the output form information,
Using the form ID related to the form data, the first ID stored in association with the form ID is acquired from the output ID information,
An ID management system that outputs a form including the first ID from the acquired form data and the first ID. In any of claims 1 to 8,
Said 1st ID is a personal number concerning a common number system, The ID management system characterized by the above-mentioned. In an ID management method of an ID management system that outputs a form with a first ID,
The ID management system has tamper resistance, and includes an ID management unit that stores the first ID and the second ID in association with each other,
The ID management system receiving form data including the second ID and not including the first ID;
The ID management system using the second ID of the received form data and acquiring the first ID associated with the second ID from the ID conversion unit;
Outputting the form including the first ID based on the obtained first ID and the form data;
Assigning a form ID to the output form data, associating the form ID with the first ID included in the output form data, and storing it in the ID management unit having tamper resistance; An ID management method comprising: In the management method of the ID management system that outputs the form with the first ID,
An output ID information stored in a tamper-resistant ID management unit by assigning a form ID to the form including the first ID, associating the form ID with the first ID,
Output form information that stores a form that does not include the first ID other than the ID management unit;
With
Receiving a creation request for a form including the first ID;
As a step of obtaining the form data concerning the form creation request from the output form information,
Using the form ID associated with the form data, obtaining the first ID stored in association with the form ID from the output ID information;
An ID management method comprising: outputting the form including the first ID from the acquired form data and the first ID.

Images