================================================================ Section 0. Contact and confidentiality ================================================================ Contact e-mail:
Emanuele Della Valle <emanuele DOT dellavalle AT cefriel DOT it> (main contact)
Irene Celino <irene DOT celino AT cefriel DOT it>
Dario Cerizza <dario DOT cerrizza AT cefriel DOT it>
Davide Sommacampagna <somma_d AT hotmail DOT it> (student)
Anna Veronesi <valery81 AT libero DOT it> (student)
Do you mind your use case being made public on the working group website and documents :
We'd be very glad if you'll publish our use case.
================================================================ Section 2. Vocabulary(ies) ================================================================ In this section we ask you to provide some information about the vocabulary or vocabularies you would like to be able to represent using SKOS. Please note: -- If you have multiple vocabularies to describe, you may repeat this section for each one individually or you may provide a single description that encompasses all of your vocabularies. -- If your use case describes a generic application of one or more vocabularies and/or vocabulary mappings, you may skip this section. -- If your vocabulary case contains cross-vocabulary links (between the vocabularies you presented or to external vocabularies), please fill in section 3! 2.1. What is the title of the vocabulary? If you're describing multiple vocabularies, please provide as many titles as you can.
SKOS representation of LOINC
2.2. Briefly describe the general characteristics of the vocabulary, e.g. scope, size...
LOINC, a Universal Standard for Identifying Laboratory Observations. Please refer to http://www.nlm.nih.gov/research/umls/loinc_main.html for further information.
2.3. In which language(s) is the vocabulary provided?
The vocabulary is provided as a database see http://www.regenstrief.org/medinformatics/loinc/downloads.
In the case of partial translations, how complete are these?
We provide an almost complete translation. We excluded from the translation only the semi-structured part.
*2.4. Please provide below some extracts from the vocabulary. Use the layout or presentation format that you would normally provide for the users of the vocabulary. Please ensure that the extracts you provide illustrate all of the features of the vocabulary.
Loinc:code - the compact version of the concept for external reference
Loinc:axis - the different dimension of the Laboratory observation:
- timing, scale, property measured, method used, system and component.
Loinc:formalName - the formal name of the concept with the references to the value of the axis
Loinc:shortName - the informal name of the concept es. HEMOGLOBIN = A3/HEMOGLOBIN.TOTAL
2.5. Describe the structure of the vocabulary. What are the main building blocks? What types of relationship are used? If you can, provide examples by referring to the extracts given in paragraph 2.4.
2.6. Is a machine-readable representation of the vocabulary already available (e.g. as an XML document)? If so, we would be grateful if you could provide some example data or point us to a hyperlink.
2.7. Are any software applications used to create and/or maintain the vocabulary? Are there any features which these software applications currently lack which are required by your use case?
No, the vocabulary maintenance is performed through an RDF/SKOS/OWL editor.
2.8. If a database application is used to store and/or manage the vocabulary, how is the database structured? Illustration by means of some table sample is welcome.
Standard RDF databases can be used
2.9. Were any published standards, textbooks or written guidelines followed during the design and construction of the vocabulary? Did you decide to diverge from their recommendations in any way, and if so, how and why?
2.10. How are changes to the vocabulary managed?
The vocabulary maintenance is performed manually.
2.11. Any additional information, references and/or hyperlinks.