Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NBAS (Package) Appl. development Hospital System master data, catalogs
IMG Activity
| ID | SIMG_ISHMED_N2HL | Maintain Diagnosis Hit List for OU |
| Transaction Code | S_KK4_74000400 | IMG Activity: SIMG_ISHMED_N2HL |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_ISHMED_N2HL | Maintain Diagnosis Hit List for OU |
| Customizing Activity | SIMG_ISHMED_N2HL | Maintain Diagnosis Hit List for OU |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHMED_N2HL |
In this IMG activity, you can maintain diagnosis hit lists for specific
units (OUs) in relation to a given institution. Diagnoses which occur frequently in the OU are included in the OU-related hit list from selected catalogs.
By setting a priority, you can specify the order in which the diagnoses are to appear in the possible entries function in diagnosis processing. If you do not make this entry, all further diagnosis entries are displayed in the hit list, sorted by ascending order of diagnosis code.
Example
The diagnoses
- pylorus
- gout and
- angina pectoris
are among the most frequently made diagnoses in the internal medecine department.
After you have assigned a priority to the diagnoses using the values 3, 1 and 2, they are displayed in the OU hit list as follows:
- 274.8 gout
- 413 angina pectoris
- 151.1 pylorus
Requirements
Standard settings
Recommendation
Too many entries in the OU-related diagnosis hit list reduce the effectiveness and clearness of this input facility.
Decide with the department which diagnosis codes from which diagnosis coding catalogs are to be included and with which priority in the OU-related diagnosis hit list.
Activities
You can create new OU-related diagnosis hit lists or change existing ones.
- You make new entries by specifying the diagnosis code.
- You can remove entries that are no longer required from the displayed values for input by selecting Set deletion flag.
Assign the priorities for your OU-related diagnosis hit list.
Further notes
It is recommended to create OU-related diagnosis hit lists for departmental OUs since diagnoses for patients are documented on a departmental basis in diagnosis processing.
By means of the Create OU-related diagnosis hit list with reference copy function, you can copy an existing OU-related diagnosis hit list for another department, then modify it if required.
If you perform the Copy reference... function in change mode, the existing entries are deleted and the entries of the reference to be copied are accepted in full.
By entering the parameter value OKAT for the user parameter DKE, you specify that the OU-related diagnosis hit list is always displayed with the Possible entries function for coding diagnoses in diagnosis processing.
Business Attributes
| ASAP Roadmap ID | 401 | |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_ISHMED_N2HL | 0 | I010004203 O I010004309 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| N2HL | T - Individual transaction object | N207 | 1 | IS-H*MED: Create OU-Specific Diagnosis Hit List | ||
| N2HL | T - Individual transaction object | N208 | 2 | IS-H*MED: Change OU-Specific Diagnosis Hit List |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
