gnumed-devel
[Top][All Lists]
Advanced

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

[Gnumed-devel] About EMR items Value Objects


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

Hi,

I'm working in gmPatientExporter. It will provide human readable ASCII export 
of patient record. It's data (eg. EMR) can be constraint by various 
criterions, as in  gmClinicalRecord get_text_dump method.

I'd like to comment this design idea: In order to abstract and isolate any 
kind of clinical items (vaccinations, allergies...), to be able to manage and 
work with them, gmClinicalRecord would create (in a method with a logiic 
similar to get_text_dump), according with data, different gmItemVO objects. 
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
                item_type (vaccination, allegy, etc..)
                episode
                modified_when
                narrative
                health_issue
                id_encounter
                -------------
                get_item_type()
                get_head_text_dump() ... date, health issue, encounter, episode
                get_text_dump() ... virtual, concrete items will define it
                get_tail_text_dump() ... ----- table, writte date, written by

        gmItemVaccinationVO (gmItemVO): derived  that encapsules a vaccination 
item
                batch no
                patient
                provider
                vaccine
                site
                -------------
                get_text_dump() ... batch no,  patient, provider, vaccine, 
site. Would call 
parent's get_head and get_tail_text_dump to complete all item information.

        ... and so with lab request, and allergies items

        gmPatientExport would call gmClinicalRecord to obtain a list of items 
and 
iterate calling item.get_text_dump(), printing/exporting to file...

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


Best regards,
Carlos




reply via email to

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