Information provision system

Abstract

To enable a user who is a resident to appropriately and timely carry out a useful or necessary procedure, and to enable a public office to appropriately and timely guide a procedure that is useful or necessary for the user who is the resident.SOLUTION: This information providing system includes: a data managing unit which extracts data on a user from a division system for each of a plurality of divisions, and which manages the extracted data for each user; a user interface computer which receives an input relating to the user, and which provides a front user interface that provides, to the user, the obtained output; a content managing unit that manages content data which defines a procedure executable by the user in accordance with the managed data by the data managing unit; and a determination engine which refers to the content data, and which determines the procedure executable by the user in accordance with an input from the user interface computer.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an information providing system, and more particularly to an information providing system for supporting administrative processing and various procedures of users (residents) in local government offices such as prefectures, cities, towns, and villages (city halls, ward offices, town halls, etc.).

Background Art

[0002] Hitherto, in local government offices such as city, town, and village offices, users who are residents have had to individually perform procedures (applications and submissions for fulfilling obligations) for exercising their rights to administrative services in the real space (such as the resident windows of the offices) and within a vertically segmented framework by field and industry type. However, today, with the advent of the digital society, there is a governance gap, and in the future, it is necessary to review responses in the cyber space and roles and actors based on functions, and the use of digital technologies and the development of new information processing systems to support these transformations are required.

[0003] For the purpose of local self-government that protects the lives and safety of residents, local government offices across the country have introduced information processing systems to manage information related to residents and efficiently perform administrative tasks. Procedures such as applications and submissions by residents as users are processed administratively using an information processing system based on a paper processing process and are managed within individual business systems. As an example, the information of the basic resident register has been managed and operated as the basic information of residents in the local government offices of the place of residence until today. However, with the development of the basic resident register network, digital information is shared among local government offices, prefectures, and the country across the country, and it has become unnecessary to attach a resident certificate in procedures in the public domain. Taking this as an opportunity, various proposals have been made to utilize digital technologies in the administrative field (see, for example, Patent Document 1), indicating that the provision of administrative services from the user's perspective is highly effective for residents.

[0004] However, administrative processing at local government offices remains stuck in an outdated application-based system. Under a vertically structured administration, while user-centric service reform is needed, the situation remains one where administrative staff still operate from the perspective of those handling the processing, unable to shift away from individual workflows based on paper-based procedures. Therefore, the government is aiming for Society 5.0 (realization through systems that highly integrate cyberspace and physical space) and promoting GovTech, which is promoting the use of digital technology to improve the efficiency, optimization, and convenience of administrative services. However, existing administrative systems lack a seamless system from an architectural perspective that provides an overall overview of the data flow, and progress is slow. In other words, the system is based on a ledger management process that relies on vertically structured paper processing in government offices, and as a result, different types of procedures for the same user are processed individually, contrary to the needs of the residents. On the other hand, residents (users themselves) who are the ones who carry out the procedures do not necessarily understand the system or know what procedures they need to follow, which leads to situations where procedures are easily missed or omissions occur and rights are not fulfilled. Unfortunately, however, a data-driven system that is perfectly tailored to each individual resident has yet to be provided.

[0005] The main reasons for this are that both the municipal staff responsible for handling these matters and the information processing systems rely on applications and notifications from residents as the starting point for administrative processing. In addition, because the systems are ledger management systems based on individual tasks, data-driven decision-making across tasks is difficult. The number of experts who can understand and propose the specific requirements of each system is decreasing year by year, and there is no system that can perform a similar role. Real-time information gathering of resident information, which is managed in a decentralized manner, is also difficult.

[0006] For example, when a resident has a child, the resident first gathers information about their rights and obligations through the internet or the government's website to find out about the rights and obligations related to them and the administrative services they are eligible for, and then proceeds with the necessary procedures. However, this reliance on residents to obtain information is problematic from the standpoint of fairness among residents, as differences in residents' information-gathering abilities can lead to disparities in access to administrative services. Government offices are also required to accurately guide residents on the administrative services they are eligible for in order to mitigate such inequalities, but such accurate guidance is not always easy because the requirements for obtaining administrative services differ among residents. [Prior art documents] [Patent Documents]

[0007] [Patent Document 1] Japanese Patent Publication No. 2002-32525 [Overview of the project] [Problems that the invention aims to solve]

[0008] In view of the above problems, this invention provides a function-based mechanism that connects cyberspace and real space, proactively guiding and presenting necessary procedures to users (residents) in a timely manner, supporting them in executing those procedures. It also provides a mechanism for government offices (the providers of administrative services) to achieve extremely efficient administrative processing for both the front-end and business systems, enabling increased efficiency through automation of administrative processes, reduction of operational risks, and strengthening data management. This invention transforms existing information processing system environments, even in the current problem of siloed (vertically segmented) business systems, into law-driven, useful information processing systems for both users (residents) and providers (officials), and facilitates the provision of necessary data.

[0009] To solve the above problems, the information provision system according to the present invention is characterized by comprising: a data management unit that extracts user data from departmental systems for each of several departments and manages it on a per-user basis; a user interface computer that provides a front user interface that accepts inputs about the user and provides the obtained output to the user; a content management unit that manages content data that defines the procedures that the user can execute according to the data managed by the data management unit; and a determination engine that determines the procedures that the user can execute by referring to the content data according to inputs from the user interface computer. [Effects of the Invention]

[0010] According to the present invention, it is possible to provide an information provision system that enables resident users to carry out useful or necessary procedures in a timely manner, and also enables government offices to provide timely guidance to resident users on useful or necessary procedures. [Brief explanation of the drawing]

[0011] [Figure 1] This is a schematic diagram illustrating an information provision system 1 according to an embodiment of the present invention. [Figure 2] An example of life event definition data managed in the content management unit 14 is shown. [Figure 3] Examples of the management screens for service definition data and service procedure definition data are shown. [Figure 4] Examples of the management screens for service definition data and service procedure definition data are shown. [Figure 5] This shows an example of a management screen for managing detailed administrative service procedure data. [Figure 6] This shows an example of a management screen for data catalog data, which serves as a dataset necessary for data presentation and review, and interface information related to the interfaces used for presentation and review. [Figure 7]This shows an example of the management screen for suggested rule data (proactive rule data). [Figure 8] This shows an example of the management screen for review rule data (first-stage review rule data). [Figure 9] This is a block diagram illustrating the configuration of the judgment engine 13. [Figure 10] This is a block diagram illustrating the configuration of the judgment engine 13. [Figure 11] This is a flowchart illustrating the operation of the information provision system 1 of this embodiment. [Figure 12] This flowchart describes the procedure for presenting user-applicable procedures on the front user interface computer 11. [Figure 13] This is a flowchart explaining the procedure for conducting the initial review of the selected procedure. [Figure 14] This is an example of an input / output screen when a user performs a procedure to input reception data, including life events and identification numbers, on the front user interface computer 11. [Figure 15] This is an example of an input / output screen when a user performs a procedure to input reception data, including life events and identification numbers, on the front user interface computer 11. [Figure 16] This is an example of an input / output screen when a user performs a procedure to input reception data, including life events and identification numbers, on the front user interface computer 11. [Figure 17] This is an example of an input / output screen when a user performs a procedure to input reception data, including life events and identification numbers, on the front user interface computer 11. [Figure 18] This is an example of an input / output screen when a user performs a procedure to input reception data, including life events and identification numbers, on the front user interface computer 11. [Figure 19]This is an example of an input / output screen when a user executes a procedure for inputting reception data including a life event and an identification number on the front user interface computer 11. [Figure 20] This is an example of an input / output screen when a user executes a procedure for inputting reception data including a life event and an identification number on the front user interface computer 11. [Figure 21] This is an example of an input / output screen when a user executes a procedure for inputting reception data including a life event and an identification number on the front user interface computer 11. [Figure 22] This is an example of an input / output screen when a user executes a procedure for inputting reception data including a life event and an identification number on the front user interface computer 11. [Figure 23] This is an example of an input / output screen when a user executes a procedure for inputting reception data including a life event and an identification number on the front user interface computer 11.

Embodiment for Carrying Out the Invention

[0012] Hereinafter, this embodiment will be described with reference to the accompanying drawings. In the accompanying drawings, functionally identical elements may sometimes be denoted by the same numbers. Note that the accompanying drawings show embodiments and implementation examples in accordance with the principles of the present disclosure, but these are for the purpose of understanding the present disclosure and are never used to interpret the present disclosure in a limiting way. The description in this specification is merely a typical example and does not limit the scope or application examples of the claims of the present disclosure in any sense.

[0013] In this embodiment, although the description is made in sufficient detail for those skilled in the art to implement the present disclosure, other implementations and forms are possible, and it is necessary to understand that changes in configuration and structure and replacement of various elements can be made without departing from the scope and spirit of the technical idea of the present disclosure. Therefore, the following description should not be construed as being limited to this.

[0014] Referring to Figure 1, an information provision system 1 according to an embodiment of the present invention will be described. This information provision system 1 may be a system for providing information to a user as a resident in, for example, a municipal office. A user (resident) visits the office and, with the assistance of an employee operating the information provision system 1, accesses the system 1 and inputs life events (birth, death, marriage, divorce, moving in, moving out, change of address, change of household, etc.) and a personality identification ID. In doing so, the system can present various applications and notifications necessary for that household and provide input support for those procedures.

[0015] Furthermore, users can access this system 1 via a network (dedicated line, etc.) using a terminal device 2 (personal computer, tablet computer, smartphone, etc.) located in a remote location, thereby receiving similar presentation of various applications and notifications, as well as input assistance during procedures. It should be noted that municipal offices are just one example of organizations to which this system may apply; this system can also be used between various organizations with similar characteristics (e.g., NGOs, unions, educational institutions, incorporated associations, foundations, private companies, etc.) and their members.

[0016] As shown in Figure 1, the information provision system 1 of this embodiment includes a front user interface computer 11 for sending and receiving information with terminal devices 2. This front user interface computer 11 is connected to a data management unit 12, a decision engine 13, and a content management unit 14 via a network (LAN, WAN, intranet, etc.).

[0017] The information provision system 1 is comprised of a front user interface computer 11, a data management unit 12, a judgment engine 13, and a content management unit 14. The front user interface computer 11 has the function of accessing the data management unit 12 to refer to data that can be viewed for the relevant user, and also to display the judgment results from the judgment engine 13.

[0018] The Data Management Unit 12 uses the resident's personality identification ID as a key to extract and integrate necessary data from the Resident Basic Register System and various departmental systems A, B, C, D… installed in various departments of the government office (e.g., Family Registry and Resident Affairs Division, Tax Division, Elderly Welfare Division, Disability Welfare Division, Social Welfare Division, Long-Term Care Insurance Division, National Health Insurance and Pension Division, Childcare Support Division, etc.), based on data catalogs defined by the Content Management Unit 14 of the Resident Basic Register System and the various departmental systems. Generally, user identification information is managed individually at the organizational and institutional level, and attribute information managed at the institutional level is managed by the core systems of each department. The Data Management Unit 12 links the procedural information generated by the Judgment Engine 13 to the integrated administrative system installed in the government office. The integrated administrative system then links to the departments responsible for various services based on the service definition settings defined by the Content Management Unit 14. The Resident Basic Register System has the basic database that constitutes the Resident Basic Register. It is also possible to connect the Data Management Unit and each departmental system via an intermediate server.

[0019] The determination engine 13 determines whether there is information regarding various applications and notifications that a resident can perform, based on the resident data acquired on a household basis by the data management unit 12 and the content data managed by the content management unit 14. The determination engine 13 compares the data input from the front user interface computer 11 and the integrated data managed on a resident basis by the data management unit 12 with the content data (rule data) managed by the content management unit 14 and determines whether or not it matches the rules.

[0020] The content management unit 14 manages, for example, life event definition data that defines life events, service definition data that specifies the services that the government provides to residents, and service procedure definition data that specifies the procedures, applications, notifications, etc. necessary for residents to acquire, relinquish, or change the content of each service. At the same time, the content management unit 14 registers, edits, and manages as content data rule data necessary to determine whether the application and notification procedures defined in the judgment engine 13 are applicable to the user.

[0021] Rule data is data that shows the substantive requirements, formal requirements, timing requirements, procedural requirements, etc., for each resident's application or notification to be approved. The content management unit 14 registers, edits, and manages content data (procedure definitions and rule data) for presenting procedures to residents and households and generating procedural information. By having the content management unit 14 manage content data independently of the judgment engine 13, it can flexibly respond to additions, changes, or deletions of rules and replace rules as needed.

[0022] The system defines life events as the events that trigger changes in basic information (personality information) managed in the Basic Resident Register System, and defines their types. Figure 2 shows an example of life event definition data managed in the Content Management Unit 14. In the management screen in Figure 2, each life event is assigned a life event code to identify the life event and a life event name, and these are managed as list data. In addition, the life event code and life event name can be edited on the editing screen.

[0023] Procedures such as applications and notifications defined by service definition data and service procedure definition data are registered, edited, and managed in a categorized manner. Defined application and notification procedures are associated with, for example, system classifications (tax, health insurance, pension, disability welfare, long-term care insurance, child welfare, etc.) and defined as procedures (new application, change, cancellation, etc.) for attribute information used to utilize each system. Figures 3 and 4 show examples of the management screens for service definition data and service procedure definition data.

[0024] In the service definition data management screen shown in Figure 3, various administrative services are defined using data such as administrative service code, administrative service name, overview, and responsible department. Furthermore, this data can be edited by the administrator as needed on the editing screen. Such a management and editing screen may be displayed on the display of a computer (not shown) that constitutes the content management unit 14.

[0025] Figure 4 shows the management screen for service procedure definition data. For each administrative service procedure, data such as the administrative service name, administrative service procedure name code, and administrative service procedure name are assigned and managed as list data. In addition, the administrative service name, administrative service procedure name code, and administrative service procedure name can be edited as needed on the editing screen. Figure 5 shows an example of a management screen for managing the details of administrative service procedure data. In this management screen, each administrative service procedure is managed in addition to the administrative service name, administrative service procedure name code, and administrative service procedure name, with the corresponding life event associated with it. Furthermore, this management content can be edited as needed on the editing screen.

[0026] Figure 6 shows an example of a management screen for data catalog data, which serves as the dataset necessary for data presentation and review, and interface information related to the interfaces used for presentation and review. This management screen manages the data catalog, which serves as the dataset necessary for presenting and reviewing service procedure data, using the administrative service procedure name code, administrative service procedure name, target person, and data catalog name. Furthermore, this management content can be edited as needed using the editing screen.

[0027] Rule data can be classified into proposed rule data and review rule data. Both rule data (proposed rule data and review rule data) consist of a definition section and a rule description section. The definition section may describe the outline of a procedure in string form and set classification values ​​related to the type of procedure. The rule description section may describe the outline of the rule in string form and include an evaluation formula that expresses the rule mathematically.

[0028] The presentation rule data is used to determine whether or not to present various procedures to a particular resident or household. When the determination engine 13 determines that a particular resident or household satisfies the presentation rule data, the procedure is presented to the resident via the front user interface computer 11 (displayed on a screen, etc.). The presentation rule data may be expressed quantitatively or qualitatively, representing the conditions that must be met.

[0029] Figure 7 shows an example of a management screen for suggested rule data (proactive rule data). This management screen manages suggested rules using the administrative service name, administrative service procedure name code, administrative service procedure name, corresponding life event, and rule code. Furthermore, this management screen can be edited as needed via the editing screen.

[0030] The review rule data is rule data that specifies the data items and conditions for their values ​​required for a user to execute a procedure, for each type of procedure, and is described on a procedure-by-procedure basis. For example, the review rule data may include an identification symbol indicating the type of procedure in the header section, and review conditions described for each review item in the payload section. When the determination engine 13 determines that a user satisfies the review rule data, the primary review for that procedure is determined to be completed as the user has met the conditions.

[0031] Figure 8 shows an example of a management screen for review rule data (primary review rule data). This management screen manages review rules (primary review rule data) by administrative service name, administrative service procedure name code, administrative service procedure name, corresponding rule code, and evaluation items. Furthermore, this management screen can be edited as needed using the editing screen.

[0032] The configuration of the judgment engine 13 will be explained with reference to the block diagrams in Figures 9 and 10. As shown in Figure 9, the judgment engine 13, as an example, is configured to perform judgments regarding the presented rules and includes an input unit 131, a data storage unit 132, a presented rule application unit 133, an output unit 134, a comparison unit 135, and a presented rule input unit 136. Also, as shown in Figure 10, the judgment engine 13, as an example, is configured to perform judgments regarding the review rules and includes an input unit 141, a data storage unit 142, a review rule application unit 143, an output unit 144, a comparison unit 145, and a review rule input unit 146.

[0033] The input unit 131 provides an input interface for inputting data from the front user interface computer 11. The data storage unit 132 is a storage unit that stores the data input from the input unit 131. The presentation rule application unit 133 extracts service definition data and presentation rule data corresponding to the user related to the data input from the input unit 131 from the content management unit 14.

[0034] The comparison unit 135 compares the user data stored in the data storage unit 132 with the suggestion rule data input from the suggestion rule input unit 136 and extracted by the suggestion rule application unit 133, and determines whether they match or not. If they match, the output unit 134 outputs the service definition data corresponding to the rule data to the front user interface computer 11.

[0035] The input unit 141 provides an input interface for inputting data from the front user interface computer 11. The data storage unit 142 is a storage unit that stores the data input from the input unit 141. The review rule application unit 143 extracts service definition data and review rule data corresponding to the user related to the data input from the input unit 141. The comparison unit 145 compares the user data stored in the data storage unit 142 with the review rule data input from the review rule input unit 146 and extracted by the review rule application unit 143 to determine whether the primary review is passed or failed. The output unit 144 outputs the result of the determination to the front user interface computer 11. Note that the input unit 141, output unit 144, and data storage unit 142 may be shared with the input unit 131, output unit 134, and data storage unit 132.

[0036] The judgment engine 13 presents procedures that the user can execute based on the data input from the front user interface computer 11 and the content data in the content management unit 14, and performs a review (initial review) of the application / notification based on the application / notification data entered by the user. Specifically, the judgment engine 13, based on the life event information and resident information selected by the user, refers to the presentation rule data in the content data stored in the content management unit 14 and presents procedures applicable to the user on the front user interface computer 11. The judgment engine 13 also applies the review rule data to the procedure selected by the user and determines whether the initial review of the procedure for that user has passed or failed.

[0037] The role of the front user interface computer 11 will be explained in more detail. A user or operator accessing the front user interface computer 11 can perform the following data input tasks. (i) Registration of information related to the reception (e.g., issuance of reception number (automatic issuance is also possible), input of information of the person performing the procedure (visitor), date (reception date, application date), etc.) (ii) Registration of information regarding life events (e.g., identification of life events (birth, marriage, divorce, death, etc.), identification of household members affected by the life event, date of occurrence of the life event, date of notification, etc.) (iii) Input of pre-interview items (information obtained by conducting a pre-interview with the user before outputting it to the data management department 12, etc., regarding information that cannot be obtained within the government office, such as when moving in)

[0038] When a life event is presented on the front user interface computer 11, the determination engine 13 returns the types of procedures that can be selected and the necessary datasets as the result of its determination regarding the user. The front user interface computer 11 can then select the procedure the user desires based on this presentation. Specifically, the procedure selection process may be performed on the front user interface computer 11 in the following steps. (i) Resident data necessary for presentation determination is obtained from the data management unit 12. (ii) After the determination process in the determination engine 13, a list of procedures indicating the selectable procedures and the datasets required for the selectable procedures are sent back from the determination engine 13 to the front user interface computer 11. The datasets may include procedure data items on a procedure-by-procedure basis. (iii) Procedure list data is displayed on the display of the front user interface computer 11, prompting the user to make a selection.

[0039] When a user selects a desired procedure from the procedure list data, the corresponding resident data and linked data are read from the data management unit 12 according to the user's identification information (personality identification ID, etc.) included in the selection action and transferred to the judgment engine 13. The judgment engine 13 reads the corresponding content data according to the received resident data and linked data. For each selected procedure, the review rule data included in the content data is compared with the input data related to the procedure, and the judgment engine 13 performs a primary review. The results are output and displayed on the front user interface computer 11.

[0040] Next, the operation of the Information Provision System 1 will be explained with reference to the flowchart in Figure 11. First, a user who is the target of information provision by the System 1 makes various applications and notifications concerning themselves to the front user interface computer 11 of the System 1 (Presentation of Life Events: Step S11). The user specifies the presented life event and inputs the user identification information of the person involved in the life event (Step S12).

[0041] The front user interface computer 11 extracts resident data for the households of residents designated as parties to a life event via the data management unit 12, and queries the determination engine 13 for that data.

[0042] The determination engine 13 presents a list of procedures that the user can perform, based on resident / household data and presentation rule data managed by the content management unit 14 (step S17). The user selects the desired procedure from the list of procedures (step S18) and enters the necessary information (step S19).

[0043] Based on the input personality information, the judgment engine 13, via the data management unit 12, extracts the necessary data regarding the resident from various core systems related to each selected procedure, sets the acquired data as the values ​​of the procedure items, and applies the review rule data to the set item values ​​to perform a primary review for the procedure. After the primary review is performed, the generated procedure data is linked to the existing integrated administrative system and various core systems via the front user interface computer 11 and handed over to the operations of each department.

[0044] Referring to the flowchart in Figure 12, the procedure for presenting applicable procedures to the user on the front user interface computer 11 will be described. First, the user inputs reception data, including life events and identification numbers, on the front user interface computer 11 (step S111). The input reception data is output to the determination engine 13 and stored in the data storage unit 132. The comparison unit 135 within the determination engine 13 extracts attribute data from the reception data stored in the data storage unit 132 (step S112), and extracts data that matches the attribute data from the content data managed by the content management unit 14 (step S113).

[0045] If matching data is extracted (detected) (Yes in step S114), the suggestion rule application unit 133 extracts suggestion rule data from the rule data corresponding to that data (step S115), evaluates the suggestion rule data (step S116), and outputs the evaluation result to the front user interface computer 11 (step S117).

[0046] Next, referring to the flowchart in Figure 13, the procedure for performing the initial review for the selected procedure will be described. When the user selects a procedure for which an application or notification can be submitted and the data for that procedure is entered, the input data is stored in the data storage unit 142 as reception data via the input unit 141. The comparison unit 145 in the judgment engine 13 extracts attribute data from the reception data stored in the data storage unit 142 (step S122), extracts examination rule data corresponding to the attribute data, and applies the examination rule to the input data (step S124). As a result of applying the examination rule, the pass / fail result of the initial review of the input data is output to the front user interface computer 11 (step S125).

[0047] Thus, in the information provision system 1 of this embodiment, the data management unit 12 manages data related to various departmental systems for each user's identification number, and the content management unit 14 determines, based on rule data managed as content data, whether various rights and obligations arise for each user and whether corresponding applications and notifications are possible.

[0048] Referring to Figures 14 to 22, an example of an input / output screen when a user performs the procedure of entering reception data, including life events and identification numbers, on the front user interface computer 11 will be explained. First, the user logs in to the front user interface computer 11 from a screen like the one exemplified in Figure 14 and begins entering the reception data. Figure 14 is an example of the starting screen when a user comes to the office in person and the staff member in charge performs the input.

[0049] Once login is complete on the starting screen in Figure 14, the user will proceed to the life event selection screen shown in Figure 15. The staff member or user selects the corresponding life event and proceeds to the screen shown in Figure 16. On the screen in Figure 16, the user enters their identity verification documents (My Number Card, driver's license, other identification documents, etc.), the identity of the person performing the procedure (applicant themselves, a member of the same household, an agent, or other), and the name of the person performing the procedure, and then proceeds to the next screen shown in Figure 17. On the screen in Figure 17, the user enters the date and time of the life event that triggered the change in basic information, the date and time of notification, whether the person performing the procedure has changed their surname, etc., and then proceeds to the screen shown in Figure 18.

[0050] The screen in Figure 18 displays a list of households that match the search criteria. When a suitable household is selected from the list, the following screen in Figure 19 displays a list of the household members. From the displayed household members, the user can select the person involved in the life event in question.

[0051] On the screen shown in Figure 20, matters to be pre-interviewed regarding the application / notification of the life event are displayed, and the staff member or user answers the displayed questions. After answering the questions, the information entered up to this point is used as input information, and a display rule judgment is made. On the screen shown in Figure 21, the procedures applicable to the person or household in question regarding the life event are listed. The staff member or user selects the procedure to be performed according to the user's wishes, etc.

[0052] After making a selection and proceeding to the next step, an application information input screen like the one shown in Figure 22 will appear. There, you specify the personal information (proceduror, applicant, subject, related parties) for the procedure, and when you press the "Complete" button, the information necessary to create the procedure information is sent to the judgment engine. The judgment engine automatically generates the procedure (application / notification) information, and the generated procedure information is displayed on the screen shown in Figure 23. The procedure is completed upon final consent confirmation (electronic signature, etc.). After residents complete their procedures, the procedure data is linked to the systems of each department within the government office.

[0053] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are possible. For example, the embodiments described above are explained in detail to make the present invention easier to understand, and the present invention is not necessarily limited to embodiments having all the configurations described. Furthermore, it is possible to replace parts of the configuration of one embodiment with the configuration of another embodiment. It is also possible to add configurations from other embodiments to the configuration of one embodiment. Furthermore, it is possible to delete parts of the configuration of each embodiment, or to add or replace other configurations. [Explanation of Symbols]

[0054] 1… Information provision system 2…Terminal device 11… Computer for front user interface 12…Data Management Department 13… Judgment Engine 14…Content Management Department 131, 141... Input section 132, 142... Data storage unit 133... Section on the application of the presentation rules 134, 144… Output section 135, 145... Comparison section

Claims

1. The data management department extracts user data from departmental systems for multiple departments and manages it on a per-user basis. A user interface computer that provides a front user interface that accepts inputs about the user and provides the obtained output to the user, A content management unit manages content data that defines procedures that the user can execute, in accordance with the data managed by the aforementioned data management unit. A determination engine that, in accordance with input from the user interface computer, refers to the content data and determines the procedures that the user can execute. Equipped with, The determination engine has presentation rule data relating to presentation rules for determining whether or not to present to the user procedures that the user can perform, The aforementioned presentation rules describe the rules for determining what procedures the user can perform during each of the user's life events and what to present to the user during that life event. The determination engine receives a request that presents the user with procedures that the user may perform, without specifying the procedures the user will perform, along with an instruction that specifies the user's life events. The determination engine, by referring to the presentation rule data using the information identifying the user and the life event received, determines from the content data the procedure corresponding to the user and the life event as a procedure that the user can execute in the received life event. An information provision system characterized by the following features.

2. The determination engine has review rule data relating to the rules of the review to be performed when the user chooses to perform the procedure, The determination engine, by referring to the examination rule data using information that identifies the user, applies the examination rule data to the procedure selected by the user and determines whether the procedure has passed or failed the examination for the user. The information provision system according to claim 1.

Images