mlhim-owners team mailing list archive

[Luciana Tricai Cavalini <lutricav@xxxxxxxxx>]

Hello MLHIMers,

Tim: I'm working on translating the Apgar archetype into CCD, so I'll
start over again with the new CDD version to see if it is better.

BTW, something else raised from the discussion with my students. It is
related to the "terminology" subject. The extremes are easy to define:
what is an "internal terminology" (such as any element whose data type
is ordinal, or with a small list of nominal terms) and what is a "real
terminology" (SNOMED-CT, ICPC, IDC-10 etc).
But there's something in the middle: we know that, at the local level,
healthcare systems develop a lot of "local terminologies" that are, in
fact, tables (especially for procedures and medications).

If we want MLHIM to be widely adopted, we need to figure out a way to
include those "local terminologies" or "tables" without being stuck in
the "terminology server" talk.

UMLS is super-powerful (LexGrid/BIG too), and of course it is the
solution for the "real terminologies", but it will take a long time
until the ideal MLHIM-based application developer (small open source
entrepeneur, close to the point of care, in a developing country) will
be able to map the "local terminologies" or "tables" into the UMLS.

On the other hand, it is absurd to ask anybody to retype their entire
"local terminologies" or "tables" as an Ontology Entry into the Ontology
sheet of the CDD.

I think I understood that XML schemas accept file attachments. So, my
suggestion for the MLHIM specifications, regarding "local terminologies"
or "tables", is to allow the attachment of the "local terminology" or
"table" file, whatever its file format is (*.csv, *.txt, *.ods, *.odb,
*.xls, *.xlsx, *.mdb, *.RData, you name it). That should be allowed in
the Ontology sheet of the CDD. So, the content attribute of that
specific Ontology Entry would be the file containing the "local
terminology" or "table".

My suggestion is for us to define this way:

If your terminology is compliant to the ISO 17117 standard (please talk
to me about it off-list ;-) ), it is a "real terminology" and then
UMLS/LexGrid/BIG should be adopted to manage it.
If not, you have 2 options:
For "internal terminologies" (let's say, an element whose cathegories
were not organized on any type of file, as a list or a table, because
they have few cathegories and no coding system*): type the cathegories
directly on the correspondent Ontology Entry.
*Example: the "Body Exposure" element of the "Body Temperature" archetype
For "local terminologies" or "tables": attach the "local terminology" or
"table" file, whatever file format, to the correspondent Ontology Entry.

As we say in my University meetings (in bad translation), "the ones who
agree with that proposal stay as you are. The others, please manifest
themselves". ;-)

Cheers, Luciana.


Em 10/02/2011 18:35, Tim Cook escreveu:
> Blueprint changed by Tim Cook:
> 
> Whiteboard changed:
>   Discussed with Luciana, her experience and the results of teaching
>   medical students to use the template to create a CCD.  I will be
>   splitting up the Datatypes page into a more manageable two pages.
> + 
> + ------------------------------------------------------
> + 
> + Need feedback now to see if this solves the issues.
> 

-- 
Esta mensagem foi verificada pelo sistema de antivírus e
 acredita-se estar livre de perigo.