Function documentationExtend Field List in All View Types

 

You can use customer-specific enhancements in the Data Dictionary and a programming enhancement in the form of a Business Add-In (BAdIs) to add any number of fields to views for the Clinical Work Station. By using your own data elements, you determine the structure of the new columns.

Example Example

Within a view, you want to check whether discharge summaries have been written for inpatient cases to be discharged. You can incorporate the Missing Discharge Summaries column in the structure of the departures list.

The system can use the BAdI to check for each patient whether a document of the category "Discharge Summary" already exists for this case.

If the discharge summary does not exist, the system will display the appropriate symbol.

End of the example.

For more information about the enhancement possibilities in the IS-H System, see Customer-Specific Modification and Enhancement Possibilities.

Activities

Add Append Structures to the Structures

At the start of the implementation, you must add "append structures" to the structures that underlie the field selections for the view types. The structures for the various view types are:

  • Occupancy: RNWP_OCCUPANCY_LIST

  • Arrivals: RNWP_ARRIVAL_LIST

  • Departures: RNWP_DEPARTURE_LIST

  • Outpatient clinic/service facility: RN1WPV007_FIELDCAT

  • Coding analyses: RNWP_MEDCONTROL_LIST

  • Preregistration: RNWP_PREREG_LIST

    Note Note

    The structures for the i.s.h.med view types are:

    • Clinical Orders: RN1WP_REQUEST_LIST

    • Transport Orders: RN1WP_PTS_LIST

    • Documents: RN2WP_DOCUMENT_LIST

    End of the note.

Append structures are customer-specific enhancements of the standard dictionary objects that are similar to tables and structures. For information about creating append structures, choose Start of the navigation path SAP Library Next navigation step Basis Components Next navigation step ABAP Workbench Next navigation step BC Next navigation step ABAP Dictionary Next navigation step Tables Next navigation step Adding an Append Structure End of the navigation path in the SAP Library.

Note Note

For the append structures, use the new data elements in the customer namespace. This offers the advantage that you can then choose the form that the documentation is to take (column headers, quick info, FI Help, and so on).

End of the note.

Once you have completed and activated the append structures, these columns become automatically available in the field list for the corresponding view types, and you can include them in the layout. For managing the layout, the same is valid for all other fields: They can be saved as a personal layout, sorting can take place based on these new columns, etc.

Filling Columns

At this stage, all columns are still empty, since filling has yet to take place. The selection takes place using the following BAdIs or customer exits:

  • Occupancy, Arrivals, Departures view types: BAdI ISH_WP_VW123_COLUMN

    Note Note

    Although customer exit SAPLN1WP still exists, we recommend that you use the above named BAdI since it provides greater possibilities.

    End of the note.

  • Outpatient Clinic/Service Facility view type: BAdI: N1_WP_LSTAMB

  • Coding Analyses view type: BAdI: N_WP_MEDCONTROL

  • Preregistrations view type: BAdI: ISH_WP_PREREG_VIEW

    Note Note

    BAdIs and customer exit for i.s.h.med:

    • Requests: BAdI: N1_WP_REQUEST

    Transport Orders: BAdI: N1_WP_PTS

    Documents: Customer exit N2WPDOC2

    End of the note.

In these BAdIs and customer exits, the system employs an interface to transfer the relevant case and movement data. This also depends on from which view type you call the enhancements. In the view type Outpatient Clinic/Service Facility, at certain calls, only a service without reference to a case is available and no movement data is available. You will have to note these exceptional cases when implementing the BAdIs and customer exits.

Note Note

You must note that a larger selection will adversely affect the running time of the view, since the system must process the enhancements (BAdIs, customer exits) after all function calls and with all changes to the views.

End of the note.