I'd like to see this "which loinc code do we use for BP?" issue escalated to 
its own ticket.

On Jul 14, 2015 1:29 PM, GPC Informatics <d...@madmode.com> wrote:
#291: Gather 2015 2nd quarterly QA results
--------------------------+--------------------------------------
 Reporter:  mish          |       Owner:  dconnolly
     Type:  problem       |      Status:  assigned
 Priority:  major         |   Milestone:  data-quality-q2
Component:  data-quality  |  Resolution:
 Keywords:                |  Blocked By:  259, 281, 285, 290, 306
 Blocking:                |
--------------------------+--------------------------------------

Comment (by lv):

 MCRF ran the scripts in < 4 hours (run incrementally, so may be less total
 time) on SQL server.

 What's the process to submit results: REDCap, Email to Tom, something
 else?

 After validating, the zero/null results seem appropriate. In some cases we
 have raw data that we might be able to use to fill calculated values.

 Example:
 \i2b2\LP29694-4\LP29696-9\LP146111-2\72165-4\72165-4: Pediatric systolic
 blood pressure percentile per age, gender and height [0 facts; 0 patients]

 *SUGGESTION:
 \i2b2\LP29694-4\LP32525-5\LP96828-6\72225-6\29545-1\8480-6\(8480-6:
 Systolic blood pressure [12308605 facts; 749329 patients])

 *COULD THE PERCENTILE BE CALCULATED OFF OF THE VALUES PROVIDED BY THIS???

 One other note: in some cases we have a term that's used in the query, but
 we're not using it in our data. Could likely swap these if 1559-6 is
 approximately the same as 1557-8?

 \i2b2\LP29693-6\LP7784-4\1557-8\1557-8: Fasting glucose [0 facts; 0
 patients]

 *SUGGESTION: \i2b2\LP29693-6\LP7784-4\1558-6\ (1558-6: Fasting glucose
 [398797 facts; 150656 patients])

--
Ticket URL: 
<http://informatics.gpcnetwork.org/trac/Project/ticket/291#comment:8>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to