#158: usable view of LOINC lab terms
-------------------------+----------------------------
Reporter: rwaitman | Owner: bos
Type: enhancement | Status: assigned
Priority: major | Milestone: data-domains3
Component: data-stds | Resolution:
Keywords: | Blocked By:
Blocking: 241, 285 |
-------------------------+----------------------------
Changes (by dconnolly):
* owner: Aaron.Meyer => bos
Comment:
Thanks for the updated flat file and code, Nate.
Meanwhile, the technique of going straight from UMLS tables is more in
line with other HERON code, so I worked with Angela a bit on that (#286).
Unfortunately, the code at KUMC and San Antonio has diverged so much that
reconciling them is quite a pain.
Also, the UMLS approach currently ends up with those AUI-based paths with
loinc codes only at the end. We talked about what it would take to
reproduce paths such as
`\i2b2\LOINC\LP31755-9\LP14559-6\LP98185-9\LP14082-9\LP52260-4\`; at the
time, I wasn't inclined to bother, but I think I have changed my mind:
AUI-based paths introduce an artificial dependency on UMLS mechanisms;
there's no reason to rule out the approach that depends only on the flat
file from the LOINC site.
Angela, here's hoping you get around to adapting the UTHSCSA_umls branch
to build this sort of code before I do.
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/158#comment:43>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
