I would not "house" all relevantly related methods for that object in it.
Your example of "patient admissions" is a separate object and the business of patient admissions is the sole responsibility of that other object. If take your line of reasoning to it end, you'll end up including things like which ward(s), the bed(s) in the ward, their GP, attending physicians, attending nurses, surgeons who operated on them, vital signs, ordered tests, test results, x-rays, MRIs, sonograms, etc. Patients move through hospitals, hospitals don't move through patients. Besides, all this information can be found in their medical record and that's a separate set of objects which refers to the patient object. Keep your objects as simple as possible, but no simpler. Chris -- Chris Velevitch Manager - Adobe Platform Users Group, Sydney m: 0415 469 095 www.apugs.org.au Adobe Platform Users Group, Sydney Topic: Making Sense of Mobile Date: 29th November 6pm for 6:30 start Details and RSVP on http://apugs.groups.adobe.com/index.cfm?event=post.display&postid=32492 -- 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.
