#158: usable view of LOINC lab terms
-------------------------+----------------------------
Reporter: rwaitman | Owner: nateapathy
Type: enhancement | Status: assigned
Priority: major | Milestone: data-domains3
Component: data-stds | Resolution:
Keywords: | Blocked By:
Blocking: 68 |
-------------------------+----------------------------
Comment (by campbell):
Nate
I think that Russ' comments are understandable for this metadata view but
are not achievable with good clinical acceptance using existing UMLS
publications. The LOINC views for Lab and Clinical that Nathan Wilson
prepared are the best that can be done right now with the LOINC Parts
hierarchy built by regenstrief and it is unmanageable in the i2b2 query
tool due to its 'flatness'.
The good news is that deploying the NW LOINC metadata with LOINC codes
deployed in C_DIMCODE as Nathan has built allows for local pragmatic
clinical views that can mirror the clinical system (EHR) browsing tool.
From our Epic results review we have extracted the browsing hierarchy
mapped to LOINC and are building the metadata from that with C_METADATAXML
populated so that numeric and code set lab results are appropriately
viewable in the i2b2 query tool.
I may or may not have that ready for Thursday but that is the approach
that UNMC is taking and I suspect that you can probably extract a CERNER
results review hierarchy of similar utility, can you not?
I think that such metadata will achieve the greatest clinical/research
acceptance across our sites since the current LOINC publication does not
have sufficiently robust ontologic organization to support the browsing
and decision support use cases that our clinical researchers expect.
Jim
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/158#comment:18>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
