Tray Card Ticket Report (People) - lists Dietary Needs (no Food)

• About the Tray Card Ticket Report (People)
• Selecting People to be in the Report
• Report Settings
  
  • Formatting Options
  • Options to Include
• FAQs
  • Why is a diet order in red font?
  • Why is an allergy "unknown"?
  • Can I sort the report by diet type or texture type?

About the Tray Card Ticket Report (People)

The tray card ticket report generates the dietary need tickets for residents and patients. 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
• 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 service/snack time notes)
• Personal menu items and associated notes (option)
• Serving size adjustments (option)
• Do not serve items (option)
• Likes and dislikes (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 Tray Card Tickets from the left side of the screen. The Tray Card Tickets section appears for you to select the report settings.

Formatting Options

• Format - select if the report is to be generated in letter size (8.5 x 11) or legal size (8.5 x 14).
  
  
• 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 - the header contains information about the person: room, dining area, diet type, interventions, date of birth, allergens, ID.
  
  • Top - header information is displayed at the top of a ticket.
  • Bottom - header information is displayed at the bottom of a ticket.
    
    
• Sort By:
  • Name - sorts the report alphabetically by last name.
  • Dining Area - sorts the report according to the delivery sequence set up for dining areas (including residence area enabled as a dining area for in-room service), and sub-sorted by tables, and further sub-sorted by seat number. 
  • Room - sorts the report according to the alphabetical/numerical order of residence areas. 
  • Delivery Sequence - sorts the report according to the delivery sequence set up for room delivery. This option would be selected for residents with in-room service.
    
    
• Day - 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.
  
  
• Meal Stacks - with Meal Stacks selected, the report is structured to create individual “stacks” of the meal periods (breakfast, lunch, dinner) when you cut or tear the tickets. Breakfast tickets are generated on the left side of the page, lunch tickets on the middle of the page, and dinner tickets on the right of the page. Therefore, when the report is printed, you can easily cut/tear the tickets into the resultant stacks of each meal period. If a ticket for a meal period/day combination is not generated for a person for any reason, then that space is left blank on the page in order to conform to the meal stack structure.

Options to Include

• Highlight Allergies and Non-Regular Diet Orders - highlights in yellow a person’s allergies and non-regular diet types, textures, and fluid types.
  
  
• Date of Birth - includes the person’s date of birth in the ticket header.
  
  
• Likes & Dislikes - includes a person’s likes and dislikes set up in their personal menu.
  
  
• Preferences and Menu Customization - 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.
  
  
• ID:
  • Client ID - includes the person’s client ID in the header.
  • MRN - includes the person’s MRN (medical record number) in the header.

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. The sort options are as follows:

• Name - sorts the report alphabetically by last name.
• Dining Area - sorts the report according to the delivery sequence set up for dining areas (including residence area enabled as a dining area for in-room service), and sub-sorted by tables, and further sub-sorted by seat number. 
• Room - sorts the report according to the alphabetical/numerical order of residence areas. 
• Delivery Sequence - sorts the report according to the delivery sequence set up for room delivery. This option would be selected for residents with in-room service.