Hi Dmitry, OBJECT_ID can point to the uid inherited from LOCATABLE, but as you can see in the model (http://openehr.org/releases/1.0.2/architecture/rm/common_im.pdf page 13), uid is optional. I wouldn't like to have my references rely on an optional attribute. I didn't designed the model, but that seems reasonable to me.
-- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com > From: [email protected] > To: [email protected]; [email protected] > Subject: Re: Party-actor-folder relationships in hierarchy > Date: Fri, 27 Nov 2015 11:11:06 +0300 > > > Hi Dmitry, > > > > Consider that the folder structure is defined for each EHR, and can vary > > vary between ehrs inside the same company. > > I would use LINK to link the org to the ehr folder struct. > > (ORGANIZATION as LOCATABLE).links[0] points to a folder/versioned folder > through URI? > > Thank you Pablo, good idea. Hard to guarantee referential integrity, but... > Why is it no class to link two entities using theirs OBJECT_ID? :) > > -- > Regards, Dmitry
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
