#229: Enrollment terms based on Catchment Area, encounters, etc.
--------------------------+----------------------------
Reporter: dconnolly | Owner: huhickman
Type: design-issue | Status: closed
Priority: major | Milestone: data-domains2
Component: data-stds | Resolution: fixed
Keywords: | Blocked By:
Blocking: 67 |
--------------------------+----------------------------
Comment (by dconnolly):
I suppose catchment area and within-50-miles should map to Geographic and
the others are algorithmic.
The mapping in our CDM ETL (#145) should answer this... but currently, the
code seems to always set ENR_BASIS to 'A'.
Ah... this is a known issue: [https://bitbucket.org/gpcnetwork/gpc-
pcornet-cdm/issue/2/enrollment-mappings-missing gpc-pcornet-cdm/issue/2
/enrollment-mappings-missing]. Nathan and I go back and forth about which
issues to track where. My sense is that the bitbucket issues might be
finer granularity than tickets here, but each major bitbucket issue should
be represented by some open ticket here. So I guess I better make one
up...
ref [https://bitbucket.org/gpcnetwork/gpc-pcornet-
cdm/src/2b34bc7b71b13382b2cb697a10688fbc37f06c0d/CDM_transform_enrollment.sql?at=default#cl-20
CDM_transform_enrollment.sql line 20]
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/229#comment:10>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
