01.05.2013 Views

Food-Service-Manual-for-Health-Care-Institutions

Food-Service-Manual-for-Health-Care-Institutions

Food-Service-Manual-for-Health-Care-Institutions

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Food</strong> <strong>Service</strong> <strong>Manual</strong> <strong>for</strong> <strong>Health</strong> <strong>Care</strong> <strong>Institutions</strong><br />

280<br />

Processing<br />

Processing involves the actions or treatments required to convert data into useful in<strong>for</strong>mation.<br />

Processing usually involves sorting and classifying data into categories, per<strong>for</strong>ming calculations,<br />

summarizing results, and storing both data and in<strong>for</strong>mation <strong>for</strong> further processing. In the<br />

accounts payable example described above, data manipulation involves determining the dollar<br />

value of all purchases made from individual vendors, as documented by invoices, to determine<br />

what is owed each vendor.<br />

Data may be further coded by classifying each purchase by type of commodity (such as<br />

produce, meat, dairy product, chemicals, or paper supplies). This allows the system not only to<br />

produce checks <strong>for</strong> vendors but also to generate in<strong>for</strong>mation that allows the food service director<br />

to monitor the dollar value of different categories of purchases.<br />

Data-processing functions are similar <strong>for</strong> all the various units of a food service operation—<br />

such as marketing, purchasing, inventory control, and meal service. According to Stair, all processing<br />

elements have a number of characteristics in common, including:<br />

• A large volume of input data<br />

• A large volume of output<br />

• Numerous users affected by the system<br />

• A need <strong>for</strong> efficient processing<br />

• Large-volume storage requirements<br />

• Fast input and output capabilities<br />

• Low computational complexity<br />

• A high degree of repetition in processing<br />

• A high potential <strong>for</strong> problems related to security<br />

• A severe adverse effect on the organization if the processing element breaks down or<br />

fails to operate correctly<br />

Each of these characteristics must be considered when developing the MIS and particularly<br />

when designing the system’s processing element.<br />

Output<br />

In an MIS, output involves producing in<strong>for</strong>mation, usually in the <strong>for</strong>m of report documents,<br />

that is appropriately relevant <strong>for</strong> the food service operation and its decision makers. Other outputs<br />

may include vendor checks, reports of purchases by food category, and analyses of patient<br />

food costs <strong>for</strong> the administration’s use. The MIS can produce reports required by local, state,<br />

or federal agencies—<strong>for</strong> example, sales tax reports <strong>for</strong> cafeteria operations. Three broad report<br />

categories are described briefly below.<br />

Types of Reports<br />

The reports output by an MIS can be classified as scheduled, demand, or exception reports.<br />

Scheduled reports are produced periodically based on a set schedule (daily, weekly, or<br />

monthly). For example, the food service manager might receive a weekly report of sales <strong>for</strong><br />

each revenue-producing food unit in the health care operation. Or, an inventory report might<br />

be produced on a monthly basis so that the value of each category of food inventory can be<br />

monitored.<br />

Demand reports, on the other hand, are developed and produced to provide specific in<strong>for</strong>mation<br />

requested by a manager. In other words, these reports are not generated on a routine<br />

basis. Thus, a manager who needed to know total sales <strong>for</strong> a specific menu item during the year<br />

would rely on the in<strong>for</strong>mation generated by a demand report.<br />

Exception reports are produced when a situation occurs outside the limits set by management<br />

and require manager action. For example, an exception report could be generated

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!