JP7506580B2 - Electronic application support device, electronic application support method, and electronic application support program - Google Patents

Description

The present invention relates to an electronic application support device, an electronic application support method, and an electronic application support program.

Traditionally, procedures related to social insurance and employment insurance have generally been carried out by submitting various application forms to the relevant government office. However, from April 2020, electronic application of some social insurance and employment insurance notification forms will become mandatory for certain corporations, and the shift to electronic application of procedures will accelerate significantly in the future.

To apply for social insurance or employment insurance online, it is necessary to use the e-Government comprehensive system (hereinafter referred to as "e-Gov"). Electronic applications and procedures can be inquired from the e-Gov website, but the function for inquiring about procedures is not user-friendly. For example, Patent Document 1 describes a system for inquiring about the status of an application on a public service website.

JP 2018-13940 A

However, the above-mentioned Patent Document 1 does not state anything about improving the efficiency of operations when querying application data that has been electronically submitted to a public service site.

The present invention has been made in consideration of the above, and aims to provide an electronic application support device, an electronic application support method, and an electronic application support program that can improve business efficiency when inquiring about application data that has been electronically submitted to a public service site.

In order to solve the above-mentioned problems and achieve the object, the present invention provides an electronic application support device that includes a memory unit and a control unit and is used to make electronic applications to public service sites via a network. The control unit is characterized by comprising: application means for storing transmission history data in the memory unit, including a transmission number, transmission date and time, the name of the person applying, and a procedure folder name, when an electronic application is made to the public service site; and application status inquiry means for acquiring a list of application statuses, including the transmission number, transmission date and time, arrival number, procedure name, procedure folder name, current status, number of official documents not yet obtained, and number of comments not yet obtained, as response results from the public service site, acquiring the name of the person applying from the transmission history data stored in the memory unit using the procedure folder name of the acquired response result as a key, and creating display data based on the acquired response result and the name of the person applying, and displaying it on an application status inquiry screen.

According to one aspect of the present invention, the application status inquiry means may create display data according to the set extraction conditions.

According to one aspect of the present invention, the extraction conditions may include at least one of the application status, the presence or absence of comments, the presence or absence of official documents, the type of procedure, and the sending date.

According to one aspect of the present invention, the application status inquiry means may download unobtained official documents or comments from the public service site in one go.

According to one aspect of the present invention, the procedure may be a social insurance or employment insurance procedure.

According to one aspect of the present invention, the public service site may be e-Gov.

In order to solve the above-mentioned problems and achieve the object, the present invention provides an electronic application support method to be executed by an information processing device having a memory unit and a control unit, and is characterized by including an application process executed by the control unit, in which, when an electronic application is made to the public service site, transmission history data including a transmission number, transmission date and time, the name of the application target, and a procedure folder name is stored in the memory unit, and an application status inquiry process is performed to obtain a list of application statuses including the transmission number, transmission date and time, arrival number, procedure name, procedure folder name, current status, number of unobtained official documents, and number of unobtained comments as response results from the public service site, obtain the name of the application target from the transmission history data stored in the memory unit using the procedure folder name of the obtained response result as a key, and create display data based on the obtained response result and the name of the application target, and display the data on an application status inquiry screen.

In order to solve the above-mentioned problems and achieve the object, the present invention is an electronic application support program to be executed by an information processing device having a memory unit and a control unit, characterized in that the electronic application support program executes the following steps: an application process executed by the control unit, in which, when an electronic application is made to the public service site, transmission history data including a transmission number, transmission date and time, the name of the person applying, and a procedure folder name is stored in the memory unit; and an application status inquiry process, in which, as a response result, a list of application status including the transmission number, transmission date and time, arrival number, procedure name, procedure folder name, current status, number of official documents not yet obtained, and number of comments not yet obtained is obtained from the public service site, the name of the person applying from the transmission history data stored in the memory unit using the procedure folder name of the obtained response result as a key, and display data based on the obtained response result and the name of the person applying is created and displayed on an application status inquiry screen.

The present invention has the effect of improving operational efficiency when querying application data submitted electronically to a public service site.

FIG. 1 is a diagram for explaining the procedure for inquiring about the status of a procedure from the e-Gov site. FIG. 2 is a diagram for explaining the procedure for inquiring about the status of a procedure from the e-Gov site. FIG. 3 is a diagram for explaining the procedure for inquiring about the status of a procedure from the e-Gov site. FIG. 4 is a diagram for explaining the procedure for inquiring about the status of a procedure from the e-Gov site. FIG. 5 is a block diagram showing an example of the configuration of an electronic application support device according to the present embodiment. FIG. 6 is a diagram showing the structure of employee information and transmission history data. FIG. 7 is a diagram for explaining an outline of the overall processing of the control unit of the electronic application support device in this embodiment. FIG. 8 is a diagram for explaining a specific example of the process of the control unit of the electronic application support apparatus in this embodiment. FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the electronic application support apparatus in this embodiment. FIG. 10 is a diagram for explaining a specific example of the process of the control unit of the electronic application support apparatus in this embodiment. FIG. 11 is a diagram for explaining a specific example of the process of the control unit of the electronic application support apparatus in this embodiment. FIG. 12 is a diagram for explaining a specific example of the process of the control unit of the electronic application support apparatus in this embodiment. FIG. 13 is a diagram for explaining a specific example of the process of the control unit of the electronic application support apparatus in this embodiment. FIG. 14 is a diagram for explaining a specific example of the process of the control unit of the electronic application support apparatus in this embodiment.

The embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Overview]
Traditionally, procedures related to social insurance and employment insurance have generally been carried out by submitting various application forms to the relevant government office. However, from April 2020, electronic application of certain social insurance and employment insurance notification forms will become mandatory for certain corporations, and the shift to electronic application of procedures will accelerate significantly in the future.

To apply for social insurance and employment insurance online, you need to use the e-Government comprehensive system (hereafter referred to as "e-Gov"). To apply for procedures through e-Gov, you need to install the e-Gov API (client application). You can apply online and inquire about procedures from the e-Gov website, but there are some issues with the procedure inquiry function.

When checking the application status of a procedure that has been applied for electronically, you can check the list of application cases by clicking on "transmission number" on the transmission case list screen. Here, e-Gov allows you to consolidate application data into a single file and send it. A transmission case refers to the data that is sent as a single file when applying electronically. A transmission number is a number that identifies a transmission case and is automatically assigned after transmission. An application case refers to each piece of application data included in a transmission case.

As it is not possible to set detailed extraction conditions for these two list functions, visibility is poor when applying for many procedures or for many employees. Specifically, many applications will be submitted around April, when many people join and leave the company. For example, it will be necessary to process employees who are leaving on March 31st, and employees who joined the company on April 1st, those returning from childcare leave (entering nursery school), those retiring at mandatory retirement age, transfer notifications, etc. In this way, the more people involved, the more difficult it becomes to manage the application status.

In addition, if there are any problems with the application, a comment file must be downloaded, and if the application is completed, an official document file must be downloaded, but these files cannot be downloaded together. In this case, the comment file is a file containing a return letter detailing any errors in the application data and other notices from the government office. The official document file is a document file issued by the government office, such as a copy of the application form, which is issued after the procedural review has been completed.

As such, downloading is required for each application (i.e., the number of employees), which can be very time-consuming when making a large number of applications. This reduces the efficiency of tasks such as (1) checking for missed submissions after application, (2) downloading comment files for those whose applications were incomplete, and (3) downloading official document files for those whose applications have been completed.

In this embodiment, we propose a mechanism to solve these problems and improve the work efficiency when checking application data submitted electronically to a public service site. Specifically, in this embodiment, (1) a mechanism that allows you to set extraction conditions when checking the application status, (2) a mechanism that allows you to download public documents in bulk, and (3) a mechanism that allows you to download comment files in bulk are constructed using the e-Gov API, thereby realizing work efficiency in the task of checking the application status.

This allows you to set various extraction conditions, such as the procedure name, applicant, submission date, and application status, improving the visibility of the application status list and making it easier to check for missed submissions. Furthermore, comment files and official document files can be downloaded all at once.

Figures 1 to 4 are diagrams for explaining the procedure for inquiring about the status of a procedure from the e-Gov site. Figure 1 is a diagram for explaining STEP 1 and Figure 2.

STEP 1: To check the status of the procedure you submitted electronically on e-Gov, first check the list of submitted cases.

STEP 2: Select the transmission number of the transmission you want to check the status of (see https://www.e-gov.go.jp/help/shinsei/manual/help704.html).

Here, the following issues arise:
(1) Because the name of the procedure is not displayed, you have to remember the date of submission, and if you apply for multiple procedures on the same day, it is difficult to tell which procedure was submitted.
(2) It is not clear whose applications are included in the submission. This can lead to missed or duplicate applications. When checking submissions, it is not possible to check on this list screen whether any applications have been missed.
(3) In order to hide all items other than the transmission item you want to check, you need to check all items you have sent in the past and hide them, which is inefficient.

Figure 2 is a diagram to explain STEP 3.

STEP 3: (If obtaining official documents or comments) Select an application from the list of applications.

Here, the following issues arise:
(1) The names of the people applying are not displayed. Therefore, in order to know who applied, you have to check each application one by one.
(2) For documents that are public, it is inefficient to have to search this screen for one or more documents that have not yet been obtained.
(3) It is not possible to download all unobtained official documents at once. For this reason, it is particularly troublesome to download official documents for the qualification acquisition notification that employees submit when they join the company. For example, if 100 people join the company, the operations from STEP 3 onwards must be repeated 100 times.

Figure 3 is a diagram to explain STEP 4.

STEP 4: Click the Official Documents and Comments List button.

Figure 5 is a diagram to explain STEP 5.

STEP 5: Click the Get button to download the official documents and comments.

The problem here is that each item must be retrieved one by one. This means that the destination folder must be selected each time. The more procedures and employees there are, the more inefficient this becomes.

In the following explanation, e-Gov will be used as an example of a public service site, but the present invention is not limited to this and can be applied to other services where names are not included in the results of inquiries about application status.

2. Configuration
An example of the configuration of an electronic application support device according to this embodiment will be described with reference to Fig. 5. Fig. 5 is a block diagram showing an example of the configuration of an electronic application support device 100 according to this embodiment. The electronic application support device 100 shown in Fig. 5 can be suitably used in, for example, a company or office (for example, an insurance office) that makes an electronic application to a public service site (for example, e-Gov).

The electronic application support device 100 may be, for example, a workstation or a personal computer. The electronic application support device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the electronic application support device 100 is connected to each other so as to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the electronic application support device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the electronic application support device 100 to the e-Gov 400 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114.

The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records computer programs for cooperating with an operating system (OS) to give instructions to a central processing unit (CPU) to perform various processes. As the storage unit 106, for example, a memory device such as a random access memory (RAM) or a read only memory (ROM), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc. can be used.

The storage unit 106 includes a data table 106a. The data table 106a is a file for storing various data such as employee information and transmission history data. Figure 6 shows the structure of the employee information and transmission history data.

Employee information may include data such as company number, employee code, and name, as shown in Figure 6.

Transmission history data is data on transmission history created when an electronic application is made, and may include SEQ, company number, transmission number, transmission date and time, employee code, name, procedure name, procedure folder name, and e-Gov submission destination identifier, as shown in Figure 6. Here, the procedure folder name refers to the name of the folder in which application data is sent, in which the data is organized into folders for each application form. For example, if qualification acquisition notifications are created for 100 people and sent in one go, the folder will become procedure folder x 100 (the name follows e-Gov specifications). The e-Gov submission destination identifier is a code representing the destination to which the application form is submitted, and is determined by e-Gov 400.

Returning to FIG. 5, the control unit 102 is a CPU or the like that provides overall control of the electronic application support device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. In terms of functional concept, the control unit 102 includes an application unit 102a, an application status inquiry unit 102b, a screen display control unit 102c, and an e-GovAPI 102d.

The application unit 102a submits an electronic application to the public service site e-Gov 400 via e-Gov API 102d. When an electronic application is submitted to the public service site e-Gov 400, transmission history data including the transmission number, transmission date and time, the name of the person to whom the application is submitted, and the procedure folder name is stored in the data table 106a. Note that the application unit 102a may be configured to be executable independently by incorporating the functions of e-Gov API 102d.

The application status inquiry unit 102b acquires a list of application status including the sending number, sending date and time, arrival number, procedure name, procedure folder name, current status, number of official documents not yet obtained, and number of comments not yet obtained as a response result from e-Gov 400, a public service site, via e-Gov API 102d, acquires the name of the applicant from the transmission history data stored in data table 106a using the procedure folder name of the acquired response result as a key, creates display data based on the acquired response result and the name of the applicant, and displays it on the application status inquiry screen. Note that the application status inquiry unit 102b may be configured to be executable independently by incorporating the functions of e-Gov API 102d.

The application status inquiry unit 102b may also create display data according to the extraction conditions that have been set. The extraction conditions may include, for example, at least one of the application status (sending, arriving, under review, review completed, procedure completed, in the process of being withdrawn, withdrawn, resubmitted, error), the presence or absence of comments, the presence or absence of official documents, the type of procedure, and the sending date. The general flow of the application status is: sending → arriving → under review → review completed → procedure completed.

The application status inquiry unit 102b may also download unobtained official documents or comments in bulk from e-Gov 400, a public service site. The procedure may be a social insurance or employment insurance procedure.

The screen display control unit 102c controls the display of various screens on the monitor 114 and the reception of inputs therefor.

e-GovAPI102d is downloaded from e-Gov400 and installed, and is a client application for various accesses to e-Gov400, such as electronic applications, obtaining a list of submitted cases, and obtaining official documents (comments).

3. Specific Examples
A specific example of the process of the control unit 102 of the electronic application support apparatus 100 in this embodiment will be described with reference to Figures 5 to 14. Figure 7 is a diagram for explaining an overview of the overall process of the control unit 102 of the electronic application support apparatus 100 in this embodiment.

(Overall processing)
An outline of the overall processing of the control unit 102 of the electronic application support device 100 in this embodiment will be described with reference to Fig. 7. When inquiring about the application status, extraction conditions can be set for the status of the procedure to be displayed. Fig. 7(A) shows the processing flow, Fig. 7(B) shows an image of the response result, Fig. 7(B) shows an image of the transmission history data, and Fig. 7(C) shows an image of the display data.

In FIG. 7 (A), (S1) the application status inquiry unit 102b uses the "Get transmission case list" of the e-Gov API 102d to obtain the application status response result (transmission cases + application cases) from e-Gov 400.

In the example of the response result image shown in FIG. 7 (B), the first line shows the sending number "000001", the sending date and time "2020/04/21 09:00:00", the arrival number "100001", the procedure name "Employment Insurance Qualification Acquisition Notification", the procedure folder name "001 (1)", and the current status "Sending". The second line shows the sending number "00002", the sending date and time "2020/04/22 09:20:00", the arrival number "200001", the procedure name "Employment Insurance Qualification Acquisition Notification", the procedure folder name "002 (1)", the current status "Review completed", the number of official documents not yet obtained "1", and the total number of official documents "1". The third line shows the sending number "000002", the sending date and time "2020/04/22 The message reads, "09:20:00", arrival number "200002", procedure name "Employment Insurance Qualification Acquisition Notification", procedure folder name "002(2)", current status "Procedure Completed", number of official documents not yet obtained "0", total number of official documents "1". Here, it is not possible to determine whose procedure status is based on the response from e-Gov400 alone.

The transmission number is a number assigned to each sending unit when multiple application cases are submitted at once. It will be the number of data items where the number of unobtained official documents is greater than 0. If 100 application cases are submitted at once, one transmission number will be assigned. The arrival number is a number assigned to each application case. 100 arrival numbers will be assigned for 100 application cases.

The application status inquiry unit 102b (S2) generates display data from the acquired response result (transmission case + application case) and the transmission history data. In this case, display/hide is set according to the specified extraction conditions.

In the image of the transmission history data shown in FIG. 7(C), the transmission number is "000001", the transmission date and time is "2020/04/21 09:00:00", the employee code is "1000000001", the name is "Yamashita Shigeru", the procedure folder name is "001(1)", the second line is the transmission number is "000002", the transmission date and time is "2020/04/22 09:20:00", the employee code is "1000000004", the name is "Yoshida Yuji", the procedure folder name is "002(1)", the third line is the transmission number is "000002", the transmission date and time is "2020/04/22 09:20:00", the employee code is "1000000006", the name is "Miyamoto Kosuke", the procedure folder name is "002(2)".

The transmission history data held at the time of application is linked to the procedure folder name in the response result to link who is performing the procedure. More specifically, the reason for linking the response result of e-GovAPI 102d to the transmission history data is that even when e-GovAPI 102d is used, only a small amount of information is returned, and the code and name of the person applying (employee) and other employee attribute information are not returned. Linking the application status to the information on the notes (such as the applicant's code and name) is a mandatory requirement. For this reason, the application status is linked to the applicant's name and displayed in a list.

In the image of the display data shown in FIG. 7 (D), the first line shows the application status "Sending", the sending date and time "2020/04/21 09:00:00", the procedure name "Employment Insurance/Qualification Acquisition Notification", the code "1000000001", the name of the applicant "Yamashita Shigeru", the official document "None", and the display flag "Display". The second line shows the application status "Review Completed", the sending date and time "2020/04/22 09:20:00", the procedure name "Employment Insurance/Qualification Acquisition Notification", the code "1000000004", the name of the applicant "Yoshida Yuji", the official document "Some documents not yet acquired", the number of official documents not yet acquired "1", and the display flag "Display". The third line shows the application status "Procedure Completed", the sending date and time "2020/04/22 The time is "09:20:00", procedure name is "Employment Insurance/Qualification Acquisition Notification", code is "1000000006", name of applicant is "Miyamoto Kosuke", official document is "All documents acquired", number of official documents yet to be acquired is "0", and display flag is "Hide". By displaying the procedure name and name in this way, it is easy to see who the procedure is for.

The display flag is set to show or hide depending on the specified extraction conditions. For official documents, if the number of unobtained official documents > 0, it will be "Some unobtained", if the total number of official documents > 0 and the number of unobtained official documents = 0, it will be "All obtained", and if the number of unobtained official documents = 0, it will be "None".

(S3) The application status inquiry unit 102b controls the data to be displayed based on the extraction conditions of the application status inquiry screen. (S4) For each piece of data where the number of unobtained official documents is > 0, the application status inquiry unit 102b uses the e-GovAPI 102d to download all the unobtained official documents (or comments) together. This process is repeated the number of times for each piece of data where the number of unobtained official documents is > 0.

FIGS. 8 to 14 are diagrams for explaining a specific example of the processing of the control unit 102 of the electronic application support device 100 in this embodiment. Specific examples of the processing of the control unit 102 of the electronic application support device 100 in this embodiment will be explained with reference to FIG. 8 to FIG. 14.

(Application Status Inquiry)
5 to 8 are diagrams showing examples of the application status inquiry screen for inquiring about the application status. The display examples in Fig. 5 to 8 show examples in which the sample data in Fig. 9 to Fig. 14 are used.

The example of the application status inquiry screen shown in Figure 5 has an extraction condition setting area for setting extraction conditions such as application status (sending, arrived, under review, review completed, procedure completed, in process of withdrawal, withdrawn, resubmitted, error), comments (yes (including acquired), yes (only not acquired), no), official documents (yes (including acquired), yes (only not acquired), no), procedure, sending date, etc.), an area for selecting the items to be downloaded (official documents not acquired, comments not acquired), an "output button" to instruct the start of download, an inquiry result display area that displays the results of the procedure status that match the extraction conditions, and a "display button" to instruct the start of inquiry.

The inquiry results display area shows the inquiry results for the following items: application status, submission date and time, procedure name, code, name of the applicant, comments, and official documents.

When the "Display button" is pressed, the application status inquiry unit 102b obtains a list of application statuses as a response result from e-Gov 400 via e-Gov API 102d, obtains the code and name of the applicant from the transmission history data stored in data table 106a using the procedure folder name of the obtained response result as a key, creates display data including the obtained response result and the code and name of the applicant according to the set extraction conditions, and displays it in the inquiry result display area.

The inquiry application screen in Figure 9 shows the display result of the inquiry status when the application status (sending, arrived, under review, review completed) and sending dates 2020/04/21 to 2020/04/27 are specified as extraction conditions. In the inquiry result display area, four details are displayed, and the first line shows the application status "arrived", sending date and time "2020/04/21 09:00:00", procedure name "Employment Insurance/Qualification Acquisition Notification", code "1000000001", name of applicant "Yamashita Shigeru", comment "none", and official document "none".

In this way, by displaying the procedure status in a list according to the extraction conditions you set, it is possible to see at a glance who is doing which procedure and what the status is.

The bulk downloading of comments or official documents will be explained with reference to the inquiry application screen in Figure 10. In Figure 10, when the download target (unobtained official documents or unobtained comments) is selected and the "Output button" is pressed, the application status inquiry unit 102b downloads all unobtained comments or official documents displayed in the inquiry result display area from e-Gov 400 via e-GovAPI 102d.

In the example shown in Figure 10, an unobtained official document is selected, so when the "Output button" is pressed, the second and third official documents displayed in the query result display area are downloaded together. On the other hand, when an unobtained comment is selected and the "Output button" is pressed, the first comment displayed in the query result display area is downloaded.

Figures 11 to 14 are diagrams showing sample data. Figure 11 (A) shows sample data of transmission history data. When an electronic application is made to e-Gov 400, the application unit 102a creates, for example, transmission history data as shown in Figure 11 (A) and stores it in the data table 106a.

In the example of transmission history data shown in FIG. 11 (A), the first line contains SEQ "1", company number "777", transmission number "19283644969383638374", transmission date and time "2020/04/21 09:00:00", employee code "1000000001", employee name "Yamashita Shigeru", procedure name "Employment Insurance/Qualification Acquisition Notification", procedure folder name "3847562927483927(1)", and e-Gov submission destination identifier "49511000010000000003825".

Figure 11 (B) shows sample data for employee information. The first line contains the company number "777," employee code "1000000001," and employee name "Yamashita Shigeru."

In FIG. 12 (A), the application status inquiry unit 102b specifies the start of the sending date as 2020/04/21 and the end of the sending date as 2020/04/28, and makes a request to e-Gov 400 via the sending case list acquisition API (e-Gov API 102d) to obtain the response result of the list of application statuses.

Figure 12 (B) is a diagram showing a data sample of the acquired response result. The first line shows the sending number "19283644969383638374", the sending date and time "2020/04/21 09:00:00", the arrival number "284845556879443856", the procedure folder name "3847562927483927 (1)", the current status "Arrived", the number of comments not yet acquired "0", the total number of comment notifications "0", the number of official documents not yet acquired "0", and the total number of official documents "0".

The application status inquiry unit 102b obtains the employee code and name of the application target from the transmission history data stored in the data table 106a using the procedure folder name of the obtained response result as a key, and adds them to the response result as shown in FIG. 13(A). In the example shown in FIG. 13(A), the employee code "1000000001" and employee name "Yamashita Shigeru" have been added to the first line.

The application status inquiry unit 102b creates display data as shown in FIG. 13(B) according to the extraction conditions set on the application status inquiry screen, such as application status (sending, arrived, under review, review completed) and sending dates 2020/04/21 to 2020/04/27, based on the data shown in FIG. 13(A), and displays it on the application status inquiry screen.

The display data shown in FIG. 13(B) has the following display data on the first line: application status "Arrived", submission date and time "2020/04/21 09:00:00", procedure name "Employment Insurance/Qualification Acquisition Notification", code "1000000001", name of applicant "Yamashita Shigeru", comment "None", and official document "None".

For the comments column, if the number of unretrieved comments > 0, it will show "some comments not retrieved", if the total number of comment notifications > 0 and the number of unretrieved comments = 0, it will show "all retrieved", and if the total number of comment notifications = 0, it will show "none".For the official documents column, if the number of unretrieved official documents > 0, it will show "some comments not retrieved", if the total number of official documents > 0 and the number of unretrieved official documents = 0, it will show "all retrieved", and if the total number of official documents = 0, it will show "none".

Figure 14 is a diagram to explain the mechanism for obtaining all unobtained comments and official documents. In Figure 14 (A), the application status inquiry unit 102b repeatedly requests downloads data for which the number of unobtained official documents is one or more by specifying the arrival number from the official document acquisition API (e-Gov API 102d), and downloads them from e-Gov 400. The process is the same for comments.

The downloaded data includes the arrival number and file data, as shown in Figure 14 (B).

The application status inquiry unit 102b unzips the file data (ZIP) and creates a folder in the specified path as shown in FIG. 14(C), and saves the data therein. The file name can be, for example, "Sent date" + "Procedure code" + "Employee code" + "_Official document" (for example, 20200422_7_1000000005_Official document).

As described above, according to this embodiment, when an electronic application is made to a public service site, the application unit 102a stores transmission history data including the transmission number, transmission date and time, the name of the application target, and the procedure folder name in the storage unit, and the application status inquiry unit 102b obtains a list of application status including the transmission number, transmission date and time, arrival number, procedure name, procedure folder name, current status, number of official documents not obtained, and number of comments not obtained as a response result from the public service site, obtains the name of the application target from the transmission history data stored in the storage unit using the procedure folder name of the obtained response result as a key, and creates display data based on the obtained response result and the name of the application target and displays it on the application status inquiry screen, thereby making it possible to improve business efficiency when inquiring about application data electronically applied to a public service site.

4. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

In addition, with regard to the electronic application support device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the electronic application support device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the electronic application support device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) to give instructions to the CPU in cooperation with the OS and perform various processes. This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the electronic application support device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a DVD (registered trademark) or Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The electronic application support device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The electronic application support device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

100 Electronic application support device 102 Control unit 102a Application unit 102b Application status inquiry unit 102c Screen display control unit 102d e-GovAPI
104 Communication interface unit 106 Storage unit 106a Data table 112 Input device 114 Output device 200 Server 300 Network 400 e-Gov

Claims (8)

An electronic application support device for making an electronic application to a public service site via a network, the electronic application support device comprising a storage unit and a control unit,
The control unit is
an application means for storing in the storage unit, when an electronic application is made to the public service site, transmission history data including a transmission number, a transmission date and time, a name of the person to whom the application is made, and a procedure folder name;
an application status inquiry means for acquiring a list of application statuses including a transmission number, transmission date and time, arrival number, procedure name, procedure folder name, current status, number of official documents not obtained, and number of comments not obtained as a response result from the public service site, acquiring the name of the application subject from the transmission history data stored in the memory unit using the procedure folder name of the acquired response result as a key, and creating display data based on the acquired response result and the name of the application subject and displaying it on an application status inquiry screen;
An electronic application support device comprising: The electronic application support device according to claim 1, characterized in that the application status inquiry means creates display data according to the set extraction conditions. The electronic application support device according to claim 2, characterized in that the extraction conditions include at least one of the application status, the presence or absence of comments, the presence or absence of official documents, the type of procedure, and the sending date. The electronic application support device according to any one of claims 1 to 3, characterized in that the application status inquiry means downloads unobtained official documents or comments from the public service site in one go. The electronic application support device according to any one of claims 1 to 4, characterized in that the procedure is a social insurance or employment insurance procedure. The electronic application support device according to any one of claims 1 to 5, characterized in that the public service site is e-Gov. An electronic application support method for causing an information processing device having a storage unit and a control unit to execute the method,
Executed in the control unit,
an application process for storing transmission history data including a transmission number, a transmission date and time, a name of a person to whom the application is made, and a procedure folder name in the storage unit when the person makes an electronic application to a public service site;
an application status inquiry process for obtaining a list of application statuses including a transmission number, transmission date and time, arrival number, procedure name, procedure folder name, current status, number of official documents not obtained, and number of comments not obtained as a response result from the public service site, obtaining the name of the application subject from the transmission history data stored in the memory unit using the procedure folder name of the obtained response result as a key, and creating display data based on the obtained response result and the name of the application subject, and displaying the data on an application status inquiry screen;
An electronic application support method comprising: An electronic application support program to be executed by an information processing device having a storage unit and a control unit,
Executed in the control unit,
an application process for storing transmission history data including a transmission number, a transmission date and time, a name of a person to whom the application is made, and a procedure folder name in the storage unit when the person makes an electronic application to a public service site;
an application status inquiry process for obtaining a list of application statuses including a transmission number, transmission date and time, arrival number, procedure name, procedure folder name, current status, number of official documents not obtained, and number of comments not obtained as a response result from the public service site, obtaining the name of the application subject from the transmission history data stored in the memory unit using the procedure folder name of the obtained response result as a key, and creating display data based on the obtained response result and the name of the application subject, and displaying the data on an application status inquiry screen;
An electronic application support program to implement the above.

Images