Bj?rn,
the main question is whether these terms exist in a terminology outside
the archetype. Then a binding is appropriate, as Ian shows below.
However, I don't think the following would parse. It should be :
term_bindings = <
["AccidentSiteTerms"] = <
items = <
["at0073"]= <[AccidentSiteTerms::V]>
["at0074"] = <[AccidentSiteTerms::T]>
>
>
>
In a better version of the parser, it would allow:
term_bindings = <
["AccidentSiteTerms"] = <
items = <
["at0073"]= <[AccidentSiteTerms::V|V - Vei, gate, fortau, gang- ,
sykkelvei|]>
["at0074"] = <[AccidentSiteTerms::T|T - Other transport area|]>
>
>
>
i.e. using the standard IHTSDO string form of a coded term, which looks like
code|natural language term|
Normally this should be accepted in any location where just the 'code'
is accepted.
- thomas
On 15/05/2013 01:11, Ian McNicoll wrote:
> Hi Bjorn,
>
> 2 options
>
> 1. Just parse the term, since you know that you are using a controlled
> terminology, the first letter will always be the key.
>
> 2. Alternatively, create a term binding, since each valueset is
> essentially a mini-terminology with a keyed 'code' i.e 'V', 'T' etc,
> or do these come from a formal terminology, such as ICD-X?
>
> e.g.
> term_bindings = <
> ["AccidentSiteTerms"] = <
> items = <
> ["at0073"]= <[AccidentSiteTerms::V::V - Vei, gate, fortau, gang- ,
> sykkelvei]>
> ["at0074"] = <[AccidentSiteTerms::T::T - Other transport area**]>
>
> >
> >
> >
>
> Ian
>
--
Ocean Informatics <http://www.oceaninformatics.com/> *Thomas Beale
Chief Technology Officer*
+44 7792 403 613 Specification Program, /open/EHR
<http://www.openehr.org/>
Honorary Research Fellow, UCL <http://www.chime.ucl.ac.uk/>
Chartered IT Professional Fellow, BCS <http://www.bcs.org.uk/>
Health IT blog <http://wolandscat.net/category/health-informatics/>
View Thomas Beale's profile on LinkedIn
<http://uk.linkedin.com/in/thomasbeale>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130515/13ea3bf7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ocean_full_small.jpg
Type: image/jpeg
Size: 4085 bytes
Desc: not available
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130515/13ea3bf7/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: btn_liprofile_blue_80x15.png
Type: image/png
Size: 511 bytes
Desc: not available
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130515/13ea3bf7/attachment.png>
