Ansicht
Dokumentation

RNCSDO00 - Hospital Discharge Report (SDO)

RNCSDO00 - Hospital Discharge Report (SDO)

Addresses (Business Address Services)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This program creates SDO files for the inpatient/day patient cases that match your selection criteria.

Integration

Prerequisites

  • Communication-specific Customizing: SAP delivers a communication standard with versions, message types, message segments, and message fields assigned to the EDI procedure (SDO). However, you can also define your own communication standard and add region-specific fields.
  • For more information about communication-specific Customizing, see 'IT: SSN Customizing Procedure' in Implementation Guide (IMG) for SAP Healthcare - Industry-Specific Components for Hospitals under Communication ->Electronic Data Interchange -> Customizing Step-By-Step->IT: SDO Customizing.

  • Status of medical documentation-specific Customizing: You must define a status profile, which is assigned to all relevant cases during case creation. The status profile can use the business transaction Communicate to SSN (NSSN) for a user status.
  • For more information about status of medical documentation-specific Customizing, see Implementation Guide (IMG) for SAP Healthcare - Industry-Specific Components for Hospitals under Medical/Nursing Documentation -> Basic Medical Documentation Status Management -> Define Status Profiles. The country version Italy contains a sample status profile called ISHCVIT0.

Features

You can select cases either using case selections or according to selection criteria.

Selection

You can specify the following selection criteria:

  • Discharge date
The system selects all cases with a discharge date that is in the specified period.
  • Case number
The system selects all cases with a case number that is within the specified range.
  • SDO unique identifier
The system selects all cases that are associated with each of the SDO IDs specified as a range.
  • Patient numbers
The system selects all cases for the specified range of patients.

When you select cases using case selection, the system retrieves all the cases in this case selection. Note: You can define your case selection for use as a selection criterion using transaction NA20.

When you select Additional Selection Criteria, you can filter cases based on the following criteria:

  • Discharge departmental organizational unit
The system selects all cases in which the departmental organizational unit (OU) of the discharge movement is within in this range.
  • Discharge nursing organizational unit
The system selects all cases in which the nursing OU of the discharge movement is within this range.
  • Med. doc. status key
The system selects all cases with the specified 4-digit status key that is defined in the Customizing activity 'Define Status Profile'.
  • Med.doc. status profile
The system selects all cases with a status profile key that is defined in the Customizing activity 'Define Status Profile'. We recommend that you specify this criterion in combination with the 'Med. Doc. Status Key' criterion if you want to select cases with a particular medical documentation status.

Execution Options

  • Test mode
  • If you execute the program in test mode, the system does not save changes on the database while the program is running.

  • If you execute the program in real (update) mode, the log is saved to the database and the status of medical documentation is changed automatically (according to the Customizing settings for the status profile assigned) for every case included in the communication process to SSN.

The SDO files are created independently of the test mode. In test mode, the system adds the characters 'TEST' to the file names.

  • Create SDO files directly
  • If you select the Create SDO files directly checkbox, you can skip ALV display of the cases and messages.

  • If you do not select the Create SDO files directly checkbox, you can select the cases to be considered for SDO file creation manually. The system displays a hierarchical ALV list of the selected cases and messages. You can use this option to check all the errors associated with the SDO records. You can then create files by manually selecting the cases to be included.

Canceled Cases

Processing of canceled cases takes place in a specific manner in the hospital discharge report. Canceled cases are usually no longer taken into account in standard SAP Patient Management reports. This is a little different in the case of the hospital discharge report.

  • Selection of cases
  • Canceled cases are included in selection if you only select using case-related criteria such as "Case number", "SDO Unique Identifier", "Patient Number" or "Case Selection" and additional selection criteria like "Discharge Dept. Org. Unit", "Discharge Nursing Org. Unit", "Med. Doc. Status Key", and "Med.Doc. Status Profile". Cancelled cases are not included if you specify the selection criterion "Discharge date".

  • ALV list output
  • If a case is canceled in the SAP Patient Management system and has not yet been sent to SSN, the system displays an error message indicating that the case has been canceled. This is not included in SDO file creation, since this need not be communicated to SSN.

  • If a case is canceled in the SAP Patient Management system, is sent to SSN after cancelation, and you attempt to communicate again, the system displays the error message 'Case has already been communicated to SSN with 'Canceled' status'. This case is not included in SDO file creation, since this need not be communicated to SSN again.

  • If a case is already communicated to SSN and is later canceled in the SAP Patient Management system, the system displays an information message indicating that the case has been canceled . This case is included in SDO file creation, since information about its cancelation must be communicated to SSN. This canceled case is communicated to SSN with the communication status "Canceled". However, the system cannot change the status of these cases, even though it is communicated to SSN.

'Case Overview' option

Within the 'Hospital Discharge report', you can mark by position the cursor on the corresponding line of the hierarchical ALV list and choose the option 'Case Overview'. As alternative you can also use a double click on the line in the ALV.

Note: you cannot immediately view the changes made to the case in the ALV list of the 'Hospital Discharge report'. Run the 'Hospital Discharge report' again to view the refreshed data, then continue with the process of SDO file creation.

Standard Variants

Output

The system displays a hierarchical ALV list of selected cases and assigned messages.If you select the 'Create SDO files directly' checkbox, you can create the SDO files with all marked cases to be included and thus skip this. A statistical analysis is also displayed, for example:

  • Total number of cases selected
The total number of cases that were selected based on selection criteria entered at the selection screen are mentioned here.
  • File creation
The file names are generated by the hospital discharge report with a predefined naming logic: ___
  • For example, the three SDO files would be assigned the following names:

  • 0001_SDO1_20071204_125647.TXT

  • 0001_SDO2_20071204_125647.TXT

  • 0001_SDO3_20071204_125647.TXT

  • Output on SAP server
If you select this option, the SDO files created are made available on the SAP server. You can specify the path where you want the files to be stored on the server in the 'Data Output Path' field on the selection screen.
  • Output to PC
If you select this option, you can enter the path where you want to store files on a local PC in the Data Output Path field on the selection screen.
  • Layout options
You can define your own set of fields to display the results in the hierarchical ALV list of cases. You can save this layout for use again the next time you execute the program.
  • Patient data on case level
Within the SDO record of the 'Hospital Discharge report', there are fields included which are patient attributes like for example the marital status. These patient attributes may change over time, but have to be kept stable for the SDO record. Therefore the system copies these patient related attributes at time of discharge on case level into the table NPNTCAS. You can see and with the corresponding authorization you can change these copied data via the SAP standard subscreen 'Patient Data on Case Level' in the Clinical Process Builder (NV2000).
The exact point of copying of patient data for a case is linked to the status of the discharge. If a planned discharge is entered into the system, the value is not copied. The patient data is copied only when the status of discharge is set to 'actual'. In cases where the discharge is canceled, the copied dataset is deleted.
After the patient data is copied the Hospital Discharge Report retrieves the patient related attributes only from this copy.
There exists one exception from this rule: The field Patient/Sex/Age in the field catalogue of the ALV reflects always the current values of the patient level. Since the field Patient/Sex/Age is not a field of the SDO record and is only used for display purposes in the ALV list, it has no influence on the data within the SDO record of the SDO files.

Activities

Background processing

The Hospital Discharge program can be scheduled for background processing with the same execution options as above. The result is the same. The advantage is that the program can be scheduled for a specified time period and the SDO files can be created without user interaction.

Assignment of Health Insurance card (TEAM card) to case

Within the SDO record of the 'Hospital Discharge report', there are details that are mandatory for foreign patients coming from EU (European Union) or other countries with special health agreements. This information can be taken from the Health Insurance card (TEAM card) of the patient.

Process:

  1. Integrate the SAP provided sub-screens 'Overview of Health Insurance Cards' and 'Health Insurance Cards Dialog' into a variant of the 'Clinical Process Builder'.
  2. Start the Clinical Process Builder with the case number to which the TEAM card must be assigned.
  3. Choose the button 'Create Card' on the ALV toolbar in the 'Overview' sub-screen. A card of type 'EU_E111' is created with a temporary number as a node for the case. A version of this card is also created as a leaf under this node. If other (newer) versions must be created for the card as a result of changes in data, select the card and choose the button 'Create Version E111' on the ALV toolbar.
  4. Enter all Health Insurance card (TEAM card) details of the patient in the 'Dialog' sub-screen visible below the 'Overview' sub-screen. When you select the card in the 'Overview' sub-screen, the 'Dialog' sub-screen displays the card details. These are prompted by the system. When you select the card version in the 'Overview' sub-screen, the 'Dialog' sub-screen shows the specific details of that version. You can also enter different details for that version.
  5. Assign the Health Insurance Card (TEAM card) to the case by assigning the Insurance relationships of the case to a version of the card.
    1. Select the card version in the 'Overview' sub-screen. A list of Insurance relationships (SSN and otherwise) for the case are displayed in the 'Dialog' sub-screen.
    2. Mark an Insurance relationship from the table control. The relationship is highlighted, indicating that this is the Insurance relationship that is to be assigned to the card version. (You can also cancel this assignment by unmarking the Insurance relationship. The relationship will no longer be highlighted, indicating that it is no longer assigned to the card version.)
Note: the list of Insurance relationships to be assigned to the card version will only be those that are not assigned to any other card version.
  1. Click 'Save'. The card (permanent number) and assignments are saved onto the database.

Example






Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 14460 Date: 20240520 Time: 083152     sap01-206 ( 263 ms )