DX Delete Bug

From CCMDB Wiki
Jump to navigation Jump to search
This was fixed via Eliminating a diagnosis from collection.

Deleting a line from s_alldiagnoses will leave blank lines in the dx form, and I am not sure how it copes with this when sending. This problem was discovered when I tried to delete the dx Panelling or Discharge Planning.

Need to ensure that

  • deleted codes can still be edited
  • deleted codes can not be sent
  • any checks related to deleted codes work or fail gracefully
  • if the dx that was deleted was the only dx listed for a patient, something predictable needs to happen

Possible approaches:

  • logical deletes (i.e. keep in S_alldiagnoses but add "deleted" column and modify all places that use this to work accordingly.
  • change forms and checks to be able to deal with deleted entries

Trish said: 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?

  • that is a good point. Collectors would have to add a different diagnosis to be able to send. I can make sure that they can't send without adding that additional dx. However, they would need to be able to determine one. Should there be cases where they can't? I would be whatever it was that made a person incapably of doing things; are there cases where this is not codable? We should likely not be deleting codes where we don't have an alternative for collectors on how to code something. Thoughts? Ttenbergen 12:28, 2012 November 1 (EDT)