- About the Tray Card Tickets (People)
- Selecting People to be in the Report
- Report Settings
- Sorting by Delivery Sequence (for Service)
- Sorting by Room (for Service)
- Sorting by Person Name (for Reviewing Tickets)
- FAQs
About the Tray Card Tickets (People)
The Tray Card Ticket report generates the dietary need tickets for residents and patients for meal periods (breakfast, lunch, dinner). The report will not list the food items to be served (apart from personal menu items). The dietary needs information on a ticket consists of the following information:
- Name (first, middle, last)
- Residence area
- ID (date of birth, client ID or MRN) (option)
- Diet order (diet, texture, fluid)
- Dining area
- Allergens
- Service notes (i.e., daily notes and individual meal period notes)
- Personal menu items and associated notes (option)
- Serving size adjustments (option)
- Do not serve items (option)
- Like preferences and dislike preferences (option)
- Diet intervention name (option)
Selecting People to be in the Report
Select the people to be included in the report via the following separate instructions: Selecting People to be Included in Reports.
Report Settings
After selecting the people to be included in the report, select Menus and Tray Tickets > Tray Card Tickets from the left side of the screen. The Tray Card Tickets section appears for you to select the report settings.
Content
-
Days - select the days or which to generate the tray card tickets.
-
Meals - select the meal periods (breakfast, lunch, dinner) to generate tray menu tickets for.
- People ID - select if you want the Client ID (ID assigned by your facility) or MRN (medical record number from the EHR system) to be displayed in the header.
Format
-
Page Size - select if the report is to be generated in letter size (8.5 x 11) or legal size (8.5 x 14).
-
Highlight Allergies and Non-Regular Diet Orders - highlights in yellow a person’s allergies and non-regular diet types, textures, and fluid types.
-
Font Size - select the font size (small (10), medium (12), large (14) ) of the tickets. Note that depending on the number of items a person receives for a meal period, the large font may generate two tickets for the person. Also note the person’s name always generates 4 points bigger than the selected font size.
-
Ticket header location - the header contains information about the person: room, dining area, diet type, interventions, date of birth, allergens, ID.
- Top of ticket - header information is displayed at the top of a ticket.
-
Bottom of ticket - header information is displayed at the bottom of a ticket.
-
Sort Tickets By
- Delivery Sequence - sorts the tickets according to the Delivery Sequence feature, which allows for the customized sorting of dining areas and their tables and seats, and residence areas that are enabled for room delivery and their rooms and beds. See Sorting by Delivery Sequence (for Service) below.
- Person Name - see Sorting by Person Name (for Reviewing Tickets) below.
- Room - for residence areas enabled for room delivery, sorts the report according the layout on the Residence Builder screen, which automatically sorts units by numerical and alphabetical order. See Sorting by Room (for Service) below for more information.
Optional Content
-
Date of Birth - includes the person’s date of birth in the ticket header.
-
Likes & Dislikes - includes a person’s like preferences and dislike preferences set up in their personal menu. Like preferences will be printed in a Likes section on the ticket, and Dislike preferences will be printed in a Dislikes section on the ticket.
-
Personal menu customizations - includes the following:
- Personal menu items and note (option)
- Serving size adjustments (option)
-
Do not serve items (option)
-
Diner Photos - if the resident has a photo on their profile (see Uploading, Changing or Deleting a Person's Profile Photo), then the photo will print in the ticket header, as per screenshot below (showing the ticket header displayed at the top of the ticket).
- Diet Intervention - includes the names of a person’s assigned diet interventions in the header. The personal menu customizations (personal menu item, fallback substitute, a do not serve item, or a serving size adjustment) that are added to a personal menu as a result of a diet intervention are not identified as diet interventions.
Sorting by Delivery Sequence (for Service)
From the Sort Tickets By drop-down, the Delivery Sequence option is available. This option sorts the tickets according to the Delivery Sequence feature, which allows for the customized sorting of dining areas and their tables and seats, and residence areas that are enabled for room delivery and their rooms and beds. For more information and instructions on setting the sorting for the Delivery Sequence feature, see Setting the Sort Order for People Reports.
With the Delivery Sequence option selected, the layout of the tickets in the report depends on the number of meal periods (breakfast, lunch, dinner) selected:
- Ticket Layout with One Meal Period Selected
- Ticket Layout with Two Meal Periods Selected
- Ticket Layout with Three Meal Periods Selected
Ticket Layout with One Meal Period Selected
With one meal period selected and the Delivery Sequence sort option selected, the tickets are printed according to the Delivery Sequence feature from top to bottom, filling stack 1 first (left), then stack 2 (middle), and then stack 3 (right).
Ticket Layout with Two Meal Periods Selected
With two meal periods selected and the Delivery Sequence sort option selected, the tickets are generated by meal period stacks, but with an empty third stack for the missing meal period. For example, if the lunch and dinner meal periods are selected, the layout of the report is as follows:
- Lunch tickets are printed in stack 1 (left) according to the Delivery Sequence feature.
- Dinner tickets are printed in stack 2 (middle) according to the Delivery Sequence feature.
- Stack 3 (right) is empty.
Because stack 3 will be empty, and results in wasted paper, the system will present a warning message of such to allow you to cancel the report or proceed with two meal periods selected.
Ticket Layout with Three Meal Periods Selected
With three meal periods selected and the Delivery Sequence sort option selected, the tickets are generated by meal period stacks:
- Breakfast tickets are printed in stack 1 (left side) according to the Delivery Sequence feature.
- Lunch tickets are printed in stack 2 (middle) according to the Delivery Sequence feature.
- Dinner tickets are printed in stack 3 (right) according to the Delivery Sequence feature.
Sorting by Room (for Service)
From the Sort Tickets By drop-down, the Room option is available. For residence areas enabled for room delivery, this option sorts the tickets according to the layout on the Residence Builder screen, which automatically sorts units by numerical and alphabetical order.
With the Room option selected, the layout of the tickets in the report depends on the number of meal periods (breakfast, lunch, dinner) selected:
- Ticket Layout with One Meal Period Selected
- Ticket Layout with Two Meal Periods Selected
- Ticket Layout with Three Meal Periods Selected
Ticket Layout with One Meal Period Selected
With one meal period selected and the Room sort option selected, the tickets are printed according to the Residence Builder screen from top to bottom, filling stack 1 first (left), then stack 2 (middle), and then stack 3 (right).
Ticket Layout with Two Meal Periods Selected
With two meal periods selected and the Room sort option selected, the tickets are generated by meal period stacks, but with an empty third stack for the missing meal period. For example, if the lunch and dinner meal periods are selected, the layout of the report is as follows:
- Lunch tickets are printed in stack 1 (left) according to the Residence Builder screen.
- Dinner tickets are printed in stack 2 (middle) according to the Residence Builder screen.
- Stack 3 (right) is empty.
Because stack 3 will be empty, and results in wasted paper, the system will present a warning message of such to allow you to cancel the report or proceed with two meal periods selected.
Ticket Layout with Three Meal Periods Selected
With three meal periods selected and the Room sort option selected, the tickets are generated by meal period stacks:
- Breakfast tickets are printed in stack 1 (left side) according to the Residence Builder screen.
- Lunch tickets are printed in stack 2 (middle) according to the Residence Builder screen.
- Dinner tickets are printed in stack 3 (right) according to the Residence Builder screen.
Sorting by Person Name (for Reviewing Tickets)
From the Sort Tickets by drop-down, the Person Name option is available. This option is typically for a review of tickets as opposed to service. With this option selected, the tickets are sorted alphabetically by last name, from left to right for each meal period/day combination. This option does not use meal stacks (i.e., all spaces on page are filled). The example below shows the resident Pam B. and her tickets for the Tuesday meal periods on the first page and her tickets for the Wednesday meal periods on the second page.
FAQs
Why is a diet order in red font?
If the diet order (diet, texture, fluid) for a person is in red font, it indicates that their diet order is invalid, and as such their diet order needs to be resolved. For more information, see Invalid Diet Orders.
Why is an allergy "unknown"?
When a Connect message contains an unknown allergen from the EHR that remains unresolved (i.e., the EHR allergen is not mapped to a MealSuite allergen group), then the report prefaces the allergy with Unknown:
If there are multiple unknown allergens, then Unknown: is listed once with each unknown allergen listed after.
Can I sort the report by diet type or texture type?
No. You cannot sort the report by diet type or texture type.