Against the backdrop of AI technology accelerating its integration into every stage of clinical trials, Clinflash attaches great importance to the efficiency gains brought by intelligence, while strictly adhering to the bottom line of compliance and data quality. We are committed to providing stable and efficient digital tools for the clinical research industry, and through continuous feature optimization and professional support, helping users cope with complex and ever-changing trial management scenarios.
This Q&A session revolves around the Clinflash EDC system's Q3 2026 version update, covering popular questions such as AI automated testing, participant mechanisms, user management optimization, and the use of the new report version. We strive to break down each item in a concise and clear manner, helping everyone quickly understand the update highlights and reduce usage confusion.
01. Under what circumstances will normal range updates break markers (SDV, DM Review, MM Review, etc.)?
Whether markers are broken depends on whether the laboratory range name is changed. If the laboratory range name is changed, markers will be broken.
02. Do nodes prior to version V2026.3.0 also support the "Participant" mechanism in exported reports?
Yes. After the V2026.3.0 update, by changing the previous nodes to the new report version in the node configuration, the report header will support the "Participant" mechanism.
03. In AI testing, does one participant output one test case?
Yes; one test case occupies one participant; one EC generates two test cases.
04. During AI testing, if a field is set with dynamic triggering, can it still be tested normally?
Yes, supported.
05. Are queries triggered when the laboratory indicator range is empty only when the laboratory range name is empty?
No. If the laboratory range name is empty, both the "Laboratory range name is empty" and "Indicator range is empty" queries will be triggered simultaneously.
06. AI testing currently generates two test cases. Are there cases where the evidence is insufficient?
In the future, we will consider generating cases from different perspectives for different scenarios.
07. Is "Field Description" in dynamic association updated in real time based on actual data? Will this setting be reflected in the SDS?
It is updated in real time. This setting is part of the CF visualization settings, not a functional configuration, so it will not be reflected in the SDS.
08. When exporting the visit view, does the exported content distinguish between the visible and hidden states of modules under the visit?
Yes, it supports differentiation.
09. Is data generated by users themselves using AI supported for upload?
The system provides a standard data upload function, which can be used to upload test scripts.
10. The new report version has removed some reports. After switching, will the corresponding reports no longer exist?
Due to historical reasons, some reports run in multiple versions, such as Unique CRF and Unique CRF V2.0. In the new report version, Unique CRF V2.0 has replaced Unique CRF, and the name has been updated to Unique CRF. The number of report types has not actually been reduced.
We hope the above summarized answers are helpful to you. If you still have other questions, you can contact our technical support team or leave a message in the comment section. We look forward to your continued attention!