#90: Diagnoses Modifiers for data attribution
--------------------------+----------------------------
Reporter: campbell | Owner: dconnolly
Type: design-issue | Status: accepted
Priority: major | Milestone: data-domains2
Component: data-stds | Resolution:
Keywords: | Blocked By:
Blocking: 70, 91, 120 |
--------------------------+----------------------------
Changes (by dconnolly):
* owner: lv => dconnolly
Comment:
Replying to [comment:10 lv]:
> Are there are requests from researchers at other sites to use these
alternative types of diagnoses? MCRF use our main Diagnosis Table for the
majority of our research. Only in a rare case would we go after anything
else.
>
> Notes:
> 1. Primary vs. Principle: after a quick, non-comprehensive check,
Cattails uses Primary.
>
> 2. Primary, Secondary: Currently we pull all diagnoses, without regard
for position. To fill Primary and Secondary, we'd need to adjust our ETL.
How would other diagnoses be handled? Are only two being loaded per
encounter for other sites?
I think "Secondary" is a bit of a misnomer; I think it just means "not
primary", and there can be may of them. The database column is just a Y/N
for primary.
> It would take significant effort for MCRF to accurately implement this
series of modifiers. I'd like to hear feedback that the additional
elements add value for researchers, as we do not have a local use case.
It seems reasonable to me that if your system doesn't distinguish primary
from secondary, you should just report the more general term, e.g.
"Billing Diagnosis". Or if you don't even know that much, just don't add a
modifier at all. For studies that require the distinction, MCRF would have
to evaluate the benefit of participating against the cost of adjusting
your ETL.
But I think I should escalate this issue, as it bears on
DataRepositoryManagement, which is included in the GPC data sharing
agreement by reference.
p.s. Thanks for the thorough review. Clearly my 10 sided die knew what it
was doing when it picked you!
more on other issues separately...
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/90#comment:12>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
