Hi Thomas,
As another member of IHTSDO Technical Committee I would like to ask from
where you have got your impression that RefSets should mainly be maintained
by the national release centers, because that is not at all my impression.
Some of the national release centers, like NHS in UK, maintain
Subsets/RefSets, but I have never heard anything about that only the
national release centers should create and maintain RefSets. My impression
is that whoever that find it useful to create and maintain an own RefSet
should be able to do it.
The only requirement to create a RefSet is the technical requirement to have
an own namespace to create the RefSet into. However, all organizations and
persons with a valid SNOMED CT license can get an own namespace.
(I have my own namespace, so if I would I could immediately produce and
release as many RefSets that I want.)
Greetings,
Mikael
From: [email protected]
[mailto:openehr-clinical-bounces at chime.ucl.ac.uk] On Behalf Of Thomas Beale
Sent: den 6 maj 2010 12:15
To: openehr-clinical at openehr.org
Subject: Re: IHTSDO meeting - term binding presentation available
On 06/05/2010 08:48, Sebastian Garde wrote:
Hi Thomas,
do you know if there is a formal way of how RefSets (=the resulting Snomed
CT codes etc.) and the RefSet query (=the query on Snomed CT to get to the
RefSet) are expressed and shared?
the ref set results are defined by Snomed RF2 ref set specs, now in draft. I
don't know whether they are allowed to be shared outside IHTSDO, but will
find out. The query language is still an open question.
Similar to what is described here but based on RefSets:
http://www.openehr.org/wiki/display/term/Ocean+Terminology+Query+Language+%2
8TQL%29
I agree that RefSets are a good way forward, but they need to be available,
reusable and sharable, etc.
they do. The current IHTSDO thinking is that ref sets will mainly be defined
by national release centres and maintained in the national extensions, with
some major refsets being in the international release. I think this is far
too restrictive a view, and that in future they will be defined and
maintained in health care facilities, regional information centres and
anywhere else that needs them. The IHTSDO representation and extension
mechanism should be usable at all these levels. How it could be used for
openEHR I have yet to find out, but am making enquiries as a member of the
IHTSDO Technical Committee).
- thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20100506/0142d7fe/attachment.html>
