Skip to main content

This page has been translated using TexTra by NICT. Please note that the translation may not be completely accurate.
If you find any mistranslations, we appreciate your feedback on the "Request form for improving the automatic translation ".

Application Management Working Team (1st) of the Review Meeting on Technical Requirements for Common Functions, etc. on the Unification and Standardization of core business systems in local governments

Overview

  • Date and Time: Friday, November 4, 2022 (2022) from 3:00 p.m. to 4:50 p.m.
  • Location: Online Meeting
  • Agenda:
    1. Opening
    2. Agenda
      1. Study Overview
      2. Issue on Application Management
    3. Other
    4. Adjournment

Materials

Relevant policies

Summary of proceedings

Date

From 3:00 p.m. to 4:50 p.m. on Friday, November 4, 2022 (2022)

Location

Online Meetings

Summary of proceedings

1. Outline of the review

  • No particular discussion

2. Issue on Application Management

1. Necessity of individual APIs for procedures for which presets are specified in the Just Service
1.1.1 Need for Specification of Individual APIs Corresponding to Just Services

Observer: approach, there is no objection to making the API, which is the endpoint from application management to core business systems, general-purpose. On the other hand, in considering the purpose of standardization and consistency with cooperation requirements, it is considered that responses should be organized at the item level, not limited to the presence or absence of presets. In other words, it is considered that what kind of data can be managed by core business systems should be organized, and what kind of data should be received from application management should be organized. It is also necessary to consider the viewpoint that there is a difference between the items required for application and examination and the items to be taken into core business systems.
Secretariat: After confirming the content of the requirements applicable to As you are aware, we are considering listing the linkage between preset application data items and management items in the basic data list as a reference for preset items as described in 1.1.2. In addition, we plan to separately consider the linkage method, etc. for items without presets and procedures as original measures, and present them next time or later.

1.1.2 Organizing the correspondence between the perfect service and core business systems items

Observer: item should be defined as a binding linkage requirement, not a reference.
Secretariat: After confirming the content of the requirements applicable to I understand. We will consider it based on the comments received.

2. Resolution of questions and shortages of specifications related to application management
2.1.1 Operational Flow and Functional Requirements for Application Management

Member: In the explanation by the Is it assumed that one common operation flow is created for each procedure or created for each procedure? has a description of "for each procedure."
Secretariat: After confirming the content of the requirements applicable to will be provided. Regarding 3.2.1., which you pointed out, it is assumed that it will be examined together with , and it is not planned to respond until the twenty twenty-five, which is the transition support period.

2.1.2 Specification of operation flow and functional requirements for exception patterns for application management

Member: In the explanation by the As an exception pattern, not only withdrawal, but also modification of the content of the application or response to the case where the data cannot be acquired within the retention period under the Fit-to-Suit Service is assumed.
Secretariat: After confirming the content of the requirements applicable to I understand. We will consider it based on the comments received.
Member: In the explanation by the Actions to be taken when an applicant unintentionally files an application twice (double registration) should also be considered.
Secretariat: After confirming the content of the requirements applicable to I understand. We will consider it based on the comments received.

2.1.3 Sorting out the division of roles and flow of the entire online application

Observer: Application Management Function? The Ministry of Internal Affairs and Communications Specifications specify a function to display application data and attached documents in a viewer.
Secretariat: After confirming the content of the requirements applicable to application management function is assumed to be the linking of address numbers and format examination.
Observer: Long-Term Care Insurance, are expected to be reviewed by core business systems. However, it is considered that the implementation of whether or not the necessary items, which are performed at the time of receipt at the counter, are described is performed by the application management function. On the other hand, it is necessary to consider whether or not the business approval authority can perform the review in the application management function.
Secretariat: After confirming the content of the requirements applicable to Long-Term Care Insurance are also assumed. As a basic idea, it is assumed that the same functions as the Ministry of Internal Affairs and Communications Specifications are specified as the minimum functional requirements as the standard specifications of the common functions, and it is requested that the division of roles in each system be recognized as unchanged.
Observer: specifications after the functional requirements, etc. of the Ministry of Internal Affairs and Communications application management function are specified?
Secretariat: After confirming the content of the requirements applicable to Ministry of Internal Affairs and Communications Specifications and the Common Function Specifications, would make it difficult to understand. Continued consideration will be given to the handling of documents in an easy-to-read form.

2.1.4 Clarification of core business systems's response at the time of receipt of application data

Member: In the explanation by the study will be reflected in the horizontal adjustment policies. When do you expect the revision of the standard specifications for each core business systems?
The Secretariat rough schedule is under consideration, but based on your comments, we would like to consult and coordinate with the relevant ministries and agencies so that the plan will be ready in time for the revision at the end of the fiscal year.

2.1.5 Clarification of differential data acquisition specifications ("acquisition target date" and "acquisition target time")

Observer: As discussed in WT, there is a possibility that there may be discrepancies in recognition between business operators, such as the date and time of application, the date and time of loading the application management function, and the time to write to the database, so we think that the definition of terms should be clarified.
Secretariat: After confirming the content of the requirements applicable to I understand. We will consider it based on the comments received.

2.1.7 Clarification of policies for the use of IFs in accordance with the Ministry of Internal Affairs and Communications Specifications

Member: In the explanation by the as a implementation handling function, is it correct to understand that file cooperation is not essential for cooperation with the resident record system?
Secretariat: After confirming the content of the requirements applicable to As you know, file linkage is possible as a transitional response, and is not required as an essential response.

2.2.5 Expected use of request parameters of the application data inquiry API

Observer: Action Plan (draft), is it assumed that access control is performed in API authentication and subsequent control is performed by the application management function?
Secretariat: After confirming the content of the requirements applicable to Since consideration of this point was insufficient, we would like to consider it again and present a policy.

3. Optimize cooperation between the application management function and the core business systems
3.1.1 Addition of application processing status registration API

Member: In the explanation by the application processing status is not within the scope of the revision of the standard specifications for common functions at the end of FY 2025?
Secretariat: After confirming the content of the requirements applicable to As you know.
Member: In the explanation by the In the Horizontal Adjustment Guidelines, it is stated that "the acquired items, etc. can be displayed, output, etc.", but is it sufficient to display the items acquired from the application management function on the screen?
Secretariat: After confirming the content of the requirements applicable to has been obtained or the results of examination in core business systems, etc., and it is assumed that the application processing status will be registered in the application management function using this function.
Member: In the explanation by the Secretariat, it was explained that the standard specifications for the application processing status registration API will not be formulated until the end of FY 2025. On the other hand, it is recognized that the requirement for the moving OSS in the resident record system is that the examination results can be returned to the application management. Is it correct to understand that this point does not fall within the scope of the transition deadline of the twenty twenty-five as the same rough schedule as other core business systems? implementation
Secretariat: After confirming the content of the requirements applicable to , consider the description so that it will be consistent as a whole, including the horizontal alignment adjustment policies.
Observer: It is considered that the unclear points will be resolved when the division of responsibility between the application management and the core business side is arranged and made into a flow. Regarding the Moving OSS, it is considered that the fact that the acceptance of applications is assumed to be implemented in the resident record system is the cause of the incomprehensibility, so it is desirable to organize the flow of that point.
Secretariat: After confirming the content of the requirements applicable to I understand. We will consider it based on the comments received.

3. Other

  • No particular discussion

End