> All software systems describe a certain data structure (if in > database, it would be a database structure). At some point, if we > want to move information between systems, we need to map one data > structure to another. I doubt implementing an all encompassing set > of database tables will be a viable solution. As Thomas Beale > (GEHR) and I repeatedly stated in our OpenHealth list postings, no > set of database tables/schema will ever be comprehensive. New > medical knowledge will always need to be incorporated!
I am fully aware of and I agree with your statements. > > > And then we could write different clients. > > > (PHP, PHP-Gtk, TclTK, Python, etc.) > > > > GNUmed (Python) uses its DB (of course) and ResMedicinae (Java) > > might eventually also use it (not reached that state yet). Now > > you have the chance to use it, too. I would like to see that! > > Sharing the DB is a good idea. However, is the DB schema easy to > extend and manage over time? For example, if I take the GNUmed DB > and modify a few of its tables (e.g. for psychiatry), how do I make > sure that I don't break compatibility with the Internal Medicine > modules? How do I make sure what I added will work with other > people's ideas for describing the psychiatry domain? You are right. That's the point. But as long as OpenEHR/GEHR is still in a research phase, it is more workable for us to use our own Domain/ ER model for prototyping and useable results. We know that it will have to be changed towards OpenEHR Archetypes in the next few years. I think that it is too early. I am currently busy enough to implement GUI and persistence layer stuff and want to leave the Domain modelling to OpenEHR for now - but plan to use it later. Have you GNUmed people had a look at the HL7 RIM? I hope most of us agree that OpenEHR is the better approach, but for the current ER Modelling that GNUmed is doing, the RIM might be very helpful: http://www.hl7.org/library/data-model/RIM/modelpage_non.htm Download "Graphical Expression Files (ZIPped)". They also splitted up the whole Domain into sub-areas (Entities, Roles, Finance, Services). > I urge you to read Thomas Beale's excellent paper: > http://www.deepthought.com.au/it/archetypes/Output/front.html Already did that. I even "robbed" his ideas (but referenced him) to incorporate them into the updated ResMedicinae Architecture presentation (Chapter 3 "DomainModelling" ff.): http://resmedicinae.sourceforge.net/model/design/presentation/index.html Best Regards, Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
