#155: Define Encounter type terms and Epic ETL
--+
Reporter: lv| Owner: huhickman
Type: design-issue | Status: assigned
Priority: major | Milestone: data-domains3
Component: data-stds |
Nice!
The norm for sharing the CSV file is via PCORNet CDT; see
#76https://informatics.gpcnetwork.org/trac/Project/ticket/76 for details.
Then re-assign #172 to Nathan or myself to update babel.
--
Dan
From: gpc-dev-boun...@listserv.kumc.edu
#178: determine whether last.visit is the last fulfilled visit or the last
scheduled visit
---+
Reporter: mish | Owner: jhe
Type: problem| Status: assigned
Priority: major | Milestone: data-quality2
Component:
The current terminology has the following for billing diagnosis modifiers:
Admit Billing Diagnosis
Principal Discharge Diagnosis
Diagnosis Present on Admission
Secondary Billing Diagnosis
Based on some emails around the time of the modifiers were added, I think the
terminology should be:
Admit
The details are (supposed to be) in
#90https://informatics.gpcnetwork.org/trac/Project/ticket/90 and
#91https://informatics.gpcnetwork.org/trac/Project/ticket/91. We approved
Jim's March 4 proposal, but what's on babel doesn't look like this at all...
PROPOSED
One questions is the source of the data
It is from the problem list or from billing data
In our research we were just going through this as we don't want a limited
number of diagnoses that get on a bill so we can understand the cluster of
problems patients have that could influence outcomes such
This looks OK to me, but I'm not really one to judge.
I'd like to get a few more opinions.
To avoid the anoybody/somebody/nobody disease, I rolled my 10 sided die and it
came up 6... MCRF.
Laurel, what do you folks think? Are you happy to deploy this at your site? If
not, what would you
#90: Diagnoses Modifiers for data attribution
--+
Reporter: campbell | Owner: lv
Type: design-issue | Status: assigned
Priority: major | Milestone: data-domains2
Component: data-stds | Resolution:
