On 22/06/2010 15:00, Ian McNicoll wrote: > Hi Igor, > > This is an interesting area which does not neatly fit within the core > openEHR focus. > > We already have the EHR domain focussed on patient clinical data and > the Demographic domain which deals with patient and provider > demographics. What you are describing does not really fit terribly > neatly with either domain, and should probably be thought of > separately as a 'Assets' domain, which may deserve its own part of the > openEHR reference model. Although the Demographics service is a > better fit for this kind of 'reference data', this still does not feel > quite correct and the Demographics Reference model is not really > appropriate for this use, in my opinion. > > One option, for now) would be to model Ward and other simiilar > assets using traditional RDBMS approach and simply use a unique ID > within the patient EHR to refer to the ward e.g patient's current > ward. You could always use Admin_entry archetypes to facilitate the > requirements modelling. > * > *
certainly some extensions would be required to the demographic reference model to cope properly with 'estate' and other kinds of asset modelling. If there is value in such addtions to openEHR, they should be made - the reference model is not meant to be static forever, indeed just the opposite. - thomas beale -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20100622/512c8a0f/attachment.html>
