What this category's data looks like
This page addresses deployment, operations, and application handover for research ethics review scenarios. Materials include ethics review applications, informed consent form templates, and risk assessment forms. Sources are paper or electronic documents submitted by institutional ethics committees and project teams, and the update cadence varies with project phases and review cycles. Field characteristics center on subject information, research purpose, risk level, signing date and signature fields, as well as version number and receipt number. When entering the deployment, operations, and application handover function, the three types of materials each play a different role: the ethics review application is used to confirm the review scope and version, the informed consent form template is used to verify signing and receipts, and the risk assessment form is used to verify risk level and date. The database and operations side is only responsible for whether connections are available and whether operation records can be handed over; it does not read or write material content, nor does it use that to determine whether materials are mixed up with one another. During handover, consistency among version, connection, and task records is the standard; if any one item is missing, it is considered incomplete.
Configuration and implementation checks
This step is determined by the connection configuration of the deployment environment (server side), not by the capability execution of a model node, and outputs whether the connection is available (service startup result and connection logs). The handover-ready deployment status and operation records are then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Ethics review application | Check whether the application number, version number, signing date, and signature field are complete, and whether they are consistent with the name, quantity, and date in the informed consent form template | Compare the application and template item by item against the handover form for number, date, and signature, and record missing items |
| Informed consent form template | Check the template version, receipt number, and signature field, and confirm that they match the date and quantity in the risk assessment form | Inspect each template's signing and receipt one by one, and mark entries with unsynchronized versions or missing signatures |
| Risk assessment form | Check the risk level, assessment date, and signature, and confirm that they are consistent with the name, quantity, and date in the ethics review application | Check the risk level and date against the handover form, and record fields that are inconsistent with the application |
| Deployment connection configuration | Check the connection results for the main business database, log database, cache, and vector database, and confirm that the startup logs show no persistent timeouts | Connect once to each item using the client, and check that the values of MONGODB_URI, REDIS_URL, and PG_URL match the instance addresses |
Three common errors
- Symptom: The name, quantity, and date for the same subject do not match between the application and the assessment form. Cause: The two materials were filled in separately without cross-checking, and no item-by-item comparison was made during handover.
- Symptom: The informed consent form template version was not synchronized, and the receipt number is missing. Cause: The version number was not written back after the template was updated, and receipts were not fully collected during the signing step.
- Symptom: After startup, the logs continuously report connection timeouts, and retrieval reports vector database errors. Check: The cache or vector database connection address is inconsistent with the instance, it is misjudged as business data being mixed together. Logs use the primary database when no separate log database is configured; inspect the actual log destination separately.
How to verify the setup
This function's acceptance: connect once to each of the main business database, log database, cache, and vector database, check the connection results in the startup logs, and confirm that MONGODB_URI, REDIS_URL, and PG_URL point to actual instances and can be connected.
Business test: check once item by item according to the handover form, see which record is missing, and focus on checking whether the name, quantity, date, and signature of the ethics review application, informed consent form template, and risk assessment form are consistent.
- Connect to the main business database, log database, cache, and vector database one by one, and record the connection results and timeout items in the startup logs.
- Check the version numbers, dates, signatures, and receipts of the three types of materials according to the handover form, mark missing items, and hand them over to the next shift.