Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NPAS (Package) Application development patient accounting system
Basic Data
| Data Element | ISH_ENTL |
| Short Description | IS-H: Copayment Obligation for Day of Discharge |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ISH_ENTL | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Discharge |
| Medium | 14 | Day of Disch. |
| Long | 20 | Day of Discharge |
| Heading | 1 | D |
Documentation
Definition
You use this parameter to specify how the program for generating copayment requests is to handle discharge days.
Input values
- 0: No copayment required for discharge day
The copayment generator always treats the discharge day as copayment-exempt.
- 1: Copayment required for discharge day
The copayment generator always treats the discharge day as liable for copayment.
- 2: No copayment required for discharge day for discharge to external hospital or different charge area
The copayment generator treats the discharge day as copayment-exempt if discharge to an external hospital or discharge reason 17, Internal Transfer with Change of Charge Area, is specified for the discharge.
- 3: Discharge day not requiring copayment for user-defined discharge reasons
The copayment generator treats the discharge day as copayment-exempt if the discharge has a discharge reason that is included in the Discharge Reasons table.
A discharge is created in the system for a merged readmission case using an absence. The system then determines the discharge belonging to the absence. If the discharge reason specified here is included in the Discharge Reasons table, the day is copayment-exempt.
If you enter a retransfer using a standard absence, specify absence start reason 16, Hospital with Retransfer, and absence end reason 18, Hospital with Retransfer, when you enter the absence. This absence is in actual fact a discharge to an external hospital. In this exceptional case, the system determines discharge reason 06, Discharge to External Hospital. If you have included discharge reason 06 in the Discharge Reasons table, the day is copayment-exempt.
You can enter discharge reasons in the Discharge Reasons table using the pushbutton adjacent to the Discharge Day field.
Please note that this pushbutton is only visible if you have specified parameter 3, Discharge day not requiring copayment for user-defined discharge reasons. To make the pushbutton visible, you must confirm your entry with Enter after selecting parameter value 3.
The default setting is 2.
Example
A patient is discharged to an external hospital. If the parameter value is 0, the discharge day does not require copayment.
- If the parameter value is 1, the discharge day requires copayment.
- If the parameter value is 2, the discharge day in the discharging hospital does not require copayment. The admitting hospital may request copayment.
- If the parameter value is 3 and reason 06 is defined in the Discharge Reasons table, the discharge day does not require payment if discharge reason 06 is specified in the discharge.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
