/
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
<div class="journal-details-container"> <h4> Task #976 has been updated by Kristiina Kahur. </h4> <div id="journal-5109-notes" class="note"><p><strong>Nordic Casemix Centre/Kristiina Kahur 25-08-2025</strong></p><p>Thank you for your feedback.</p><p>Most of the updates are done now in MBC/NDMS.</p><p>Remaining issues/comments concern:</p><ol><li>Following SWE ATC codes in dg and proc table had redundant space (double space) in code text (IN rows indicated with <span class="ck-font-color-5">XX</span>). The redundant spaces were removed and there were no difference between the code currently in MBC/NDMS and no changes were made. Please double-check if the text of OUT rows is correct and let us know if there is a need to change it. Redundant space may create issues while comparing different tables (SoS vs NMDS):</li></ol><figure class="table"><table><tbody> <tr> <td><strong>in/out</strong></td> <td><strong>code_nat</strong></td> <td><strong>text_nat</strong></td> </tr> <tr> <td>IN</td> <td>QI07AI07</td> <td>Hundparvovirus, levande +<span class="ck-font-color-5">XX</span>hundparainfluensavirus, levande + leptospira, inaktiverad, Veterinärläkemedel</td> </tr> <tr> <td>OUT</td> <td>QI07AI07</td> <td>Hundparvovirus, levande +<span class="ck-font-color-5">X</span>hundparainfluensavirus, levande + leptospira, inaktiverad, Veterinärläkemedel</td> </tr> <tr> <td>IN</td> <td>QI07AJ10</td> <td>Valpsjukevirus, levande<span class="ck-font-color-5">XX</span>+ hundadenovirus, levande + parainfluensavirus, levande + hundparvovirus, levande + hundcoronavirus, inaktiverat + leptospira, inaktiverad, Veterinärläkemedel</td> </tr> <tr> <td>OUT</td> <td>QI07AJ10</td> <td>Valpsjukevirus, levande<span class="ck-font-color-5">X</span>+ hundadenovirus, levande + parainfluensavirus, levande + hundparvovirus, levande + hundcoronavirus, inaktiverat + leptospira, inaktiverad, Veterinärläkemedel</td> </tr> <tr> <td>IN</td> <td>QI20CL01</td> <td>Minkenteritvirus/parvovirus<span class="ck-font-color-5">XX</span>+ inaktiverad Clostridium<span class="ck-font-color-5">XX</span>+ inaktiverad Pseudomonas, Veterinärläkemedel</td> </tr> <tr> <td>OUT</td> <td>QI20CL01</td> <td>Minkenteritvirus/parvovirus<span class="ck-font-color-5">X</span>+ inaktiverad Clostridium<span class="ck-font-color-5">X</span>+ inaktiverad Pseudomonas, Veterinärläkemedel</td> </tr> <tr> <td>IN</td> <td>QR03AK05</td> <td>Reproterol<span class="ck-font-color-5">XX</span>och natriumkromoglikat, Veterinärläkemedel</td> </tr> <tr> <td>OUT</td> <td>QR03AK05</td> <td>Reproterol<span class="ck-font-color-5">X</span>och natriumkromoglikat, Veterinärläkemedel</td> </tr> <tr> <td>IN</td> <td>R03AK05</td> <td>Reproterol<span class="ck-font-color-5">XX</span>och natriumkromoglikat</td> </tr> <tr> <td>OUT</td> <td>R03AK05</td> <td>Reproterol<span class="ck-font-color-5">X</span>och natriumkromoglikat</td> </tr> </tbody></table></figure><p>2. FYI, plus code KASE22 is not in NCPS+ at the moment and will be added while adding the new SWE code KAE22. The same applies to new plus code ZMXX09 which is not currently in NCSP+ (in your table those two plus codes are not indicated as new NCSP+ codes).</p><p>3. You suggest adding "Inactivated at 31.12.2030" text to the text of SWE codes DV148, DV149, QV011, ZV530. As you said, the codes will be inactivated 2026 and removed from def.tables starting from 2031 version. In this case we add text "Inactivated at 31.12.2025" in the beginning of SWE code text (and not “Inactivated at 31.12.2030”).</p><p>4. XU060 <i>Kroppsvisitation efter beslut enligt lag</i> and XU061 <i>Ytlig kroppsbesiktning efter beslut enligt lag</i> (both mapped to new NCSP+ code WVXX10 <i>Body search)</i> are given OR 0 value. Please let us know if this is ok as there was no information in proc_feat table concerning features of new codes XU060 and XU061.</p><p>5. SWE code DT015 will have change of text and mapping to new NCSP+ code ZXXX51 <i>Intraventricular to brain or heart</i>. Code will retain OR 0 value and PROCPR 01V04 Direct CNS medication.</p><p>6. You suggest mapping new SWE code:</p><ul> <li>AK117 <i>Transrektal ultraljudsundersökning av prostata och vesiklar </i>to KEDE1B<i> Rectal ultrasound examination of prostate</i>, and</li> <li>AK118<i> Transperineal ultraljudsundersökning av prostata och vesiklar</i> to KEDE1A <i>Percutaneous ultrasound examination of prostate</i>.</li> </ul><p>In addition, you suggest change of the text of SWE code AK046 <i>Ultraljudsundersökning, prostata och vesiklar</i> -> <i>Ultraljudsundersökning, prostata och vesiklar, suprapubiskt</i> retaining the mapping to KEDE1A Percutaneous ultrasound examination of prostate (as AK118).</p><p>This means that SWE codes AK046 and AK118 are mapped to KEDE1A and AK117 to KEDE1B.</p><p>In all versions KEDE1A has OR 0 and this is what you suggest to add to new SWE code AK118 as well (AK046 has it already).</p><p>At the same time, in all other versions KEDE1B has OR 0 similarly to KEDE1A. You suggest to add OR 2 and PROCPR 40V14 <i>Ultrasonography</i> (used only in SWE version) to new code AK117/KEDE1B. Would you like to add PROCPR 40V14 to code AK118 (and AK046) as well in SWE version? And would you consider giving OR 0 value to AK117 to keep it consistent with other national versions?</p><p>7. SWE codes SP821, SP822, SP823, SP824 are all mapped to NCSP+ code PHXX90 <i>Other catheter care </i>and will get through mapping OR 0 (as you suggested) as well as PROCPR 40V78 <i>Code not compatible with follow-</i>up. Is adding the latter to codes SP821, SP822, SP823, SP824 ok? If not, mapping needs to be revised.</p><p>8. SWE code TPJ30 <i>Perkutan punktion av lymfocel</i>e is mapped to PJXX10<i> Puncture of lymphocele</i>. Through mapping the code would get following features:</p><ul> <li>OR 0 </li> <li>PROCPR 03S99 <i>Minor procedure in ear, nose and throat diseases</i> </li> <li>PROCPR 09S08 <i>Other skin, subcutaneous tissue or breast procedure, not OR procedure</i> </li> <li>PROCPR 09V04 <i>Skin excision and biopsy</i> </li> </ul><p>You suggested adding OR 2 to code TPJ30, no PROCPRs. Please advise if we should remap TPJ30 → PJXX10 so that it has only OR 2 value. Or we keep the mapping as it is and the new code TPJ30 will get the grouping features as indicated above?</p><p> </p><p> </p></div></div> <hr/> <p>The updates for NCSP, ICD and ATC for SWE2026PR0 can be found in two TCs as indicated by respective names. </p>
