Hmm. I can see why some groups might want to limit the scope of their applications to EHR pure clinical, research type usage that ONLY had clinically relevant demographic data.
But I don't think OpenEHR as a whole should have that scope limitation. Nor do I think it does, to date the archetypes have shown to be quite flexible in modeling a variety of data. If Oceans direction is not to tackle hospital administrative and demographic data which is critical to EMR type applications which run in a live, working system then I totally understand that - you have limited resources and have already done so very much. This might explain (ahem) the delay in getting demographics online. But what is more concerning to me is that we have a new set of ADLs that are using a new structure that is not compatible with the current set of editors. Bert said he might have overlooked something, I never looked in order to overlook - I took for granted that the ADL structure was already maximally defined and that any demographic or administrative data would fit into this structure. Having looked at new the new demographics they cover demographics and not general administrative data typical to most HL7 interfaces. I have not ruled out create the archetypes ourselves but I don't have enough resources today. Our system can support many coding systems but I would have like to understand if OpenEHR leadership are going to support the broader needs of the community - and we recognize they need resources to do that - it cannot fall on Oceans shoulders - but at the same time if CKM becomes the preferred tool we should organize accordingly. -- Gregory Caulton Principal at PatientOS Inc. personal email: caultonpos at gmail.com http://www.patientos.com corporate: (888)-NBR-1EMR || fax 857.241.3022 > Greg Caulton wrote: >> I am confused - hopefully you saying that those particular 'older' >> demographic models are not supported? >> >> But there are newer ones right being added to the CKM that conform to >> the ADL structure the other clinical ADLs use? > > Hi Greg, > > the new ones, based on ISO 22220, made by Rigoleta Dutra and Sergio > Freire in Brazil will replace any of those early ones. I think they are > still messing around with them a bit before putting them on CKM. > Initially, they don't have a GUI editor tool, and have to be edited by > hand in ADL (one of the reasons we took the trouble to make sure ADL > was > human-readable). > >> >> You are not saying an AQL query for >> >> Women over 50 - 70, last mammogram > 2 years >> >> cannot be supported because demographics are not relevant? > > it already can, regardless of demographics, because such clinically > relevant data as date of birth and sex are recorded in the EHR anyway - > you would not attempt to do a join across EHR and demographic services > to answer that query. Although, if you had a service more oriented to > demographics + admin events, you could potentially satisfy this query > on > it; however, in general, clinical queries will refer to a mixture of > basic data like age, sex, maybe occupation (where relevant to health) > etc, as well as the 'hard' clinical data; they would normally be run on > an EHR containing this data. > > > - thomas beale > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >
