Diet meal requests

The Front Desk Agent records a service request against an existing meal order. The request holds a Standard or Special Diet service type, a ward label, a service date and a meal count. The parent order supplies the patient and ward reference, so the agent checks that link before saving. The label lets the Operations Reviewer identify the request type before the next service handoff.

A patient with an Accepted order may need a Special Diet request for a particular service date. The Front Desk Agent opens the order, checks its patient and ward, and records the request with the intended count. The Operations Reviewer examines that attributed request beside the parent order. The Property Manager can then see the request with the service case before coordinating the next task.

• Source identity. Confirm the linked order and its patient and ward before acting on a related record.
• Current work. Use the relevant status, date and assignee to identify what needs attention today.
• Evidence. Keep the charge, receipt or completed task associated with the order that caused it.

Agree which Front Desk Agent enters requests and which Operations Reviewer checks the linked evidence. The request’s ward is text, while the order has a ward reference; make the team’s rule for matching them explicit. Set a consistent meaning for the service date and count so a request for the wrong day is caught before preparation. Decide how a correction reaches the reviewer when a patient, ward or meal count changes.

The Standard and Special Diet choices identify the service request type. Staff should agree what each choice means in their operating practice and who handles the request after review. Keep the parent order’s identifier visible at intake so a request for another patient is not attached by mistake.

Start with an Accepted order for a known patient and ward. The Front Desk Agent enters a request for a service date inside the order’s interval and records the intended meal count. The Operations Reviewer opens the request and parent order together, checks the actor and source identity, and inspects any changed date or count before the next handoff. If the ward label differs from the ward on the order, correct the source entry before the request is used.

Then try a second submission of the same request. The saved result should be returned without a duplicate request. Change the linked order or count and have the reviewer examine the new input rather than treating it as the original action. The Property Manager should be able to identify the current request from the order during the next shift.

• Diet meal requests — Review service type, date and count alongside each request’s linked order.
• Meal order queue — Find Accepted orders that need a service handoff.

See the working process for the record handoffs and the data model for the references behind them.