expEDIum Medical Billing v5.1 Release Notes1) [Ticket # 10973] MDR: Collection Report | Enhanced Default Report, New Report - By Service Line One of the clients requested us for a

eMB Release Notes v5.1 Page 1 of 47 For Restricted Use

iTech Workshop Private Limited

expEDIum Medical Billing

v5.1

Release Notes Release Date | May 16, 2020



Table of Contents

1) [Ticket # 10973] MDR: Collection Report | Enhanced Default Report, New Report - By Service Line .............................................3

2) [Ticket # 10974] PH: Patient Payment Agreements ............................................................................................................................6

3) [Ticket # 11026] MDR: Patient Demographics Enhancement | Patient Alternate Address and Employment Status .................. 14

4) [Ticket # 11182] iTech: Admin Module | Process - Manual Trigger | UI Improvements ................................................................ 17

5) [Ticket # 11237] MDR: Account Feature Settings - Populate default claim fields in New Claim Form (Prof/Inst) ........................ 17

6) [Ticket # 11240] PH: AR Summary Report – Enhancemnt - Monthly, Half-Yearly, Yearly options .................................................. 19

7) [Ticket # 11248] MDR: Manage Reporting Procedure Codes + Show/Hide Option in Patient Statements ................................... 21

8) [Ticket # 11354] PH: Transunion Secure FTP Connection issue | Transmission Library Upgrade and Module Changes ............ 25

9) [Ticket # 11430] PH: Ledger: Generate Receipt fails to print due to carriage return/line feed in transaction notes ................... 25

10) [Ticket # 11466] MDR2: New Claim (Prof/Inst) - Pre-configure practice, provider and facility details ..................................... 25

11) [Ticket # 11476] MDR: UB04 Claims - Medical Record Number not getting saved .................................................................. 31

12) [Ticket #11539] PH: Patient Eligibility History Window | Show more information/New Columns ............................................ 31

13) [Ticket # 11541] PH: Posting - Ability to see more claims in the batch, Enhanced Search Claim Filters/Sort Options ........... 31

14) [Ticket #11542] MDR + iTech Internal: Appointment Report Enhancements ........................................................................... 33

15) [Ticket #11548] PH: Enhancement - DOS column on Claim Screen under Posting Batch ........................................................ 34

16) [Ticket #11549] PH: Enhancement | New Filter “Under Aged” in Aging Reports ...................................................................... 34

17) [Ticket #11572] MDR: Batch Error - Claims Created through ESB giving error while posting ................................................... 36

18) [Ticket #11585] PH: Enhancement - Age Group Filter in Revenue Board Report ...................................................................... 37

19) [Ticket # 11629] MDR: Anesthesia claims support in ESB ......................................................................................................... 38

20) [Ticket #11630] MDR: ESB Enhancment - Sync Hospitalization Date with the Date of Service ............................................... 39

21) [Ticket #11631] MDR: Clear option to clear payer information in patient demographics ......................................................... 40

22) [Ticket #11634] iTech: External Pay - Change in logic to call Rest API when locally hosted .................................................... 41

23) [Ticket #11649] PH: Posting Batch Enhancement – Allow longer batch name (60 char) and enhance batch notes filter ..... 41

24) [Ticket #11652] PH: Close Button and Corner Close Icon are not appearing on Eligibility History Window when opened from

claim screen .................................................................................................................................................................................................. 42

25) [Ticket #11665] iTech: Disable Transaction Amount | Multi-Claim Online Payment - By Claims, By SFS Program ................. 43

26) [Ticket #11682] iTech | Quick sanity testing the Manager module required ............................................................................ 44

27) [Ticket #11686] iTech: Edit Ledger Transaction Window - SFS Program should not be editable ............................................. 44

28) [Ticket #11714] PH: Revenue Board Report | Self Pay Claims - Patient Payment Amount is shown in Insurance Payment

Amount wrongly ............................................................................................................................................................................................. 45

29) [Ticket #11715] PH: Medicaid Claims by RA Date report - Shows inaccurate claim count and check amount ....................... 46



expEDIum Medical Billing v5.1 Release Notes

This release note describes tickets that are either enhancements or new features or bug fixes.

Some tickets may refer to other tickets from previous releases. These tickets are combination of

change requests from any of our partners and that are internally identified at iTech. A summary of

tickets is provided in the last page of this release note. On request, we can provide any specific

release note for any earlier release. This release note is also available from our website at

http://www.itechws.com/releasenote for the last few releases.

1) [Ticket # 10973] MDR: Collection Report | Enhanced Default Report, New

Report - By Service Line

One of the clients requested us for a feature enhancement in the “Collection Report” – to have a

new type of collection report with the “Service line” details. Hence, a new filter Report Type is

introduced in the collection report screen. This drop-down filter will have two options Default and

By Service Line.

Default – This is the default collection report with the existing filters.

By Service Line – This is the collection report with the service line details. When this option is

chosen in the drop down, a new check box “Exclude Services with Zero Charges” will appear on

screen and is enabled by default.

The collection report will have two options “Create Report” and “View Report”.

Create Report - When the report type is chosen as “By Service Line”, a confirmation message will

be shown on screen with a create and cancel option.

http://www.itechws.com/releasenote



On clicking create, a pop-up window will appear on screen to view the service line collection report

from the View Report option.

A new button View Report is introduced in the collection report screen. The user can view the

created Default and by service Line collection reports from the View Report option. New tabs

Default and By Service Line is introduced in the “View Report” option with Archive and Delete

options.

Previously, the collection report was viewed from the view report option under Reports >> View

menu. In this version, the Default and Service Line collection report will be created under View

Report screen in Collection Reports module itself.

The earlier default collection reports created by users will be available from the drop box under

Reports >> View.

Go to “Service Line” tab to view the Service line-based collection reports. These are saved in HTML

format in the drop box. Click the View icon in the report row to open the report. Below shows the

sample “Collection Report by Service Line”.



This report can be exported to PDF/Excel using the Export icon provided at the top right corner of

the report.

To archive the reports and move to archive section, please select one or more reports using the

check boxes provided, and click on Archive button.

The reports can be still viewed by clicking on View button, and exported to PDF/Excel. Select one

or more reports and click on Delete button to permanently delete the reports.

The newly created Default Collection Reports will be dropped in this new drop box. The format will

be the same CSV format always as before. These reports can be by clicking on the “Default” tab.

Click on download icon near each report to download the CSV file.



To archive the reports and move to archive section, please select one or more reports using the

check boxes provided, and click on Archive button.

The default collection reports in CSV format can be still downloaded by clicking on Download

button, select one or more reports and click on Delete button to permanently delete the reports.

2) [Ticket # 10974] PH: Patient Payment Agreements

As per the client request a new feature called “Patient Payment Agreements” (PPA) is introduced

in eMB. It is a simple agreement where the patient agrees to pay certain amount over a period

until he/she completely pays of the balance due. Here both the clinic and patient agree upon and

signs an agreement.

This feature is available on demand for specific clinics where the PPA feature is enabled in the

feature settings from the admin module. The system supports configurable template-based

patient payment agreement form that can be customized for each clinic.

Once the feature is made available for clinics, the users can:



1) Create Patient Payment Agreements.

2) View/Edit Agreement details.

3) Print Agreement.

By default, PPA will be disabled for all the accounts. On demand, administrator can enable PPA

when a request is received from a practice account. The PPA feature can be enabled only from

Admin module as shown below.

The PPA feature access is available to the operators/users under a practice account based on the

privileges configured by the administrator under user role settings or custom operator privilege

settings.

View Only - If checked, then user will not be able to create new patient payment agreement, edit

and manage it.

Manage - If checked, the user will be able to add, edit and manage patient payment agreements.

In this case, View Only option is not applicable - it will be unchecked and disabled.

The Practice Administrator Users will have the user role pre-configured to have PPA-Manage

enabled and will be applicable when the clinic has PPA feature enabled.

Templates Configuration

This option is available from the Upload Template option provided for each practice account in the

account list screen in administrator login.

1) The administrator can upload one or more templates and assign one or more templates

to a practice account.

2) The administrator can name the templates, enable/disable templates, select and assign

the templates to be used, and set a default template.



3) The administrator can delete the templates which are not used/inactive.

4) The template set as default, will appear in template drop down as the chosen template by

default in the view patient payment agreement screen on the practice module.

Ledger Transaction Types

In the user login, a new check box is introduced “Allow PPA” in the add/edit custom transaction

type screen. This is available under Maintenance >> Ledger Transaction Types >> Add/Edit

custom transaction types. The Allow PPA check box will appear only if the Transaction Type is

Accountable and the Amount Type is Payment. The user can enable “Allow PPA” option by selecting

the check box and save the settings. When this option is enabled, the transaction type can be

used to make patient payment agreement-based instalment transactions.

Patient View List and Patient Ledger

When the practice account is enabled with the allow PPA option, a new icon for PPA will appear in

the Patient List screen and Patient Ledger screen to manage PPA.



Patient List Screen

The PPA management option is provided here for the clinics who manage patient demographics

from eMB itself

Patient Ledger Screen

The PPA management option is provided on patient ledger screen if the system is integrated with

EMR and the clinics manage patient demographics from EMR itself. For such installations, the

patient list screen will not be accessible to users, and hence they manage it from the option

provided in patient ledger screen,

When the user clicks on PPA icon/link, a context menu will appear on screen to add new/manage

patient payment agreements.

The context menu will have two options:

1) Create new PPA – for users with Manage privilege only.

2) List PPA – for both View and Manage privilege.

List PPA

When the user clicks on List PPA, a new window will appear on screen with the list of PPA’s created.

This window will display Status of PPA, PPA ID, Agreement Amount, Interval (weekly, monthly,

quarterly, half yearly, yearly), Instalment Amount, No of Instalment, Agreement Start Date,

Agreement End Date, Created Date and Created By.

The right end column of the window displays the menu context for each PPA. For the Manage

operator privilege the menu context for each PPA will be as follows:

1) View Agreement

2) View/Edit Agreement Details

3) View Transactions



For the view only operator privilege the menu context for each PPA will be as follows:

1) View Agreement

2) View Agreement Details

3) View Transactions

Create new PPA

The users can create PPA from Patient Ledger screen and the Patient View List screen. This PPA

icon will appear for practice accounts only if PPA feature is enabled for the account and individual

operators/user under that practice account can access the PPA features based on the privileges

granted to them.

When the user clicks on Create a new PPA, it allows the user to create a new Agreement for each

patient.

The create PPA screen will have certain fields that are auto populated, and some fields must be

filled in by the user.

Agreement Details

1) Agreement ID: The Agreement ID will be generated by system.

2) Agreement Name: The user must enter the Name of agreement (Mandatory field).



3) Agreement Date: This is the date when the agreement is created. The system will always

consider the current date, and hence it is not editable.

Instalment Amount Details

1) Agreement Amount: User must enter the agreement amount, and amount should be

greater than 0.00 (Mandatory field).

2) No. of Instalments: User must enter the number of instalments, and value should be

greater than 0 (Mandatory field).

3) Instalment Amount: Instalment amount will be auto calculated based on agreement

amount and no. of instalments.

4) Start Date: This is the official start date of the payment agreement based on which the

other details of the agreement are arrived at. To be specified by user

5) Interval: The user can choose the interval, based on patient choice who will pay after

certain interval. Currently system supports only five intervals i.e. weekly, monthly,

quarterly, half yearly and yearly (Mandatory field).

6) End Date: It is a system calculated end date of PPA based on No. of Instalments, start date

and interval provided by the user.

Patient Details

1) First Name: Auto populated Patient First Name.

2) Last Name: Auto populated Patient Last Name.

3) PAN: Auto populated PAN.

4) Current Balance Due: This is the patient's current balance due when the agreement is

created. This is for informational purpose and will not change based on the subsequent

transactions in patient ledger.

Insured/Guarantor Details

1) First Name: Auto populated - Patient’s Primary Insured First Name.

2) Last Name: Auto populated - Patient’s Primary Insured Last Name.

Practice Details

1) Name: The user can choose the practice name from the drop down and other fields

(Address, city, state, zip and NPI) will be auto populated based on practice name the user

has selected and this is a mandatory field. This is given as a dropdown as there are chances

that the account will have multiple Practices/Billing Offices configured.

2) Notes: Here user can write a note for the PPA and it is not a mandatory field.

Toggle button - On top right of the screen there is a toggle button to enable/disable PPA. By default,

it will be always enabled.

View Agreement:

The View Agreement screen displays the actual patient payment agreement in the format based

on the template chosen.

The left top corner of the screen displays the "choose template" dropdown where the user can

choose any pre-configured PPA templates and click on Print PPA button to open the agreement in

Print Preview screen. The user can print the agreement directly or Export to PDF from the options

provided in Print Preview Screen.

If the template is not configured, then an alert message will be displayed on the screen.



View/Edit Agreement Details:

The user can view the agreement details from this screen. The user can edit the agreement details

if no transaction is made yet under that PPA.

But the PPA can be enabled/disabled using the anytime toggle button provided if there are

transactions made under it. However, the user will not be able to edit the greyed-out fields such as

Agreement Date, Instalment Amount and End Date.

View Transactions:

This screen will display the list of ledger transactions and the instalment amounts made under a

PPA. It acts as a PPA tracker which also displays PPA details, PPA Status, Total Agreement Amount

and Outstanding Balance.



There are 3 Statuses for a PPA:

1) Created: When a PPA is created, the status will be in created status. The status is

displayed as a yellow icon.

2) In Progress: When a transaction is made for a PPA and Outstanding Balance is greater

than 0.00 then status will change to In Progress mode. The status is displayed as a green icon.

3) Complete: If the Outstanding Balance is less than or equal to 0.00 then status will be

changed to Completed. The status is displayed as an orange icon.

From the List PPA screen, only the PPAs that are in status “Created” can be deleted, that too only

one at a time.

Patient Ledger

Currently, we are supporting PPA only in the patient level ledger transaction screen. The user can

add PPA transaction from patient ledger by choosing the transaction types marked as Allow PPA.

A PPA drop down field will appear on Add Transaction screen when “Allow PPA” is enabled for the

transaction type. The PPAs which are completed and/or disabled will not be listed in this dropdown.

The user can select the appropriate PPA name with ID from the drop down when the payment

transaction is made from the screen,



Note: When the PPA is selected from the dropdown an alert will be shown on the screen that a PPA

is selected.

Once the transaction is made after choosing PPA, the user will not be allowed to change the

selected PPA from the Edit Transaction screen.

3) [Ticket # 11026] MDR: Patient Demographics Enhancement | Patient

Alternate Address and Employment Status

There was a request for a feature enhancement in the Patient Demographics window. The clinic

requested us to add Patient Alternate Address details and new options in the Employment Status

drop down.

In Employment Status, three new options are introduced -

1) Part-Time Employed

2) Self-Employed

3) Retired

Note: The option “Employed” status is now renamed as “Full-Time Employed” in the dropdown.



A new toggle button is introduced in the Address section of the Patient Demographics screen to

switch between main address and alternate address. By default, the “Main” address of the patient

will be shown on screen. The user can switch the toggle button for alternate address and the

alternate address details will be shown on screen.

The new address fields introduced in the alternate address tab are-

1) Alternate Address1

2) Alternate Address2

3) Alternate City

4) Alternate State

5) Alternate Zip

The employment status and Alternate address details are supported in the following modules.

1) Inbound Patient XML - eCPPatientDMGListener (Soap Webservice)

2) Patient Add/Edit (UI)

3) Patient Import (csv/xml)

4) Patient Export (csv/xml)

5) Import/Export CSV Map Configuration (from Admin)

6) Outbound Patient XML

7) Patient Lookup (only employment status changes)



8) Patient Refresh (only employment status changes)

9) ESB (only employment status changes)

10) Enrich Thin Claims (only employment status changes)

11) Persist DMG (only employment status changes)

The XML payload changes are:

NEW VARIABLES

<xs:element ref="patientAlternateAddress1" minOccurs="0" maxOccurs="1" />

<xs:element ref="patientAlternateAddress2" minOccurs="0" maxOccurs="1" />

<xs:element ref="patientAlternateCity" minOccurs="0" maxOccurs="1" />

<xs:element ref="patientAlternateState" minOccurs="0" maxOccurs="1" />

<xs:element ref="patientAlternateZip" minOccurs="0" maxOccurs="1" />

<xs:element name="patientAlternateAddress1" type="xs:string" />

<xs:element name="patientAlternateAddress2" type="xs:string" />

<xs:element name="patientAlternateCity" type="xs:string" />

<xs:element name="patientAlternateState" type="xs:string" />

<xs:element name="patientAlternateZip" type="xs:string" />

EXISTING VARIABLE – ADDITIONAL OPTIONS ADDED AS ALLOWED VALUES

<xs:element ref="patientEmploymentStatus" minOccurs="0" maxOccurs="1" />

<xs:element name="patientEmploymentStatus">

<xs:simpleType>

<xs:restriction base="xs:string">

<xs:enumeration value="E" /> 

<xs:enumeration value="PE" /> 

<xs:enumeration value="SE" /> 

<xs:enumeration value="RE" /> 

<xs:enumeration value="F" /> 

<xs:enumeration value="P" /> 

<xs:enumeration value="" /> 

</xs:restriction>

</xs:simpleType>

</xs:element>

The Patient Payload XML Schema for both inbound and outbound will be provided on demand.

The schema changes are backward compatible, and the patient payload used in the previous

version will continue to work with the new schema file.

There are no corresponding changes in the claim schema file or claim payload/fields. The newly

added options in the patient employment status will be now mapped like this.

Patient Employment

Status (DMG

Employment

Dropdown

(Claim)

Student

Dropdown

(Claim)

Employed (E) Yes Select/Empty Existing Map

Full Time Student (F) No Full Time Existing Map

Part Time Student

(P)

Yes Part Time Existing Map

Self Employed (SE) Yes Select/Empty New Map



Part Time Employed

(P)

Yes Part Time New Map

Retired (RE) No Select/Empty New Map

4) [Ticket # 11182] iTech: Admin Module | Process - Manual Trigger | UI

Improvements

Previously, in v4.9 release a trigger button “Account cache for claim validation” was introduced in

the admin module to manually trigger the caching. Due to the addition of more triggers and the

process trigger screen got crowded and was confusing to the portal administrators. Hence, we

have changed the UI of the Automatic Processes screen by introducing new icons for better

presentation and ease of use.

This is available under Admin>>Process>>Automated>>Trigger.

5) [Ticket # 11237] MDR: Account Feature Settings - Populate default claim

fields in New Claim Form (Prof/Inst)

There was a request for a new feature enhancement in the UB04 claim form. The clinic asked us

to default few of the commonly used fields in professional and institutional from new primary claim

screen. both Practice and Admin module. These fields can be configured under Maintenance >>

Feature Settings >> Claim >> Institutional from both practice login and admin login. The clinic can

default the values as per their choice, so that while they create a new primary UB04 claim the

chosen default values will be auto populated from the feature settings.



The “Default UB Facility Type” and “Default UB Service Lines Count” are existing settings.

Additionally, we have introduced,

1) Default UB Insurance Program

2) Default UB Admission Type

3) Default UB Admission Source and

4) Default UB Patient Status Code

in the Institutional feature settings screen.

The default values chosen in the settings screen will appear in the New Primary Institutional claim

form. When the claims are cloned to new primary claim screen, the following default values will

be populated in the new claim screen, but will be over written by the values in the source claim.

By default, the UB Frequency Code will be "2” and the UB service Lines Count will be “10”in feature

settings drop down. The Type of Bill will be shown as a read only value which is a combination of

“0 + UB Facility Type + UB Frequency Code” in the settings.

As we introduced “Default UB Insurance Program” in New Primary UB Claim Default, a new

configuration Default HCFA Insurance Program is introduced in the feature settings for

Professional claims in both Practice and Admin module. This configuration is available under

Maintenance >> Feature Settings >> Claim >>Professional.

The feature settings for claim is now categorized into General, Professional and Institutional for

both PHD and Non-PHD accounts.

General – The existing feature setting configurations “Show Clone Option” and “Default Sort

Order” which are common for professional and institutional claim are available under this option.



6) [Ticket # 11240] PH: AR Summary Report – Enhancement - Monthly, Half-

Yearly, Yearly options

One of the clients requested us for a new feature enhancement in the AR Aging report. The clinic

wants us to add new type of period in the date filters for a given year. In this version, we have

introduced new Type of filters such as Monthly, Half Yearly and Yearly in the AR Aging report for

report type - Default (For Public Health and Non-Public Health) and By Program List (for Public

Health only). Previously, our system was designed to support the date range filter only on quarterly

basis. From this version, the report is enhanced to have above mentioned date range filters.

1) Fiscal year - The filter name “year” is changed to Fiscal Year. This will have the current Fiscal

year selected by default. The default is based on the default fiscal year start month configured

in the account feature settings. The user can choose the appropriate fiscal year from the drop

down.

2) Type – This filter will have four drop-down option namely Monthly, Quarterly, Half-Yearly and

Yearly. By default, Quarterly will be selected.

In the sub drop down, the user must select appropriate quarter, month, half year or year. Based

on the type of period selected, all twelve months, all four quarters, both half years and year will

be shown. By default, current month, quarter, half year or year will be selected.

Monthly

Below shows the monthly Default AR Aging Report.



Half Yearly

Below shows the Half yearly Default AR Aging Report.



Yearly

7) [Ticket # 11248] MDR: Manage Reporting Procedure Codes + Show/Hide

Option in Patient Statements

One of the clients requested us to have a new feature enhancement in the Patient Statement

settings screen. They wanted to exclude Reporting Procedure Codes while printing patient

statements to save paper while printing. Hence, we have introduced a new screen to manage the

Reporting Code List in the practice module under maintenance tab for both PHD and Non PHD

accounts. This is available under Maintenance >> Reporting Code List > List. This screen will

display the Reporting Code, Description, Created Date and Updated Date.

Admin Module

The Reporting Code List access is available to the operators/users under a practice account based

on the privileges configured by the administrator under user role settings or custom operator

privilege settings. This is available under Admin >> Maintenance >> User Roles >> Add new User

Role/Edit User Role >> Reporting Code List.



View Only - If checked, then user will not be able to add, edit and delete the Reporting Code List.

When view only option is enabled, the add, edit and delete will be disabled.

Add- If checked, then user will be able to add a new Reporting Code to the List.

Edit - If checked, then user will be able to edit/update the existing Reporting Code to the List.

Delete - If checked, then user will be able to delete the selected Reporting Code from the List.

Practice Module

The users can search the reporting code using filters such as Code, Description and Sort by. The

Code and Description filter has a text field with sub filter options such as Equals, start with, End

with and contains. The Sort filter will sort the code list based on the Created Date or Procedure

Code in Descending or Ascending order.

The user can Add, Edit and Delete a Reporting code based on the privileges set by admin for each

practice account.

1) Add New- The user can add new Report Procedure code to the list by entering the code

and short description from the Add new option and save them. The system will display a

confirmation message on screen after duplicate check.

2) Edit Report Procedure Code - The user can edit the Report Procedure code by updating

the code and description from the Edit option and save them. The Edit Report Procedure

code screen will display the Created by, Created Date, Last updated by and Last Updated

Date. The system will display a confirmation message for updating the report procedure

code to the list “Are you sure you want to update?”, On clicking yes, a confirmation

message will be displayed on screen after the duplicate check is passed.



3) Delete – The user can select delete report procedure code by selecting them from the list.

The system will display a confirmation message to delete the selected code from the list

“Are you sure you want to delete the selected code(s)?”, On clicking Ok, a confirmation

message will be displayed on screen.

The user can print the Reporting Code List from the Print option and export it to PDF.

Patient Statement Settings

A new flag “Exclude services with reporting codes” is introduced in the Patient statement settings

screen for single and bulk patient statements.

The “Exclude services with reporting codes” flag is based on the following criteria:

1.) The “Exclude services with reporting codes” flag will appear only if “Show Service Lines” flag is

checked.

2.) By default, the “Exclude services with reporting codes” flag will be unchecked and will not

exclude any reporting procedure codes in the patient statement.



3.) When a user checks the "Exclude services with reporting codes" flag, it will exclude all the

reporting procedure codes that are available in Reporting Code List screen when service line

details are printed on patient statement.

4.) The “Exclude services with reporting codes” flag will be hidden like the Show Procedure Code

and Show Procedure Code Description code check box when the Show Service Lines” flag is

unchecked.

Single Patient Statement

A new flag "Exclude services with reporting codes" is introduced in the create single patient

statement screen. By default, it will be unchecked and appear only if Show Service Lines flag is

checked.

This configuration saved in patient statement settings can be overridden on the fly from the above

screen before creating the statement.

Create Bulk Patient Statement

A new flag "Exclude services with reporting codes" is introduced in the create bulk patient

statement screen. By default, it will be unchecked and appear only if Show Service Lines flag is

checked.

This configuration saved in patient statement settings can be overridden on the fly from the above

screen before creating the statement.

Manage Patient Statement

The flag "Exclude services with reporting codes" is displayed with value (Yes/No) in the Additional

Information screen based on the criteria chosen for Task View, File View and Patient View.



8) [Ticket # 11354] PH: Transunion Secure FTP Connection issue |

Transmission Library Upgrade and Module Changes

One of the clients had reported an issue with the eligibility batch inquiries are not responded by

the payer. It was noticed that while sending bundled IEV batches (270 files), the system was

unable to upload files using Secure FTP automatically to TransUnion and hence the inquiries did

not reach the payer to respond. There was a connection issue between eMB and the Secure FTP

server due to an outdated SFTP File Transfer library we use. The library is now updated with the

latest version and the SFTP Connection logic is changed as per the new library API to fix this issue.

Please this is happening only while connecting to Transunion and not any other clearinghouses.

Note: The 270 batches which failed to upload are currently shipped to Transunion manually by

iTech support team

9) [Ticket # 11430] PH: Ledger: Generate Receipt fails to print due to

carriage return/line feed in transaction notes

One of the clinics were unable to generate a ledger transaction receipt due to line breaks in the

transaction notes. When the user was trying to generate receipt for patients having transaction

notes with carriage return/line feed characters, the Generate Receipt module failed to print the

Ledger Transaction Receipt. This issue is fixed.

Also, the user can generate receipt having transaction notes with carriage return/line feeds from

patient ledger and print them from the following ledger screens - patient level and claim level

(Single/multiple), Debt Set Off, Posting >> Manage and Posting screen - Semi-Auto SFS

adjustment transaction, Ledger opened using Web API.

10) [Ticket # 11466] MDR2: New Claim (Prof/Inst) - Pre-configure practice,

provider, and facility details

There was a request for a new feature enhancement in the New Primary Professional and New

Primary Institutional Claim forms. The clinic asked us to default the Billing Provider, Service

Facility, Rendering Provider and Serviced By fields for New Primary Professional claims. And also,

the Billing Provider, Service Facility, Rendering Provider, Serviced By, Attending Provider and

Operating Provider for New Primary Institutional claims.

The configuration of these fields is added in the feature settings for Professional and Institutional

claims. This can be configured from both Practice and Admin module in both PHD and Non PHD

accounts and is available under Maintenance >> Feature Settings >> Claim >>

Professional/Institutional. The clinic can default the values as per their choice, so while creating



a new primary HCFA 1500/UB04 claim the chosen default values will be auto populated from the

feature settings.

1) Professional – This feature setting is for Professional claim forms. The “Default HCFA Service

Lines Count” is an existing feature. In this requirement, we have introduced Billing Provider,

Service Facility, Rendering Provider and Serviced By fields to the Professional claim feature

settings screen. The clinic can select the option for the above fields and save the settings. The

default values chosen will be auto populated in the new Primary Professional claim form.

a) Billing Provider - The Billing Provider will have a “look up” drop down with fields such as “Name,

Address1, Address2, City, State, Zip, NPI, Tax ID and Taxonomy Code”.

The user can configure the default practice/billing provider details to be populated in the billing

provider section of the claim when a new primary professional claim form is opened from the

menu. At least “Name, Tax ID, and NPI” must be configured to successfully save the default

configuration. If Tax ID Type is not configured, EIN will be assumed and saved. The user can leave

it empty if he/she do not want to save as default. If billing provider is not configured here, the new

claim screen will populate the primary practice/billing provider details in the billing provider

section (existing behavior retained for backward compatibility).

b) Service Facility – The Service Facility will have a “look up” drop down with fields such as “Name,

Address1, Address2, City, State, Zip and NPI”.



The user can configure the default service facility details to be populated in the service facility

section of the claim when a new primary professional claim form is opened from the menu. At

least the “Name” must be configured to successfully save the default configuration. The user can

leave it empty if he/she do not want to save a default.

c) Rendering Provider - The Rendering Provider will have a “lookup” drop down with fields such as

“First Name, Middle Name, Last Name, NPI and Taxonomy Code”.

The user can configure the default rendering provider details to be populated in the rendering


menu. At least “First Name, Last Name and NPI” must be configured to successfully save the

default configuration. The user can leave it empty if he/she do not want to save a default.

d) Serviced By – The Service By will have a “lookup” drop down with fields such as “First Name,

Middle Name, Last Name and NPI”.

The user can configure the default serviced by provider details to be populated in the serviced by


menu. At least “First Name and Last Name” must be configured to successfully save the default

configuration. The user can leave it empty if he/she do not want to save a default.



2) Institutional - This feature setting is for Institutional claim forms. The “Default UB Service Lines

Count” is an existing feature. In this version, we have introduced Billing Provider, Service

Facility, Rendering Provider, Serviced By, Attending Provider and Operating Provider fields to

the Institutional claim feature settings screen. The clinic can select the option for the above

fields and save the settings. The default values chosen will be auto populated in the new

Primary Institutional claim form.

a) Billing Provider - The Billing Provider will have a “look up” drop down with fields such as “Name,

Address1, Address2, City, State, Zip, NPI, Tax ID and Taxonomy Code”.

The user can configure the default practice/billing provider details to be populated in the billing

provider section of the claim when a new primary institutional claim form is opened from the

menu. At least “Name, Tax ID, and NPI” must be configured to successfully save the default

configuration. If Tax ID Type is not configured, EIN will be assumed and saved. The user can leave

it empty if he/she do not want to save as default. If billing provider is not configured here, the new

claim screen will populate the primary practice/billing provider details in the billing provider

section (existing behavior retained for backward compatibility).



b) Service Facility – The Service Facility will have a “look up” drop down with fields such as “Name,

Address1, Address2, City, State, Zip and NPI”.

The user can configure the default service facility details to be populated in the service facility

section of the claim when a new primary institutional claim form is opened from the menu. At least

the “Name” must be configured to successfully save the default configuration. The user can leave

it empty if he/she do not want to save as default.

c) Rendering Provider – The Rendering Provider will have a “look up” drop down with fields such

as “First Name, Middle Name, Last Name, NPI and Taxonomy Code”.

The user can configure the default rendering provider details to be populated in the rendering


menu. At least First Name, Last Name and NPI must be configured to successfully save the default

configuration. The user can leave it empty if he/she do not want to save as default.



d) Serviced By – The Serviced By will have a “lookup” drop down with fields such as “First Name,

Middle Name, Last Name and NPI”.

The user can configure the default serviced by provider details to be populated in the serviced by


menu. At least “First Name and Last Name” must be configured to successfully save the default

configuration. The user can leave it empty if he/she do not want to save as default.

e) Attending Provider – The Attending Provider will have a “lookup” drop down with fields such as

“Name, Address1, Address2, City, State, Zip, NPI and Taxonomy Code”.

The user can configure the default attending provider details to be populated in the attending



default configuration. The user can leave it empty if he/she do not want to save as default.

f) Operating Provider – The Operating Provider will have a “lookup” drop down with fields such as

“First Name, Middle Name, Last Name and NPI”.

The user can configure the default operating provider details to be populated in the operating



default configuration. The user can leave it empty if he/she do not want to save as default.



Note: When a claim is cloned and opened in new claim screen, the default saved feature settings

will be pre-populated in the new claim, but will be overwritten by the information in the source

claim.

11) [Ticket # 11476] MDR: UB04 Claims - Medical Record Number not

getting saved

One of the clients had reported an issue with the Medical Record Number not being saved in the

UB04 claim form Box 3b. It was noticed that MRN went missing when the claim was

resubmitted/saved back after opening in edit mode.

This issue was happening because the MRN was not there in update claim query for institutional

claims when claim is edited and submitted. However, the MRN was getting saved when a new

claim is created and submitted. This issue is fixed now.

12) [Ticket #11539] PH: Patient Eligibility History Window | Show more

information/New Columns

There was a request for a new feature enhancement in the Patient Eligibility History window. The

clinic had asked us to remove the DOS, Procedure Code Modifier and Procedure Code columns

as the inquiries were not done based on Procedure codes and introduce Insurance Type

(Primary/Secondary), Payer ID and Payer Name. This is done as shown in new eligibility history

screen provided below. This screen is available under Patient >> Eligibility status >> Patient

Eligibility History window or can be accessed or Web API.

13) [Ticket # 11541] PH: Posting - Ability to see more claims in the batch,

Enhanced Search Claim Filters/Sort Options

One of the clients requested us to have a feature enhancement in the Posting Batch screen. They

want to see all the claims listed for a batch in a single page. Hence, we have introduced a new



option Records Per Page at the bottom of the “Claims for Batch” screen. The Records Per Page

will have four drop-down options such as 10, 20, 50 and 100. By default, the Records Per Page

will be displayed as “10”. The clinic can choose the no of claims to be displayed in single page

from the drop down. The no of records chosen per page will be dynamically synchronised with the

list of claims in the first page when the user moved to other pages. And also, the “Go” to Page

option work in sync with the Records Per Page option.

Also, new filters are introduced to the Add new search claims screen for adding claims to manual

Batch in the posting module.

1) Payer ID – This is an existing filter with a text field. In this version we have introduced two

drop-down options IN and NOT in the Payer ID filter. This filter will support multiple payer IDs

with comma separated values. By default, the Payer ID filter will be selected as” IN”.

2) Payer Name - This is an existing filter with a text field. We have introduced four drop-down

options Starts With, Contains, Equals and Ends with in the Payer Name filter. By default, the

Payer Name filter will be selected as “Starts with”.

3) Claim Closure Status – We have introduced this new filter in Add search claims screen and

will have three drop-down options such as All, Opened and Closed. By default, Claim Closure

filter will be selected as “Opened”.

4) Sort By – This new Sort option is introduced with five dropdowns such as Claim Received date,

Date of Service, Patient First Name, Patient Last Name and Payer ID. The user can sort it by

Descending or Ascending order. By default, Sort By filter will be selected as “Claim Received

Date in “Descending” order.

We have introduced a new column Payer ID in the Add search claims result screen. The column

name “Carrier” and “Other carrier” is replaced with Payer Name and Other Payer, respectively.



14) [Ticket #11542] MDR + iTech Internal: Appointment Report

Enhancements

As per the client request, we have introduced two new filters Appointment Created Date and

Appointment ID in the Appointment Detail Report search screen. The Appointment created date is

added under the existing date filters and the Appointment ID separately as a text filter. This is

available under Reports >> Appointment >> Detail.

Additionally, we have introduced Appointment Created Date column next to Appointment Date

column in the Appointment Detail Report.



15) [Ticket #11548] PH: Enhancement - DOS column on Claim Screen

under Posting Batch

One of the clients requested us to add a new feature in the Batch List screen of the Posting

module. The clinic asked us to add DOS (Date of Service) column in the posting batch screen.

Hence, we have introduced “DOS” column next to Patient Name in the Posting Batch screen. Also,

the “DOS” column is also available in the Print Preview screen which can be exported to PDF.

“DOS” in the Print Posted Claim Search Report screen.

16) [Ticket #11549] PH: Enhancement | New Filter “Under Aged” in Aging

Reports

There was a request for a feature enhancement in the Aging report - to add new option to filter the

“Under Aged” patients at the time of service. Hence, we have introduced the filter Under Age and

Show Patient Age (as on DOS) filter with a check box in the Aging report search screens. By default,

these options will be unchecked. The clinic can enable the Under Age option to fetch the Aging

report for patients below 18 years of age and enable the “Show Patient Age (as on DOS)” to display

the “Patient Age” column in the report.

The Under Age filter is introduced in the following search screens:

1) Aging by Program by Payer - Insurance Claims

a) Summary – Default/Periodic

b) Detail - Default/Periodic

2) Aging by Program by Payer – Self Pay Claims

a) Summary – Default/Periodic

b) Detail - Default/Periodic

The Show Patient Age (as on DOS) is introduced in the following search screens:



1) Aging by Program by Payer - Insurance Claims

• Detail - Default/Periodic

2) Aging by Program by Payer – Self Pay Claims

• Detail - Default/Periodic

The Under Age filter will fetch records of all patient who age is <18. The age calculation logic is

based on Patient DOB against the Date of Service in the claim (Patient Age = "DOS - Patient DOB”)

By default, the “Show Patient Age (as on DOS)” option will be unchecked. The user can enable the

check box to display the “Patient Age” column in the Detail report and the print page.



17) [Ticket #11572] MDR: Batch Error - Claims Created through ESB giving

error while posting

One of clients reported this issue in the Posting module for batch claims created through ESB.

When an operator creates a claim through ESB, the claims in the posting module was giving an

error. This issue was happening because the User Key in the claim table which was expected to

carry Practice Account User Key was having User Key of the operator who created the claim from

ESB. This was creating problems while posting and the user was not able to save the posting. A

database exception was found caused by wrong column key used. This is fixed in this version now.



18) [Ticket #11585] PH: Enhancement - Age Group Filter in Revenue Board

Report

One of the clients requested us for a new feature enhancement in the Revenue Board report. The

clinic asked us to add “Age group” filter in Revenue Board report. A new filter “Age group is

introduced for both report type – Summary and Detail. The Age Group filter will display a list of age

criteria between the range. The range of the age selected is inclusive of the start and end value

age values.

The Age Group filter will have the following age criteria -

All, <1, 0-18, 1, 1-6, 2, 3-4, 3-5, 5, 6, 6-9, 7-10, 7-18, 10-14, 11-12, 13-18, 15-19, <18, 19-24,

20-24, 25-44, 45-64, 65+ and Custom.

By default, the Age Group filter will display “All”. The user can select the age group from the list

and fetch the report based on the criteria chosen. The patient age calculation logic is based on

the Patient DOB on the date of service (Patient Age = DOS - Patient DOB).

The custom age group will have sub filters such as Equals, Greater than, Less than and Between

with a text field. The user can customize the age criteria by selecting the sub filter with the age

entered in the text field. The text field is allowed to have up to 3-digit numeric values. The custom

age value is restricted for more than 3 digits.



The Revenue Board Detail report will have the “Age Group” filter with the custom sub filters. Also,

a new option Show Patient Age (as on DOS) is introduced to show the Patient age in the Revenue

Board Detail report. By default, this option will be unchecked. The user can enable the check box

to display the “Patient Age” column in the Revenue Board Detail report and the print page.

Below shows the sample Revenue Board Detail report with the Patient Age as on DOS and Age

group.

19) [Ticket # 11629] MDR: Anesthesia claims support in ESB

There was a request for a new enhancement in the ESB claim form. The clinic asked us to add

anesthesia time field in the ESB claim form. Hence, a new field "Anesthesia” is introduced with



the “Start and Stop" time under each service line in the ESB claim form. The anesthesia Start and

Stop time will be displayed in “Hours-Minutes” format.

When an ESB is submitted, the anesthesia Start and Stop time is validated on the following button

options:

1) Save - The "Anesthesia Start and Stop" time will not be validated when the ESB is saved.

2) Save + Mark as Completed- The "Anesthesia Start and Stop" time will be validated when the

ESB is saved & Marked as Completed.

Print ESB

If the ESB/Claim has Anesthesia timings specified, the "Anesthesia Start and Stop" column will

display the timing on the print page.

If the ESB/Claim has no Anesthesia timings the "Anesthesia Start and Stop" column will be shown

empty on the print page.

The "Anesthesia Start and Stop" timings are validated using the following rule:

1) The Anesthesia Start/Stop field must have valid 4digit time format in "hhmm". If the format is

incorrect, a message Invalid Anesthesia Start/Stop time will be shown.

2) The Start time must be lesser than the Stop time, else a message Anesthesia Start Time is

greater than Stop Time will be shown.

When the ESB is submitted as claim, the anesthesia time will be carried forward to the

professional claim screen/database.

20) [Ticket #11630] MDR: ESB Enhancement - Sync Hospitalization Date

with the Date of Service

One of the clients requested us for a new feature enhancement in the ESB claim form. The clinic

asked for synchronization of DOS with the Hospitalization date. Hence, we have introduced a new

synchronization icon with the “Hospitalization Dates for Current Services” field. This icon will



synchronize/populate the Date of Service from the Hospitalization Date. When this icon is clicked,

the DOS will be populated in the service line section based on the Hospitalization Date specified

in the ESB

The Hospitalization Date fields will be taken for synchronization based on the following conditions:

1) The hospitalization “From” and “To” date should be present.

2) The hospitalization “From” and “To” date format should be Valid.

3) The hospitalization “From” date is earlier or same as “To" date.

The Date of Service fields will be synchronized only if:

1) Both the “From” and “To” Date of service field is empty.

2) At least one other field in the service line section must be populated with values to synchronize

DOS.

21) [Ticket #11631] MDR: Clear option to clear payer information in

patient demographics

There was a request for a new feature enhancement in the Patient Demographics tab. The clinic

asked us to add “Clear” button in the Insurance tabs. Hence, we have introduced a new “Clear”

button under the Primary, secondary and Tertiary tabs separately in the Patient Demographics

screen. This “clear” button will erase all data in the payer fields in the respective tabs.

By default, in Primary Insurance tab the “Clear” button will appear under Prof Payer, Inst Payer

and Eligibility Payer. If “Self-Pay Patient” is checked, the “Clear” button will not appear in the Prof

payer and Inst Payer tab as the payer information is read-only, but will appear under Eligibility

Payer tab.

The “Clear” button will appear for Prof Payer, Inst Payer, Eligibility Payer under Secondary and

Tertiary insurance tabs.



22) [Ticket #11634] iTech: External Pay - Change in logic to call Rest API

when locally hosted

A new logic is introduced to call the Rest API by skipping SSL if External Pay is hosted locally and

not remotely on another server/domain. A remote flag is added in the External Pay properties file

to identify where the External Pay is hosted. hosted server is SSL certified.

expEDIumPay.host.location.remote

The allowed values are 0, and 1.

The properties file will carry the value 0 by default as installation default. (The program default is

1)

If the value is 1, it means the External Pay microservice is hosted remotely. The system will directly

go and connect to the app hosted over SSL

If the value is 0, it means the External Pay microservice is hosted locally, and it should go through

a custom code snippet which will bypass SSL Verification to avoid certificate error.

If any other value other than 0 and 1 are configured, the system will consider it as 1, the program

default (remotely hosted)

23) [Ticket #11649] PH: Posting Batch Enhancement – Allow longer batch

name (60 char) and enhance batch notes filter

One of the clients requested us for a new feature enhancement in the “Batch Name” field and

“Batch Notes” filter. The clinic asked us to extend the length of “Batch Name” and add filter to the

“Batch Notes”.

In this version, we have extended the length of batch name text field from 25 characters to 60

characters in the Create Batch screen and the Edit Batch details screen. The user can

create/modify a Batch Name with up to 60 characters of length in the text field.

If the length of the Batch Name is more than 30 characters, the Batch Name in the Batch list

column will be shown with a suffix of three dots after 30 characters. Also, a mouse hover is

introduced in the Batch List screen on batch name row to view the full Batch Name. Previously,

the mouse hover was only displaying Full Batch Notes in the Batch List screen. Now, both Batch

Name and Batch Notes will be shown when the mouse is hovered.



In this version, a new sub filter is introduced in the “Batch Notes” filter in the Batch/Claim search

screen. This is available under Posting >> Manage >> Batch/Claim search >> Batch Notes. The

Batch Notes contain filters such as Equals, starts with, Contains and Ends with. By default, the

filter will be chosen as “contains”. The user can choose the criteria with the text and search for

Batch notes.

24) [Ticket #11652] PH: Close Button and Corner Close Icon are not

appearing on Eligibility History Window when opened from claim screen

One of the clients reported an issue in the Eligibility History window. The “close” button and “close”

icon at the right corner was not appearing on the Eligibility History window from the claim screen.

However, when the Eligibility History window was opened for the first time, the close icon appeared

at the top right corner of the window and while refreshing the claim screen, the close icon

disappeared. Due to this, the user was unable to close the Eligibility History window. This issue

was happening when eMB claims screens are opened in multiple tabs by the same user. There

was a conflict between the eligibility history windows opened from EMR over Web API (using a Web



API flag) and the eligibility history window opened eMB Screen when opened in different tabs and

refreshed.

This flag fetching logic on these conflicting screens is enhanced to work in a multi-tab scenario

now. The issues are resolved from the following modules, and the close button and icon will always

appear when the eligibility history window is opened from eMB pages directly.

1) Claims

a) Add/Edit/Clone/View Primary Professional

b) Add/Edit/Clone/View Secondary Professional

c) Add/Edit/Clone/View Primary Institutional

d) Add/Edit/Clone/View Secondary Institutional

2) Patient

a) Eligibility >> Batches

b) Eligibility >> Inquiries

3) Appointments

a) Agenda View

25) [Ticket #11665] iTech: Disable Transaction Amount | Multi-Claim

Online Payment - By Claims, By SFS Program

In this version, we have disabled the “Amount” field for online payment transactions in the Patient

Balance Summary - By Claims and Patient Balance Summary - By SFS Program screen. The claim

balance for each claim is displayed as the transaction amount.

As per the design, we when multiple claims are selected for making single online payment

transaction, the amount field should be disabled, and user should not be able to make changes

to each claim balance.



26) [Ticket #11682] iTech | Quick sanity testing the Manager module

required

The manager module functionalities are tested and approved as of this version (v5.1), to prepare

the system to have any future enhancements in manager module.

27) [Ticket #11686] iTech: Edit Ledger Transaction Window - SFS Program

should not be editable

There were issues with the SFS program drop down in Edit Transaction ledger window when the

program in the claim/claim ledger is not available in the state specific SFS Program Lookup table.

These issues are now resolved.

1) When the transaction is opened in edit mode from claim ledger, only the SFS Program Abbr.

with a hyphen as a read only label is appearing without SFS Program Name.

Fix: This is fixed to display the SFS Program Abbreviation and SFS Program Name

2) When the transaction is opened in edit mode from Patient Ledger, the SFS Program dropdown

is appearing with the entry "Select" with no SFS Program selected

Fix: The following fixes are done -

a) If Patient level transaction is opened in edit mode, and SFS Program Abbr. is not available

(removed) in the ledger from the ledger master, then the SFS Program dropdown will show

as “Select”. The user can choose the program from dropdown before updating the

transaction.

b) If Patient level transaction is opened in edit mode, and SFS program Abbr. is disabled from

"Patient demographics --> SFS tab”, then we will be populating that SFS Program Abbr.

selected as the first option in the dropdown with red color (indicating that this entry is an

odd item in the list as the list always show the programs enabled/enrolled for the patient).



c) If Claim level transaction is opened in edit mode on claim ledger, and SFS Program is not

available (removed) in the ledger master, then we will be populating empty value for the

SFS Program Abbr. label in the edit transaction window. Also, when the transaction is

updated, the system will be validating this as a mandatory field and report error. The client

shall report these issues to support personnel as it requires analysis and surgical

corrections.

d) If Claim level transaction is opened in edit mode on claim ledger, and SFS Program is

disabled from "Patient demographics --> SFS tab”, then the system will be populating that

SFS Program Abbr. in the SFS Program Abbr. label in edit transaction window as read-only.

e) If Claim level transaction is opened in edit mode on patient ledger, and SFS Program is

not available (removed) in the ledger master, then the system will be populating empty

value for the SFS Program Abbr. Also, when the transaction is updated, the system will be

validating this as a mandatory field and report error. The client shall report these issues

to support personnel as it requires analysis and surgical corrections.

f) If Claim level transaction is opened in edit mode on patient ledger, and SFS Program is

disabled from "Patient demographics --> SFS tab, then the system will be populating that

SFS Program Abbr. in the SFS Program Abbr. label in edit transaction window as read-only.

28) [Ticket #11714] PH: Revenue Board Report | Self Pay Claims - Patient

Payment Amount is shown in Insurance Payment Amount wrongly

In Revenue Board report, for insurance claims, the insurance payment amount was always taken

from the ledger payment columns for the transaction types

a) Primary Insurance Payment (Auto)

b) Secondary Insurance Payment (Auto)

c) Primary Insurance Payment (Manual)

d) Secondary Insurance Payment (Manual)

The patient paid amount is fetched separately from the transaction entries which are marked as

“Patient Payment”

For the Self Pay claims, we had a wrong query to fetch the insurance amount from ledger payment

column all the time without any conditions. This was fetching the patient paid amount and all other

payment/credit transaction amounts and is getting populated as insurance payment amount. This

is now fixed.

We used the same insurance payment amount query used for insurance claims itself for Self-Pay

claims, so that it returns zero almost always. If there are cases where it returns a non-zero value,

it should be a genuine case of a Self-Pay claim having posting info (if it was previously submitted

as an insurance claim).



29) [Ticket #11715] PH: Medicaid Claims by RA Date report - Shows

inaccurate claim count and check amount

In this report, the following logic was used to detect Medicaid primary claims –

Insurance Type = Primary

AND

Insurance Program Name (Box 1) = Medicaid

The claims in question were not having Box 1 as “Medicaid” and was having “Other” and were not

appearing in the report.

We enhanced the Medicaid check logic in the report as below to fix the issue

Insurance Type = Primary

AND

Insurance Program Name (Box 1) = Medicaid

OR

Claim Filing Indicator in Claim = MC

OR

Payer Name contains the word Medicaid

OR

Insurance Plan Name contains the word Medicaid



Bugzilla List of tickets # ID Client Ext. Ticket

#

Summary Version

1 10973 MDR Via email MDR: Collection Report | Enhanced Default Report, New Report - By Service Line V5.1

2 10974 PH 33060 PH: Patient Payment Agreements V5.1

3 11026 MDR Via

email/GTM

MDR: Patient Demographics Enhancement | Patient Alternate Address and Employment

Status

V5.1

4 11182 iTech Internal iTech: Admin Module | Process - Manual Trigger | UI Improvements V5.1

5

11237

MDR

Via email MDR: Default Frequency Code as "2 Interim-First Claim" & Box 39a Value Codes & Type of

Bill from 0831 to 0832 on UB04 claims V5.1

6 11240 PH 888131 PH: AR report - To be enhanced to have Yearly and Half yearly date filters. V5.1

7 11248 MDR Via email MDR: Manage Reporting Procedure Codes + Show/Hide Option in Patient Statements V5.1

8 11354 PH 889003 PH: Transunion Secure FTP Connection issue | Transmission Library Upgrade and Module

Changes

V5.1

9 11430 PH 889576 PH: Ledger: Generate Receipt fails to print - CRLF/line break in transaction notes V5.1

10 11466 MDR Via email MDR2: New Claim (Prof/Inst) - Pre-configure practice, provider, and facility details V5.1

11 11476 MDR Via email MDR: UB04 Claims - Medical Record Number not getting saved V5.1

12 11539 PH 890061 PH: IEV Patient History table show more information-FEATURE REQUEST V5.1

13 11541 PH 890074 PH: Ability to see more claims, sort, claims on the Posting Batch screen - FEATURE REQUEST V5.1

14 11542 MDR

iTech

Internal MDR + Itech Internal: NFS in Appointment V5.1

15 11548 PH 889973 PH: Adding a DOS column to posting batch-FEATURE REQUEST V5.1

16 11549 PH 888854 PH: Request to add a filter to Aging Report to filter "Under Aged " patient at the time of

service

V5.1

17 11572 MDR Via email MDR: Batch Error - Claims Created through ESB carry different user key and hence posting

such claims gives error.

V5.1

18 11585 PH 890206 PH: Add Age Groups to Revenue Board Summary and Detailed report V5.1

19 11629 MDR Via email MDR: Anesthesia claims Support in ESB V5.1

20 11630 MDR Via email MDR: NFS-Correlate the Dates for Hospitalization Date with the Date of Service V5.1

21 11631 MDR Via email MDR: "Clear All" option to clear out all Insurance Information - from Patient dmg. V5.1

22 11634 iTech Internal iTech: External Pay - Change in logic to call Rest API locally by skipping SSL V5.1

23 11649 PH 890390 PH: Need longer batch list name -extend the length of Batch Name to 60 Characters and

enhance Batch Notes filter

V5.1

24 11652 PH 890179 PH: Close Button and Corner Close Icon are not appearing on Eligibility History Window

when open from claim screen

V5.1

25 11665 iTech Internal iTech: Disable Transaction Amount | Multi-Claim Online Payment - By Claims, By SFS

Program

V5.1

26 11682 iTech Internal iTech | Quick sanity testing the Manager module required V5.1

27 11686 iTech Internal iTech: Edit Ledger Transaction Window - SFS Program should not be editable V5.1

28 11714 PH 888213 PH: Revenue Board Report | Self Pay Claims - Patient Payment Amount is shown in

Insurance Payment Amount wrongly

V5.1

29 11715 PH 888624 PH: Medicaid Claims by RA Date report - Shows inaccurate claim count and check amount V5.1

*** END OF DOCUMENT ***

Documents

expEDIum Medical Billing v5.1 Release Notes1) [Ticket # 10973] MDR: Collection Report | Enhanced Default Report, New Report - By Service Line One of the clients requested us for a