Hello,
We want to thank you for your continued patience as we work
through some recent performance challenges with the reporting console. We
understand how frustrating latency can be, and we want to assure you that
resolving this is a top priority for our team.
As a first major step to improving performance and reducing
latency, we upgraded our servers on May 1. As a byproduct of this upgrade, new
versions of all reports were created.
As a result, any saved links in your "Recents" or "Favorites" will no longer work, as they point to outdated versions. To resolve this, access the latest versions of the reports from the standard folders. The new links will be automatically added to your "Recents" section, and you'll have the option to favorite the updated reports. Please click here to view the Pentaho Favorites and Recents user guide.
We apologize for the inconvenience. Know that our team
is here to help you through this change.
Here is a quick look at what else we are doing to improve your reporting in the short and long term.
What We’re Doing Now
- Vendor Collaboration: We’re actively working with our current reporting vendor to identify and implement solutions that will further reduce latency
Direct Report Delivery: To make things easier in the meantime, our team can schedule your frequently used reports to be emailed directly to you on a cadence of your choice—daily, weekly, or monthly.
We’re excited to share that we’re transitioning all
reporting to Power BI by the end of this year. This move will bring a faster,
more modern, and user-friendly experience with enhanced capabilities and
reliability.
We truly appreciate your understanding as we work through
these changes and build a better reporting experience for you. If you’d like to
set up scheduled report deliveries, reach out to your account manager.
Note: Upcoming Report Change Notification
Report Name: 14 and 14.5 Reports
Overview
On Friday, August 22, 2025, the 14 and
14.5 reports will be updated to include a new field indicating if an EHR
Session Code was used to collect data collection questions.
Key Changes
A new column will be added to the end of the report (last
column) called “EHR Session Code”. This field will show as a yes/no and
indicates that the data collection process included data provided via the
Electronic Health Record Data Exchange feature.
We are excited to announce that we are expanding our capacity by adding additional media servers. This enhancement will improve the overall performance and reliability of our services.
How to Identify Impact: To determine if this update will impact your system, please work with your IT department. They will be able to assess any necessary changes to your environment.
Action Required: If your system uses firewall whitelists to control IP address access, please ensure that the following additional IP addresses/ranges are allowed by August 1, 2025, to avoid any intermittent issues with calls:
- 108.163.1.104 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.1.105 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.1.106 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.1.107 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.1.108 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.109 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.110 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.111 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.112 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.113 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.114 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.115 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.116 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.117 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.1.118 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.1.119 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.3.104 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.3.105 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.3.106 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.3.107 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.3.108 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.109 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.110 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.111 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.112 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.113 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.114 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.115 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.116 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.117 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.118 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
- 108.163.3.119 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound) New
If you have previously whitelisted the following subnets as per the recommendations in the document AMN Interpreting App Technical Specifications, you will not need to take any further action.
- 108.163.1.0/24 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
- 108.163.3.0/24 Ports 80, 443 TCP 16000-16009 UDP (SRTP) (Outbound)
Deadline: Please ensure that any necessary changes are completed by August 1, 2025.