[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] About EMR items Value Objects

From: Carlos Moro
Subject: Re: [Gnumed-devel] About EMR items Value Objects
Date: Sat, 27 Mar 2004 16:29:09 +0100
User-agent: KMail/1.6


On Saturday 27 March 2004 09:52, Karsten Hilbert wrote:
> There's no need to name them gm*VO. The very fact of
>     vacc = gmVaccination.cVaccination()
> and thus vacc being
>     isinstance(cVaccination)

Right. We can also add another useful field to base clase, instead of 
item_type. item_table: 'vaccination', 'lab_request', 'allergy'.

> makes it a value object, namely an instance.
> I would just call them gm* or c*.

Sure, i agree.

> > Once we got them, we can easily work with them, eg. in text dumping their
> > information. The design would be somehing like this:
> >     gmItemVO: parent class with  members and methods common for every item
> > type id
> pk -> primary key
> Note that this is ambigous as one of those objects can span
> several tables.

I'm not really sure about it, but at first maybe we could use  'pk serial 
primary key' sql table field, at least to keep some track of the item... 

> >     gmPatientExport would call gmClinicalRecord to obtain a list of items
> > and iterate calling item.get_text_dump(), printing/exporting to file...
> This still is but a better text *dump*. Eventually, for the
> *exporter* I was thinking of a more formatted output, grouped
> by clinical sanity (see that earlier mail). Yes, that's
> harder.

Oops, sorry it's correct ;) . We could provide in vos those simple 
get_XX_text_dump() just, as a quick text dump of its contents (that maybe 
could be used later in gmClinicalRecord.get_text_dump())... But, the export 
tool would provide some methods that retrieve adecuate values object's fields 
to provide a more estructured text (as Karsten proposed):

>>Patient details:
>>Treated from ... to ...
>>1) Allergy status:
>>2) Vaccination status:
>>3) Course of treatment:
>>health issue
>> episode
>>  encounter
>>  encounter
>> episode
>>  encounter
>> episode
>>  ...
>> ...
>>Chronological chart:
>>date | source | values

> >     I think these objects could be useful for other modules (in future
> > code), so they could be located in client/vos...
> client/business/

Best regards,

PD: I'm now trying python eclipse 2.1 plugin (
projects/pydev/), it's yet alpha but really nice as editor, class navigator, 
and cvs ;)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]