Hi All The idea of a device as an agent is interesting and at some point devices will have features of agents. The use of a re-useable cluster is clearly the solution - regardless of which part of openEHR it belongs.
The problem here is that we have demographic and EHR models - that share some classes - and an ID that requires declaration. Generally, I think the best approach is to think if information might be in the EHR - if so, then it needs to use EHR or common classes. Until we have a commitment to use an authorative source of IDs for archetypes regardless of where they are generated, I think we will struggle. I will say more in another post. Cheers, Sam On 18/06/2012 2:18 AM, pablo pazos wrote: > Hi Gustavo, > > As Heather pointed out, the solution seems to be to reference the > internal structure of a device (or any other demographic archetype) > through a CLUSTER. But I think those demographic concepts should be > also modelled as complete, separate demographic archetypes, > referencing the same internal structure (CLUSTER). This allow us > (developers) to create functionalities for searching and processing on > demographic archetypes. > > About the internals of a test, I think most often includes both ACTION > and OBSERVATION, because an ACTION could be used when you need to > record information about the execution itself (being or not a clinical > intervention on the patient, e.g. the recording of the device used to > make the test should be part of the ACTION not of the OBSERVATION), > then the OBSERVATION(s) could hold the information about the test > result or information about clinical findings during the test. Then > the whole record of a test execution should be recorded into a > COMPOSITION that references those ACTION(s) and OBSERVATION(s). > > The INSTRUCTION of a test could reference to a device that should be > used on the test, but during the test maybe another device was used, > and that should be part of the ACTION that executes the INSTRUCTION. > > Does this makes sense to you? Please correct me if I'm wrong. > > My student detected some oftalmologic concepts that are not in the > CKM, maybe I can put you both in contact to collaborate on the > modelling of those concepts. > > -- > Kind regards, > Ing. Pablo Pazos Guti?rrez > LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez > Blog: http://informatica-medica.blogspot.com/ > Twitter: http://twitter.com/ppazos > > ------------------------------------------------------------------------ > From: gbacelar at gmail.com > Date: Sun, 17 Jun 2012 10:03:15 +0100 > Subject: Re: An ACTION or INSTRUCTION referencing an AGENT, is it > possible? > To: openehr-clinical at lists.openehr.org > > Hi Pablo, > I'm an ophthalmologist and would be gladful to help. > > There are some issues about the archetype class and the nature of the > test. As it is a study test it must be considered the existence of an > intervention. If it does not include, so the most appropriate would be > to record as an OBSERVATION archetype for the test. If it includes an > intervention, then the most appropriate is to record as ACTION. For > both situations use the "Device" CLUSTER on the CKM to record the > device, remembering this archetype is not adequate to record a > substance (e.g. fluorescein). > > To record the device that should be used for the test at an > INSTRUCTION archetype, also consider the element "Description of > Procedure" of "Procedure Request" archetype on CKM, which could be > used to specify the device. > > I hope it was helpful. > -- > Gustavo Bacelar > MD + MBA + Med Informatics > gustavobacelar.com <http://gustavobacelar.com> > +351 91 203 2353 > +55 71 8831-2860 > Skype: gustavobacelar > > > _______________________________________________ openEHR-clinical > mailing list openEHR-clinical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org > > > _______________________________________________ > openEHR-clinical mailing list > openEHR-clinical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20120618/616b7287/attachment.html>
