In our domain, we don't need overly generalized messaging. We have a very limited scope that really matters. Messaging for limited scopes would be very easy and quick to implement - alas, we are too focussed on overly generalizing.
I think standards organisations get too general because they focus on supporting all use cases - and don't get me wrong, if its important for someone to be able to store it clinically, then I don't want to rule out a mechanism for the standard to represent it.. but at another much more practical level, you need a subset for your messaging format that answers the real practical questions i.e. this is a list of currently prescribed medications for a patient - why can't we agree on what that would look like, and leave the representation of 'history of allergies of father as relayed to doctor through daughter of patient' type stuff out for now..
OpenEHR has the better approach IMHO - but my personal preference would be even more domain specific (and thus simpler)
agreed - I as a technical person can pick up an openehr archetype and go "ah, that's where I'd store the hba1c reading and units".. Andrew _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
