#715: NextD request on mapping payer_type variable
--------------------------+-----------------------
Reporter: afurmanchuck | Owner: nsmith
Type: problem | Status: assigned
Priority: critical | Milestone: next-d
Component: data-stds | Resolution:
Keywords: | Blocked By:
Blocking: 713 |
--------------------------+-----------------------
Comment (by xsong):
`when PAYER_TYPE_PRIMARY in (NULL, 'OT','NI')` doesn't work, the predicate
should be `case when PAYER_TYPE_PRIMARY in ('OT','NI') or
PAYER_TYPE_PRIMARY is null then 0 else 1 end`.
Replying to [comment:22 xsong]:
> No, if "NI" and "OT" are imputed automatically for all non-mapped
encounters. But if that's the case, should we always have 100% mapping for
primary payer (when NULL is assigned with an "NI" or "OT")?
>
> But I think it does make more sense to collect summaries just for
meaningful payer info. I will update the summary codes by using `when
PAYER_TYPE_PRIMARY in (NULL, 'OT','NI')` instead.
> Replying to [comment:21 dconnolly]:
> > Song, I see `when PAYER_TYPE_PRIMARY is not null`... that succeed for
`NI` and `OT`. Is that on purpose? That is: do you want to count "no
information" and "other" as successfully mapped payer types?
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/715#comment:23>
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
