OP 21.2.23 Maintenance Release On-Premise: July 12, 2023 | Cloud: Per email communication
Issue Resolutions
MySQL - Incorrect Person Showing in Contact 1 Column
Previously, the incorrect family contact was showing in the Contact 1 column of the Demographic tab in the DAR, and users were unable to fix the sort order using the Fix Sort # button. This was due to an issue with the Stored Procedure in MySQL DB's.
Now, the contact listed in spot 1 of Family Contacts will display correctly in the Contact 1 column of the Demographic tab in the DAR. Also, if the contacts are not ordered properly, the user can now click Fix Sort # to correct this without incident. If there is legacy data showing the wrong contact, users will have to click Fix Sort # to correct the order and the correct contact will display.
MySQL - Insurance A/R Report Not in Alphabetical Order
Previously, when the following Insurance A/R Reports were selected, and the Show Patient Details radio button was selected, the insurances were not listed in alphabetical order:
- Ins Payer - Ins AR
- Ins Payer- Pat A/R
- Ins Payer- Pat Resp Date A/R
- Ins Payer- Secondary Resp Date A/R
Now, the insurances will display in alphabetical order as desired.
OP 21.2.22 Maintenance Release On-Premise: June 29, 2023 | Cloud: Per email communication
Issue Resolutions
MySQL - Missing Required Demographic Info Pop-up
Previously, when a patient was missing required demographic information and notes were added under Notes/Addl Info, upon clicking Save, a "Dataset not in edit or insert mode" error would appear and the notes would not save.
Now, when a patient has missing required demographic information and you attempt to save notes under Notes/Additional Info, you will get a pop-up informing you of the information missing to update the chart accordingly.
Double Voids Fixed with Revert Patient Responsibility
Previously, on Daysheeted claims, when the patient responsibility transaction line was selected and the Revert Patient Responsibility button was clicked, the voided patient responsibility line was created, but the patient responsibility remained. Once the screen was refreshed, a negative amount displayed because the system had created a "double void". Duplicate voids were also appearing if a crossed out patient responsibility line was selected and the Revert Patient Responsibility button was clicked.
Now, Double Voids will not appear when you select the Patient Responsibility transaction line and click the Revert Patient Responsibility button.
OP 21.2.21 Metadata Only Release On-Premise: June 27, 2023 | Cloud: Per email communication
Issue Resolutions
Immunization Reminder Letters Saving in Patient’s Chart
PLEASE REVIEW these release notes for an important issue resolution.
There was an instance where, if a user generated a batch letter from the vaccine status recall, the complete batch of all the individual patient's letters was subsequently added into one single patient's Document Management center as a disclosure record. This has been resolved, and now any report with more than one patient will no longer be associated with a patient's chart. We have confirmed that this did not result in any misdirected disclosure of data.
In this metadata-only release, a cleanup database script will now be implemented so that reports with more than one patient will no longer be associated with a patient's chart.
OP 21.2.21 Maintenance Release On-Premise: June 22, 2023 | Cloud: Per email communication
Issue Resolutions
Immunization Reminder Letters Saving in Patient’s Chart
There was an instance where, if a user generated a batch letter from the vaccine status recall, the complete batch of all the individual patient's letters was subsequently added into one single patient's Document Management center as a disclosure record. This has been resolved, and now any report with more than one patient will no longer be associated with a patient's chart. We are confirming that this did not result in any misdirected disclosure of data.
MySQL Resolutions
Reverting Patient Responsibility Puts Balance on Insurance Tab in Payments Window
Previously, when reverting patient responsibility on a claim, the balance was remaining as a patient balance in the Payments window. Now, reverting patient responsibility on a claim will correctly remove the balance from the patient and display under the Insurance tab of the Payments window.
Merging Contacts
Previously, when merging two contacts, an error message was displayed and prevented the merge from happening. Now, you can merge two contacts with no issue in MySQL DB.
Charges <30 days Showing in the Appropriate Aging Buckets
Previously, charges < 30 days were showing in the 90+ aging bucket. Now, charges will show in the appropriate aging buckets.
Performance Improved for Admin Documents
Office Practicum has shortened the time it takes to open the Administrative Document repository.
OP 21.2.20 Maintenance Release On-Premise: June 14, 2023 | Cloud: Per email communication
Issue Resolutions
Added Reporting for Status of Delivery for Automated Messages
In order to track the delivery status of PMX+ Automated Messages, we have added a Message Type column in the Messages Sent tab so that users can easily identify an Automated Message from a Personalized Message, when reviewing the delivery status.
OP 21.2.19 Hotfix Release On-Premise: June 12, 2023 | Cloud: Per email communication
Issue Resolutions
Upload and View Documents (MySQL)
A previous release prevented some users from accessing Documents when using Direct S3 credentials. This has been resolved, and users will retain the ability to upload and view documents even if they lack Keycloak access.
This release contains everything included in the 21.2.18 Maintenance Release
Scroll down to the 21.2.18 Release to see all release notes.
OP 21.2.18 Maintenance Release On-Premise: June 12, 2023 | Cloud: Per email communication
Issue Resolutions
Refills coming into OP under 2 different names
Previously, for practices that merged and had their systems migrated from OP to OP, there was an issue where Pharmacies were sending unique IDs from old prescriptions that were no longer valid in your OP due to the merging. This was creating downstream impacts where the incorrect patient was being matched in the incoming refill requests.
OP has put in additional steps where patient matching is being performed on top of ID matching based on the criteria.
Medications (ERX) Prescriptions in a "SENT" status resending automatically according to PM RCOPIA Job Schedule
Previously, every time the Update Status job for Medications was run, the Medication Record was getting updated, and downstream it was creating an Audit Log record every time. This was creating too many logs where the record was not actually getting updated with a new status.
Now, the Audit Records won’t get updated when the job runs with no change in the status.
Texas ImmTrac2 Registry Participants: Ability to Send TX specific Consent Status Values within the VXU PD1-12 field to ImmTrac2
An update has been performed in the Privacy/Consent screen to allow a user to select any of the 3 custom consent codes that ImmTrac2 supports:
- TXA - Consented Adult, >=18 years old
- TXY - Consented ImmTrac Child, <18 years of age
- TXD - Disaster consent
OP 21.2.17 Release On-Premise: June 5, 2023 | Cloud: Per email communication
New/Updated Vaccines
Added Admin CPT Code(s) for new COVID Bivalent Guidelines
With the new guidelines for bivalent-only COVID vaccine series, the AMA also released new ADMIN CPT codes to be utilized, as well as editing the text of some of the existing codes. OP has added in the new codes (0121A, 0141A, 0142A, 0151A, 0171A, 0172A) and updated existing codes (0124A, 0134A, 0144A, 0154A, 0164A, 0173A, 0174A).
Note: In order to expedite providing this information, this release includes only the addition of the relevant codes. Specific billing logic related to the codes is not included.
Added COVID19 MOD BIV 6M-11 To OP Database
We have added a new entry into the Vaccine Code table, COVID19 MOD BIV 6M-11, to represent the recent guideline recommendation changes from the CDC and the FDA. To eliminate confusion, OP recommends practices no longer use the existing COVID19 MOD BIV 6-11 entry in the code table, as the new indications for bivalent dosing now include all the way down to 6 months in the same formulation / dosage.
Updated EUA Fact Sheets for COVID-19 Pfizer, Moderna and Janssen
Updated to the most recent versions of the COVID EUA Fact Sheets for Pfizer, Moderna, and Janssen vaccines as per the CDC recommendations.
Improved Functionality For All Users
New Support Hub Link Updated in OP
The new and improved Support Hub has a new link, which can be accessed in the same place as before: Help > Support Hub.
Automated Messages: Track Message Details in Patient Chart
If you have the new Automated Messages, you can track the message details like who, what and when the message was sent from Messages within a patient Chart.
Improved Functionality for Providers and/or Clinical Staff
Behind the Scenes Pre-Work: Up-to-Date ePrior Auth Status Field
Previously, the ePrior Auth Status field within the ePrior Auth tab on the ePrescribe screen did not properly update to reflect an accurate, up-to-date status of the ePA authorization request sent to a PBM. The required workaround was for you to launch the ePA Worklist in order to view the up-to-date status of the request.
Now, backend work has been done so that in a future release, the correct, up-to-date ePA authorization status will display in the ePrior Auth Status field in the ePrior Auth tab on the ePrescribe screen so that the user can easily and readily view the status to know whether or not action must be taken on their authorization request.
Note: This will be available in future feature releases after Surescripts certification is approved.
Issue Resolutions
Save Staff as a Preference in Task Manager
Previously, the Staff search fields were unable to be saved in the Task Manager window as a preference. This has been fixed, and you can now save any radio button as a preference, as well as any staff member from the Staff drop-down.
Patient Responsibility Now Readable on Tracking Screen
Previously, when the patients had one of the following Types listed under their insurance - Patient Responsibility select Deductible + copayments, Deductible + coinsurance, or No Pay (do not bill patient) - it was overlapping the Patient Balance information in the Billing Panel of the Tracking screen. Now, the Patient Balance information has been moved down to allow the Patient Responsibility to be readable.
Secondary Insurance Displays as Desired
Previously, when a patient had a secondary insurance, the name of the insurance was not displaying on the Billing Panel of the Tracking screen, Clinical Overview, or the Patient Banner. Now, the secondary insurance name will always display as desired when a patient has an active secondary insurance.
MySQL Resolutions
- Previously, the Patient tab in the Add Payments and Adjustments screen was showing all charges. Now, the Patient tab will only show charges with an open balance.
- An error was occurring when trying to archive tasks that have not been started yet in the Admin >Archive Records > Database Clean-up > Tasks. This was preventing tasks from being archived. This has been resolved, so that the error message will no longer display and you can archive tasks.
OP Address Book Allows the Minus (-) Sign that is a part of the Direct Email to be saved
Within the Address book, OP previously added an email validation logic to ensure that users inputted valid email address formats. This was to ensure that any external communications from OP that leveraged an email address, such as Direct Messaging, or other potential 3rd party integrations were ensured to have a valid email address entered within OP. There was a bug that was fixed whereby OP was flagging email addresses that contained a hyphen "-" as being invalid. and was not allowing the user to save the address. This has now been resolved.
Column Error When Scheduling a Patient
Previously, when filtering by Provider in the Patient Search window, a #2300Column error was appearing and preventing the search results from loading. This has been resolved, and you are now able to filter by Provider when searching for patients in the Patient Search window.
Keycloak Resolutions - Reset Role and Reset Password
Reset Role Workflow Keycloak User
Keycloak is a back-end system that OP uses for user authentication. If a user’s Keycloak Admin role gets out of sync (meaning the system still sees them as a Keycloak Admin and they don't have the AA_AccessSecurity_mi permission or they have the permission but the system doesn't recognize them as an admin), another Keycloak Admin can reset their role. You will be able to tell that the role is out of sync if the following occurs:
- The user no longer has the AA_AccessSecurity_mi permission but can still see the Reset Role and Reset PW columns on the Credentials tab of the Correspondent record.
- The user has been given the AA_AccessSecurity_mi permission but can't see the Reset Role and Reset PW columns on the Credentials tab of the Correspondent record.
To reset the role, navigate to Correspondents > select Keycloak > Credentials tab, then click the Reset Role button for the out of sync user.
Reset Password Workflow for Authentication Failures
If there is an issue with authentication during background access management (Keycloak) login during OP login, OP will present an error message to the user letting them know they need to reach out to a Keycloak Admin:
To fix the error, the Keycloak Admin will need to reset the user's Keycloak password (not OP password). Navigate to Correspondents > select Keycloak > Credentials tab, then click the Reset PW button for the user.
Note: Keycloak admins have the AA_AccessSecurity_mi permission. Until the Keycloak password is fixed, the user will be able to access OP but some of the integrated products like Data Rec, Carequality, PMX+ will not work.
OP 21.2.5 Metadata Release On-Premise: May 3, 2023 | Cloud: Per email communication
OP Metadata/Maintenance Update: On-Premise Action Required, No Change to Build Number
An important Maintenance update is required to upgrade backend components that will support future OP release builds. This update will not impact the current OP build number, and Practices will continue to see the most recent Build Number, 21.2.5, in Help > About if currently up-to-date with releases. No action is required for Cloud Practices. However, On-Premise Practices will need to run the update via the Web Updater. If this update is not completed, future OP updates may be unsuccessful.
Added Admin CPT Code for Pfizer 6m-4 year booster dose
Added the associated administration code 0174A for use of the Pfizer Bivalent 6m-4 vaccine when specifically given as a booster dose to patients who received a valid 3 dose primary series of the Pfizer monovalent 6m-4 year vaccine. This is a different code than the one used for the Pfizer Bivalent 6m-4 vaccine when it is given as the 3rd dose in the primary series, after 2 monovalent doses.
This release contains everything included in the 21.2.5 Feature Release
Scroll down to the 21.2.5 Release to see all release notes.
21.2.5 Release On-Premise: April 25, 2023 | Cloud: Per email communication
Look out for these icons! |  Less Clicks Campaign! |  Major Update | You asked, we listened! |
New Features
Payment Processing Rules
You can now set rules to automate how your practice processes electronic remittance advices (ERAs). Previously, OP would try to suggest a match status (Paid, Matched, Denied, etc) for each CPT line item, but these suggestions often do not meet the needs of the practice. Now the Match Status can be set based on a practice's customizable rules. For example, every time payer ABC denies CPT code 99000, you can automatically mark that transaction as Matched to accept the write-off.
See documentation of this new feature here, and the F1 Window Map here. Path: Billing tab > More button (Customize Group) > Payment Processing Rules.
Improved Functionality For All Users - You Asked, We Answered!
Search Option for Guarantor
In the full patient search screen, you may now search by Guarantor. The search works identically to the existing searches by Patient and by Family Contact.
PMX and OP Notify: Unlimited Messages with Flat Monthly Fee
The pay-per-message credits system is being replaced with unlimited messages under a flat monthly fee. Previously, you would see the number of credits. Following this release, that area will be blank.
The specific impact to your practice will be dependent on the services you are contracted for. See the PMX Credits Communication article for more information.
Improved Functionality For Non-Clinical and/or Billing Staff
Warn When Daysheeting Future Dates
OP permits you to set parameters for the transactions you want to include in a daysheet, including date of service (DOS). Previously, an end user could daysheet future DOS; this potentially could "lock down" transactions that were entered in error (such as anticipated future charges that have not yet actually happened), creating a compliance risk for practices.
Now, if the user selects a future date in the "Only on/before" date, the user is prompted with a warning popup message. The user may choose to override the warning if desired.
Insurance Now in Claim Status History
The Claim Status History window at the bottom of a patient's Claims screen allows the user to see when particular claims were queued, transmitted, and accepted by clearinghouses and payers.
Now the Claim Status History window has a new column, Insurance, which shows the insurance to which a particular claim transmission event is pointed. This field can be enabled using the "hamburger”, and can be saved as a preference to always appear.
Claim Status Notes Autorefresh
OP permits users to add new Claims Statuses to a claim in a patient's Claim screen for custom tracking, annotations, etc. Previously, after adding a new Claim Status, it would disappear from the Claim Status window. The user had to click on another claim, then back on the original claim, to see the newly added Claim Status.
Now, the new Claim Status stays visible without having to force a refresh.
Document Max Page Limit Increased
Previously, OP users could only create new image documents (e.g. monochrome TIFF) with a maximum page size of 50. If the user needed to import a document of more than 50 pages, the user was forced to split the document into chunks of no more than 50 pages. To accommodate larger file sizes, this maximum page restriction has been raised to 99 pages.
Practices can now set a Global Preference > Basic "Scanning page limits per database record" of 1-99 pages for monochrome. Page limits for greyscale and color images have not changed.
PMX Message Too Long
Previously, if a user tried to create a PMX message exceeding 137 characters, the message would limit the characters to 137, but the fact the user had exceeded the message limit was not well signposted.
Now, the user will get a warning message in red that says "The message text may not be longer than 137 characters."
Issue Resolutions Impacting Workflows for All Users
Multi-Chart Error Resolved
Patient Search Irregularity Fixed
Deprecated Radio Button in Tasks
Document Storage of Image Files
Print to PDF for Multiple Documents
Issue Resolutions Impacting Providers and/or Clinical Staff Workflows
Add Scrollbars to Asthma Action Plan
Previously, clinicians using relatively small screens (e.g. laptops) could not see the bottom or far right of the Action Plan tab when creating an Asthma Action Plan. This constricted their ability to complete the Red Zone.
Now, horizontal and vertical scroll bars have been added.
