Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PDX = P for EI encounters? #19

Closed
dckc opened this issue Apr 14, 2017 · 1 comment
Closed

PDX = P for EI encounters? #19

dckc opened this issue Apr 14, 2017 · 1 comment

Comments

@dckc
Copy link
Contributor

dckc commented Apr 14, 2017

Documentation for the PDX field of DIAGNOSIS says:

Principal discharge diagnosis flag. Relevant only on IP and IS encounters.

but then Table IVE. Principal Diagnoses for Institutional Encounters in the EDC report has a row for EI.

Is PDX actually relevant to EI as well as IP and IS?
@smerek smerek self-assigned this Apr 14, 2017
dckc added a commit to dckc/i2p-transform that referenced this issue Apr 14, 2017
@dckc
don't exclude EI, UHC when looking for PDX=P
9092891 
Though the CDM spec says "Relevant only on IP and IS encounters," table
Table IVE. Principal Diagnoses for Institutional Encounters of the EDC
report includes a row for EI as well.

We raised CDMFORUM/CDM-ERRATA#19 about this.

Meanwhile, we have been counting only Epic billing diagnoses as
discharge diagnoses when looking for PDX. The
`\Diagnosis\Billing\Primary\` modifier used in UHC should be counted as
well. This modifier is also used in IDX, which will raise our count of
"For ED, AV, and OA encounter types, mark as X=Unable to Classify." but
that seems worthwhile.
@dckc dckc mentioned this issue Apr 14, 2017
Merged
@smerek
Copy link

smerek commented Apr 14, 2017

Hi Dan.
Good catch! Yes, PDX should be included for EI encounters too. We revised the implementation guidance for this when we created the spec for CDM v3.1.

Implementation guidance is on iMeet here: https://pcornet.imeetcentral.com/p/aQAAAAAC4Zr4

@smerek smerek closed this as completed Apr 14, 2017
@smerek smerek removed their assignment Apr 14, 2017
@dckc dckc mentioned this issue Apr 19, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dckc @smerek