Hi Thomas, Thanks for the info. Just to clarify my understanding, you feel that the namespace attribute in for information only and so can be set as we choose.
However, I am not sure that I understand your statement "all target OBJECT_IDs of the various concrete types are already globally unique". Do you mean using UUIDs for EHRID, PersonID etc? Can you elaborate some more one how this is being managed? regards Dileep V S *Founder* HealtheLife Ventures LLP m: +91 9632888113 a: 106, Innovation Centre, IIIT, Electronics City, Bangalore 560100 w: healthelife.in e: [email protected] On Wed, Dec 12, 2018 at 5:51 PM Thomas Beale <[email protected]> wrote: > Hi Dileep, > > as far as I know, all target OBJECT_IDs of the various concrete types > are already globally unique. I suspect the namespace attribute will not > be used in the future, or will have just informational value. It would > be useful to know what other implementers currently do with this attribute. > > - thomas > > On 12/12/2018 11:18, Dileep V S wrote: > > Hi, > > Compositions require id_namespace for composer and healthcare > > facility, along with id & id_scheme, to uniquely identify them. How do > > we ensure universal uniqueness for such name spaces? Is there any > > central registry where EHR systems are supposed to register their > > namespaces? > > > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
