/
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 #813 has been updated by Kristiina Kahur. </h4> <div id="journal-4396-notes" class="note"><p><strong>2023-03-09 Expert Group</strong></p><p>This case in linked to <span class="mention" data-mention="#822"><a class="issue tracker-8 status-1 priority-20 priority-lowest multieditable-container scheme scheme-4" title="Development initiative: Further development of NordDRG (Active)" href="https://nordcaseforum.easyredmine.com/issues/822">#822</a></span> . <br>Given that the introduction of ICD-11 and ICHI will require changes in NDMS, grouper and def.tables, this change will be done once the actions concerning the transition to ICD-11 and ICHI will be taken.</p><p>Until then, this case remains further active.</p></div></div> <hr/> <p><strong>Mats Fernström, the National Board of Health and Welfare, Sweden 2022-02-01</strong> (Swe ID C913)<br>The term MDC is used in two completely different meanings in NordDRG. In the table drg_logic, MDC means the MDC to which the principal diagnosis must belong to and in the table drg_name, MDC means the MDC to which the DRG belongs. It is not always so that the MDC of the principal diagnosis is the same as the MDC of the DRG. In the Swedish version of NordDRG for 2022 there are 251 rules where the MDC of the principal diagnosis differs from the MDC of the DRG outcome, which corresponds to 194 different DRGs.</p><p>To make the grouping logic more transparent and to avoid future misunderstandings we suggest that the headline ‘mdc’ in the table drglogic is changed to dg_mdc (= diagnosis-mdc) and that the headline ‘mdc’ in the table drg_name is changed to drg_mdc.</p>
