> Thomas Beale wrote > > Andrew Patterson wrote: > > Given Australian government > > departments barely keep their names for more than a few years, what are > > the chances the URL is still working? If it is a local reference, what are > > the > > chances the machines still have the same IP addresses or names? > > > this points to the need to use safe URLs that will work. Do we think the > URL "http://snomed.org" is safe? Maybe we need "http://terminology.net" > or somesuch. The use of URLs whose meaning will not change over time is > not to be taken lightly... [...] A safe URL is needed for each clinical terminology authority. (e.g. standards are managed by ISO, Standards Australia etc.; SNOMED UK and SNOMED AUS may have country specific needs) > > I think having URL's in the archetype definition mixes the 'configuration' > > of > > the system with the definition. I guess I would like to see some sort of > > query language in this space so that one could say > > > > <"at0004"> = < > > <"snomed"> = <all 'route of medication' where refset('australia')> > > <"icd-10"> = <12312-23> > > Agreed. > this is where we were about 1-2 years ago in the thinking of this > problem; now we have reached a point of: > * firstly having realised that the query should not itself go into the > archetype, only an id for the query [...] > I am not sure what we should be doing about ideas like > "refset('australia')" though.... > - thomas beale The query tool needs to manage this, as it should manage the language. I suggest the user (or user environment) should be able to select whether to look at local terminology or that of another country (the default may be where the patient's record was created, and the patient was travelling at the time or subsequently emigrated).
On storing a new event, the term accessed at the time should be stored in the record, not (just) the SNOMED code or URL, because the terminology may be updated on the server, and a future access should show the info known at the time of entry. Colin Sutton (not an authoritative answer!) #################################################################################################################### IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. The CTC is not responsible for any unauthorised alterations to this e-mail or attachment to it. Views expressed in this message are those of the individual sender, and are not necessarily the views of the CTC. If you receive this e-mail in error, please immediately delete it and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. ##################################################################################################################### -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 4046 bytes Desc: not available URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070107/c85c7e10/attachment.dat> -------------- next part -------------- _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical

