Enrollment qualification identification device and identification method

Abstract

The application discloses a registration qualification identification device and a screening method, relates to the technical field of registration information processing, and comprises an examination data access module, a qualification condition conversion module, a post portrait generation module, a related experience calculation module and an evidence anchor point output module. The post registration conditions are converted into qualification condition nodes and ability element sets, historical post information, similar post responsibility samples and proof materials are converted into post routine task portraits, the ability coverage relationship is generated to determine the related historical posts and the related experience duration, and the evidence anchor point chain and the boundary item review package are formed. The application can reduce the misjudgment risk caused by the judgment of the post name, the certificate name or the artificial experience, and improve the consistency, the interpretability and the traceability of the registration qualification screening result.

Description

Technical Field

[0001] This invention relates to the field of registration information processing technology, and more specifically, to registration eligibility identification equipment and identification methods. Background Technology

[0002] Current application qualification reviews typically involve obtaining job application requirements, applicant information, employment start and end dates, employer certifications, certificates, and other supporting documents from the application system. The system then performs field verification, or reviewers conduct manual checks. While existing methods can assess hard requirements such as education, age, and certificate validity based on explicit fields, for job requirements specifying relevant work experience or specific skills, the review process goes beyond just the employment period. It also considers whether the applicant's past job duties cover the skills required for the applied position. In practice, the names of applicants' past job titles may differ from the applied position, and some job titles are niche or industry-specific. Ordinary reviewers may find it difficult to accurately understand the typical work objects, actions, rules, and outcomes of those past positions. The existing application system typically relies on job titles, general descriptions in employer certifications, certificate names, or the experience of reviewers to determine the relevance of past positions. This can easily lead to the misclassification of experiences with similar job titles but mismatched routine tasks as relevant, or the exclusion of experiences with atypical job titles but routine tasks that cover the job's competency requirements. When application requirements further specify a certain number of years of relevant experience, the current method usually only directly combines the start and end dates of employment with manually determined job relevance. It lacks a chain of evidence linking job competency requirements, routine tasks of past positions, employment time materials, and the location of supporting documents. This results in the determination of the duration of relevant experience depending on human interpretation, unstable results in identifying boundary job experiences, and difficulty in tracing back the specific basis for determining whether a past position was relevant or irrelevant during subsequent corrections, reviews, or objection handling. Establishing an interpretable correspondence between job competency requirements and routine work content of past positions during the application qualification review process, and determining the relevance of past positions and the duration of relevant experience accordingly, so that the qualification screening results have a stable basis for judgment and traceable evidence support, is a technical problem that needs to be solved. Summary of the Invention

[0003] To overcome the aforementioned deficiencies of the prior art, this invention provides an application qualification identification device and identification method, which transforms the application qualification review from judging by job title or human experience into a traceable mapping between qualification condition nodes, a set of ability elements, a profile of routine job tasks, ability coverage relationships, and an evidence anchor chain, thereby improving the consistency, interpretability, and controllability of relevant experience identification.

[0004] To achieve the above objectives, the present invention provides the following technical solution: Registration eligibility verification equipment includes: The review data access module obtains job application requirements, job responsibilities, applicant information, historical job information, employment history materials, supporting documents, and a sample set of similar job responsibilities. It extracts applicant identifiers and job identifiers from the applicant information and job application requirements, generates application record identifiers based on these identifiers, identifies the location of supporting documents, and associates the job application requirements, job responsibilities, historical job information, employment history materials, supporting documents, supporting document locations, and the sample set of similar job responsibilities into application review data according to the application record identifiers. The qualification condition conversion module extracts the conditions that point to work experience requirements or job competency requirements from the job application conditions and job responsibility information, converts the condition content into qualification condition nodes, and extracts the competency objects, competency actions and competency results from the qualification condition nodes to generate a set of competency elements. The job profile generation module determines the target similar job responsibility samples corresponding to the historical job information based on the historical job information, sample collection of similar job responsibilities and supporting materials in the application review data. It extracts the work objects, execution actions and results corresponding to the historical jobs, and aggregates the work objects, execution actions and results according to the historical jobs to generate a job routine task profile. The relevant experience calculation module maps the capability objects, capability actions, and capability results in the capability element set to the work objects, execution actions, and results in the job routine task profile, respectively, to generate capability coverage relationships. Based on the capability coverage relationships, it determines the relevant historical positions corresponding to the qualification condition nodes, reads the employment time materials corresponding to the relevant historical positions, calculates the relevant experience duration, and compares the relevant experience duration with the experience duration requirements in the qualification condition nodes to obtain the experience duration identification results. The evidence anchor output module generates an evidence anchor chain based on the qualification condition nodes, capability element set, relevant historical positions, job routine task profiles, employment time materials, location of supporting materials, and experience duration verification results, and outputs the application qualification verification results based on the evidence anchor chain. When the capability object, capability action, or capability result does not form a corresponding field, or when the work object, execution action, or result in the job routine task profile is not associated with the location of supporting materials, a boundary item review package is generated.

[0005] Furthermore, the job profile generation module addresses the issue that historical job titles do not accurately reflect their routine work content. This module identifies target similar job responsibility samples from a set of similar job responsibility samples that correspond to historical job information, and extracts the supporting responsibilities related to the historical job and showing their location from the supporting documents. Subsequently, it extracts the work object, actions performed, and results achieved from the target similar job responsibility samples and the location-related supporting responsibilities, respectively. Fields that can be located in the supporting documents are used as the main profile fields, and fields reflecting the job's typical performance in the target similar job responsibility samples are used as supplementary profile fields. The main and supplementary profile fields under the same historical job are then deduplicated and merged to generate a routine task profile for the job. Through this process, historical jobs are no longer only reviewed by their job titles, but are transformed into a structured profile containing work objects, actions performed, results achieved, and the location of supporting documents, representing the capabilities that historical jobs can cover under normal performance conditions.

[0006] Furthermore, the relevant experience calculation module addresses the lack of a calculable correspondence between job competency requirements and the routine work content of historical positions, as well as the difficulty in consistently determining the duration of relevant experience. This module writes a set of competency elements into the condition-side field group and a profile of routine job tasks into the job-side field group. Based on consistent field types and the relationship that field content, after synonym merging or hierarchical merging, points to the same work content, it establishes object-related edges, action-related edges, and result-related edges. It then aggregates the corresponding edges formed between the same qualification condition node and the same historical position to generate competency coverage relationships, and determines the relevant experience duration based on these relationships. The relevant historical positions are identified. Based on this, the relevant experience calculation module reads the relevant historical position's corresponding tenure materials, determines the relevant tenure time period according to the application deadline, merges multiple relevant tenure time periods under the same application record identifier, and only counts the overlapping parts once to obtain the relevant experience duration. Then, the relevant experience duration is compared with the experience duration requirement in the qualification condition node to obtain the experience duration identification result. Through this process, the relevant experience is no longer judged directly by the reviewer based on experience from the job title, but is limited to the relevant historical positions by the ability coverage relationship, and the relevant historical positions inherit the tenure materials to calculate the relevant experience duration.

[0007] Furthermore, the evidence anchor point output module addresses the issues of lacking replayable evidence for registration qualification verification results and the untraceability of the boundary experience review process. This module establishes condition anchor points by linking qualification condition nodes with sets of ability elements; establishes coverage anchor points by linking corresponding edges in the ability element sets, job routine task profiles, and ability coverage relationships; and establishes job evidence anchor points by linking relevant historical job records, employment time materials, and supporting documents corresponding to those historical jobs. These anchor points are then linked in a chain according to the generation order of condition anchor points, coverage anchor points, job evidence anchor points, and experience duration verification results, generating an evidence anchor point chain. When an ability object, ability action, or ability... When the results of the effort do not form corresponding edges, or when the work objects, actions performed, or results formed to form capability coverage relationships are not associated with the location of the supporting materials, the evidence anchor output module generates uncovered capability elements and unlocated profile fields, and generates a boundary item review package accordingly. At the same time, a review anchor is established between the boundary item review package and the evidence anchor chain. Through this processing, the results of the registration qualification screening can be traced back along the qualification condition nodes, capability element sets, job routine task profiles, capability coverage relationships, employment time materials, and the location of supporting materials. The boundary item review results can also be written back to the evidence anchor chain, thereby improving the interpretability of the screening results and the controllability of the review.

[0008] The technical effects and advantages of this invention are as follows: 1. Convert job application requirements into a set of qualification criteria nodes and ability elements, convert historical job positions into job routine task profiles, and then form an evidence anchor chain to change the review from judging by job name experience to a traceable mapping, reducing the risk of misjudgment of atypical job experience. 2. Use the content of the responsibilities with location identifiers in the supporting materials as the main profile field, and use the sample of the responsibilities of similar target positions as the supplementary profile field. Combine them to generate a profile of the routine tasks of the position, so that the routine work content of niche positions has a structured basis for identification. 3. Unify the set of competency elements and the profile of routine tasks of the job into the object field, action field and result field, and establish corresponding edges to generate competency coverage relationship, so that the job competency requirements and historical routine tasks of the job form a calculable correspondence. 4. Determine the relevant historical positions based on the ability coverage relationship, then read the corresponding employment time materials to calculate the relevant experience duration, and only count the overlapping parts of multiple relevant employment time periods once to avoid irrelevant or overlapping experiences being incorrectly accumulated; 5. Establish condition anchor points, coverage anchor points, and job-related evidence anchor points to generate evidence anchor point chains. When the capability coverage is incomplete or the profile field lacks material locations, generate boundary item review packages to improve the ability to replay the screening results and the controllability of the review. Attached Figure Description

[0009] Figure 1This is a schematic diagram of the modules of the present invention; Figure 2 This is a flowchart illustrating the generation process of the relationship between the job's routine task profile and capability coverage in this invention. Figure 3 This is a flowchart illustrating the generation process of the evidence anchor chain and boundary item verification package of this invention. Detailed Implementation

[0010] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0011] Refer to the instruction manual appendix Figure 1-3 Registration eligibility verification equipment includes: Review data access module In this implementation process, taking the scenario of a unit recruiting a data review position as an example, the application requirements for this position require applicants to have more than two years of relevant experience in document review, data organization, or standardization processing; the applicants' previous positions may include positions with names that are not exactly the same as the job title, such as medical record coder, bidding specialist, and archive digitizer; the review data access module first completes the access and association of the basic data required for application review, providing a unified data foundation for subsequent qualification condition conversion, generation of job routine task profiles, calculation of ability coverage relationships, and generation of evidence anchor chain; The review data access module retrieves job application requirements, job responsibilities, applicant information, historical job information, employment history materials, supporting documents, and a sample set of similar job responsibilities. Specifically, job application requirements are the qualification requirements text recorded in the recruitment announcement, job description, or application system, including work experience requirements, job competency requirements, experience duration requirements, and application deadline. Job responsibilities information is the job description text corresponding to the advertised position, used to supplement the explanation of job competency requirements. Applicant information includes the identity information, applied position information, and historical job application information filled in by the applicant in the application system. Historical job information is recorded in the applicant's information or materials. The following information is required: the former job title, historical job category field, historical job responsibility keywords, employing unit information, and the employing unit industry field determined by the employing unit information; materials proving the employment period include labor contracts, social security records, employing unit certificates, employment documents, or other materials that can prove the start and end dates of employment; supporting materials include employing unit certificates, job descriptions, project records, deliverables, work records, or other materials that can support the content of historical job responsibilities, employment period, or deliverables; the sample set of similar job responsibilities is a pre-compiled or authorized collection of job responsibility samples, which must include at least the sample job title, sample job category field, and sample job description field. The system extracts applicant identifiers and job identifiers from the information submitted by applicants and the job application requirements. A registration record identifier is then generated based on these identifiers. Specifically, the applicant identifier is determined by the applicant's account number in the registration system, a de-identified value of their identity document number, or the applicant number assigned by the system. The job identifier is determined by the job code, job name number, or job number under the recruitment batch. The registration record identifier is generated by combining the applicant identifier and the job identifier, and is used to distinguish between different applicants applying for different positions or different application batches. After obtaining job application requirements, job responsibilities, and a sample set of similar job responsibilities, the system extracts job identifiers from the application requirements and responsibilities, and extracts sample job names, job category fields, and job description fields from the sample set. Based on historical job names, job category fields, or keywords from historical job information, the system identifies target similar job responsibilities samples from the sample set. During execution, the data access module uses historical job information as the search entry point, matching historical job names with sample job names, historical job category fields with sample job category fields, and historical job responsibility keywords with sample job descriptions. The description field is matched; when the sample job description contains the historical job name and the industry field of the employing unit is the same, or when the sample job description contains keywords of the historical job description and the sample job description field corresponds to the keywords of the historical job description, the corresponding sample is determined as the target similar job description sample, and the sample job description content is the job description text extracted from the sample job description field; for example, in the data review job application scenario, when the applicant fills in the historical job as medical record coder, the historical job description keywords include medical record homepage, coding, quality control, return and repair, statistical report, the review data access module determines the target similar job description sample corresponding to medical record coder from the similar job description sample set accordingly; After obtaining the employment time materials, the start time, end time, and employing unit fields corresponding to the historical positions are extracted from the materials, and these fields are then associated with the historical position information. Specifically, the start and end times are extracted from the date field, contract period field, start and end time field in the certificate text, or social security payment period field in the employment time materials; the employing unit field is extracted from the unit name, employer field, or certificate issuing unit field in the employment time materials. If multiple employment time materials correspond to the same historical position, the data access module reviews and associates the start time, end time, and employing unit fields in each employment time material with the historical position information. Subsequently, the relevant experience calculation module determines whether to read the corresponding employment time materials based on the relevant historical position records. After obtaining the supporting documents, the text paragraphs, image areas, table fields, or document page numbers in the supporting documents are marked with their positions to obtain the supporting document locations. A correspondence is then established between these locations and the job responsibilities, tenure, or achievement verification content within the supporting documents. Specifically, the supporting document location indicates the position of the material within the supporting documents that can be referenced by subsequent modules. When the supporting documents are text files, the supporting document location can include page numbers, paragraph numbers, or field positions. When the supporting documents are scanned copies or images, the supporting document location can include document page numbers and image area coordinates. When the supporting documents are table files, the supporting document location can include worksheet names, row and column positions, or field cell positions. The review data access module records the supporting document location simultaneously when extracting job responsibilities, tenure, or achievement verification content, enabling the subsequent job profile generation module to generate supporting responsibilities content with location associations, and also enabling the evidence anchor output module to write the supporting document location into the evidence anchor chain. The application review data is linked by the application record identifier, including job application requirements, job responsibilities, historical job information, employment history materials, supporting documents, location of supporting documents, and sample job responsibilities for similar positions. This results in application review data used for subsequent qualification conversion, job profile generation, and evidence anchor chain generation. During execution, the application review data uses the application record identifier as the primary index, creating a callable data set for the same application record, including job application requirements, job responsibilities, historical job information, employment history materials, supporting documents, location of supporting documents, and sample job responsibilities for similar positions. The qualification conversion module reads the job application requirements and job responsibilities from the application review data, the job profile generation module reads historical job information, sample job responsibilities for similar positions, and supporting documents, and the evidence anchor chain output module reads the location of supporting documents from the application review data. This ensures that subsequent modules process data corresponding to the same application record, avoiding the mixing of data from different applicants or different positions.

[0012] Eligibility Conversion Module In this implementation process, taking the scenario of a unit recruiting a data review position as an example, the application requirements for this position include more than two years of experience in document review, data organization or standardization processing; the qualification condition conversion module reads the job application conditions and job responsibility information from the aforementioned application review data, and converts the natural language conditions related to work experience requirements or job ability requirements into a set of qualification condition nodes and ability elements that can be matched with the fields of the job's regular task profile. The qualification requirement conversion module extracts experience-related phrases, ability-related phrases, job-related phrases, and achievement-related phrases from the job application requirements and job responsibilities information. Conditions containing experience-related phrases and at least one of the following phrases are identified as work experience requirements or job ability requirements. Specifically, experience-related phrases are text fragments containing terms like "full," "above," "no less than," "cumulative," "engaged in," and terms like "years" and "months." Ability-related phrases are text fragments indicating abilities such as document review, data processing, standardization, quality verification, and classification coding. Job-related phrases are text fragments indicating job responsibilities or achievements. The text fragments of work items and the output requirement fragments are text fragments that represent the output results such as the formation of review records, the organization of ledgers, coding results, quality control records, and reports. During execution, the qualification condition conversion module first segments the job application conditions and job responsibility information according to punctuation, clause number, or field label to obtain several candidate condition fragments. Then, it identifies the experience requirement fragments and the ability requirement fragments, job responsibility fragments, or output requirement fragments in the candidate condition fragments. When a candidate condition fragment simultaneously meets the condition of containing the experience requirement fragment and containing at least one of the following fragments: ability requirement fragments, job responsibility fragments, or output requirement fragments, it is determined to be the condition content pointing to the work experience requirement or job ability requirement. When converting condition content into qualification condition nodes, the module extracts the condition source location, experience duration requirement, application deadline, and ability description content corresponding to the condition content, and writes these information into the qualification condition node. The condition source location indicates the clause number, field position, page number, or paragraph position of the condition content in the job application conditions or job responsibility information. The experience duration requirement indicates the minimum required work experience duration. The application deadline defines the cutoff point for calculating the relevant experience duration. The ability description content records text in the condition content that points to job abilities or work content, excluding the experience duration requirement. During execution, the qualification condition conversion module extracts the numerical values ​​and time units containing the experience duration phrase from the condition content and converts them into experience duration requirements. It reads the application deadline from the application deadline field, announcement deadline field, or application system deadline field in the job application conditions. Finally, it writes the condition source location, experience duration requirement, application deadline, and ability description content into the same qualification condition node, ensuring that the qualification condition node simultaneously possesses the conditions source, duration requirement, and ability description foundation. Capability objects are obtained by extracting phrases pointing to the processing objects from the capability description content, capability actions are obtained by extracting phrases pointing to the execution behavior, and capability results are obtained by extracting phrases pointing to output files, processing results, or business results from the capability description content or job responsibility information. Among them, capability objects are the objects that are processed, reviewed, organized, verified, or coded in the job capability requirements, capability actions are the corresponding execution behaviors in the job capability requirements, and capability results are the output files, processing results, or business results that can be formed after the capability actions are executed. During execution, the qualification condition conversion module determines capability objects based on noun phrases in the capability description content, determines capability actions based on verb phrases, and determines capability results based on phrases indicating output, formation, generation, archiving, feedback, and reporting, and their objects. In the data review job scenario, when the condition content is more than two years of relevant experience in document review, data organization, or standardization processing, documents, data, and business materials can be used as capability objects, review, organization, and standardization processing can be used as capability actions, and review records, organized ledgers, and standardized data results can be used as capability results. The capability objects, capability actions, and capability results are associated with the same qualification condition node to generate a capability element set corresponding to the qualification condition node. Specifically, the capability objects, capability actions, and capability results extracted under the same qualification condition node are written under the same node index, and their source fields or source terms are retained, so that the capability element set can be matched with the work objects, execution actions, and results in the job routine task profile in the subsequent related experience calculation module. When there are multiple capability objects, multiple capability actions, or multiple capability results under the same qualification condition node, the qualification condition conversion module saves them separately according to the same qualification condition node, without merging them into a single text, so that the subsequent capability coverage relationship can establish object corresponding edges, action corresponding edges, and result corresponding edges item by item.

[0013] Job profile generation module In this implementation process, taking the scenario of a unit recruiting a data review position as an example, the applicant's previous positions may be positions with names that are not exactly the same as the recruitment position, such as medical record coder, bidding specialist, or archive digitizer. The position profile generation module is used to convert the previous position from the position name into a regular task profile of the position that can be matched with the set of ability elements. This implementation process relies on the previous position information, the sample set of similar position responsibilities, supporting materials and the location of supporting materials in the aforementioned application review data, and provides the position-side field foundation for the subsequent generation of ability coverage relationship. The job profile generation module extracts historical job names, employer industry fields, and historical job responsibility keywords from historical job information. It then reads target similar job responsibility samples determined by the review data access module, or selects sample job responsibility content from a set of similar job responsibility samples that meets any of the following conditions to determine the target similar job responsibility samples corresponding to the historical job: the sample job responsibility content contains the historical job name and the employer industry field is the same; or, the sample job responsibility content contains historical job responsibility keywords and the sample job responsibility description field corresponds to the historical job responsibility keywords. Here, the historical job name is the job name recorded in the applicant's historical job information, the employer industry field is the industry category field of the employer in the historical job, and the historical job responsibility keywords are selected from historical job information, certificates, and other relevant data. Keywords that characterize the routine work content of a past position are extracted from the application materials or information submitted by the applicant. During execution, the job profile generation module first searches for sample job names or sample job content in the sample set of similar job responsibilities using the past job name, and then limits the industry scope of the sample job content to the industry field of the employing unit. If the past job name does not directly match the sample job content, it continues to match the keywords of the past job responsibilities with the sample job description field. In the scenario of a unit recruiting a data review position, when the applicant's past job is a medical record coder, the keywords of the past job responsibilities can include medical record homepage, diagnosis code, surgical code, quality control return, and statistical report. The job profile generation module selects the sample job content containing the above responsibilities as the target similar job responsibility sample. The system extracts the content of proof responsibilities associated with the historical position from the supporting materials and reads the location of the supporting materials corresponding to the content of proof responsibilities to obtain the content of proof responsibilities with location association. The content of proof responsibilities is the recognition result of text, table fields or image areas in the supporting materials that record the responsibilities of the historical position, the actual matters handled, the results documents or work content. The location of the supporting materials is the location data formed by the aforementioned review data access module after marking the location of text paragraphs, image areas, table fields or document page numbers in the supporting materials. During execution, the position profile generation module retrieves the responsibility description paragraphs, results proof paragraphs or project record fields corresponding to the historical position in the supporting materials according to the historical position name, employing unit field or employment time content, and binds the responsibility description paragraphs, results proof paragraphs or project record fields to the location of the supporting materials to form the content of proof responsibilities with location association. The system extracts work objects, actions, and results from both target-like job responsibility samples and location-related certification responsibilities. The work objects, actions, and results from location-related certification responsibilities are used as primary profile fields, while those from target-like job responsibility samples are used as supplementary profile fields. Work objects are those typically processed, reviewed, organized, coded, or verified by the historical position; actions are the routine processing behaviors performed on these work objects during the historical position's duties; and results are documents, records, coding results, ledgers, reports, or business processing results generated after the actions are completed. Specifically, fields extracted from location-related certification responsibilities by the job profile generation module are supported by the location of supporting documents and are therefore used as primary profile fields. Fields extracted from target-like job responsibility samples supplement the routine work content of the historical position and are therefore used as supplementary profile fields. When the historical position is a medical record coder, the medical record cover page and treatment records can be used as work objects; verification, coding, return for repair, and statistics can be used as actions; and coding results, quality control records, and statistical reports can be used as results. The main profile field and supplementary profile field under the same historical position are deduplicated and merged to generate a regular task profile for the position. The regular task profile includes the historical position, work object, execution action, results, and the location of supporting materials corresponding to the main profile field. During execution, the position profile generation module uses the historical position as the aggregation object and assigns the main profile field and supplementary profile field under the same historical position to the work object, execution action, and results, respectively. When the main profile field and supplementary profile field have the same content or point to the same responsibility content, the main profile field and its supporting material location are retained. When the supplementary profile field does not appear in the main profile field but can represent the regular responsibility content of the historical position, the supplementary profile field is written into the regular task profile of the position. The generated regular task profile of the position includes both the job responsibility content that can be located in the supporting materials and the fields in the target similar job responsibility samples that can supplement the understanding of the regular task. In this implementation process, the job profile generation module merges historical job information, target similar job responsibility samples, and location-related certification responsibilities into a regular job task profile. This allows historical jobs to participate in the calculation of capability coverage relationships based on work objects, actions performed, results achieved, and the location of supporting materials. In application: if an applicant applies for a data review position with experience as a medical record coder, the job profile generation module first determines the target similar job responsibility samples corresponding to medical record coders from the set of similar job responsibility samples. Then, it extracts location-related certification responsibilities from unit certificates or work records. Subsequently, it aggregates fields such as the medical record cover page, treatment records, verification, coding, return for repair, coding results, and quality control records into a regular job task profile, which is then used by the relevant experience calculation module to match the fields with the capability element set corresponding to the qualification condition nodes.

[0014] Relevant experience calculation module The relevant experience calculation module takes over the aforementioned set of competency elements and the profile of routine tasks for the job, converts the competency requirements of the applied job to the routine task content of the historical job into the same field structure for comparison, and then inherits the service time materials of the historical job that forms a competency coverage relationship and calculates the relevant experience duration; first, a field correspondence relationship is formed, then the relevant historical job is determined, and finally the experience duration identification result is formed; The relevant experience calculation module writes the ability objects, ability actions, and ability results from the ability element set into the object field, action field, and result field, respectively, to obtain the condition-side field group. Among them, the condition-side field group is the structured result of the ability requirements corresponding to the qualification condition node. The object field is used to store the ability objects, the action field is used to store the ability actions, and the result field is used to store the ability results. During execution, the relevant experience calculation module reads the ability element set corresponding to the qualification condition node, writes the ability objects into the object field, writes the ability actions into the action field, and writes the ability results into the result field, so that the work experience requirements or job ability requirements originally expressed in natural language are transformed into a comparable field group. The work objects, actions, and results from the job's routine task profile are written into the object field, action field, and result field, respectively, to obtain the job-side field group. The job-side field group is the structured result of the routine tasks corresponding to the historical job. The object field is used to store the work objects, the action field is used to store the actions, and the result field is used to store the results. During execution, the relevant experience calculation module reads the job's routine task profile under the same historical job and writes the work objects, actions, and results into fields of the same type as the condition-side field group, so that the routine work content of the historical job can correspond to the set of ability elements in the qualification condition node according to the field type. Fields with the same field type in the conditional field group and the job-side field group, and whose content is based on job responsibility information, similar job responsibility samples, and job responsibility content in supporting materials, are merged synonymously or hierarchically to point to the same work content. Corresponding edges are established between fields that are the same type in both the conditional field group and the job-side field group, belonging to the same field type in object fields, action fields, or result fields. During execution, the relevant experience calculation module first limits the comparison between similar fields, and then determines whether the field content points to the same work content based on job responsibility information, similar job responsibility samples, and job responsibility content in supporting materials. Corresponding edges are established between fields that meet this condition. In the data review job scenario, the data on the conditional side and the medical record cover and treatment records on the job side can be merged hierarchically based on the data processing objects. The review on the conditional side and the verification and quality control on the job side can be merged synonymously or hierarchically based on the review execution behavior. In the relevant experience calculation module, synonym merging is used to group different expressions pointing to the same work content into the same field, and hierarchical merging is used to group lower-level work content into corresponding higher-level work content. Synonymous merging handles situations where different textual expressions have the same work content, while hierarchical merging handles situations where qualification condition nodes use higher-level ability requirements while the job's routine task profile uses lower-level specific tasks. During execution, the relevant experience calculation module uses job responsibility information, target similar job responsibility samples, and job responsibility content in supporting materials as the merging basis, not solely based on word surface similarity. Corresponding edges include object-corresponding edges, action-corresponding edges, and result-corresponding edges. Object-corresponding edges connect ability objects and work objects, action-corresponding edges connect ability actions and performed actions, and result-corresponding edges connect ability results and formed results. During execution, the relevant experience calculation module saves the correspondences formed under different field types separately, enabling subsequent statistical analysis of the coverage of the same qualification condition node and the same historical job at the object, action, and result levels. The object-related edges, action-related edges, and result-related edges formed between the same qualification condition node and the same historical position are aggregated to generate the capability coverage relationship between the qualification condition node and the historical position. The capability coverage relationship is used to represent the coverage status of the capability element set in the qualification condition node by the regular task profile of the historical position. During the calculation, the relevant experience calculation module uses the qualification condition node and the historical position as the combinatorial key to aggregate the object-related edges, action-related edges, and result-related edges already formed under the combinatorial key. The aggregation result is used as the capability coverage relationship between the qualification condition node and the historical position. Based on the capability coverage relationship, the corresponding object edge, action edge, and result edge for the same historical position are counted. Specifically, the relevant experience calculation module counts whether each historical position has formed an object edge, action edge, and result edge under each qualification condition node, and records the capability element set field and the job routine task profile field pointed to by each edge. The statistical results are used to distinguish between relevant historical positions and the set of historical positions to be reviewed. In the relevant experience calculation module, when a historical position and a qualification condition node simultaneously have object-corresponding edges, action-corresponding edges, and result-corresponding edges, the historical position is identified as a relevant historical position. A relevant historical position is one whose routine task profile covers the set of capability elements corresponding to the qualification condition node at the object, action, and result levels. During execution, the relevant experience calculation module does not use whether the historical position name is the same as the recruitment position name as the basis for relevance, but rather uses the simultaneous existence of the three types of corresponding edges in the capability coverage relationship as the basis for determination. When a historical position lacks any one of the object-corresponding edge, action-corresponding edge, or result-corresponding edge between it and a qualification condition node, the historical position is added to the set of historical positions pending review. This set of historical positions pending review is used to store historical positions that have not formed a complete capability coverage relationship but may still have boundary correspondences. During execution, the relevant experience calculation module records the types of missing corresponding edges, enabling the evidence anchor output module to generate a review package of uncovered capability elements and boundary items. The relevant historical positions, qualification condition nodes, and corresponding edges that form capability coverage relationships are associated and saved to obtain relevant historical position records. Among them, relevant historical position records are used to connect relevant historical positions with their corresponding qualification condition nodes and corresponding edges of objects, actions, and results. During execution, the relevant experience calculation module uses relevant historical position records as the basis for subsequent reading of employment time materials, avoiding the direct inclusion of employment time of historical positions that have not formed capability coverage relationships into the relevant experience duration. The module retrieves the relevant historical job records and their associated tenure information. It then extracts the start and end dates of the tenure from these records and retrieves the application deadline from the eligibility criteria node. The start and end dates are derived from the tenure information associated with the relevant historical job, while the application deadline is derived from the eligibility criteria node. During execution, the relevant experience calculation module only reads the tenure information linked to the relevant historical job records and does not read the tenure information of the pending historical job set or unrelated historical jobs for relevant experience duration calculation. The relevant work period is generated based on the start time, end time, and application deadline. During the calculation, the relevant experience calculation module uses the start time as the starting point of the relevant work period and the end time as the application deadline to determine the end time. If the start time is later than the application deadline, the work period data will not be generated as a relevant work period to be counted. If the start time is not later than the application deadline, the relevant experience calculation module will continue to determine the end time of the relevant work period. In the relevant experience calculation module, when the end time of employment is empty or later than the application deadline, the application deadline will be used as the end time of the relevant employment period. Here, an empty end time of employment means that the employment period is recorded as to date, currently employed, or no end date is recorded. When calculating, the relevant experience calculation module does not change the original end time of employment in the employment period materials, but only uses the application deadline as the calculation endpoint when calculating the relevant employment period, so that the calculation of the relevant experience duration is consistent with the application deadline in the qualification condition node. When the same registration record identifier corresponds to multiple related historical positions, the multiple related employment periods are merged, and the overlapping part is counted only once to obtain the relevant experience duration. During the calculation, the relevant experience calculation module arranges multiple related employment periods in chronological order, retains only one time for overlapping time intervals, and then calculates the merged total duration according to the time unit required by the experience duration in the qualification condition node. If there are two related historical positions under the same registration record identifier, one of which is from January 2021 to June 2023, and the other is from May 2022 to January 2024, then the overlapping part from May 2022 to June 2023 is counted only once. The experience duration requirement is retrieved from the qualification condition node, and the relevant experience duration is compared with the experience duration requirement. The experience duration requirement is the minimum experience duration requirement extracted from the condition content by the qualification condition conversion module. During calculation, the relevant experience calculation module converts the relevant experience duration into a unit of measurement consistent with the experience duration requirement before comparison. If the experience duration requirement is in years, when calculated by days, it is accumulated based on the number of natural days covered by the relevant employment period; when calculated by months, it is accumulated based on the complete natural month or the monthly conversion method specified by the registration system; when the relevant experience duration is converted into years, the conversion method uniformly adopted under the same registration record identifier is used. In the relevant experience calculation module, when the relevant experience duration is not less than the experience duration requirement, an experience duration satisfaction result is generated; when the relevant experience duration is less than the experience duration requirement, an experience duration insufficiency result is generated. The experience duration satisfaction result or experience duration insufficiency result is used as the experience duration screening result. The experience duration screening result is used to indicate whether the cumulative working time corresponding to the relevant historical position meets the experience duration requirement in the qualification condition node. During execution, the relevant experience calculation module associates and saves the experience duration screening result with the qualification condition node, relevant historical position records, and relevant working time periods, so that the evidence anchor output module can generate the evidence anchor chain. In this implementation process, the relevant experience calculation module converts the field correspondence between the set of ability elements and the routine task profile of the position into an ability coverage relationship. This ability coverage relationship then limits the relevant historical positions. The relevant historical positions then read the employment time materials to calculate the relevant experience duration, thus ensuring that the experience duration identification result no longer directly depends on the job name or total employment time. In application: When an applicant applies for a data review position in a unit with experience as a medical record coder, the relevant experience calculation module first writes the ability objects, ability actions, and ability results of the data review position into the condition-side field group. Then, it writes the work objects, execution actions, and results from the routine task profile of the medical record coder position into the position-side field group. When the medical record cover page, treatment records, and data form an object correspondence, and verification, coding, quality control, and review, organization, and standardization processing form an action correspondence, and coding results, quality control records, statistical reports, and review records and standardized data results form a result correspondence, the medical record coder position is identified as a relevant historical position. The relevant experience duration is then calculated based on the corresponding employment time materials, and the experience duration identification result is output.

[0015] Evidence Anchor Output Module The evidence anchor output module takes the capability coverage relationship, relevant historical job records, and experience duration verification results generated by the relevant experience calculation module, and organizes the qualification condition nodes, capability element sets, job routine task profiles, employment time materials, and supporting material locations into an evidence anchor chain that can be replayed. When the capability coverage relationship is incomplete or the profile field lacks supporting material locations, the evidence anchor output module generates a boundary item review package and writes the review results back to the evidence anchor chain through the review anchor. The evidence anchor output module reads qualification condition nodes, competency element sets, relevant historical job records, job routine task profiles, employment time materials, the location of supporting documents corresponding to relevant historical jobs, relevant experience duration, and experience duration verification results. Among them, qualification condition nodes and competency element sets come from the qualification condition conversion module, relevant historical job records, competency coverage relationships, and experience duration verification results come from the relevant experience calculation module, and job routine task profiles and supporting document locations come from the job profile generation module and review data access module. During execution, the evidence anchor output module uses the registration record identifier as an index to read data that has already formed a corresponding relationship under the same registration record, avoiding writing the supporting document locations of other applicants or other positions into the current verification link. Condition anchors are established by linking qualification condition nodes with sets of competency elements. Coverage anchors are established by linking the corresponding edges in the competency element sets, job routine task profiles, and competency coverage relationships. Job evidence anchors are established by linking the locations of relevant historical job records, tenure time materials, and supporting documents corresponding to relevant historical jobs. Condition anchors record the correspondence between qualification condition nodes and competency objects, competency actions, and competency results. Coverage anchors record the coverage relationship between the competency element sets and job routine task profiles through object-corresponding edges, action-corresponding edges, and result-corresponding edges. Job evidence anchors record the evidence correspondence between relevant historical jobs, tenure time materials, and supporting document locations. During execution, the evidence anchor output module first uses the qualification condition node as the root anchor node, then writes the competency element sets, corresponding edges, job routine task profiles, relevant historical job records, tenure time materials, and supporting document locations into the corresponding anchors according to their data source relationships. The evidence anchor chain is generated by linking the condition anchors, coverage anchors, job evidence anchors, and experience duration verification results in a chain. The evidence anchor chain is a data chain representing the generation path of the application qualification verification results. The chain order is consistent with the dependencies between qualification condition nodes, capability coverage relationships, relevant historical job records, employment time materials, and experience duration verification results. During execution, the evidence anchor output module uses the condition anchors as the starting point of the chain, connects the coverage anchors to the corresponding capability element set, connects the job evidence anchors to the relevant historical job records that form capability coverage relationships, and then connects the experience duration verification results to the corresponding employment time materials and relevant experience duration, ensuring that each verification conclusion can be traced back to the qualification condition node and supporting material location. The application eligibility verification results are output based on the evidence anchor chain. These results include eligibility condition nodes, relevant historical positions, relevant experience duration, experience duration verification results, and the location of corresponding supporting documents. During execution, the evidence anchor output module reads data that has formed a complete chain of relationships from the evidence anchor chain and generates the corresponding application eligibility verification results. When the experience duration verification result indicates that the experience duration is met, the application eligibility verification results record that the experience duration requirement in the eligibility condition node is met. When the experience duration verification result indicates that the experience duration is insufficient, the application eligibility verification results record that the relevant experience duration is insufficient and retain the location of the corresponding relevant historical positions and supporting documents. The system reads capability coverage relationships, job routine task profiles, relevant historical job records, and a set of historical jobs awaiting review. The set of historical jobs awaiting review is formed by the relevant experience calculation module when a historical job lacks any of the following types of corresponding edges: object corresponding edge, action corresponding edge, or result corresponding edge. During execution, the evidence anchor point output module reads the set of historical jobs awaiting review along with capability coverage relationships and job routine task profiles to determine whether a boundary item review package needs to be generated. In the evidence anchor output module, when a capability object, capability action, or capability result does not form a corresponding edge in the capability coverage relationship, an uncovered capability element is generated. This uncovered capability element refers to the capability object, capability action, or capability result in the capability element set corresponding to the qualification condition node that is not yet covered by the job's regular task profile. During execution, the evidence anchor output module reads capability objects, capability actions, and capability results item by item from the capability element set and checks whether there are corresponding object-corresponding edges, action-corresponding edges, or result-corresponding edges in the capability coverage relationship. Fields without corresponding edges are written into the uncovered capability element. When the work object, execution action, or result formed in the job's regular task profile used to form the capability coverage relationship is not associated with the supporting material location, an unlocated profile field is generated. This unlocated profile field refers to the job's regular task profile field that has participated in the capability coverage relationship judgment but lacks supporting material location. During execution, the evidence anchor output module does not generate unlocated profile fields for all supplementary profile fields, but only checks the work object, execution action, or result formed to form object-corresponding edges, action-corresponding edges, or result-corresponding edges. If the field is not associated with the supporting material location, it is written into the unlocated profile field. A boundary item review package is generated based on qualification condition nodes, uncovered capability elements, relevant historical job records, a set of historical jobs to be reviewed, job routine task profiles, the location of associated supporting documents, and unlocated profile fields. Review anchors are then established between the boundary item review package and the qualification condition nodes, capability element sets, and job routine task profiles in the evidence anchor chain. The boundary item review package is used to handle data requiring review when capability coverage is incomplete or the job routine task profile lacks supporting document locations. Review anchors are used to incorporate the boundary item review package into the evidence anchor chain. During execution, the evidence anchor output module points uncovered capability elements to the corresponding capability element set, unlocated profile fields to the corresponding job routine task profile, and associates the set of historical jobs to be reviewed with the qualification condition nodes, forming a boundary item review package that can be reviewed and written back. The system receives the review results for the boundary item review package, writes the review results into the review anchor point, and updates the registration qualification screening results based on the evidence anchor point chain after writing the review results. The review results are confirmation results for uncovered capability elements, unlocated profile fields, or sets of historical positions to be reviewed. The review results include at least one of the following: confirmed coverage, confirmed non-coverage, supplementary supporting materials location, or maintaining the pending review status. During execution, the evidence anchor point output module writes the review results into the review anchor point, so that the review results are linked with the qualification condition node, capability element set, job routine task profile, and supporting material location. Then, the registration qualification screening results are re-determined based on the updated evidence anchor point chain. In this implementation process, the evidence anchor output module organizes qualification condition nodes, capability element sets, job routine task profiles, capability coverage relationships, relevant historical job records, employment time materials, and supporting material locations into an evidence anchor chain. When boundary items exist, the review path is preserved through boundary item review packages and review anchors. In application: when an applicant applies for a data review position in a certain unit with experience as a medical record coder, the evidence anchor output module links the data review-related qualification condition nodes, the medical record coder job routine task profile, object corresponding edges, action corresponding edges, result corresponding edges, employment time materials, and supporting material locations in a chain. If the quality control record in the medical record coder job routine task profile has participated in the result corresponding edge but lacks supporting material locations, the evidence anchor output module generates an unlocated profile field and forms a boundary item review package. After receiving the review results, it writes them into the review anchor and then updates the application qualification screening results.

[0016] Furthermore, the present invention also discloses a method for verifying the eligibility of applicants for the aforementioned equipment, comprising: S1. Obtain job application requirements, job responsibilities, applicant information, historical job information, employment history materials, supporting documents, and a sample set of similar job responsibilities. Extract applicant identifiers and job identifiers from the applicant information and job application requirements. Generate application record identifiers based on the applicant identifiers and job identifiers. Identify the location of supporting documents by marking their positions. Then, associate the job application requirements, job responsibilities, historical job information, employment history materials, supporting documents, supporting document locations, and the sample set of similar job responsibilities into application review data according to the application record identifiers. S2. Extract the conditions that point to the work experience requirements or job competency requirements from the job application conditions and job responsibility information, convert the conditions into qualification condition nodes, and extract the competency objects, competency actions and competency results from the qualification condition nodes to generate a set of competency elements. S3. Based on the historical job information, sample set of similar job responsibilities and supporting materials in the application review data, determine the target similar job responsibility sample corresponding to the historical job information, extract the work objects, execution actions and results corresponding to the historical positions, and aggregate the work objects, execution actions and results according to the historical positions to generate a job routine task profile; S4. Match the capability objects, capability actions, and capability results in the capability element set with the work objects, execution actions, and results in the job routine task profile to generate capability coverage relationships; determine the relevant historical positions corresponding to the qualification condition nodes based on the capability coverage relationships, read the relevant historical position's tenure materials, calculate the relevant experience duration, and compare the relevant experience duration with the experience duration requirements in the qualification condition nodes to obtain the experience duration identification results; S5. Generate an evidence anchor chain based on the qualification condition nodes, capability element set, relevant historical positions, job routine task profile, employment time materials, location of supporting materials, and experience duration, and output the application qualification verification results based on the evidence anchor chain; when the capability object, capability action, or capability result does not form a corresponding field, or the work object, execution action, or result in the job routine task profile is not associated with the location of supporting materials, generate a boundary item review package.

[0017] The above description is merely a preferred embodiment of the present invention and does not limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A registration eligibility recognition device, characterized in that, include: The review data access module obtains job application requirements, job responsibilities, applicant information, historical job information, employment history materials, supporting documents, and a sample set of similar job responsibilities. It extracts applicant identifiers and job identifiers from the applicant information and job application requirements, generates application record identifiers based on these identifiers, identifies the location of supporting documents, and associates the job application requirements, job responsibilities, historical job information, employment history materials, supporting documents, supporting document locations, and the sample set of similar job responsibilities into application review data according to the application record identifiers. The qualification condition conversion module extracts the conditions that point to work experience requirements or job competency requirements from the job application conditions and job responsibility information, converts the condition content into qualification condition nodes, and extracts the competency objects, competency actions and competency results from the qualification condition nodes to generate a set of competency elements. The job profile generation module determines the target similar job responsibility samples corresponding to the historical job information based on the historical job information, sample collection of similar job responsibilities and supporting materials in the application review data. It extracts the work objects, execution actions and results corresponding to the historical jobs, and aggregates the work objects, execution actions and results according to the historical jobs to generate a job routine task profile. The relevant experience calculation module maps the capability objects, capability actions, and capability results in the capability element set to the work objects, execution actions, and results in the job routine task profile, respectively, to generate capability coverage relationships. Based on the capability coverage relationships, it determines the relevant historical positions corresponding to the qualification condition nodes, reads the employment time materials corresponding to the relevant historical positions, calculates the relevant experience duration, and compares the relevant experience duration with the experience duration requirements in the qualification condition nodes to obtain the experience duration identification results. The evidence anchor output module generates an evidence anchor chain based on the qualification condition nodes, capability element set, relevant historical positions, job routine task profiles, employment time materials, location of supporting materials, and experience duration verification results, and outputs the application qualification verification results based on the evidence anchor chain. When the capability object, capability action, or capability result does not form a corresponding field, or when the work object, execution action, or result in the job routine task profile is not associated with the location of supporting materials, a boundary item review package is generated.

2. The registration eligibility identification device according to claim 1, characterized in that, In the review data access module, after obtaining the job application conditions, job responsibility information and a sample set of similar job responsibilities, the module extracts the job identifier from the job application conditions and job responsibility information, extracts the sample job name, sample job category field and sample responsibility description field from the sample set of similar job responsibilities, and determines the target similar job responsibility sample from the sample set of similar job responsibilities based on the historical job name, historical job category field or historical job responsibility keywords in the historical job information. After obtaining the employment time materials, extract the employment start time, employment end time and employing unit fields corresponding to the historical positions from the employment time materials, and associate the employment start time, employment end time and employing unit fields with the historical position information; After obtaining the supporting documents, the text paragraphs, image areas, table fields or document page numbers in the supporting documents are marked to obtain the location of the supporting documents, and a correspondence is established between the location of the supporting documents and the job responsibilities, tenure or achievement certification content in the supporting documents. The application record identifier is used to link the job application requirements, job responsibilities, historical job information, employment time materials, supporting documents, location of supporting documents, and similar job responsibilities samples to obtain application review data for subsequent qualification conversion, generation of job routine task profiles, and generation of evidence anchor chain.

3. The registration eligibility identification device according to claim 1, characterized in that, In the qualification condition conversion module, the experience requirement segment, ability requirement segment, job responsibility segment, and achievement requirement segment are extracted from the job application conditions and job responsibility information. The condition content that contains the experience requirement segment and at least one of the ability requirement segment, job responsibility segment, or achievement requirement segment is identified as the condition content that points to the work experience requirement or job ability requirement. When converting condition content into qualification condition nodes, extract the condition source location, experience duration requirement, application deadline and ability description content corresponding to the condition content, and write the condition source location, experience duration requirement, application deadline and ability description content into the qualification condition node. Capability objects are obtained by extracting phrases pointing to the processing objects from the capability description content, capability actions are obtained by extracting phrases pointing to the execution behavior, and capability results are obtained by extracting phrases pointing to output files, processing results, or business results from the capability description content or job responsibility information. Associate capability objects, capability actions, and capability results according to the same qualification condition node to generate a set of capability elements corresponding to the qualification condition node.

4. The registration eligibility identification device according to claim 1, characterized in that, In the job profile generation module, the historical job name, employing unit industry field, and historical job responsibility keywords are extracted from the historical job information. Sample job content that meets any of the following conditions is selected from the sample set of similar job responsibilities to obtain the target similar job responsibility sample corresponding to the historical job: the sample job content contains the historical job name and the employing unit industry field is the same; or, the sample job content contains historical job responsibility keywords and the sample job description field corresponds to the historical job responsibility keywords. Extract the content of proof responsibilities associated with the historical position from the supporting materials, and read the location of the supporting materials corresponding to the content of proof responsibilities to obtain the content of proof responsibilities with location association; The work objects, actions, and results are extracted from the target similar job responsibility samples and the proof responsibility content with location association, respectively. The work objects, actions, and results from the proof responsibility content with location association are used as the main profile fields, and the work objects, actions, and results from the target similar job responsibility samples are used as supplementary profile fields. The main profile field and supplementary profile field under the same historical position are deduplicated and merged to generate a regular task profile for the position. The regular task profile for the position includes the historical position, work object, execution action, results, and the location of supporting materials corresponding to the main profile field.

5. The registration qualification identification device according to claim 1, characterized in that, In the relevant experience calculation module, the ability objects, ability actions and ability results in the ability element set are written into the object field, action field and result field respectively to obtain the conditional field group. Write the work object, the action to be performed, and the result to be formed in the job routine task profile into the object field, action field, and result field, respectively, to obtain the job-side field group; Fields with the same field type in the condition-side field group and the job-side field group, and whose content is based on job responsibility information, similar job responsibility samples, and job responsibility content in supporting materials, are combined using synonym merging or hierarchical merging to point to the same job content. Corresponding edges are established for fields that are the same job content. Synonymous merging is used to group different expressions pointing to the same job content into the same field, and hierarchical merging is used to group lower-level job content into corresponding higher-level job content. Corresponding edges include object corresponding edges, action corresponding edges, and result corresponding edges. Aggregate the object-corresponding edges, action-corresponding edges, and result-corresponding edges formed between the same qualification condition node and the same historical position to generate the capability coverage relationship between the qualification condition node and the historical position.

6. The registration qualification identification device according to claim 5, characterized in that, In the relevant experience calculation module, the corresponding edges of objects, actions, and results for the same historical position are counted according to the ability coverage relationship. When there are object-corresponding edges, action-corresponding edges, and result-corresponding edges between a historical position and a qualification condition node, the historical position is identified as a relevant historical position. When a historical post is missing any of the following types of corresponding edges: object, action, or result, it will be added to the set of historical posts pending review. The relevant historical positions, qualification condition nodes, and corresponding edges that form capability coverage relationships are associated and saved to obtain the relevant historical position records.

7. The registration qualification identification device according to claim 6, characterized in that, In the relevant experience calculation module, the relevant historical position records are read to obtain the relevant historical position time materials, the start time and end time of the relevant historical position are extracted from the historical position time materials, and the application deadline is read from the qualification conditions node. The relevant employment period is generated based on the start time, end time, and application deadline. When the end time is empty or later than the application deadline, the application deadline is used as the end time of the relevant employment period. When the same registration record identifier corresponds to multiple related historical positions, the multiple related employment periods are merged, and the overlapping parts are counted once to obtain the relevant experience duration; Read the experience duration requirement from the eligibility criteria node, and compare the relevant experience duration with the experience duration requirement; When the relevant experience duration is not less than the experience duration requirement, an experience duration satisfaction result is generated; when the relevant experience duration is less than the experience duration requirement, an experience duration insufficiency result is generated, and the experience duration satisfaction result or experience duration insufficiency result is used as the experience duration screening result.

8. The registration qualification identification device according to claim 7, characterized in that, The evidence anchor output module reads qualification condition nodes, ability element sets, relevant historical job records, job routine task profiles, tenure time materials, the location of supporting materials corresponding to relevant historical jobs, relevant experience duration and experience duration identification results. Establish condition anchor points by connecting qualification condition nodes with sets of ability elements, establish coverage anchor points by connecting corresponding edges in sets of ability elements, job routine task profiles and ability coverage relationships, and establish job evidence anchor points by connecting the positions of relevant historical job records, tenure materials and supporting materials corresponding to relevant historical jobs. The evidence anchor chain is generated by linking the condition anchors, coverage anchors, job evidence anchors, and experience duration identification results in a chain. The results of the registration qualification verification are output based on the evidence anchor chain. The registration qualification verification results include qualification condition nodes, relevant historical positions, relevant experience duration, experience duration verification results, and the location of corresponding supporting materials.

9. The registration qualification identification device according to claim 8, characterized in that, The evidence anchor output module includes reading capability coverage relationships, job routine task profiles, relevant historical job records, and a set of historical jobs pending review. When a capability object, capability action, or capability result does not form a corresponding edge in the capability coverage relationship, an uncovered capability element is generated. When the work objects, actions, or results used to form capability coverage relationships in the job routine task profile are not associated with the location of the supporting materials, an unlocated profile field is generated. Based on the qualification condition nodes, uncovered capability elements, relevant historical job records, set of historical jobs to be reviewed, job routine task profiles, location of associated supporting materials, and unlocated profile fields, a boundary item review package is generated, and a review anchor point is established between the boundary item review package and the qualification condition nodes, capability element sets, and job routine task profiles in the evidence anchor point chain. Receive the review results for the boundary item review package, write the review results into the review anchor, and update the registration qualification screening results based on the evidence anchor chain after writing the review results.

10. A method for verifying registration eligibility, applied to the registration eligibility identification device according to any one of claims 1 to 9, characterized in that, include: S1. Obtain job application requirements, job responsibilities, applicant information, historical job information, employment history materials, supporting documents, and a sample set of similar job responsibilities. Extract applicant identifiers and job identifiers from the applicant information and job application requirements. Generate application record identifiers based on the applicant identifiers and job identifiers. Identify the location of supporting documents by marking their positions. Then, associate the job application requirements, job responsibilities, historical job information, employment history materials, supporting documents, supporting document locations, and the sample set of similar job responsibilities into application review data according to the application record identifiers. S2. Extract the conditions that point to the work experience requirements or job competency requirements from the job application conditions and job responsibility information, convert the conditions into qualification condition nodes, and extract the competency objects, competency actions and competency results from the qualification condition nodes to generate a set of competency elements. S3. Based on the historical job information, sample set of similar job responsibilities and supporting materials in the application review data, determine the target similar job responsibility sample corresponding to the historical job information, extract the work objects, execution actions and results corresponding to the historical positions, and aggregate the work objects, execution actions and results according to the historical positions to generate a job routine task profile; S4. Match the capability objects, capability actions, and capability results in the capability element set with the work objects, execution actions, and results in the job routine task profile to generate capability coverage relationships; determine the relevant historical positions corresponding to the qualification condition nodes based on the capability coverage relationships, read the relevant historical position's tenure materials, calculate the relevant experience duration, and compare the relevant experience duration with the experience duration requirements in the qualification condition nodes to obtain the experience duration identification results; S5. Generate an evidence anchor chain based on the qualification condition nodes, capability element set, relevant historical positions, job routine task profile, employment time materials, location of supporting materials, and experience duration, and output the application qualification verification results based on the evidence anchor chain; when the capability object, capability action, or capability result does not form a corresponding field, or the work object, execution action, or result in the job routine task profile is not associated with the location of supporting materials, generate a boundary item review package.

Images