#155: Define Encounter type terms and Epic ETL --------------------------+--------------------------------- Reporter: lv | Owner: campbell Type: design-issue | Status: reopened Priority: major | Milestone: data-stds-gov-plan Component: data-stds | Resolution: Keywords: | Blocked By: Blocking: 160 | --------------------------+--------------------------------- Changes (by dconnolly):
* status: closed => reopened * resolution: invalid => * blocking: => 160 Old description: > Create a GPC definition for "Encounter"; may be based upon input from > DSSNI or unique to the network. > > Discussed on the dev call 9/16/14. New description: Create a GPC definition for "Encounter"; may be based upon input from DSSNI or unique to the network. - SQL queries to classify Epic CLARITY encounters according to type - ''Cattails, Cerner design should follow straightforwardly'' - term hierarchy (names, paths) for - aggregated counts on babel - federated queries initially discussed on the dev call 9/16/14. -- Comment: Looks like next step could be to get details on this: Epic has provided an unfortunate excess of encounters such that administrative, billing and non-patient care events are all assigned as encounters. Segregating between ED and hospitalizations as well as ambulatory surgery is a bit convoluted but we have sorted out the Clarity data structures necessary to do so. - [http://listserv.kumc.edu/pipermail/gpc-dev/2014q3/000373.html Campbell 15 Aug] -- Ticket URL: <http://informatics.gpcnetwork.org/trac/Project/ticket/155#comment:3> 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