Glossary of Dietary Management Terms

Healthcare food service runs on vocabulary that is precise inside the department and opaque outside it. These are the terms that come up when evaluating dietary software, defined plainly, with no assumption that you already work in a kitchen.

Diets and textures

The clinical instructions that determine what a patient may be served.

Diet order: The prescribed instruction for what a patient may eat and drink, issued by a clinician and held on the patient record. It typically combines a therapeutic component (for example renal or carbohydrate controlled), a texture level, and a fluid consistency. Everything downstream in a dietary system, from which menu items are offered to what prints on the tray ticket, derives from the diet order.
Therapeutic diet: A diet modified for a clinical reason rather than a preference, such as a renal, cardiac, carbohydrate controlled, low sodium, or high protein diet. Therapeutic diets restrict or emphasise particular nutrients, so menus have to be built and analysed against them rather than filtered by hand.
Texture-modified diet: A diet in which food is altered in texture so it can be chewed and swallowed safely, used mainly for residents and patients with dysphagia. Common levels run from regular through soft and bite-sized, minced and moist, and pureed. The texture level travels with the meal and must be visible to the cook, the tray line, and whoever serves it.
IDDSI: The International Dysphagia Diet Standardisation Initiative, a global framework that gives texture-modified foods and thickened drinks standard names and numbered levels. Its purpose is to remove ambiguity: before IDDSI, terms like soft or thick meant different things in different facilities, which is a genuine safety problem when a patient transfers between them.
IDDSI levels: A numbered scale from 0 to 7 covering both drinks and foods. Levels 0 to 4 describe drink thickness, running from thin (0) through slightly thick, mildly thick, moderately thick, and extremely thick. Levels 3 to 7 describe foods, running from liquidised and pureed through minced and moist, soft and bite-sized, to regular. Levels 3 and 4 appear on both scales because those consistencies can be either drunk or eaten.
Thickened liquids: Drinks thickened to a specified consistency so they move more slowly and are less likely to be aspirated by someone with swallowing difficulties. Older terminology used names like nectar thick and honey thick; the IDDSI framework replaced these with numbered levels to make the intended consistency unambiguous.
Adaptive equipment: Utensils and tableware that help a resident eat independently, such as a plate guard, a built-up handle, a spill-proof cup, or a nosey cup. Adaptive equipment needs belong on the tray ticket alongside the food, because the tray is assembled by someone who has not met the resident.
Never-serve item: A food flagged so that it is not served to a particular patient, usually a strong dislike rather than a clinical allergy. In Dietech it is set as a Never Serve adjustment on the patient's meal pattern, with a reason such as prescriber or resident choice, and applied every time that patient's menu is built. A Replace With adjustment swaps the item for one the patient can have instead.
Always-served item: A standing item a particular patient receives at every meal, such as a specific beverage, condiment, or supplement. Recording it once and applying it automatically is more reliable than expecting staff to remember it at every service.

Kitchen and service

How a meal is planned, produced, and delivered.

Tray ticket: The printed slip that travels with a patient's meal tray, listing the patient, their diet, texture and fluid consistency, allergies, adaptive equipment, the items on the tray with portion sizes, and the cart, tray, and location the meal is going to. It is the document that tells everyone downstream of the diet office what this particular tray must contain.
Tray line: The assembly line in a healthcare kitchen where individual patient trays are put together, usually as a moving belt with staff at stations adding items. It is the point where a meal stops being bulk production and becomes one named patient's tray, so it is where diet, texture, and allergy information has to be correct.
Production tally: A count of how much of each item the kitchen needs to prepare for a given meal service, calculated from actual patient selections and current census. Production tallies are the main lever on food waste, because a kitchen working from an estimate rather than a count will over-produce as insurance.
Menu cycle: A repeating schedule of menus, commonly running over several weeks before returning to the start, often with seasonal and holiday variants. Running a cycle rather than planning meal by meal makes nutritional analysis, purchasing, and production forecasting tractable.
Selective menu: A menu that offers patients a choice between alternatives at each course, rather than a single set tray. Selective menus improve satisfaction and reduce plate waste, at the cost of needing a system that can capture each patient's choices and turn them into accurate production counts.
Service window: The scheduled period during which a particular meal service is delivered. Grouping kitchen display orders by service window means the line sees what is due now rather than everything due that day.
Kitchen display system (KDS): Screens in the kitchen that show meal orders as they arrive, replacing printed tickets. In healthcare a KDS carries clinical information a restaurant system does not, including the diet order, texture level, and allergies, and it reflects late diet changes without needing a reprint.
Guest tray: A meal ordered for a visitor, usually a family member eating with a patient in the room. Handling guest trays in the same system as patient meals keeps them on the production count and, where relevant, on the bill.
Nourishment: A supplementary food or drink served between meals, often to support residents at nutritional risk. Nourishments are planned, produced, and documented separately from main meal service, and acceptance is recorded because that is the point of serving them.

Clinical and regulatory

The documentation side of a dietary department.

Positive patient identification (PPID): Confirming that the item about to be given to a patient is intended for that specific patient, typically by scanning their wristband and matching it against the item. Familiar from medication administration, it applies to meal trays for the same reason: a texture-modified or allergy-restricted tray delivered to the wrong bed is a safety incident, and tray delivery is otherwise verified only by someone reading a name.
MRN: Medical record number, the identifier a hospital assigns to a patient and carries on their wristband. A dietary system that can read the MRN can use existing hospital wristbands for tray verification rather than requiring a second, dietary-specific wristband.
Intake study: A structured record of how much a patient actually consumed over a defined period, as opposed to what was served. Intake data is what makes a nutritional assessment meaningful, which is why keeping it in the same system as the meal record matters.
Meal acceptance: The recorded proportion of a served meal that a resident ate. Tracked over time it is an early indicator of clinical decline, a driver of menu changes, and a routine part of survey documentation.
Nutritional assessment: A dietitian's structured evaluation of a patient's nutritional status, drawing on weights, intake, diagnoses, laboratory values, and diet tolerance, and producing recommendations that feed the plan of care.
Plan of care: The documented set of goals and interventions for a resident, including nutritional interventions. Dietary entries in the plan of care have to align with the diet order, the assessment, and what is actually being served, and inconsistency between those is a common survey finding.
Census: The current count and composition of patients or residents in a facility, including who is admitted, discharged, or on leave. Census drives production counts, so a dietary system reading a stale census will produce the wrong number of meals.
PDPM: The Patient Driven Payment Model, the Medicare payment methodology for skilled nursing facilities that determines reimbursement from patient characteristics rather than volume of therapy delivered. Nutritional status and related clinical documentation contribute to it, which is why dietary records have a reimbursement dimension as well as a clinical one.
State survey: The periodic inspection of a long-term care facility by state regulators, covering dietary services among other areas. Surveyors typically ask to see diet orders and changes, allergy records, weight tracking, meal acceptance, and assessment documentation, which is why those records need to be produced as work happens rather than assembled afterwards.

Integration and purchasing

How the dietary system connects to everything else.

HL7: A long-established family of messaging standards for exchanging clinical data between healthcare systems. In dietary integration the relevant message types are ADT for patient admissions, transfers and discharges, and order messages carrying diet orders from the EHR to the dietary system.
ADT feed: The stream of Admission, Discharge and Transfer messages a hospital broadcasts as patients move. For a dietary department it answers the questions that determine meal production: who is here, where are they, and who has left.
FHIR R4: Release 4 of Fast Healthcare Interoperability Resources, a modern web-API-based standard for exchanging health data. It is generally simpler to work with than classic HL7 messaging and is the basis for most current EHR integration programmes.
SMART on FHIR: A specification that lets an external application be launched from inside an EHR already knowing which patient and user are in context, using standard authorisation. In practice it means a clinician can open the dietary system on the right patient from the chart rather than searching for them again.
USCDI: The United States Core Data for Interoperability, a federally defined baseline set of health data classes that certified systems are expected to be able to exchange. It sets the floor for what an integration should be able to carry.
Order guide: The list of products a facility is approved to buy from a given supplier, with contracted pricing attached. Ordering from an order guide rather than a general catalogue keeps purchasing inside negotiated pricing.
Par level: The stock level an item should be maintained at, used to trigger reordering. Par levels set too high tie up cash and produce spoilage; set too low they cause substitutions that undermine the planned menu.
GPO: A group purchasing organisation, which negotiates supplier pricing on behalf of many member facilities. Purchasing systems need to apply GPO contract pricing so that what is ordered matches what has been negotiated.
Cost per patient day: Total food cost divided by patient days over a period, the standard operating metric for a healthcare food service department. It is only meaningful when production, purchasing, and census data are accurate, which is why the three usually need to live in one system.

Evaluating dietary software?

We will walk through how any of these work in practice, using your own diets and menu cycle rather than a canned demonstration.

Schedule a Demo Call (716) 565-9400