DX Delete Bug

From CCMDB Wiki
Revision as of 11:17, 2012 November 1 by Ttenbergen (talk | contribs) (Created page with " ensure that deleting a DX from allDiagnoses will not break anything. Either make deletes logical, or else allow code to cope with discrepancy. Caused problems when we tried t...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

ensure that deleting a DX from allDiagnoses will not break anything. Either make deletes logical, or else allow code to cope with discrepancy. Caused problems when we tried to delete 906 panelling and discharge planning, make sure it doesn't happen again. Ttenbergen 11:46, 2012 November 1 (EDT)


No dx codes are inherently prioritized, so I am not sure what you mean by the first part.

When you send, the program takes all DXs it finds, and sorts them by the priority. This means it should never send blanks. It’s one of the things I will need to confirm, and this applies to us ever deleting _any_ diagnoses.

Example: Admit 1 is 906 No other admit codes. (this happens when pt goes from a teaching to a non teaching). How will you handle. Admit 1 will just be blank? • Good point, I will need to address what happens if there is only one DX.

From: Trish Ostryzniuk Sent: Thursday, November 01, 2012 11:03 To: Tina Tenbergen Subject: RE: Panelling and Discharge Planning

DX code if as follows Admit 1 is 906 priority 1 Admit 2 is 907 priority 2

How will you handle. When sent will admit 1 be blank and admit 2 only be include in DX 2 slot.

Example: Admit 1 is 906 No other admit codes. (this happens when pt goes from a teaching to a non teaching). How will you handle. Admit 1 will just be blank?

I just want to be clear on who is analyzing this allied health consult data. Julie get upset if she is not “in the loop” from the start if she is to be involved in any analysis.