/
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 #822 has been updated by Kristiina Kahur. </h4> <div id="journal-4398-notes" class="note"><p><strong>2023-03-09 Expert Group</strong></p><p>Given that the introduction of ICD11 and ICHI will require changes in NDMS, grouper and def.tables, this change will be done once the actions concerning transision to ICD11 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-23</strong> (SWE ID C927)<br>This is a reminder that we still want a development in the direction that we outlined in case <a href="http://documents.norddrg.net/issues/545"><s>#545</s></a> but we have created this new case since <a href="http://documents.norddrg.net/issues/545"><s>#545</s></a> is closed (see Kristiinas comment 10-8-2021). Our wishes are repeated below in short. There might be further wishes from other countries as well. The matter must be discussed by the Expert group (a smaller working group first?) and eventually decided by the Board, since the changes mean changes in the program code for all groupers, which in turn will cause some costs. With this in mind, it may be a good idea to implement the changes at the same time as ICD-11 is implemented, as the program code in the groupers then must be updated anyhow.</p><p>In the grouping rules (table drg_logic) there is a terrible mess with type of care (e.g. primary care), type of contact and type of profession in the fields for diagnoses and procedures. In addition, procedures are specified in the fields for diagnoses (via dgprop).<br>Instead, the rules should have separate fields for administrative parameters like type of care, contact and profession and there should be more fields for procedures so it is possible to construct rules based on more than two procedures without using dgprop. There should also be fields for the patient’s functionality or for severity of illness and other factors that can be of interest to include in the grouping logic in the future.<br>Furthermore, we should discuss if there should be a marker on certain rules that tells the grouper that the demands in the dgprop fields are of the type “AnyOf” (now it is always “AllOf”). Then, for example, the 32 rules for DRG Q55N ’Nyfödd, födelsevikt 2500 g eller mer, med annat signifikant problem’ (= DRG 390X ‘Neonate, birthweight 2500 g or more, with other significant problem’) could be replaced by only 2 rules. (However, such a change has a rather limited ability to reduce the total number of rules, I think, so it may be not worth the effort.)</p><p>A possibility to have multiple coding for procedures (similar to asterisk-dagger for diagnoses) so that general qualifiers (NCSP codes beginning with Z) are hooked to the right intervention code is important, however. With the present logic, an irrelevant bilateral procedure (e.g. peripheral intravenous catheters) can lead to a DRG for major bilateral interventions (e.g. DRG 471N ‘Bilateral or multiple major joint procs of extremities’).</p><p>The question about if two or more diagnoses with CC property should generate MCC property in case <a href="http://documents.norddrg.net/issues/818">#818</a> can be added to these development discussions.</p><p>When ICD-11 is implemented in NordDRG, we all have to cope with new codes and then, at the same time, it could be appropriate to introduce systematic DRG codes that are common for all countries. It could be similar to the present Swedish codes but with more characters.</p>
