What this category's data looks like
Laboratory hazardous chemicals procurement and ledger involve three types of materials: hazardous chemicals procurement applications, usage registration, and inventory ledger. Procurement applications record the product name, specification, quantity, application date, and approval signature; usage registration records the user, quantity used, date of use, and custodian signature; the inventory ledger records the balance quantity, inbound/outbound dates, and review signature. The three types of materials come from different sources and update at different rhythms: procurement applications are submitted as needs arise, usage registration is updated with each use, and the inventory ledger is summarized daily or by batch. When the materials enter the conversation logs and audit feature, procurement applications serve as the basis for demand, usage registration serves as evidence of consumption, and the inventory ledger serves as the baseline for balances; together, the three support anomaly tracing and manual review.
Configuration and implementation checks
This step is performed by the conversation record interface (by application and session dimension), which outputs the session message list and the total record count, including role and reference information. The "anomaly list and review conclusions" are then completed manually or by an external system. The message list is not a version ledger of business materials; it is used only as session evidence.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemicals procurement application | Product name, quantity, application date, and approval signature are consistent across the three materials | Open the procurement application and inventory ledger, compare product name, quantity, and date item by item, and check the signature field; use chatId to locate the corresponding session record |
| Usage registration | The user, quantity used, date of use, and custodian signature are traceable | Compare the inbound/outbound dates and quantities in the usage registration and inventory ledger, and check the receipt and signature; after paging through to retrieve all records, verify dataId and value |
| Inventory ledger | The balance quantity reconciles consistently with procurement and usage records | Sort by date to check balance changes and confirm version synchronization; page through to retrieve all records by the total record count total, and when the status code is 200, sample one record to verify the role and reference information |
| Conversation record interface output | The session message list and total record count match, and the role and reference information are readable | Pull two pages consecutively to compare the offset and total count, and open a single record to verify the role, reference, and elapsed time fields |
Three common errors
- Symptom: The name, quantity, and date of the same batch of hazardous chemicals do not match between the procurement application and the inventory ledger. Cause: The two materials are registered separately, no cross-check is performed, and versions are not synchronized.
- Symptom: The usage registration lacks the custodian signature or receipt, making it impossible to confirm the responsible person during anomaly tracing. Cause: The usage process is not closed-loop, and the signature step is skipped.
- Symptom: The interface returns empty but there are sessions in the interface, or only the first page is retrieved. Cause: The sources of the application and session identifiers are inconsistent, and the pagination parameters do not page through according to the total count.
How to verify the setup
Feature acceptance: Page through to retrieve all records by the total record count total, sample one record to verify the role, reference information, and time, and when the status code is 200, confirm that _id, dataId and value are readable.
Business test: Create an anomaly record and see whether the source material can be traced.
- Pull conversation records by application and session dimension with pagination, pull two pages consecutively to compare the total count and offset, and confirm that the total record count matches the number of messages.
- Open a single record to verify the role field, reference, and elapsed time, confirm that message roles correspond to the original conversation, and record the number of references separately by array length.