Hi Everyone, I have an OOP question for those in the know. We write a Patient Management System and have been steadily creating objects and CFCs for all new work. The time has come to do "something" with our patients.
Normally I would have an object, and all relevantly related methods for that object would be "housed" within the same object. The issue I have is - that just about everything relates to a patient in a behaviour / code sense. I can easily see the patient object groing to some obscene length because of all the things you can do to a patient. Eg you can admit a patient. discharge a patient re-admit a patient etc. or illustrative purposes let's consider discharging a current patient. There is a pre-defined set of steps that need to be done. * Ensure that the user has an appropriate level of authorisation for THIS process. ** This is a method in a "permissions" sub-system that we have already created. ** Ensure THIS patient is valid to be discharged. ** you cannot discharge a patient that is already discharged ** you cannot discharge a referred patient that has not been admitted. * Provide a form to collect the relevant data required for the discharge record. ** Some of this information is stored in a dischargeinformation table ** Some of this data is stored directly in the patient table - and would be a property of the yet-to-be-created patient CFC. My question is; Where does the business logic for this "kind of thing" go? It's patient related so I figure it should go in the patient object. But it's not completely operating on just the patent object. the discharged information will not be part of the normal patient object . I look forward to some insight - and thanks as always! Gavin "Beau" Baumanis -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
