/
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 #853 has been updated by Kristin Dahlen. </h4> <div class="details"> <span><strong>Assignee</strong> set to <i class="new-value">Kristin Dahlen</i></span><br/> </div> <div id="journal-4377-notes" class="note"><p>Norway uses a selection of ATC-codes in our logic. It is mostly in use in our STG-system (covering expensive patientadministered drugs), but we also have a selection of ATC-codes with properties in our DRG-logic.</p><p>As mentioned earlier Norway do not see the importance of having all ATC-codes in the DRG-logic tables, as we only uses a small selection of the codes in the logic. The ATC-codes are though used in the hospitals and is reported to the Norwegian patientregistry where they are validated. </p><p>The ATC-codes as a whole can therefore be removed from the Norwegian tables, but we need to find a way to manage the ATC-codes that shall have properties. This can be discussed separate by Norway and the center.</p><p> </p></div></div> <hr/> <p>This case is related to ticket <span class="mention" data-mention="#690"><a class="issue tracker-11 status-5 priority-21 priority-default multieditable-container closed" title="NDMS: Use of ATC codes in NordDRG and NDMS (Closed)" href="https://nordcaseforum.easyredmine.com/issues/690">#690</a></span> about the maintenance of ATC codes. For sake of clarity, a new ticket is created.</p><p>By now, there is a special module for maintenance of ATC codes in NDMS/MBC and as a next step we would like to discuss with members of EG in 2023 Spring meeting and decide how to proceed with the maintenance of ATC codes and their features in NDMS.</p><p>For this, please provide the country information concerning the following items so that this can be discussed in EG 2023 Spring meeting:</p><ol> <li>Are 5-characters ATC codes still in use and there is need to keep them active in 2024 definition tables?</li> <li>Are ATC codes which are used in diagnosis codes or procedure codes tables identical or there can be ATC codes which are included only in procedure codes table and not in diagnosis codes table (and vice versa)?</li> <li>Please check the features of ATC codes in 2023 tables and indicate if there is need for correction in 2024 tables (tables are attached to this ticket).</li> <li>Please inform in case there is no need to keep ATC codes in definition tables at all and the codes can be removed. </li> </ol><p>Based on the feedback we can proceed with next steps in maintenance of ATC codes and making necessary changes in def. tables.</p>
