Retiring an ICD10 or CCI Code: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
Because we may have old entries for | Because we may have old entries for a diagnosis or procedure code code, we can't just delete it from wiki and the [[S-tables]] when we no longer want to use it. This page describes how to retire one of these codes. | ||
== | == Tables affected == | ||
* dropdown / [[s-tables]]: [[s_ICD10 table]] / [[s_CCI_1 table]] / [[s_CCI_2 table]] / [[s_CCI_Picklist table]] | |||
* data / [[L-tables]]: [[L_ICD10 table]] / [[L_CCI_Component table]] / [[L_CCI_Picklist table]] | |||
* to some degree this applies to other dropdown tables as well, but most of the others don't have start and end dates | |||
== Consider how to handle the transition == | |||
Some records will already have the code assigned. For these, the data will stay intact, but the dx/px will look "blank". Only the code number is stored in these [[L-tables]], and the verbal Dx/Px description is shown by the field because it looks up the code in the [[s-tables]]. The data source for the dropdown filters out values with dates that puts today's date out of their valid range, so the entered value has no corresponding entry in the dropdown, which then displays it as blank. The fact that there will be blanks needs to be addressed. Options: | |||
* change it before the value is retired so there are none left; a query may need to be made available to collectors to find all instances efficiently; possibly by putting a cross-check to force the change | |||
* let it be; accept that some will be blank, expect that collectors will have entered the correct thing on the first go-around | |||
* leave the old value available until the last record with it is sent, but put code on the change event of the field that rejects entering the record going forward | |||
** depending on how that is implemented, it could also be a permanent solution to this that deals with other codes in the future, but it would add 4 more bits of code that run all the time and slow things down as the program is used | |||
== Actual steps to retire the value == | |||
=== In [[CCMDB.accdb]] === | |||
# find the code in the relevant [[s-tables|s-table]] | |||
# change the Stop_date to today's date | # change the Stop_date to today's date | ||
# [[Rolling out changes|roll out change]] as usual | # [[Rolling out changes|roll out change]] as usual | ||
Line 8: | Line 21: | ||
== On the wiki == | == On the wiki == | ||
# remove any <code><nowiki>{{CCI category| xxx}}</nowiki></code> / <code><nowiki>{{ICD10 category| xxx}}</nowiki></code> calls from the page | # remove any <code><nowiki>{{CCI category| xxx}}</nowiki></code> / <code><nowiki>{{ICD10 category| xxx}}</nowiki></code> calls from the page | ||
#* This is not necessarily the best way to do it, since it will no longer show the entry to someone wanting to review legacy data for that code; | |||
# put reason for retiring the code under <code><nowiki>== Additional Info ==</nowiki></code> | # put reason for retiring the code under <code><nowiki>== Additional Info ==</nowiki></code> | ||
# change the <nowiki><code>| StopDate =</nowiki></code> to today's date | # change the <nowiki><code>| StopDate =</nowiki></code> to today's date | ||
#* the change in date will change how the the CCI/IDC10 templates work; the following templates: | #* the change in date and removal of category will change how the the CCI/IDC10 templates work; the following templates: | ||
#** [[Template:ICD10 dx]] | #** [[Template:ICD10 dx]] | ||
#** [[Template:CCI PickList Procedure]] | #** [[Template:CCI PickList Procedure]] | ||
#** [[Template:CCI 1 Procedure component]] | #** [[Template:CCI 1 Procedure component]] | ||
#** [[Template:CCI 2 Procedure component]] | #** [[Template:CCI 2 Procedure component]] | ||
#** possibly other templates and ad-hoc queries as they get added; these will be somewhat hard to track but a [[Special:ReplaceText]] search for a query looking for the affected table will show a list with many false positives but pretty much all true positives | |||
#* will behave as follows for retired codes | #* will behave as follows for retired codes | ||
#** add them to category [[:Category:Retired Code]] | #** add them to category [[:Category:Retired Code]] | ||
Line 20: | Line 35: | ||
[[Category:Retired Code| *]] | [[Category:Retired Code| *]] | ||
[[Category:ICD10]] |
Latest revision as of 19:57, 3 July 2025
Because we may have old entries for a diagnosis or procedure code code, we can't just delete it from wiki and the S-tables when we no longer want to use it. This page describes how to retire one of these codes.
Tables affected
- dropdown / s-tables: s_ICD10 table / s_CCI_1 table / s_CCI_2 table / s_CCI_Picklist table
- data / L-tables: L_ICD10 table / L_CCI_Component table / L_CCI_Picklist table
- to some degree this applies to other dropdown tables as well, but most of the others don't have start and end dates
Consider how to handle the transition
Some records will already have the code assigned. For these, the data will stay intact, but the dx/px will look "blank". Only the code number is stored in these L-tables, and the verbal Dx/Px description is shown by the field because it looks up the code in the s-tables. The data source for the dropdown filters out values with dates that puts today's date out of their valid range, so the entered value has no corresponding entry in the dropdown, which then displays it as blank. The fact that there will be blanks needs to be addressed. Options:
- change it before the value is retired so there are none left; a query may need to be made available to collectors to find all instances efficiently; possibly by putting a cross-check to force the change
- let it be; accept that some will be blank, expect that collectors will have entered the correct thing on the first go-around
- leave the old value available until the last record with it is sent, but put code on the change event of the field that rejects entering the record going forward
- depending on how that is implemented, it could also be a permanent solution to this that deals with other codes in the future, but it would add 4 more bits of code that run all the time and slow things down as the program is used
Actual steps to retire the value
In CCMDB.accdb
- find the code in the relevant s-table
- change the Stop_date to today's date
- roll out change as usual
On the wiki
- remove any
{{CCI category| xxx}}
/{{ICD10 category| xxx}}
calls from the page- This is not necessarily the best way to do it, since it will no longer show the entry to someone wanting to review legacy data for that code;
- put reason for retiring the code under
== Additional Info ==
- change the <code>| StopDate = to today's date
- the change in date and removal of category will change how the the CCI/IDC10 templates work; the following templates:
- Template:ICD10 dx
- Template:CCI PickList Procedure
- Template:CCI 1 Procedure component
- Template:CCI 2 Procedure component
- possibly other templates and ad-hoc queries as they get added; these will be somewhat hard to track but a Special:ReplaceText search for a query looking for the affected table will show a list with many false positives but pretty much all true positives
- will behave as follows for retired codes
- add them to category Category:Retired Code
- hide the page content under the Template:LegacyContent
- the change in date and removal of category will change how the the CCI/IDC10 templates work; the following templates: