I see this as an opportunity for some joint work on specification of
terminology binding, in the intersection of interests between the openEHR
community and for one: IHTSDO.
I hope the following notes are both helpful and true, corrections are most
welcome!
[Specialists language from the SNOMED CT technical lexicon is in '' marks]
The identification of bindable 'components' from SNOMED CT is certainly via
ReferenceSet IDs (not yet part of the standard but very soon will be) via
SubsetIDs
For SubsetIDs I would expect the {URI/URN etc.} to include a 'Version'
For Concepts the 'ConceptID' should of itself be adequate
For query specifications - mentioned somewhere in this thread - the only way to
identify these will in the future be via an 'intensional' ReferenceSet
definition, but to be meaningful this may (in some cases must) be used in
conjunction with the named Edition of SNOMED CT against which this will be run.
For enumerated ReferenceSet members (not the query but a results set of a
query) then the ReferenceSetID would be needed.
In all the above cases it is necessary to consider if the named 'Edition' and
'Release' of that 'Edition' may need to be included. The proposed uses of
'Module' Identifiers is a further topic.
The 'Releases' are identified such as "UK Edition"
Releases are identified in ways that are decided by each SNOMED CT 'National
Release Center' such as the effective date, but this is not a formal convention.
[Anyone wanting the finer points of detail for IHTSDO standards and common
practice for issuance and use of : Namespaces, Editions, Release Centres,
ModuleIDs and other such metadata are invited to join, say, the Special
Interest Groups in IHTSDO.
Overall, in this intersection of interests between multiple information models
(say HL7 and UK's LRA), and multiple terminology and classification schemes
(say SNOMED CT and ICD and..) makes this topic one where working-up rather than
handing-down a solution is most likely to happen and succeed.
Tom Seabury
-----Original Message-----
From: openehr-technical-bounces at openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of
michael.law...@csiro.au
Sent: 21 February 2011 03:47
To: openehr-technical at openehr.org
Subject: Re: constraint binding error
Surely spaces should not be an issue here as these strings do not really
identify anything. Instead, one should be using SCTIDs as in:
terminology:Snomed?v=2002?s=135394005
Further issues include:
* the version should be specified using an ISO 8601 basic representation of
YYYYMMDD (or YYYYMMDDThhmmss Z for development versions),
* "Snomed" is insufficient - is this the International release, or SNOMED
CT-AU or ... My understanding of Release Format 2 (see 7.4.4.13 in the
Technical Implementation Guide) indicates that the moduleId (also an SCTID) is
the appropriate thing to use, and
* one may also (almost always) wish to use a ReferenceSet for terminology
binding. These are also designated by an SCTID (and would require a moduleId
and version as well)
This would then give us something like:
terminology:SNOMED?m=32506021000036107&v=20101130&s=135394005
On 21/02/11 12:22 PM, "Peter Gummer" <peter.gummer at oceaninformatics.com>
wrote:
Diego Bosc? wrote:
> and we have also to deal with spaces!
> <terminology:Snomed?v=2002?s=Antiallergenic drugs (product)>
Spaces are illegal in URIs. The correct form for the subset would be:
subset=Antiallergenic%20drugs%20(product)
- Peter
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
********************************************************************************************************************
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
********************************************************************************************************************
