Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Submission Details page at /fw/submissions/:id displays the full contents of a single form submission, along with tools for managing its lifecycle, annotations, and supporting documents.

​
Overview

The Submission Details page shows all field responses from a submitted form. Submitted data may contain PHI — this page is subject to access controls and audit requirements. The page is gated by FW_PERMISSIONS.SUBMISSIONS_VIEW at the route level. The page includes:
  • Submission field values — All form fields with their submitted responses, including file attachments and signature captures.
  • AI Summary Card — Shown for non-draft submissions (SME: confirm AI summary scope and PHI handling).
  • Status workflow — A dropdown to update the submission status (draft, submitted, reviewed, completed, rejected).
  • Notes — A textarea to add internal notes visible to staff.
  • Signatures — A card listing captured signatures when the form includes signature-type fields.
  • Attachments — A drag-and-drop zone for uploading supporting files and a list of existing attachments with download and delete actions.
  • PDF export — Download PDF and Export with Letterhead buttons for non-draft submissions; Signed PDF button when signature fields are present.

​
Who it’s for

Requires fw.submissions.view permission (FW_PERMISSIONS.SUBMISSIONS_VIEW), enforced by RequirePermission in src/routes/fw.tsx.

​
Before you start

  • You must have the fw.submissions.view permission.
  • The submission must exist. If not found, the page shows “Submission not found” with a link back to the list.
  • PDF export requires the submission to have a status other than draft.

​
Steps

Viewing a submission:
  1. Navigate to /fw/submissions/:id or open a submission from the Submissions list.
  2. Review field values in the Submission Details card. Signature fields show the captured image; file fields show a preview or link.
  3. Review the AI Summary Card if available (non-draft submissions).
Changing status:
  1. In the Status sidebar card, select a new status from the dropdown.
  2. The status updates immediately. Timestamps for reviewed and completed events are shown below the dropdown.
Adding a note:
  1. In the Notes card, enter the note text in the textarea.
  2. Select Add Note. The note is appended to the list with creator and timestamp.
Uploading an attachment:
  1. In the Attachments card, drag a file onto the drop zone or click to select.
  2. The file uploads and appears in the attachments list.
Downloading an attachment: Select the download icon next to the file. A signed URL is generated with a 1-hour expiry and the file opens in a new tab. Exporting as PDF:
  • Download PDF — Generates a standard PDF export.
  • Export with Letterhead — Opens the FormSubmissionExportDialog for branding and formatting options.
  • Signed PDF — Available when the form has signature fields; generates a PDF with embedded signatures.

​
Key concepts

  • Submission status lifecycle — draft → submitted → reviewed → completed (or rejected). Status changes are persisted via useSubmissionMutation.
  • PHI — Form submission data frequently contains PHI. Access is gated by fw.submissions.view. Notes and attachments should not contain PHI beyond what is necessary.
  • Signature capture — Signature-type fields that lack a value and have a capturable status show a “Capture Signature” button powered by SignatureDialog.
  • Attachment storage — Files are stored in the submission-attachments Supabase storage bucket. Download links use signed URLs expiring after 1 hour.

Forms & Workflow

Forms & Workflow core overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/fw.tsx
  • src/cores/fw/pages/SubmissionDetailPage.tsx
  • src/cores/fw/hooks/useSubmissionDetail.ts
  • src/cores/fw/hooks/useSubmissionMutation.ts
  • src/platform/forms/hooks/useFormSubmissionPdf.ts
  • src/platform/signatures/SignatureDialog.tsx