1. What StudyOps currently does
Study Search
Filters local mock study records and provides a path into a visibility audit.
Visibility Audit
Generates a local, heuristic visibility score with explainable categories and recommendations.
StudyOps Monitoring preview
Describes a planned monitoring workflow and early product options; it does not provide live monitoring today.
Early Access Request
Prepares a message in your own email client without submitting a form to a Nurenyx backend.
2. Core workflow
- Search for a study.
- Select Run visibility audit.
- Review the heuristic score and recommendations.
- Explore StudyOps Monitoring.
- Request early access.
3. Visibility Audit guidance
Registry Completeness
Reviews whether the supplied study metadata includes useful registry-oriented identifiers and details.
Patient-Facing Clarity
Estimates how understandable the supplied study title and condition context may be for a patient-facing experience.
Recruitment CTA Strength
Reviews the recruitment status and whether the supplied metadata supports a clear next step.
Search/AI Discoverability
Estimates how well the supplied identifiers, title, condition, and URL could support search and AI discovery.
Operational Readiness
Reviews sponsor or site context, recruitment status, and other supplied signals that support operational follow-up.
The score is a heuristic intended for workflow validation. It is not clinically validated and is not currently based on live registry validation.
Study Search and Visibility Audit use the same local scoring source. Choosing Run visibility audit can prefill the audit through the URL and automatically run it once.
Reset audit clears the form, generated report, URL-prefill state, and saved local draft. A direct visit without URL-prefill data may restore a saved draft from that browser.
4. Common questions
Why do scores differ between studies?
The local heuristic applies category-specific rules and weights to the metadata supplied for each study. Differences in identifiers, title, condition, URL, sponsor or site, and recruitment status can change the result.
Is StudyOps using live registry data?
No. The current prototype uses local mock Study Search data and user-supplied metadata. It does not validate results against live ClinicalTrials.gov, Health Canada, or another registry.
Are reports saved to a Nurenyx server?
No. Saved server-side audit reports are not implemented. Visibility Audit may keep a non-sensitive intake draft in your browser's localStorage.
Can I create an account?
No. The current prototype has no authentication, user accounts, organizations, or workspaces.
Can I pay for StudyOps today?
No. There is no active billing or payment processing. Monitoring plan content is an early product and pricing hypothesis.
Can I enter patient data?
No. Do not enter patient data, PHI, or other sensitive or confidential clinical information anywhere in the prototype.
What does Planned or Coming soon mean?
It means the feature is a roadmap or preview signal and is not currently available as an implemented workflow.
Why does the local development version show a React development notice?
That notice can appear while the app is running in local development mode. It is not expected in an optimized preview or production deployment.
5. Troubleshooting
- Refresh the page.
- Use Reset audit to return Visibility Audit to a clean state.
- If a draft appears stale, clear the stored site data or localStorage for StudyOps. This removes browser-local draft data for the site.
- Try a current desktop browser.
- Confirm JavaScript is enabled.
- If the issue continues, contact innovations@nurenyx.ai.
6. Contact
For StudyOps support or product questions, email innovations@nurenyx.ai. You can also review the current Privacy Notice and Security page.
7. Product boundary
StudyOps is not medical advice. It is not currently a clinical service, and it is not a clinical system of record.
Do not enter patient data or PHI.