Programme SAP RNAABW00 - IS-H: Adjust Services for Absence

Description
This program performs a service adjustment for the selected cases inaccordance with the absence of a patient.
Patient absences are entered as movements (start and end of absence) anddo not delimit services when they are entered. This is performed by thisprogram which cancels, delimits or creates new services, if necessary.
The following adjustments can be made:

  • The service is entirely within the period of absence

    • The service is cancelled.
    • The absence period is entirely within the service period and the service
      • start and end dates are after the absence start and end dates
      The service is delimited with the start date of the absence and a newservice is created from the absence end date
      • The service start date is before the absence period and the end date is
        • during the absence period
        The end of the service is delimited with the start of the absence.
        • The service end date is after the absence period and the start date is
          • during the absence period
          The start of the service is delimited with the end date of the absence.
          Selection must be carried out according to the discharge date, caesnumber, or selection indicator. In addition, you can limit yourselection via the movement type of the absence start date and by certainservices.
          Using the chapter entitled Set Parameters forHandling Absences, you can define whether the absence start or endday is to be billed for.
          In this table, you can also define the minimum duration of absence forthe absence movements that are to be taken into account by the system.The duration of absence refers to full days of absence (that is, 24hours).
          By specifying an absence service, you can generate a new service for theabsence period. This period of absence, in turn, is dependent on theparameters used to bill the absence start and end days. This enables thebasic charge of an assigned bed to be billed with a reduced nursingcharge, if necessary.
          The minimum duration of absence and the absence service are proposedfrom the settings table and can be overwritten before this program isexecuted.
          A test mode is also available.

          Precondition

          • Only inpatient and day patient cases are taken into account. If you
            • define your selection according to discharge dates, only dischargedcases are taken into account. If you enter case numbers in the selectionbox, the specified cases are taken into account, even if they have notbeen discharged yet.
            • Services that have been billed in the interim are taken into account if
              • the absence start date is after the last interim billing date of theservice.
              • Planned movements are only taken into account, if the status of the
                • absence start date is not planned. A planned absence end date isprocessed in the same way as a patient who has not returned (end date12/31/9999).
                • Only extended services with the indicator absence-relevant are
                  • adjusted, irrespective of whether they are flagged as billable ornon-billable.
                  • A minimum duration of absence of 0 days is only meaningful if the
                    • absence start and/or end date is not billed.
                    • Note that the absence service is also generated if no other service
                      • adjustment is performed for the absence in question. This prevents theabsence service from being generated more than once for the same absenceperiod.

                      Output
                      A log is output for all of the selected cases with a relevant absencemovement and contains the absence-relevant extended services with theirstart and end dates before and after adjustment as well as a list ofabsence movements. Absence-relevant services that have been changed,cancelled, created, or left unchanged are also indicated. You can alsorestrict the log to include only services that have changed.
                      An extended log provides an explanation of why certain cases were notadjusted (for example, if the minimum duration of absence was notreached).

                      • Absence start date: 01/14/96 (24:00)

                      • Absence end date: 01/07/96

                      • Service start date: 01/01/96

                      • Service end date: 01/20/96

                      • Absence start date indicator set (not billed)

                      • Absence end date indicator not set (billed)

                        • Adjust exist. services: 01/01/96 - 01/13/96 (24:00) and 01/17/96 -
                          • 01/20/96
                          • Create absence service: 01/14/96 (00:00) to 01/16/96 (24:00)

                            • Further notes
                            Every day with a period of absence of 24 hours is regarded as a day ofabsence. If a period of absence starts at 00:00 and has not ended by24:00, this day is regarded as a full day of absence, irrespective ofwhether the absence start date is billed or not. Similarly, an absenceend date is always regarded as a full day of absence if it ends at24:00and started at 00:00.
                            Note that, if the absence starts at 24:00, this day is regarded as a dayof absence. The parameters that define how the absence start date isbilled determine whether this day is billed or not. Absence end daysthat end at 00:00 are also processed in the same way. This day isregarded as an absence end day and is billed in accordance with thedefined billing control parameters.
                            Planned absences are not taken into account by the system. If you haveentered an absence start date with the status 'Actual' but theabsence end date with the status 'Planned', the system does notadjust the service until you change the status of the absence end dateto 'Actual'.

                            • If you shorten a period of absence after the service was adjusted for
                              • the original period, the system cannot extend the extended service tothe new absence start or end date. By activating the rule type R5 in thecheck schema, you can output messages regarding charge gaps indepartmental per diems and base nursing charges for the defined checkperiods. Messages cannot be generated for personal items, since thereare no unique rules to govern how these items are contained in the case.In this case, the personal items must be adjusted manually. The absenceservice, if present, is adjusted to the modified period. If the absenceperiod contains several absence services that require adjustment, thesystem cancels these services and creates a new absence service for theperiod in question.
                              • If you have cancelled a period of absence after a service adjustment has
                                • taken place, the system generates the services for the cancelled absenceperiod under certain conditions. In doing so, it checks whetherabsence-relevant extended services end on the absence start date andstart again at the absence end date. If these services were alsogenerated by the actions contained in the rule type R9 or by the programRNAABW00, the system extends these actions to cover the period of thecancelled absence. The absence service, if present, is cancelled if itis no longer within an absence period.