/
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 #1005 has been updated by Lotta Sokka. </h4> <div class="details"> <span><strong>Description</strong> updated (<a title="View differences" href="https://nordcaseforum.easyredmine.com/journals/5491/diff?detail_id=5601">diff</a>)</span><br/> </div> <div id="journal-5491-notes" class="note"><p>We support Mats’s suggestion with a little moderation (see below in red):</p><p> </p><ul> <li data-list-item-id="e5e89c70a8b729be7bba6893d133fc623">The few ultrasound procedures with OR 1 are all performed under open surgery or laparoscopy and we see no need to change the OR value for those procedures.</li> <li data-list-item-id="ef15e504e0e56fcbd2c2dc514e54f441a">Ultrasound procedures that are performed transcutaneous could have OR 0 (zero) except when needle<span class="ck-font-color-4"> or any other</span><span> </span>biopsy, <span class="ck-font-color-4">injection, punction or canalization</span><span> </span>is performed, then OR 2 is more adequate.</li> <li data-list-item-id="e8c05fa2c52cb48eb7c8c9e8f5ddc8f44">Other ultrasound procedures, for example together with endoscopy, could have OR 2.</li> </ul><p> </p><p>We will go through the features of the ultrasound procedures in our version and in case any changes are needed, come back with a suggestion.</p></div></div> <hr/> <p>With a reference to <span class="mention" data-mention="#982" data-mention-uid="e904a598"><a class="issue tracker-2 status-5 priority-21 priority-default multieditable-container closed" title="Case: OR value of proc codes KEDE1B and KEDE1A (on other ultrasound examination codes) (Closed)" onclick="if (!event.metaKey && !event.ctrlKey && event.button === 0) { event.preventDefault(); EasyVue.showModal('issue', 982); return false; }" href="https://nordcaseforum.easyredmine.com/issues/982">#982 - OR value of proc codes KEDE1B ...</a></span>, it was decided in EG Spring meeting that we create a new case to allow countries to have a look and check the OR values of all ultrasound codes as they lack consistency - some have OR 1, some OR 2 but most have OR 0. </p><p>Text written by Sweden/Mats is copied here:</p><p>In the Swedish version of NordDRG, the OR property 2 has a rather low impact. Out of 4 576 rules in the table drg_logic there are only 120 rules with the letter P. Most of them (109 rules) are about endoscopy. However, the OR value can be seen as a very rough estimate of resource consumption and then we have thought of a <u>principal</u> thinking: </p><ul> <li data-list-item-id="e80279baa4a1659ffc0bd4c572e64bf39">Ultrasound procedures that require laparotomy, laparoscopy, thoracotomy, or incision of the skin could have OR 1. </li> <li data-list-item-id="e968f91a85699e2c341bb48385e1d506f">Ultrasound procedures that require endoscopy could have OR 2. </li> <li data-list-item-id="ebe7f6a38466150cc61ced6fd6c6f2843">Ultrasound procedures that are performed transcutaneous could have OR 0 (zero) except when needle biopsy is performed, then OR 2 is probably more adequate. </li> </ul><p>With this principle in mind, we tried the following six changes on our patient database for 2024: </p><ul> <li data-list-item-id="e52df273772ab25ec5b00c64bc0f1e7d6"> <strong>AF032</strong> Intrakoronart ultraljud och doppler (<strong>FNDE1B</strong> Intravascular ultrasonography of coronary arteries) <i>from OR 2 to OR 1</i>. </li> <li data-list-item-id="e36f736adf207c13ee2f51d5d620ccc5d"> <strong>AP052</strong> Intravasalt ultraljud (<strong>PXDE1B</strong> Endovascular ultrasonography) <i>from OR 2 to OR 1</i> </li> <li data-list-item-id="e31cd5de323ac3deaa04cb1ff55144d9c"> <strong>TKE20</strong> Punktionsbiopsi av prostata med MR-ultraljudsfusionsteknik, transrektal (<strong>KEXX00</strong> Prostate needle biopsy) <i>from OR 0 to OR 2</i>. </li> <li data-list-item-id="e382473c058522bfa7f93bcafe8055f0e"> <strong>TKE23</strong> Punktionsbiopsi av prostata med MR-ultraljudsfusionsteknik, transperineal (<strong>KEXX00</strong> Prostate needle biopsy) <i>from OR 0 to OR 2</i>. </li> <li data-list-item-id="e22c1af97f6b690c7fbc1713d9a02cdbc"> <strong>XGX10</strong> Intrapleural ultraljudsundersökning (<strong>GXDE00</strong> Intrapleural ultrasonography) <i>from OR 2 to OR 1</i>. </li> <li data-list-item-id="e890b3864650fd8402398d9f6b84ac207"> <strong>XPX30</strong> Endovaskulärt ultraljud (<strong>PXDE1B</strong> Endovascular ultrasonography) <i>from OR 2 to OR 1.</i> </li> </ul><p>The result was that we got a lot of cases in DRG Z60 ‘Annan sällsynt, eller felaktig, kombination av huvuddiagnos och åtgärd’ (DRG 477 ‘Other rare or incorrect combination of principal diagnosis and procedure’) because of the change from OR 2 to OR 1 for FNDE1B, PXDE1B and GXDE00. </p><p>The question then is whether these cases really are incorrectly primary coded or whether the grouping logic needs to be supplemented with new rules that lead to adequate descriptive DRGs. </p><p> </p><p>Using this as a starting point, all countries are kindly invited to share their thoughts on three principles Mats is suggesting when it comes to determining the OR value of ultrasound procedures and check the data if they support this. If not, or if countries suggest different approach, please share via this ticket.</p><p> </p><p>The task type is currently set to ‘Development initiative.’</p>
