#715: NextD request on mapping payer_type variable
--------------------------+-----------------------
 Reporter:  afurmanchuck  |       Owner:  meiliu
     Type:  problem       |      Status:  assigned
 Priority:  critical      |   Milestone:  next-d
Component:  data-quality  |  Resolution:
 Keywords:                |  Blocked By:
 Blocking:                |
--------------------------+-----------------------
Changes (by dconnolly):

 * cc: gpc-dev@… (added)
 * owner:  dconnolly => meiliu
 * status:  new => assigned
 * component:  data-stds => data-quality
 * milestone:   => next-d


Comment:

 Mei, I don't see any indication that KUMC could substantially improve our
 coverage, regardless of timeline. Do you?


 By the way... if categories 9, 9999, NI, UN, and OT are acceptable, then
 KUMC is done already. None of our records have out-of-spec values for
 ENCOUNTER.PRIMARY_PAYER (ref Table IIB. Values Outside of CDM
 Specifications). The 80.4% missing in our Table IVC. Missing or Unknown
 Values are NI, UN, or OT values.

 For reference, see [https://github.com/kumc-bmi/i2p-
 transform/blob/master/curated_data/payer_map.csv payer_map.csv] and other
 details in [http://listserv.kumc.edu/pipermail/gpc-dev/2018q3/004844.html
 PCORNet CDM insurance payer mapping by KUMC for next-D].

 ----

 For reference: the 8 GPC sites participating in next-d are IOWA, UNMC,
 MCW, IU, KUMC, UMN, UTSW, MU.

 (presuming no change since Aug 2016 in ticket:398#comment:10 )

--
Ticket URL: 
<http://informatics.gpcnetwork.org/trac/Project/ticket/715#comment:1>
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