/
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-5083-notes" class="note"><p><strong>Nordic Casemix Centre/Kristiina Kahur 12-08-2025</strong></p><p>Before making the changes in MBC/NDMS, we would like to clarify and get your feedback to following issues:</p><ol><li>Would you like to remove or inactivate the following codes:</li></ol><p>DV148 <i>Byte av perifer venkateter</i><br>DV149 <i>Avlägsnande av perifer venkateter</i><br>QV011 <i>Träningsprogram (i)</i><br>ZV530<i> Nationell högspecialiserad vård (i)</i></p><p>These codes do not appear in the proc_feat table therefore the assumption is that the codes will be inactivated and remain in the def.tabels (incl proc_feat table) another five years. Please confirm.</p><ol> <li>We suggest creating one new NCSP+ code WVXX10 <i>Body search or examination</i> for SWE codes XU060 <i>Kroppsvisitation efter beslut enligt lag</i> and XU061 <i>Ytlig kroppsbesiktning efter beslut enligt lag</i> and mapping both SWE codes to one code instead of creating two separate codes. Is this ok?</li> <li>Are the new SWE codes starting with ZM (e.g. ZMC02 <i>Kejsarsnitt utfört i latensfas</i>) meant to be coded as additional codes to the main procedure code and they cannot coded alone? If so, we suggest to create new NCSP+ codes with ‘<strong>X</strong>’ in the middle instead of ‘<strong>S</strong>’ for codes starting with ZM<ol><li>E.g. ZMC02 <i>Kejsarsnitt utfört i latensfas</i> -> ZM<strong>X</strong>C02 <i>Caesarean section performed in latent phase</i> </li></ol> </li> <li> <p>You suggest adding a new code AK018 <i>Transperineal ultraljudsundersökning av prostata och vesiklar</i>. However, in SWE version code AK018 is currently used with text “<i>Pyelografi, antegrad, med punktion</i>” and it is mapped to NCSP+ code KADB3E <i>Antegrade pyelography</i>. </p> <p>Please advise how to proceed – whether we change the text of current code AK018 and re-map it to KXDE1X<i> Other ultrasound examination of retroperitoneal space and genito-urinary tract</i> as you suggested, or there is a typo in new code which needs to be corrected or something else.</p> </li> <li>For your information, code DD009 had been in use and was inactivated in 2009. Then the text of the code was P<i>erkutan trakeotomi</i> and it was mapped to GBSA00 <i>Tracheotomy</i>. Given that code DD009 is not in active use anymore it will be added to 2026 SWE version as a new code with text <i>Undersökning och behandling i rotationsstol</i>, mapped to NCSP+ code DFXX00 <i>Postition maniputlation for vertigo</i> as you suggested.</li> </ol><p>Looking forward to getting your feedback (incl your views on the mapping of veterinary ATC codes (see earlier comment)) via Forum (this ticket) or in EG meeting on Sept 2nd.</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>
