Totally agree. The change in domain name is, BTW, less likely than a change in software vendor. With OID's chances are that not the hospital will have an OID, but the software package installation, as a sub of the software package, as a sub of the software company. FQDN of the software company or the hospital is never worse. And the whois objection is extra: this feature isn't even defined for OID.
On 9 Mar 2005, at 2:31h, Thomas Beale wrote: > Jan Dockx wrote: > >> There is such a system: DNS. Why in heavens name did we invent a new >> one? >> > DNS is great. In fact, I would suggest that DNS has more chance of > including more organisations (represented by their domain names) than > ISO OIDs. But...what if a hospital changes domain name, but is still > the same hospital? DNS does not have identifying information other > than the domain name administrator details (what whois returns); is > this enough? In any case, DNS only works for organisations and > sometimes pieces of organisations. But how do we want to identify a > prescription for example, or a lab result? One way is with an OID; > another way is domain_name+lab_result_id. I think the latter is much > more realistic today, even if the former seems more theoretically > satisfying (even if it completely unreadable to humans;-) > > - thomas > > - > If you have any questions about using this list, > please send a message to d.lloyd at openehr.org > Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 2415 bytes Desc: not available URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20050310/42ad5798/attachment.bin>
