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
A fun thought for you before I go to sleep tonight -
Does the patient admit himself to the Hospital (assuming it's a Hospital),
or does the Hospital admit the patient to itself?
Think about it from a real work perspective.
(Not really knowing how Hospitals work.. but) I would have thought that t
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
Chris has a point. The Patient.cfc need not be too large. You must decide if
you will invoke other CFCs or extend them.
Extending is trickier but worth it if you get it right.
Have you considered CF9s built in ORM?
> Date: Tue, 14 Dec 2010 23:10:57 +1100
> Subject: Re: [cfaussie] OOP question.
HI Mark / Chris,
Thanks for the reply.
I suppose my dilemma is that I can't really think of anything other than the
patient that I can attribute this task too.
So in this "grey area" do I create a separate a separate object?
That seems the most sensible, but... I just thought I would check. Beca
Hi Mark,
I am in agreement.
The reason for my post is that I could see the patient object getting REALY big
if I included things like this is in it.
As for the ORM, (despite the fact that I am using ORM)
I'm not sure how that has any effect here at all.
Surely the process of persistence is a dis
Well how does a hopsital manage this?
On Wed, Dec 15, 2010 at 8:30 AM, Gavin Beau Baumanis wrote:
> * Patient Admissions
>
A Hospital has a series of patients that it has admitted. So I expect you
would have:
Hospital.admit(patient)
> * Patient Discharges
>
Ditto:
Hopsital.dischard(patient)
Oh nice, I kinda like that.
There is a central Admissions department, that manages what Ward and/or
services a Patient goes to.
Makes sense to me.
Mark
On Wed, Dec 15, 2010 at 10:06 AM, Barry Beattie wrote:
> IMHO Hospital is too big.
>
> the way I see it, it's admissions that
>
> Admissions.a
IMHO Hospital is too big.
the way I see it, it's admissions that
Admissions.admit(patient)
and
Admissions.dischard(patient)
my 2c only.
On Wed, Dec 15, 2010 at 8:11 AM, Mark Mandel wrote:
> Well how does a hopsital manage this?
>
> On Wed, Dec 15, 2010 at 8:30 AM, Gavin Beau Baumanis
> w
I won't be able to make it. I'm flying to Sydney tomorrow evening :(
Have fun and Merry Christmas to you all.
Sent from my iPhone
On 14/12/2010, at 4:18 PM, Chong wrote:
> I will be there (i also rsvped on the group page)
>
> On Dec 14, 4:01 pm, Paul Kukiel wrote:
>> I'll be there.
>>
>>
I'll be there
Regards
Dale Fraser
http://dale.fraser.id.au
http://cfmldocs.com
http://learncf.com
http://flexcf.com
-Original Message-
From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf
Of MrBuzzy
Sent: Wednesday, 15 December 2010 12:37 PM
To: cfaussie@googlegro
Hi Gavin,
Try not to think of OO design as an ER diagram with related methods bolted on
to the tables - I did this once a long time ago, I'm sure there's an
anti-pattern name for it, and it is not how OO apps get built.
Use objects to isolate code that may need to change independently of other
12 matches
Mail list logo
