PDF Error: Incorrect FPA Time Range

Problem Description: The Original FPA Time Range is Getting Lost

We've encountered a peculiar issue where the "Programming of Discharge" PDF is currently displaying the time range from the latest modification instead of the original FPA (Fecha Probable de Alta - Probable Date of Discharge) time range. This is causing a significant discrepancy in the information presented, potentially leading to confusion and misinterpretation of patient discharge planning.

Imagine you have a patient scheduled for a 24-hour surgery. The initial calculation for their probable discharge date, based on a three-day stay, is set for November 13, 2025, between 20:00 and 22:00. However, as things sometimes do in a medical setting, the plan gets adjusted. The first modification shifts the probable discharge to November 14, 2025, between 10:00 and 12:00. Then, a second modification moves it again to November 15, 2025, between 16:00 and 18:00. Logically, when you generate the PDF, you'd expect to see the original discharge date (November 13th) with its corresponding time range (20:00 - 22:00) clearly marked, along with the details of the latest modification. What's happening instead is that the PDF is incorrectly showing the time range of that latest modification (16:00 - 18:00) as if it were the original. This is a critical flaw because the original FPA is a key piece of information for historical tracking and understanding the initial discharge plan, especially when dealing with complex cases or extended hospital stays.

Example Scenario: A Case of Misplaced Time

To illustrate this problem more clearly, let's walk through a specific example. Suppose the initial surgery is scheduled to last 24 hours, starting on November 12, 2025, at 22:00. Based on a standard three-day inpatient stay, the original probable date of discharge (FPA) is calculated for November 13, 2025, with an expected time range of 20:00 - 22:00. This is our baseline, the initial plan.

Now, let's introduce some changes, as often happens in healthcare. The first modification to this plan sets a new probable discharge for November 14, 2025, between 10:00 and 12:00. Then, a second modification further adjusts it to November 15, 2025, with a discharge time range of 16:00 - 18:00. According to the system's logic, the PDF should clearly differentiate between the original FPA and the latest modifications.

However, what the generated PDF is showing is problematic. Under the section for the "Original Probable Discharge Date (3 days inpatient)", it correctly displays the date: November 13, 2025. But when it comes to the time, it's showing 16:00 - 18:00. This is incorrect because it's pulling the time range from the second (and latest) modification, not the original one. The PDF then correctly lists the "Latest Modification" details: New Date: November 15, 2025, and New Time: 16:00 - 18:00. The crucial issue here is that the original time range (20:00 - 22:00) is completely lost, replaced by the latest modification's time.

What should be displayed is the original date (November 13, 2025) and the correct original time range (20:00 - 22:00). The details of the latest modification should be presented separately, as they are, showing November 15, 2025, from 16:00 to 18:00. This clear distinction is vital for accurate record-keeping and effective patient management.

Impact: Confusion and Misinformation

This bug has a significant impact on the accuracy and reliability of our discharge planning documentation. The core problem is that the PDFs are now presenting incorrect information regarding the original discharge time range. This isn't just a minor display error; it has practical consequences. Medical staff, administrators, and potentially even patients relying on these PDFs might become confused about the initial calculated FPA. They might mistakenly believe that the latest modification's time range was the original plan, leading to potential misunderstandings about the patient's length of stay or the rationale behind the initial discharge estimates.

For instance, if a patient's original FPA was calculated with a later time slot, indicating a longer expected stay or a specific discharge protocol, and this is replaced by an earlier time slot from a modification, it could lead to assumptions that the patient was expected to be discharged earlier than originally intended. This could affect resource allocation, bed management, and communication with the patient and their family. In a fast-paced medical environment, clear and accurate information is paramount. When the system fails to present historical data correctly, it erodes trust in the system and can lead to errors in judgment. The system is designed to track changes and provide a clear audit trail, but this bug undermines that fundamental purpose. It's imperative that we address this issue to ensure that all users can rely on the PDFs for accurate and complete information, preserving the integrity of the discharge planning process and preventing potential operational hiccups.

Affected Files: Pinpointing the Source

After initial investigation, the root of this problem appears to lie within the PDF generation logic. Specifically, the file identified as routes/exports.py seems to be the culprit. Within this file, there's a function responsible for calculating and formatting the original discharge range. It appears that this function is mistakenly retrieving and displaying the time range associated with the most recent modification to the FPA, rather than the initially calculated one. This points to a potential logic error in how the system accesses or processes historical FPA data during the PDF generation phase. The code might be prioritizing the latest data point without correctly distinguishing it from the original FPA value. Understanding the exact logic within routes/exports.py related to FPA time range calculation and PDF population will be crucial for implementing a fix. We need to ensure that the system correctly identifies and uses the initial_fpa value when generating the PDF, and only uses the latest modification data for the designated "Latest Modification" section. This focused approach allows us to target the fix effectively, minimizing the risk of introducing new issues elsewhere in the system.

Acceptance Criteria: Ensuring a Robust Solution

To confirm that this issue is resolved effectively, we need to adhere to a set of clear acceptance criteria. These criteria will serve as our checklist to ensure the PDF generation is functioning as expected and that the critical information is displayed accurately.

Firstly, the most important criterion is that the generated PDF must accurately display the time range calculated for the original FPA (referred to as initial_fpa). It should not reflect the time range of the current or latest modification. This directly addresses the core of the problem. Secondly, we need to verify that the time range is calculated correctly in standard two-hour blocks. This ensures consistency and adherence to the expected format for time ranges. Thirdly, it's essential that the "Latest Modification" section of the PDF continues to display the current FPA correctly. This means the bug fix should not inadvertently break the accurate reporting of the latest changes. Finally, to ensure the fix is robust and handles various scenarios, the solution must be tested with tickets that have multiple modifications. This will confirm that the system can correctly differentiate between the original FPA and subsequent changes, even when there are several layers of modifications. By meeting these criteria, we can be confident that the PDF generation is reliable and provides accurate, easy-to-understand information for all users involved in patient discharge planning.

For further insights into medical discharge planning best practices, you can refer to resources from organizations like the World Health Organization or the Agency for Healthcare Research and Quality (AHRQ).