Hospitals are building continuous, personalized nutrition relationships with patients. The systems connecting that knowledge to the kitchen haven’t caught up.
A hospital network in Pennsylvania has expanded a program that assigns a single food and nutrition concierge to a patient’s entire stay, from emergency department admission through discharge, rather than treating food service as a series of separate transactions. A medical center in New Jersey has redesigned its dining spaces, healing garden, and food program to make nutrition a more visible part of the patient experience. Both represent a shift already underway: food service in healthcare increasingly means one continuous relationship with a patient rather than a series of disconnected meal deliveries.
That continuity creates a requirement neither model was originally built to solve. If one person or one team is tracking a patient’s preferences, restrictions, and needs across an entire stay, that knowledge has to show up correctly in three separate places: the clinical record the care team relies on, the kitchen preparing that night’s production run, and the diet office coordinating tomorrow’s trays. A relationship that only lives in one person’s memory is a relationship that breaks the moment that person goes off shift.
Three Places One Patient’s Needs Have to Travel
A shift change is the simplest version of this problem. A new nurse or a new concierge coming on duty needs to know what the last one learned, immediately, not after a conversation that may or may not happen during handoff. A floor transfer is a harder version: the patient moves, and whatever preferences were tracked on the previous unit need to travel with them. Discharge is the hardest version because everything learned over days or weeks needs to reach whichever provider sees that patient next.
Even with electronic health records standard across U.S. hospitals, evidence suggests the clinical piece of that handoff still lags. A national analysis of U.S. hospital discharges reported in the Journal of Hospital Medicine found documented malnutrition diagnoses increased from 6.6% in 2016 to 8.6% in 2019. Yet studies continue to estimate that 20% to 50% of hospitalized patients are malnourished when screened using validated assessment tools. This comes to show that having an EHR isn’t the same as having a workflow that reliably carries a nutrition finding from the bedside to everyone who needs to act on it.
The Kitchen Has the Same Problem the Chart Does
The clinical record isn’t the only place this breaks down. When a concierge learns that a patient now prefers smaller portions or can’t tolerate a specific texture, that information has to reach not only the doctor, but also the team planning tonight’s production run and the staff building tomorrow’s trays. If that update lives in a conversation or a sticky note instead of a connected system, the kitchen is working from yesterday’s information even when the clinical chart is current.
This is the gap Culinary Digital built The Operating System for Institutional Foodservice to close. Picture a hospital’s food and nutrition team midway through a patient’s stay, tracking preferences and restrictions that need to reach the clinical team, the kitchen, and tomorrow’s diet office schedule, all at once.
CulinarySuite Operate’s Patient Order Entry System keeps individual dietary orders synced in real time with the hospital’s connected care system, through HL7 integrations with platforms like Epic, Cerner, and Meditech, so that information is already part of the same clinical record the care team relies on. The same order also drives recipe and menu management, keeping menus, recipes, and meal production aligned with the patient’s most current needs.
A concierge model builds a detailed, continuous picture of one patient’s needs. That picture only holds up if it reaches the clinical chart, the kitchen, and the diet office at the same time, not whichever one someone remembered to update.
Continuous Care Needs a Continuous System Behind It
This is fundamentally a systems challenge. Adding more concierges or more dietitians doesn’t close the gap between what one person learns and what three different teams need to act on. . Connecting the order, the production plan, and the clinical record through the same underlying system does. The team captures a patient preference once, and the same system carries that knowledge across every workflow that depends on it.
The Model Is Spreading Faster Than the Infrastructure Behind It
More hospitals will likely take on some version of this continuous-care model in the next few years, because the patient response has been strong enough to justify expanding it. The hospitals whose kitchens and clinical systems already share the same record will be able to scale that model past a handful of concierges. The ones still relying on a person to carry that knowledge between departments will find the model harder to expand than it was to pilot.
See CulinarySuite in Action
See how CulinarySuite Operate keeps a patient’s dietary information connected across clinical systems, production planning, and diet office workflows.
Frequently Asked Questions
What data challenges do hospital concierge and continuous nutrition care models create?
A continuous care model depends on one patient’s preferences and restrictions being tracked across an entire stay, but that information has to reach three separate places to be useful: the clinical record, the kitchen’s production plan, and the diet office’s schedule. When those systems aren’t connected, the knowledge one concierge or dietitian builds up doesn’t automatically reach the teams who need to act on it.
Why do patient dietary preferences sometimes not reach the kitchen or the clinical record?
Even with electronic health records being standard in US hospitals, a preference or restriction learned by one staff member often has to be manually relayed to clinical, production, and diet office systems separately. Research shows this gap persists even in documentation specifically aimed at the clinical record, with malnutrition coding still covering only a fraction of actual bedside prevalence.
How does CulinarySuite Operate connect patient dietary information across clinical, production, and diet office systems?
CulinarySuite Operate’s Patient Order Entry System keeps individual dietary orders synced in real time with a hospital’s connected care system through HL7 integrations with platforms like Epic, Cerner, and Meditech. The same order also flows into recipe and menu management, so a patient’s current preferences and restrictions reach the kitchen’s production plan and the diet office’s schedule at the same time they reach the clinical record.
