#715: NextD request on mapping payer_type variable
--------------------------+-----------------------
Reporter: afurmanchuck | Owner: nsmith
Type: problem | Status: assigned
Priority: critical | Milestone:
Component: data-stds | Resolution:
Keywords: | Blocked By:
Blocking: |
--------------------------+-----------------------
Comment (by lv):
Replying to [comment:11 afurmanchuck]:
> NU understood hardship of linking of some encounters to proper
insurance. We ask each Next-D site to address following questions:
>
> 1. Does your site capture current insurance status of the patient in the
source system?
> 2. If yes, would it be possible to get longitudinal records on such
status for each patient? An example, NU has table that contains list of
insurances for each patient with start and end date on each.
>
> '''Please, provide response by 4pm on 2018-10-02.'''
When a tight deadline is expected, it is important to have representation
on the gpc-dev call to address questions.
Based on the call earlier today, there is a request that Northwestern
clarify and issue clear guidelines on what data they want: encounter-based
financial class or coverage history from accounts?
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/715#comment:15>
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
