Build and publish a form
A form template defines the questions the clinic asks. Publishing creates the version used for new patient requests, so later edits do not silently change a form that was already shared.
- Use stable question labels that a provider and patient can understand.
- Mark a question required only when the response is necessary for the clinic workflow.
- Preview the complete form before publishing it.
Prepare a secure patient link
Choose a published form and the intended patient. Orvexa AI prepares an expiring response link and an email draft. A clinic team member still verifies the recipient and sends the message from the clinic's email system.
- Confirm the patient before creating the request.
- Do not paste a patient link into a shared channel or support message.
- Orvexa AI does not send the email automatically.
Track and review the response
Ready to send, Opened, Response received, Expired, and Cancelled describe the request lifecycle. The dashboard brings requests needing action into the same patient queue as report follow-up.
- Renew an expired request instead of reusing its old link.
- Continue to report generation only from the intended patient.
- Confirm submitted answers in the report review before approval.