N

Nurenyx

StudyOps

← Back to StudyOps

Product support

StudyOps Help

Use this guide to understand the workflows available in the current prototype, interpret Visibility Audit results, and resolve common local-browser issues.

1. What StudyOps currently does

Study Search

Searches live ClinicalTrials.gov and Health Canada records, keeps source provenance visible, and provides a path into a visibility audit. Demonstration data is separate and clearly labeled.

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

Sends a validated business request to Nurenyx when email delivery is configured, with an equivalent mailto and manual-copy fallback when online delivery is unavailable.

2. Core workflow

  1. Search for a study.
  2. Select Run visibility audit.
  3. Review the heuristic score and recommendations.
  4. Open the sponsor-ready report to print it or use your browser's Save as PDF option.
  5. Share a non-sensitive plain-text summary or request a full Nurenyx visibility review by email.
  6. Explore StudyOps Monitoring.
  7. Request early access.

3. Contact and review requests

Request early access from the Monitoring page or shared contact page. Choose the explicit request type, then provide your name, work email, organization, research role or relationship, and a short non-sensitive business-use description.

To request a full visibility review, generate an audit and choose Request a full visibility review from the report. StudyOps carries only bounded study and report context such as title, registry ID, source, recruitment status, score, source registry URL, provenance, and originating route. It never sends the browser-local report URL or unrelated localStorage data.

If online delivery is unavailable or cannot be confirmed, the form retains every entry and provides a structured email fallback. Open it in your email app or expand the manual-copy content. Sending the fallback remains your choice, and response times are not guaranteed.

4. 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, medical advice, a treatment-safety or scientific-validity assessment, regulatory approval, or a clinical system of record. Live registry metadata can supply the input, but the registry publisher does not validate the StudyOps score.

A registry may not supply every field. Source-unavailable audit fields are marked unavailable and treated neutrally rather than as negative clinical findings.

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, saved local draft, and current local report record. A direct visit without URL-prefill data may restore a saved draft from that browser. The report route never silently substitutes demonstration data when no valid report exists.

Export / Save as PDF uses the browser print dialog. Share report summary uses the system share sheet when available, otherwise it copies a plain-text summary or exposes a manual-copy fallback. No permanent shared report URL is created.

5. 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?

Yes. Study Search can request live public records from ClinicalTrials.gov and Health Canada. Source availability may vary, and publisher data can be delayed, incomplete, or changed. Clearly labeled demonstration records remain available through an explicit action. Visibility Audit remains heuristic.

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 and the current generated report in your browser's localStorage so the report can survive refresh on that device.

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.

6. 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 contact delivery is unavailable, use the displayed mailto or manual-copy fallback; your form entries remain on the page.
  • If one registry reports a warning, review results from the other source or retry later. A Health Canada cold request can take longer because its public dataset is large.
  • If the issue continues, contact innovations@nurenyx.ai.

7. Contact

For StudyOps support or product questions, email innovations@nurenyx.ai. You can also review the current Privacy Notice and Security page.

8. 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.