/
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 #982 has been updated by Lotta Sokka. </h4> <div id="journal-5191-notes" class="note"><p>Finland does not want this change in our 2027 version.<br> </p><p>When analyzing our data we found no cases where proc code KEDE1A (KE1AE <i>Eturauhasen ultraäänitutkimus</i>) had been used, so we couldn’t compare costs between these two procedures.<br> </p><p>Cases where proc code KEDE1B (KE1BE <i>Eturauhasen ultraäänitutkimus peräsuolen kautta</i>) had been used were mainly grouped to either 912O <i>Disease or disorder of the male reproductive system, short therapy w/o significant procedure</i> or 911O <i>Disease or disorder of the kidney and urinary tract, short therapy w/o significant procedure</i>. The mean cost for 912O was 274 € (for 912O cases where KEDE1B had been used 394 €) and for 911O 326 € (448€ for the cases where KEDE1B had been used).<br> </p><p>If OR value for KEDE1B was changed to 2, the cases would mainly be grouped to either 812O <i>Non-extensive procedure of male reproductive system, short therapy</i> (mean cost 967 €) or 811O <i>Non-extensive procedure of urinary tract, short therapy </i> (mean cost 937 €). In terms of cost homogeneity, KEDE1B cases do not really fit into these two groups.<br> </p><p>Clinically we do acknowledge that resourcewise KEDE1B is more demanding than KEDE1A. However, as Finland is aiming to work on the gender neutral grouping this year and this would be a part of that solution, we don’t want to change the OR value at this point.</p></div></div> <hr/> <p>This case emerged during updates of Swedish primary classifications (see <span class="mention" data-mention="#976"><a class="issue tracker-15 status-5 priority-21 priority-default multieditable-container closed" title="Primary classifications: 2026 updates of NCSP, ICD and ATC (Sweden) (Closed)" onclick="if (!event.metaKey && !event.ctrlKey && event.button === 0) { event.preventDefault(); EasyVue.showModal('issue', 976); return false; }" href="https://nordcaseforum.easyredmine.com/issues/976">#976 - 2026 updates of NCSP, ICD and ...</a></span>) and concerns the OR value of NSCP+ codes KEDE1B <i>Rectal ultrasound examination of prostate </i>in relation to OR value of KEDE1A <i>Percutaneous ultrasound examination of prostate.</i></p><p>The issue was discussed during EG Autumn meeting and it was decided to create a separate ticket for countries to check their data and confirm if they want to keep current OR values of KEDE1B or change it. </p><p><strong>KEDE1A </strong>has OR 0 in all versions.<br>National codes mapped to KEDE1A:<br>•FIN - KE1AE Eturauhasen ultraäänitutkimus<br>•ICE - KEDE1A Percutaneous utlrasound examination fo prostata<br>•LAT - KEDE51 Prostatas Eksterna ultrasonografija<br>•NOR - SKE0AK UL Prostata - ekstern undersøkelse<br>•SWE - AK046 Ultraljudsundersökning, prostata och vesiklar<br>•SWE (new) AK118 Transperineal ultraljudsundersökning av prostata och vesiklar<br>•SWE (new) AK130 Datortomografi, urografi</p><p><strong>KEDE1B </strong>has OR 0 in ICE, FIN and NOR versions, SWE suggest to give OR 2 value to KEDE1B<br>National codes mapped to KEDE1B:<br>•FIN - KE1BE Eturauhasen ultraäänitutkimus peräsuolen kautta<br>•ICE - KEDE1B Rectal ultrasound examination of prostate<br>•NOR - SKE0BK UL Prostata - transluminal undersøkelse<br>•SWE (new) - AK117 Transrektal ultraljudsundersökning av prostata och vesiklar</p><p>The argument to give code <strong>KEDE1B </strong>OR 2 instead of OR 0 was that rectal ultrasound of prostate is generally considered the more demanding procedure than percutaneous ultrasound of prostate.</p><p>Even though the OR values of those two codes were discussed during the meeting, it might be reasonable for countries to have a look and check the OR values of all ultrasound codes.</p><p>It was decided that in 2026PR version, code <strong>KEDE1B </strong>(and respective national codes) will get OR 2 value in SWE version and there is no changes in FIN, ICE and NOR version, i.e. we keep OR 0.</p><p>We will get back to this in 2026 Spring meeting.</p><p> </p>
