What this category's data looks like
University admissions medical examination organization involves three types of materials: medical examination forms, re-examination applications, and restricted-major notifications. Medical examination forms are issued in batches by the university hospital or a designated medical examination institution, and include name, candidate number, past medical history, conclusions for each subject, and the chief examiner's signature; re-examination applications are submitted by the candidate or the department after receiving the initial examination conclusion, and include the reason for application, the original abnormal item, the appointment date, and the review signature; restricted-major notifications are delivered by the admissions office before admission, and include the restricted clauses, the corresponding majors, and the receipt signature. When the three types of materials enter the form input node, their roles differ: the medical examination form provides the original abnormal items, the re-examination application provides the handling request, and the restricted-major notification provides the destination of the conclusion. The update rhythm advances with admissions batches, and the field characteristics are concentrated in four items: name, quantity, date, and signature. Any misalignment will cause a break in the exception tracing chain.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The exception list and review conclusion are completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters the interaction state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Medical examination form | Abnormal items must be supported by original records, and the name, quantity, date, and chief examiner's signature must be aligned item by item | Check the field names one by one in the node configuration, and confirm that they correspond one-to-one with the medical examination form fields |
| Re-examination application | The reason for application, original abnormal item, appointment date, and review signature must be complete, and must match the abnormal items in the medical examination form | Check the required settings one by one, and confirm that the key material fields have been marked as required |
| Restricted-major notification | The restricted clauses, corresponding majors, and receipt signature must be complete, and the version must be synchronized with the current batch | Reference this field in a subsequent node and run a test, and confirm that the subsequent node can retrieve the corresponding field value |
| formInputResult and selectResult | After the field values are submitted, they must be retrievable by subsequent nodes, and the interaction state must be able to exit normally | Reference the formInputResult and selectResult fields in a subsequent node and run a test, and check the retrieved field values |
Three common errors
- Symptom: The name and quantity of the same abnormal record do not match between the medical examination form and the re-examination application. Cause: The fields in the two places are filled in separately, without backfilling based on the original records of the medical examination form.
- Symptom: The version of the restricted-major notification is not synchronized with the current admissions batch, and the clauses do not match the majors. Cause: After the notification material is updated, it is not re-entered into the form input node for verification.
- Symptom: The medical examination form or re-examination application lacks the chief examiner's signature or receipt, and exception tracing stops in the interaction state. Cause: The required markers do not cover the signature and receipt fields, and after submission the subsequent nodes cannot retrieve the values.
How to verify the setup
Acceptance of this feature: Fill out the form once and submit it, check the field values retrieved by subsequent nodes, and confirm that the formInputResult and selectResult field values can be referenced and that the interaction state exits normally.
Business test: Create an abnormal record, see whether it can be traced back to the source material, and check whether the name, quantity, date, and signature are consistent across the medical examination form, re-examination application, and restricted-major notification.
- Check the field names one by one in the node configuration, and confirm that the form fields correspond one-to-one with the fields of the medical examination form, re-examination application, and restricted-major notification.
- Check the required settings one by one, and confirm that the key material fields have been marked as required, and that after submission the subsequent nodes can retrieve the corresponding field values.