Hi Pablo, You news to be clearer about the requirement. Depending on the real requirement the student may be right. Remember that demographic model is recording instances of parties not classes. So if the requirement is to record the specific instance of device recording attributes such serial number, last calibration date etc then he is perfectly correct to reference this instance using a participation and party ref. However if he is just recording the type of device then you would use a protocol structure as per the blood pressure. Including an agent object by value within an entry is not allowed and in cases where we do need to record an instance of a device by value because we don't want the overhead of first recording the instance in a demographic repository and then referencing it then we do use the cluster approach that Heather referred to, but this is an implementation choice or even driven by the modeling process which wants to use a single model and by value associations to aid in model understanding. From experience, I don't think it is absolutely necessary to attempt to model the party model in the cluster structure, it just makes the model hard to understand and implement. Heath On 17/06/2012 12:41 PM, "pablo pazos" <pazospablo at hotmail.com> wrote:
> I'm correcting student papers for the openEHR course in spanish. > A student has modelled oftalmologic studies for diabetic patients, with a > demographic archetype of AGENT class to model all the devices used on the > test. > > It could be very usefull to let record the device information in the > ACTION archetype to say "this is the device we use for this test", or at > the INSTRUCTION archetype to say "this is the device that should be used > for the test". > > I'm sure some of you have solved this requirement, and I'll be very > thankful if you can enlight me, because I don't see how the information > model can solve this. > > Thanks a lot. > > -- > 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 <http://twitter.com/ppazos> > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120618/e2224d7f/attachment.html>
