Hi Tom,
I agree that I need a tool to create RefSets, but it is still simple tools
that are needed. I also agree that the namespaces are not for everyone, but
the Namespace Allocation Policy document is very liberal about who that
should be able to acquire a namespace. I therefore don?t think that lack of
a namespace is a practical problem for RefSet creation.
Greetings,
Mikael
From: [email protected]
[mailto:openehr-clinical-bounces at chime.ucl.ac.uk] On Behalf Of Seabury Tom
(NHS Connecting for Health)
Sent: den 6 maj 2010 18:32
To: For openEHR clinical discussions
Subject: RE: IHTSDO meeting - term binding presentation available
Hi Mikael, Thomas
There are certainly instances of sets being generated by authorities other
than national release centres, ones that conform to the SNOMED CT guidance,
which requires their identifiers include a recognised namespace.
Two aspects of this topic are 1) that you need access to tools which
allocate unique identifiers, in accord with the standard and 2) that the
allocation of namespace identifiers cannot be assumed to be a free-for-all
although at last count there were in the region of 110, some of which were
allocated to individuals. To use a Namespace you are obliged to conform to
the SNOMED CT licence conditions and similar good behaviour.
Those with an interest in this topic may wish to join, for example, the
SNOMED CT Implementation Special Interest Group via this link:-
http://www.ihtsdo.org/join-us/help-improve-snomed-ct/
To join an established Special Interest Group mail to: info(at)ihtsdo.org
stating which group you wish to join,
?Special Interest Groups (SIGs) are open and ongoing bodies that examine
issues related to specified topics that are relevant to the IHTSDO and its
members.?
Tom Seabury
IHTSDO
From: [email protected]
[mailto:openehr-clinical-bounces at chime.ucl.ac.uk] On Behalf Of Mikael
Nystr?m
Sent: 06 May 2010 16:51
To: 'For openEHR clinical discussions'
Subject: RE: IHTSDO meeting - term binding presentation available
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
****************************************************************************
****************************************
This message may contain confidential information. If you are not the
intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or
take any action in reliance on its contents:
to do so is strictly prohibited and may be unlawful.
Thank you for your co-operation.
NHSmail is the secure email and directory service available for all NHS
staff in England and Scotland
NHSmail is approved for exchanging patient data and other sensitive
information with NHSmail and GSI recipients
NHSmail provides an email address for your career in the NHS and can be
accessed anywhere
For more information and to find out how you can switch, visit
www.connectingforhealth.nhs.uk/nhsmail
****************************************************************************
****************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20100507/ce23e667/attachment.html>
