Nordic DRG Grouper changes (made on 15th, 25th and 29th June, 2020)
|Priority:||Error correction||Due date:|
|Initiator:||Owner / responsible:||Nordic Casemix Centre|
The changes made in Nordic DRG Grouper on 25th and 29th of June, 2020 were as follows:
29.6.2020 - replaced standalone packaging scripts with executable publishing scripts.
25.6.2020 - procedure Property grouping rule with secpro '-' value can only pass for cases with OR value 1 (reverted change from 17.4.2020).
#1 Updated by Kristiina Kahur over 1 year ago
- Subject changed from Nordic DRG Grouper changes (made on 25th and 29th June, 2020) to Nordic DRG Grouper changes (made on 15th, 25th and 29th June, 2020)
The changes made in Nordic DRG Grouper on 15th of June, 2020 were as follows:
-when inactivating a case's compl, its middle character is always converted to 'C' for matching to complication exclusion (previously only 'G' was converted)
-inactive compl is activated only if it wasn't inactivated based on compl.ex matching
-removed complication property type J from definitions and case features
-updated .NET from version 2.1 to version 3.1
-updated standalone packaging scripts to support releasing the grouper with dependencies preinstalled
#2 Updated by Mats Fernström about 1 year ago
Mats Fernström, the National Board of Health and Welfare, Sweden 2020-08-12
Your descriptions are short and sometimes hard to understand. Now I wonder what “procedure Property grouping rule with secpro '-' value can only pass for cases with OR value 1” means. I have two questions.
1. Long time ago I learned from Martti that a minus sign alone (without any specified procpro) in the field “secpro” means that any secondary procedure code with OR = 1 is not permitted. Is it still so?
2. Quite a lot of rules have a minus sign and a specified procpro in the field “secpro”. In the rule with ID 401D012005 for example there is “-01S29” in the field “secpro”. Does that mean that a secondary procedure code with procpro 01S29 and OR = 1 is not permitted or are all secondary procedure codes with procpro 01S29, irrespective of the OR value, not permitted?
Then a matter of principles. We in the Swedish DRG team think that changes in the Nordic master grouper must be discussed and decided by the Nordic expert network (like changes in the grouping logic) unless it's just about error corrections, as it seems to be in this case.
#3 Updated by Kristiina Kahur about 1 year ago
Nordic Casemix Centre/Kristiina Kahur 12-8-2020
Sorry for being unclear.
The answers to your questions (double-checked with Martti):
1) '-' sign alone means that secondary procedure(s) cannot have OR=1 value (as you described) unless it is the procedure code having the same procpro and OR value as indicated in 'procpro' field. So yes, it is still so and there has been no changes how the grouper works.
2) the rules using secpro with '-' sign means that any secondary procedure code having respective procedure property (with '-' sign) is not permitted regardless of OR value. Using your example it means that no secondary procedure code with procpro 01S29, regardless of OR, value is permitted.
As for making the changes in Nordic DRG Grouper, we very much agree with you (and others) that all changes in the grouper must be discussed in the Expert Group. So far the changes have concerned the error corrections and therefore have not been discussed in the Expert Group.