IntellectTM
IMPORTANT PROGRAM MODIFICATIONS
The following Release Notes include the features and modifications made in the current update. PCS suggests you provide each department a copy of the Release Notes so they are aware of the changes which may affect their department.
In order to be aware of ALL changes in the software, please read all release notes from the version you are currently on through to the version to which you are updating.
Update may include items labeled ATTENTION which will IMMEDIATELY affect Billing and other daily tasks. Please be sure to notify all departments which will be affected.
If you would like to update to the latest version, please click here for authorization forms and instructions.
Effective version 20.10.22
Release Date: October 22, 2020
Registration
FIX Registration --► Regular --►Patient and Registration --► Worker --►Worker
It was reported that when PT DEMO is updated in PCM, the <City> and <State> in Intellect was not updated. The problem has been corrected in this release.
Note: PCM users must be updated to the newest version of PCM.
Charges
FIX Charges --► Modify -- PQRS Report
It was found when users deleted a Diagnosis from an entry that was posted on a previous Entry date, the PQRS report was inserting the diagnosis that was deleted on the report.
As of this release, the PQRS report review is as follows:
· If NO changes are made via Charge/Modify, the program pulls from the RDX.
· If changes are made via Charge/Modify to the Dx codes, Intellect looks at th_primary_dx:
o Delete /Modify updates the th_primary_dx
o Add adds the DX code to All the charges (with that visit#) in th_primary_dx
Billing
NEW Billing --► Tele Com -- Office Ally
Prime Clinical received an email from Office Ally indicating that a new URL will be launched for sftp connection. This change affects any transactions you currently have going back and forth to Office Ally via the OnStaff/Intellect program.
Email from Office Ally:
Office Ally is updating our EFT server. With this change, we are also updating our URL.
Current: ftp.officeally.com
New: ftp10.officeally.com
The new server is currently live. All usernames/passwords have been brought over so no changes need to be made on that end. I do not have a hard cutover date as of right now. I know our team is wanting to move everyone over as quickly as possible.
We knew we were going to be making an update to our server, but I was unaware that the URL would be changing.
We are working on figuring out how to get this information out to all of our SFTP users. We hope to have an answer on this soon.
.
In response to Office Ally's change, this Prime Clinical Systems release includes programming changes to meet the new URL requirements.
NEW Billing --► Tele Com -- Zirmed
Prime Clinical was notified by a client that the Zirmed clearing house made changes to the sftp server. The client also sent us the email from Zirmed stating the deployment date for the new changes was 9/27/2020. For your reference:
From: Waystar Alerts <do-not-reply@waystar.com>
Sent: Thursday, September 24, 2020 9:07 AM
Subject: Action Required: Update SFTP settings by September 27th, 2020 to continue transferring files with Waystar
Action Required: Update SFTP settings by September 27th, 2020 to continue transferring files with Waystar
From: |
Re: |
Post Date: |
Client Support Team |
Action Required: Update SFTP settings by September 27th, 2020 to continue transferring files with Waystar |
09/24/2020 |
An update to your SFTP settings is required to continue transferring files to/from Waystar.
These required changes only apply if you connect to SSH FTP Waystar’s host “sshftp.waystar.com” which is also known as “sshftp.zirmed.com"
Reason for Notice
Please read this notification carefully, as this transition will require changes on your side. If these changes are not made as recommended, there is a high likelihood that your file transfer process will fail.
What you need to do now:
1. Share this notice with your IT team and/or Practice Management (whoever handles your file transfer application)
2. Block time on your IT and/or Practice Management's calendar before September 27th to complete testing using provided test site + instructions
3. On September 27th make the update
Zirmed's change also included a change to the URL that was currently being used. In response to Zirmed's change, this Prime Clinical Systems release includes programming changes to meet the new URL requirements.
NEW Billing --► Tele Com --►Submit Claim --►BOP and GOP
A new segment was added to the ANSI 837P file - CLM REF D9. Note: The REF D9 is already included in the 837I.
To Include this segment in the ANSI 837P, the Utility --►Insurance --►Telecom <Clearing House> field must = N.
This new segment is required when this information is deemed necessary by transmission intermediaries (Automated Clearinghouses, and others) who need to attach their own unique claim number.
TR3 Notes: 1. Although this REF is supplied for transmission intermediaries to
attach their own unique claim number to a claim, 837-recipients are not required under HIPAA to return this number in any HIPAA transaction. Trading partners may voluntarily agree to this interaction if they wish.
597 TR3 Example: REF✽D9✽TJ98UU321~
Schedule
FIX Schedule --► Appointment --►Full Day --►Modify Patient Demographics
In version 20.09.11 and prior, it was reported that when a patient account is locked and a user tried to modify that patients' demographics from the schedule, if the user clicked Modify Insurance they were stuck in an inescapable loop. The problem has been corrected in this release.
Addendum
Appended 10/27/2020
Electronic Billing – (Trizetto)
In the 10.10.22 version, there was an issue with downloading of files via sftp for any clearing house (primarily Trizetto due to changes to their server) where the files appeared to have downloaded and deleted from the folders on the sftp site. However, the files never downloaded but were deleted from the sftp folder(s).
As of 10/27/2020, PCS is using a third party library to do sftp. Because of the Trizetto changes, PCS had to use the new version of the library and found after the issue was reported in the 20.10.22 version the new version of one of their functions was behaving differently than previous versions. This was due to the use of the newer version of the JSCH jar file, which is used for SFTP.