Is there a way to not generate a patient statement

juggernautsei · April 16, 2025, 3:12pm

Is there a way to tell the system not to generate a statement for a particular patient?

stephenwaite · April 16, 2025, 4:55pm

Hi @juggernautsei , that’d be a nice feature add, for now have to use a special insurance to trap them.

juggernautsei · April 16, 2025, 5:28pm

We have a request. If there are others who read this post and are interested. Leave a comment or suggestion how this should be implemented in the system.

hitechelp · April 18, 2025, 1:45pm

We have the opposite problem, we can’t generate a patient statement/invoice.
At least not a useful one. Can anyone explain how we can get the v7xx version to produce a professional looking one that isn’t split over 3 pages with the last page being blank? This worked perfectly well in v6xx but now it’s rubbish. I’ve been after the answer for a year now and nothing put forward so far has worked.

juggernautsei · April 18, 2025, 2:31pm

Maybe you can join me on this project. I have posted at the bottom of this PR what the changes will do to the statement output. It has the potential to do what you want. Can you take it and pull it into your development environment?
I would like to see what it looks like with a load of data. It sounds like you have a load of data for testing what the statement will look like. Using the twig does eliminate the blank page that is being generated by the current HTML. ← Click the link to see the PDF that this code generates.

github.com/openemr/openemr

first steps toward twig - Patient Statement

master ← juggernautsei:patient-statement-twig

opened 06:24PM - 19 Mar 25 UTC

juggernautsei

+1632 -1908

Fixes #8102 #### Short description of what this resolves: Converts the heade…r of the patient statement to a call to a twig template to separate the logic from the presentation #### Changes proposed in this pull request: Convert header to a twig templage #### Does your code include anything generated by an AI Engine? Yes #### If you answered yes: Verify that each file that has AI generated code has a description that describes what AI engine was used and that the file includes AI generated code. Sections of code that are entirely or mostly generated by AI should be marked with a comment header and footer that includes the AI engine used and stating the code was AI. Codeium generated 80% of the code. The template and the refactoring of the function report header 2.

PR has been updated 4 - 19

juggernautsei · April 18, 2025, 2:37pm

Personally, I think this part needs to be removed. This is a hold over from a bi gone error. I rarely buy a stamp to pay a bill in the mail. The only time I do that is when I am trying to delay the payment as long as I can. In our current world, this is a security hazard waiting to happen. There should just be office contact information at the end to call or a QR code to the patient portal.

@stephenwaite what are your opinions?

hitechelp · April 18, 2025, 4:21pm

Love the look of this! Now I just need to get SMTP working to quit mailing them. I will certainly join in on this effort, if the cc section could be modified by users that would be awesome. If not, then it could be used for signature authorization to charge a card already on file, or perhaps a check box to select which one?

juggernautsei · April 19, 2025, 10:06pm

I did what I suggested to remove the credit card information from the bottom of the statement and added a footer. The footer contains the billing location address, phone, fax. See attached PDF. This is cleaner.

These are the two other files that I made changes to for this to all work. I will update my PR to show all the code.

sl_eob_search.php (66.1 KB)
Config_Mpdf.php (1.3 KB)

Stmt_Harry_3 (8).pdf (79.6 KB)

After reviewing what has been completed so for. I am of the opinion that the address page should be a separate feature function that is enabled in the globals. While we can’t accommodate every type of envelope out there. We can say which envelope type the system is built for and they can elect to use that one or have a developer change the code to meet the window envelop they want to use.

The PDF has an addPage function, which can be wrapped up in the global setting. If enabled, print page two on the back of page one and fold it for the window envelope.

hitechelp · April 20, 2025, 6:45pm

Using your files provided, I’ve managed to produce a decent plain text version after editing the statement.inc.php to remove the cc stuff and added a “Call to pay by credit card” line. However the “Modern” version is still rubbish, and my php skills aren’t quite up to the task of successfully cleaning that one up.

Here’s what they look like;
Stmt_Andy_1155-15.pdf (1.7 KB)
Stmt_Andy_1155-13.pdf (83.6 KB)

juggernautsei · April 20, 2025, 9:08pm

Mark up what you think the “Modern” version is supposed to look like. You can think it is rubbish but others think it look ok. But what I am seeing you show me as rubbish is the predecessor to what I am creating.

hitechelp · April 21, 2025, 8:04pm

I’ve reworked the Modern statement as far as I can. There are only 2 items I cannot fix, both are located in the footer. The page # and a bold horizontal line.
The footer is a nice touch. Thank you Sherwin, you rock.
ModernStatement.pdf (23.4 KB)

We use the printer dialog to print the second page with the addresses on the back.

juggernautsei · April 22, 2025, 2:58am

In the sl_eob_search, comment out this line and the footer goes away.

 $pdf2->SetFooter($footer);

The footer is controlled by the mPDF. It puts in the line. I don’t think it can be removed because it is automatic. If you want to remove just the page number.

 <td width='5%'>{PAGENO}/{nbpg}</td>

Remove the curly braces and the content thereof.