Based on the clinical concepts of the New University Hospital and decisions about design and architecture we can identify a range of functional requirements that describe future processes, working methods etc on New University Hospital. Decisions for example that we build single person patient rooms single rooms or the establishment of cluster pharmacies will also require a wide range of requirements for future solutions.
From these functional requirements we then can identify a number of IT requirements that will make us able to solve or meet the functional requirements. These IT requirements can be assembled in IT solutions that solve one or usually more functional requirements. In other words, it reflects the clinical concepts and architecture and design requirements for future hospital - IT solutions ensure that these can be realized.
The following is an example where the kitchen and food logistics concept and the choice of making local floor kitchens around the hospital will cause the food to be transported from the central kitchen out to the floor kitchens. Here it is prepared and served on trays to patients. The Central kitchen staff therefore requires that they can monitor the food temperature from leaving the central kitchen to arrival in the floor kitchen. This is referred to as they want to monitor if the "temperature chain is broken." This can be solved in many ways, and one of them is to install censors in the crates which food is stored in. Data on temperature must be collected in an IT system, and to be given an alarm if the temperature rises to an agreed level and therefore the temperature chain is broken. Functional requirements from the central kitchen about securing healthy food that are always cold ends with an IT solution or an expansion of existing solution, so it is possible to continuously monitor the temperature of the food and give a warning if the temperature rises above a defined level.
The method is rather easy to understand, to communicate and it ensures that we always focuses on the business requirements and not start with IT. I guess a simple, understandable and effective method is always preferred in a busy schedule. It works for us at least.
The following is an example where the kitchen and food logistics concept and the choice of making local floor kitchens around the hospital will cause the food to be transported from the central kitchen out to the floor kitchens. Here it is prepared and served on trays to patients. The Central kitchen staff therefore requires that they can monitor the food temperature from leaving the central kitchen to arrival in the floor kitchen. This is referred to as they want to monitor if the "temperature chain is broken." This can be solved in many ways, and one of them is to install censors in the crates which food is stored in. Data on temperature must be collected in an IT system, and to be given an alarm if the temperature rises to an agreed level and therefore the temperature chain is broken. Functional requirements from the central kitchen about securing healthy food that are always cold ends with an IT solution or an expansion of existing solution, so it is possible to continuously monitor the temperature of the food and give a warning if the temperature rises above a defined level.The method is rather easy to understand, to communicate and it ensures that we always focuses on the business requirements and not start with IT. I guess a simple, understandable and effective method is always preferred in a busy schedule. It works for us at least.
Ingen kommentarer:
Send en kommentar