MANSOQ Knowledge
← Knowledge library

Clinical care

Update a resource request status and review its request letter

Review the available statuses, verify a saved Approved record and inspect the actual populated request-letter preview.

6 min read · Source baseline f6e9f05f

Verification and applicability

Actual 1920 × 1080 Chrome screenshots from isolated synthetic MANSOQ source f6e9f05f. Existing Staff creates one own-origin request to an existing synthetic public destination, saves one note and changes Pending to Approved through normal UI. Independent normal Staff resource/comment GET200 reads verify the same UUID, exact origin/destination, no patient, no assigned person and retained note. No new grants, directory visibility changes, external contact, real care/financial/transport action or all-role/facility qualification.

Check your installed version, permissions and local configuration.

Before you begin

1. Use Update Status and review the full status menu

From saved request detail, Update Status opens the full update form. The pictured Status menu lists Pending, Approved, Rejected, Cancelled, Transportation to be arranged, Transfer in progress and Completed. Approved is the only subsequent status submitted in this package; the other choices are visible options and require separate workflow teaching.

Review all seven status options without implying delivery. Actual wide MANSOQ synthetic Staff own-origin synthetic resource coordination, comments and request letter view.1234
Review all seven status options without implying delivery · 2026-10-18Recorded baseline screen · 1920 × 1080
Capture details

Actual 1920 × 1080 Chrome pixels; pinned source f6e9f05f. Staff own-origin synthetic resource coordination, comments and request letter

  1. Status field: The current persisted state is Pending before this change.
  2. Approved option: This is a software state in the synthetic example.
  3. Transport-related choices: Visible options alone do not prove transport workflows.
  4. Completed option: This visible option has not been selected or saved in this package.

2. Verify the saved Approved state and modification actor

After the local synthetic status update is submitted, saved detail shows Approved and the updated Staff audit timestamp. The origin, destination, synthetic reason/contact and note are retained. Independent Staff GET200 verifies the same request UUID and approved state. Request Letter and Update Status remain available. This is a software record state, not clinical approval or evidence of delivery.

Verify saved Approved state and the last modification actor. Actual wide MANSOQ synthetic Staff own-origin synthetic resource coordination, comments and request letter view.1234
Verify saved Approved state and the last modification actor · 2026-10-18Recorded baseline screen · 1920 × 1080
Capture details

Actual 1920 × 1080 Chrome pixels; pinned source f6e9f05f. Staff own-origin synthetic resource coordination, comments and request letter

  1. Approved record state: Confirm the saved local software state.
  2. Update Status: Open the full form for an authorized subsequent status update.
  3. Request Letter: Preview a letter populated from this saved resource record.
  4. Last modification: The audit identifies the Staff actor and updated time.

3. Review the actual populated request-letter preview

Open Request Letter. Compare the reference UUID, origin Clinic, synthetic title/reason, category and Approved status with the saved detail. This configured training letter shows the creator and the last modifying user/times in its Requested By and Approved by blocks, plus a synthetic watermark. The pictured Print control and Back control are available. This package does not certify a print dialog, downloaded PDF or dispatched letter.

Review the request letter populated from the saved Approved record. Actual wide MANSOQ synthetic Staff own-origin synthetic resource coordination, comments and request letter view.123456
Review the request letter populated from the saved Approved record · 2026-10-18Recorded baseline screen · 1920 × 1080
Capture details

Actual 1920 × 1080 Chrome pixels; pinned source f6e9f05f. Staff own-origin synthetic resource coordination, comments and request letter

  1. Reference number: Compare the letter reference to the saved request UUID.
  2. Synthetic reason: Review the saved reason before any printing.
  3. Current status: This preview reflects the saved Approved state.
  4. Updated actor: The Approved by block uses the saved modifying user in this template.
  5. Print: Use the normal browser print workflow when needed.
  6. Back: Return to the saved request detail.

Status groups and unobserved branches

The source groups Pending, Approved, Transportation to be arranged and Transfer in progress under Active; Completed, Rejected and Cancelled are in the Completed group. This package does not include saved Completed/rejected/cancelled/transport states, incoming destination processing, assigned-user selection, multiple comments, pagination or patient-linked requests. Those branches remain separate capture tasks.

Version and access scope

These screenshots retain the original f6e9 training source provenance. The existing Staff account was observed only in its own origin Clinic. Separately tested access repairs do not make these baseline screenshots evidence that a later release or another role/facility has been verified.

Troubleshooting

A request seems absent from the default list after changing status

Check Incoming versus Outgoing, Active versus Completed group and the exact status tab. The default Pending filter does not display an Approved request.

The letter has an Approved by name

In this template that block uses the saved modifying user for approved/rejected status. Verify the audit and your organization’s approval process; the printed name alone does not establish a real clinical or external approval.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.