/
Shortcuts: "t:" searches only in tasks, "p:" searches only in projects, "u:" searches only in users. For example, "t:analysis" or "p:prototypeXYZ" All available shortcuts: t|task|tasks|i|issue|issues - search only by tasks; p|project|projects - search only by projects; u|user|users - search only by users.
Hash #: By using # with task ID, you will jump to the task directly. Without the # symbol, the result only matches the searched numbers (don't expect ID).
Operators AND OR NOT XOR: For example 'man OR (dog AND cat)'.
Operators '+' and '-': A group of terms with some marked with + and - will match items containing all of the + terms, but none of the - terms. Terms not marked with + or - contribute towards the item rankings. You can also use + and - on phrases and on bracketed expressions. For example 'one +two -three'.
Operator NEAR: 'one NEAR two NEAR three' matches items containing those words within 10 words of each other. You can set the threshold to n by using NEAR/n like so: one NEAR/6 two.
Operator ADJ: ADJ is like NEAR but only matches if the words appear in the same order as in the query. So 'one ADJ two ADJ three' matches items containing those three words in that order and within 10 words of each other. You can set the threshold to n by using ADJ/n like so: 'one ADJ/6 two'.
Phrase searches: A phrase surrounded with double quotes ("") matches items containing that exact phrase. Hyphenated words are also treated as phrases, as are cases such as filenames and email addresses (e.g. /etc/passwd or president@whitehouse.gov).
Searching for proper names: If a query term is entered with a capitalised first letter, then it will be searched for unstemmed.
Wildcards: The query parser supports using a trailing '*' wildcard, which matches any number of trailing characters, so 'wildc*'' would match wildcard, wildcarded, wildcards, wildcat, wildcats, etc.
Searching within a free-text field: You can search within specific fields. For example 'title:support content:shop' might find items with 'support' in the title and 'shop' in the content. You can also specify a prefix on a quoted phrase (e.g. title:"one two") or on a bracketed subexpression (e.g. title:(mice men)). Allowed search fields: title, content, journals, attachments.
Recently viewed
Mail subject
Reply to
Mail copy
Mail sender
Mail recipient
Task #1013 has been updated by Mats Fernström. Mats Fernström, the National Board of Health and Welfare, Sweden, 2026-05-12 (SWE ID C1078)Thank you Kristiina for raising the issue with PROCPR 99S90. I've been thinking about it for years without doing anything, mostly because 99S90 has the low impact on the grouping that you describe. It was Martti and I who many years ago invented the principle to automatically add 99S90 to certain PROCPR values and then we mostly selected the PROCPR values with the lowest numbers for all MDCs (except 18 and 23). It was somewhat of a "Quick and dirty" principle because none of us had time and energy to assess all thousands of operation codes. The principle has worked OK in Sweden, I think, however not automated in our tool, NordDRG Admin. At least there has been no complaints from our NordDRG users, which can also be explained by the fact that 99S90 is involved in very few grouping rules. However, looking at the list of procedure codes with 99S90, there are some codes where 99S90 can be questioned. The Swedish DRG team suggests the following: The principle to attach 99S90 to certain fixed PROCPR values, and just those, gives us less flexibility if we want to change the grouping logic in the future. That is the main reason why we from now on, when new procedure codes are added to NordDRG, should abandon the principle that some PROCPRs automatically render 99S90. Instead, all new codes should be assessed individually regarding 99S90 (see further down about methods). Therefore, we agree to change the text for 99S90 to just “Extensive procedure”.So far, existing codes with 99S90 may in principle keep that property since the system has worked OK, but some revision should be done: Having codes with 99S90 but without OR 1 is contradictory, existing codes with 99S90 should have OR 1. If OR 1 is not appropriate for some reason, 99S90 should be removed. This can be seen as “errors to be corrected”. Existing codes that are missing 99S90 according to the old principle based on certain PROCPR values (7 codes in SWE version) should be assessed individually regarding 99S90 (see further down about methods). Further revisions: For example, percutaneous measures (about 90 codes) should be reviewed. (We doubt that someone in the EG wants to review all the approximately 1 900 codes with 99S90). Methodological aspects when assessing whether a procedure should have 99S90 or not We must consider costs for the whole hospital stay, not only for the operation. Even a moderately large operation can sometimes entail large costs for the whole stay. And costs are more important than medical complexity in this context, because the difference between DRG Z50/468 and Z60/477 is mainly the DRG weight, which is based on costs. If the cost for hospital stay with a certain procedure is known, it can be compared with the average costs for DRG Z50/468 and Z60/477. If the cost is closer to the cost for DRG Z50/468 than the cost for DRG Z60/477, then 99S90 can be added to that procedure. If the cost for hospital stay with a new procedure is unknown, we can look for similar procedures in the system and copy the judgement concerning 99S90. If the alternative above isn’t possible, i.e. it is a completely new procedure without known or estimated costs, 99S90 cannot be added to that procedure. The decision about 99S90 must wait until we have cost data. This case concerns PROCPR 99S90 Extensive procedure - list created during the exporting process and how it is used across all national versions.Use of PROCPR 99S90 was reviewed both from a clinical perspective and from the perspective of cross‑country differences.There is no clear definition of “extensive procedure”. However, in casemix or DRG context one could define it as a procedure with high resource intensity that significantly increase expected costs, length of stay, complexity, and clinical risk. Its role is primarily grouping logic, not clinical description.In the NordDRG system, PROCPR 99S90 is used to identify extensive procedures and, on that basis, to allow grouping to DRG 468/X Rare or incorrect combination of diagnosis and extensive procedure/X. This distinction is necessary to separate cases that are not considered extensive, which are instead grouped to DRG 477/X Rare or incorrect combination of diagnosis and other procedures/X.In addition, PROCPR 99S90 is used in the rules of following DRGs: drg_comb drg_text_comb nat_ver 442X Other OR procedures for injuries, w CC est/lat/ice/fin/nor 443M Other major OR procedures after injuries, w MCC swe 443C Other major OR procedures in general anaesthesia for injuries, w CC swe 443N Other major OR procedures in general anaesthesia for injuries, w/o CC swe 443X Other OR procedures for injuries, w/o CC est/lat/ice/fin/nor PROCPR 99S90 with minus (-) sing is not used in any DRG rules (minus sign is used in case to avoid grouping of case with a procedure code having PROCPR 99S90). After having a look at the used on PROCPR 99S90, here are some observations:There are procedure codes which are having OR value 0 or 2, yet having PROCPR 99S90. The codes are as follows: code_plus text_plus or_val nat_ver* JCSE35 Laprascopic operation on oesophageal atresia or congenital tracheo-oesophageal fistula 0 nor NHSQ60 Revision of ampution or exarticulation of ankle or foot 0 ice/fin FKSC61 Repair of mitral valve insufficiency by a transluminally inserted clip 2 fin/est NAO10D Termokoagulasjon i kolumna, CT-veiledet 2 nor NAXA00 Heat coagulation of vertebral lesion 2 ice/fin/nor NAXT60 Manipulation of the spine 2 ice/fin *As Norwegian version is primarily maintained by Helsedirektoratet, there can be differences between the tables maintained in NDMS and HS.2. There are cross-country differences among some codes: code_plus text_plus or_val nat_ver Comment LESF03 Posterior colporrhaphy 1 est/lat/ice/fin/nor Not used in SWE version LESF10 Colpoperineoplasty 1 est/lat/ice/fin/nor Not used in SWE version FZSA00 Total cardiopulmonary bypass in normothermia or moderate hypothermia at concurrent surgical procedure 1 swe Used only in SWE version KKSB11 Percutaneous endoscopic excision of retroperitoneal tumour 1 swe Used only in SWE version LESF40 Vaginal repair of enterocele 1 swe Used only in SWE version LESF41 Laparoscopic repair of enterocele 1 swe Used only in SWE version ZTXA40 Graft of synthetic skin substitute 1 swe Used only in SWE version Things to consider: remove PROCPR 99S90 from procedure codes with OR 0 or 2, or change the OR value of procedure codes. harmonise the use of PROCPR 99S90 across countries, based on the principle that identical procedure codes are interpreted consistently regardless of country, whether as “extensive” or “non‑extensive". Revise all procedure codes from PROCPR 99S90 perspective (see attached a table of procedure plus codes with PROCPR 99S90 in 2027PL0 version). Given that PROCPR text Extensive procedure - list created during the exporting process was used during the transition of definition tables from FoxPro to NDMS in 2018, I suggest to change the text: Extensive procedure - list created during the exporting process -> Extensive procedure. This case is meant to be discussed in next EG Spring meeting. Any comments or views on this issue are welcome any time.
Mats Fernström, the National Board of Health and Welfare, Sweden, 2026-05-12 (SWE ID C1078)
Thank you Kristiina for raising the issue with PROCPR 99S90. I've been thinking about it for years without doing anything, mostly because 99S90 has the low impact on the grouping that you describe.
It was Martti and I who many years ago invented the principle to automatically add 99S90 to certain PROCPR values and then we mostly selected the PROCPR values with the lowest numbers for all MDCs (except 18 and 23). It was somewhat of a "Quick and dirty" principle because none of us had time and energy to assess all thousands of operation codes.
The principle has worked OK in Sweden, I think, however not automated in our tool, NordDRG Admin. At least there has been no complaints from our NordDRG users, which can also be explained by the fact that 99S90 is involved in very few grouping rules. However, looking at the list of procedure codes with 99S90, there are some codes where 99S90 can be questioned.
The Swedish DRG team suggests the following:
The principle to attach 99S90 to certain fixed PROCPR values, and just those, gives us less flexibility if we want to change the grouping logic in the future. That is the main reason why we from now on, when new procedure codes are added to NordDRG, should abandon the principle that some PROCPRs automatically render 99S90. Instead, all new codes should be assessed individually regarding 99S90 (see further down about methods). Therefore, we agree to change the text for 99S90 to just “Extensive procedure”.
So far, existing codes with 99S90 may in principle keep that property since the system has worked OK, but some revision should be done:
Methodological aspects when assessing whether a procedure should have 99S90 or not
This case concerns PROCPR 99S90 Extensive procedure - list created during the exporting process and how it is used across all national versions.
Use of PROCPR 99S90 was reviewed both from a clinical perspective and from the perspective of cross‑country differences.
There is no clear definition of “extensive procedure”. However, in casemix or DRG context one could define it as a procedure with high resource intensity that significantly increase expected costs, length of stay, complexity, and clinical risk. Its role is primarily grouping logic, not clinical description.
In the NordDRG system, PROCPR 99S90 is used to identify extensive procedures and, on that basis, to allow grouping to DRG 468/X Rare or incorrect combination of diagnosis and extensive procedure/X. This distinction is necessary to separate cases that are not considered extensive, which are instead grouped to DRG 477/X Rare or incorrect combination of diagnosis and other procedures/X.
In addition, PROCPR 99S90 is used in the rules of following DRGs:
PROCPR 99S90 with minus (-) sing is not used in any DRG rules (minus sign is used in case to avoid grouping of case with a procedure code having PROCPR 99S90).
After having a look at the used on PROCPR 99S90, here are some observations:
*As Norwegian version is primarily maintained by Helsedirektoratet, there can be differences between the tables maintained in NDMS and HS.
2. There are cross-country differences among some codes:
Things to consider:
This case is meant to be discussed in next EG Spring meeting. Any comments or views on this issue are welcome any time.