Autopsy: Difference between revisions
Jump to navigation
Jump to search
TOstryzniuk (talk | contribs) m (→Legacy Data) |
TOstryzniuk (talk | contribs) |
||
Line 4: | Line 4: | ||
==Autopsy Report follow up and Review Process== | ==Legacy Data== | ||
Dates collected | |||
Oct 16.00 STOPPED process in 2004 | |||
===Autopsy Report follow up and Review Process=== | |||
*When reviewing an autopsy report we will '''no longer''' be changing the DX admit or acquired codes. What we will do is '''add''' any '''significant''' findings in the autopsy report in an empty slot at the end of your admit or acquired codes using the subcode “50”. | *When reviewing an autopsy report we will '''no longer''' be changing the DX admit or acquired codes. What we will do is '''add''' any '''significant''' findings in the autopsy report in an empty slot at the end of your admit or acquired codes using the subcode “50”. | ||
Revision as of 14:42, 2009 April 3
Autopsy
- Autopsy field - YES or NO.
Legacy Data
Dates collected Oct 16.00 STOPPED process in 2004
Autopsy Report follow up and Review Process
- When reviewing an autopsy report we will no longer be changing the DX admit or acquired codes. What we will do is add any significant findings in the autopsy report in an empty slot at the end of your admit or acquired codes using the subcode “50”.
- autopsy report follow up and DX coding updates will longer to be done. TOstryzniuk 19:15, 9 December 2008 (CST)
Discussion
- This seems to refer to a process that is no longer used, but that itself superseded another process. I have added two headings that are empty for each of the processes. Could someone fill in a brief summary under each? Feel free to change the headings if I misunderstood and the headings I made are not applicable. Ttenbergen 13:12, 16 October 2008 (CDT)
Dec 9. 2008
●Autopsy – the plan is to stop collecting this field however I will let you know when. Will need assess the changes that need to be made to program before implemented.TOstryzniuk 18:00, 9 December 2008 (CST)