#90: Diagnoses Modifiers for data attribution
--------------------------+----------------------------
 Reporter:  campbell      |       Owner:  campbell
     Type:  design-issue  |      Status:  assigned
 Priority:  major         |   Milestone:  data-domains2
Component:  data-stds     |  Resolution:
 Keywords:                |  Blocked By:
 Blocking:  70, 91, 120   |
--------------------------+----------------------------

Comment (by westr006):

 Instead of surveying users, we connected with the Director for our
 Informatics Consulting Service (ICS).  The ICS takes requests from
 researchers for data from our CDR and then translates it for the IT staff
 for data delivery.  Below are her comments after processing hundreds of
 requests for data.

 "When it comes to data requests, the only distinction that has been of
 interest is admit vs discharge diagnosis; some users are interested in the
 discharge diagnoses in particular.
 Almost none of our users distinguish between where a diagnosis comes from
 - whether it is admit vs discharge vs professional;  primary vs non-
 primary; billing vs. clinical/EMR.

 Our current implementation of i2b2 has a primary vs. secondary modifier
 but I think that just about nobody uses it (one problem with our
 interface, I think, is that you have to choose the primary modifier on
 each diagnosis, as opposed to being able to apply it en bloc to a group of
 diagnoses)."

 On the other hand, as a researcher who does data mining, I need to
 understand all diagnoses on the problem list at the time of an encounter,
 the admitting diagnosis, and the discharge diagnosis.  For discharge, we
 do rely on the billing diagnosis (primary and secondary).  We have not
 investigated the difference between provider vs billing discharge
 diagnosis.

 After review v1 vs v2 – I would recommend v1

--
Ticket URL: 
<http://informatics.gpcnetwork.org/trac/Project/ticket/90#comment:23>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to