It may save you trouble if I just give you a dataset of 2 columns: Patient num, 
corrected NA-3000 value.

-----Original Message-----
From: GPC Informatics [mailto:d...@madmode.com]
Sent: Tuesday, February 23, 2016 4:01 PM
To: McDowell, Bradley D; Nadkarni, Prakash; dconno...@kumc.edu
Cc: m...@pmean.com
Subject: Re: [gpc-informatics] #475: Invalid UIOWA value for NAACCR Item 3000

#475: Invalid UIOWA value for NAACCR Item 3000
---------------------------+--------------------------------
 Reporter:  brad_mcdowell  |       Owner:  prakashnadkarni
     Type:  problem        |      Status:  reopened
 Priority:  major          |   Milestone:  cohort-char-bc-db
Component:  data-stds      |  Resolution:
 Keywords:                 |  Blocked By:
 Blocking:                 |
---------------------------+--------------------------------

Comment (by brad_mcdowell):

 Prakash, can you let me know how the original variables from the tumor  
registry  mapped onto the '5' values in the datamart? Were they all the  same 
value? I need to know this so I can get a tentative corrected  frequency 
distribution for this variable. It would also be helpful to have  the original 
code that was involved.

--
Ticket URL: 
<http://informatics.gpcnetwork.org/trac/Project/ticket/475#comment:8>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics


________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________
_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to