What this category's data looks like
Materials for continuing education credit hour recognition usually fall into three categories: course filing forms, study certificates, and credit hour recognition forms. The course filing form is submitted by the training provider before the course starts, and its fields include the course name, number of class hours, course start date, instructor signature, and filing receipt; the study certificate is obtained by the learner after completing the study, and its fields include the course name, study start and end dates, actual credit hours, and the issuing unit's seal; the credit hour recognition form is compiled and filled in by the recognition agency, and its fields include the person identifier, course name, recognized credit hours, recognition date, and reviewer signature. Materials are updated by batch or by year, and it is common to see inconsistencies in abbreviated course names for the same course across different materials, mismatches between the number of credit hours and the recognized number, misalignment between the course start date and the study start and end dates, as well as unsynchronized versions, missing signatures, or missing receipts. When entering this feature, the three types of materials together constitute the original record source for exception tracing: the course filing form is used to verify the course and class-hour baseline, the study certificate is used to verify the actual learning behavior and dates, and the credit hour recognition form is used to verify the recognition result and the signature chain. Only when the three corroborate one another can the review conclusion be supported.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the application settings, and outputs the reference range of historical messages and the answer constraints. Memory turns control how many previous turns of dialogue can be referenced at most when answering; if the value is too small, the preceding context cannot be used, and if the value is too large, irrelevant content is brought in and consumption increases. The "exception list and review conclusion" is then completed by the model, while the external entry point and authorization are handled by the publishing service and file permissions.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | Check whether the course name, number of class hours, course start date, instructor signature, and filing receipt are complete, and determine whether the course name is consistent with that in the study certificate | Retrieve the original filing form and compare it field by field with the study certificate and the credit hour recognition form; use chatId to associate the dialogue records of the same batch and confirm that the course name referenced in follow-up questions has not been rewritten |
| Study certificate | Check the study start and end dates, actual credit hours, and issuing unit's seal, and determine whether they match the class hours in the filing form and the recognized credit hours in the recognition form | Search for the study certificate by person identifier and course name, and check whether the dates fall after the filing course start date; retain the original material description in messages to avoid referential misalignment during the second round of follow-up questions |
| Credit hour recognition form | Check the recognized credit hours, recognition date, and reviewer signature, and determine whether the quantities and dates are consistent with the filing form and study certificate | Verify the name, quantity, and date of the recognition form against the two source materials one by one, and list records missing signatures or receipts separately; use variables to record the material version number so that unsynchronized versions can be traced |
| Memory turns | Match the range of preceding context required by the question, and determine whether the reference from the first round can be correctly carried forward in continuous follow-up questions | Check the current value in the application settings, run a trial with two consecutive question turns, and compare the usage records of the two runs |
Three common errors
- Phenomenon: the same course has different abbreviated names in the filing form and the study certificate, and the recognition form copies one of them. Cause: the three materials do not use a unified standardized name, and the check did not compare them character by character.
- Phenomenon: the class hours in the filing form, the actual credit hours in the study certificate, and the recognized credit hours in the recognition form do not match across the three places. Cause: after materials are updated by batch, versions are not synchronized, and the old version is still in circulation.
- Phenomenon: the credit hour recognition form lacks the reviewer signature or the study certificate lacks the issuing unit's receipt. Cause: the review step was not completed before archiving, and the signature chain was not closed.
How to verify the setup
Feature acceptance: use two consecutive follow-up questions and see whether the second question carries forward the reference from the first question. In the first round, ask about the course name and date of a certain exception record; in the second round, use a reference to ask about the corresponding field of that record in another material, and check whether the answer still points to the same record; at the same time, confirm that chatId, messages, and variables remain stable during the follow-up.
Business test: create an exception record and see whether the source material can be traced. Construct a record with inconsistent course name, quantity, or date, trace it back layer by layer to the course filing form, study certificate, and credit hour recognition form, and confirm that the exception is supported by original records and that the reviewer signature can be checked.
- Check the current value of memory turns in the application settings, run a trial with two consecutive question turns, and confirm that the second question can correctly carry forward the reference from the first question.
- Compare the usage records of the two runs, confirm that consumption changes accordingly after adjusting the number of turns, and that the opening message is not treated as preceding context.