From intake to a reviewed case
Five steps. The analysis layer drafts. A person files the case, or keeps it in AE Connect.
-
01
Intake
Public reporter form. Custom organization forms. Email a safety person files into the case.
-
02
Structured case record
Reporter, patient, product, and event, held on the organization.
-
03
AI analysis layer
A draft of priority, seriousness, coding, causality, timelines, gaps, and a summary.
-
04
Human review
Safety staff read the source and accept or override the draft.
-
05
Outputs
ICSR and E2B(R3). Export for Argus, Veeva, or ArisGlobal, or keep AE Connect as the safety database.
The public reporter form does not need an AE Connect account. Each organization customizes that form (fields, branding, products, and languages) and shares its own link. An emailed report is brought into the case by the safety team. AE Connect does not submit or transmit the ICSR. Oracle Argus, Veeva Vault Safety, and ArisGlobal LifeSphere are product names of their owners.
What the analysis layer drafts
Every item below is a suggestion. A qualified person reviews it. Nothing is submitted to a regulator from this layer.
-
Priority
A priority score so the queue can surface the cases that need a person first.
-
Seriousness criteria
A suggested serious or not serious call, against death, a life threatening event, hospitalization, disability, a congenital anomaly, or another medically important event.
-
Suggested MedDRA coding
A preferred term and system organ class for the reviewer to confirm. This suggestion is not a MedDRA license and not a coded case.
-
WHO-UMC causality suggestion
A WHO-UMC category with a short reason. The reviewer accepts it or replaces it.
-
FDA and EMA reporting timeline guidance
A suggested reporting deadline, including the usual 7 day and 15 day expedited clocks. The draft does not start the clock and does not file the report.
-
Missing information checklist
Gaps the case still needs, including a reporter, a product, and an onset date, so follow up can start before the file is complete.
-
Case summary
A short narrative the reviewer can read next to the source and export with the triage draft.
How triage runs today
The call that writes the draft goes through a provider layer. The case record stays the same when the model behind that call changes.
-
Leading foundation models
The layer works with leading foundation models. Organization settings choose the Claude model used for the current call.
-
Customer cloud or a custom endpoint
The same layer can run inside the customer's cloud, for example on AWS Bedrock, or point at a custom model endpoint.
This is the path in the product now. The model in the next section is not this path.
Roadmap
In development
The QORO PV model will power AE Connect triage
The QORO PV model will be the in house technology that runs AI triage for AE Connect. It is in development. It is not in the product, it is not live, and it is not validated.
-
QORO will build and host it
QORO will build the model and host it. Once it is deployed, triage will not depend on a third party model.
-
It will cite public guidance
The model will be grounded in public regulations and guidance, and it will cite the passages it retrieves. The grounding set will include ICH E2A, ICH E2B(R3), ICH E2D, FDA 21 CFR 314.80, FDA 21 CFR 600.80, and EU GVP.
-
It will be validated before production
Before the model is used in production, the core functionality will be fully validated. That work will include computer system validation and documented testing against qualified human reviewers. Validation will happen first. It has not happened yet.
The model will be tuned on triage data. Licensed MedDRA coding is on the roadmap and will not be part of the first production use unless that work is finished and stated separately.
Status: in development. Not available in the trial. Not in production. Not validated. Until this model is in production, triage keeps using the provider layer above.
Organization scope, roles, and the audit log
These are controls in the workspace. AE Connect is 21 CFR Part 11 validated. Data handling is on the trust page.
-
Organization scope
Cases, the public form, settings, and the audit log belong to one organization. The signed in session sends that organization id with each request. A signup without an invite creates a new organization, and that person is the Org Admin. Teammates join by invite.
-
Role based access
Organization roles are Org Admin, Manager, PV Specialist, and Reporter. User management, invites, the form builder, settings, and the audit log are admin screens, not open to every role. A QORO operator role can open cross organization administration. Customer roles stay inside their organization.
-
Audit log
The audit log records activity in the organization, including case updates, triage, status changes, and E2B export. An admin can review the log and export it.