Conversation Records and Traceability for School Mental Health Screening and Referrals: Coordinate Operations and Application Handover

Student Mental Health: review chat records for operational handover. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This page addresses the primary and secondary school mental health screening and referral scenario, and the materials include three types: psychological screening plans, interview records, and referral forms. Screening plans are usually updated by psychological teachers per semester, and contain scale names, screening dimensions, decision thresholds, and rescreening rules; interview records are filled in by homeroom teachers or psychological teachers on each occasion, and contain interview dates, student identifiers, chief complaint summaries, and preliminary assessments; referral forms are generated by psychological teachers after coordinating with parents and medical institutions, and contain referral reasons, receiving units, receipts, and signatures. When these three types of materials enter the conversation records and auditing function, screening plans serve as the basis for session creation, while interview records and referral forms serve as session content and citation sources, aggregated by application and session dimensions to form a paginated, exportable, and reviewable session message list and total record count. Versions, dates, and signatures are the anchors for field verification, and the update cadence follows semester screening batches and individual case referral milestones.

Configuration and implementation checks

This step is executed by the conversation records interface (by application and session dimensions), which outputs the session message list and total record count, including role and citation information. The handover-ready deployment status and operation records are then completed manually or by an external system.

ObjectCheckVerification action
Psychological screening planThe plan name, screening dimensions, decision thresholds, and version date must be consistent with the version referenced by the interview records and referral formsIn the session message list, sample one screening-related record, verify the plan name and version date, and compare the same version referenced by the interview records and referral forms
Interview recordThe interview date, student identifier, chief complaint summary, and signature must be consistent with the corresponding fields in the referral formPaginate through all records by application and session dimensions, verify the interview date and student identifier, and check whether the referral form is missing a signature or receipt
Referral formThe referral reason, receiving unit, receipt, and signature must be consistent with the decision result of the screening planOpen one referral-related record, verify the referral reason and receiving unit, and compare the screening plan decision result with the receipt and signature
Conversation records interface outputThe total record count and pagination parameters match, role fields alternate, and citation and duration fields are queryableUse chatId and appId to pull two consecutive pages, verify total and offset, sample one record to verify role, citation information, and time, and confirm the status code is 200

Three common errors

  • Symptom: The name, quantity, and date of the same record do not match between the screening plan and the interview record. Cause: The two sets of materials are maintained separately and are not registered under the same version date and field definitions.
  • Symptom: The referral form is missing a signature or receipt, and the dates in the interview record and referral form are inconsistent. Cause: The handover step did not verify signatures and receipts item by item, and versions were not synchronized.
  • Symptom: The interface returns empty but sessions exist in the UI, or only the first page is retrieved. Cause: chatId does not match the actual session, and pagination offsets were not pulled continuously.

How to verify the setup

This feature's acceptance: paginate through all records by total record count, sample one record to verify role, citation information, and time, confirm total and response code of 200, and verify chatId, dataId, and the value field.

Business testing: verify each item once according to the handover form, see which record is missing, and compare the fields, dates, and signatures of the screening plan, interview records, and referral forms.

  • Pull two consecutive pages by application and session dimensions, compare the total record count and offset, and after confirming there are no omissions, export the session message list.
  • Sample one record, open value, verify role, citation information, and duration, then compare the versions and signatures of the screening plan, interview records, and referral forms.

References