Reports -> Blank Forms -> Superbill/Fee Sheet: Typographical Error.

[tybanash]

A) Outreachy Username: tybanash B) Issue title: Reports -> Blank Forms -> Superbill/Fee Sheet: Typographical Error. C) Report Date: 10/5/2019 D) Sites Affected: Documentation and NHANES. E) OS/ browser used: Windows/Chrome F) EHR Workflow module: “Superbill/Fee Sheet” under “Blank Forms” which is under the “Reports” menu group. G) Steps to Reproduce the Issue:

1. Login with your account details.
2. Click on the menu group “Reports.”
3. Click on the module “Blank Forms.”
4. Select “Superbill/Fee Sheet.”

H) Expected Behavior: The table input should be spelt “Products.” I) What Actually Happened: The table input is instead spelt as “Producto.” J) Screenshots with Explanation: The word found on the first row fifth column is spent wrongly.
Below is the related code viewed in the Chrome Inspector. K) Estimation of Severity: Distracting or confusing but workflow can continue correctly (Minor). M) Solution: On the Chrome Inspector, look for the printed_fee_sheet.php file found under the interface file. Go to line 240 and delete “o” in “Producto” and add “s”.

[jonathanzhang53]

Hey this is what it looks like for me. I also scrubbed through the codebase for "producto" but it was only in the translation database. Maybe it has something to do with the language of the data you are looking at?

It doesn't seem to be a hard-coded typo.

[muarachmann]

@tybanash this is still on, any worries don't hesitate to reach out for help

[maggienegm]

From what I understand from the code, the column headings in this report are generated from specific tables and from fee_sheet_codes.php (if it has been uploaded).

I have looked through those specific tables within my local app's database and didn't see any mention of "producto." (The word "producto" does exist in the Spanish translation tables though.) My local app also didn't have a fee_sheet_codes.php file uploaded.

My next step would be to check the doc's server database, but I don't have access. How should I proceed solving this issue?