As of January 1st, 2024, we are discontinuing support for our older versions of the program, including Progeny 9 and Progeny 10. While we are sad to see them go, we are excited to fully embrace our latest version, Progeny 11, which has been active for our Cloud clients for quite some time.
Converting your database is a large task, and we are here to help make it as easy as possible. Below is a detailed description of the features and changes, the process, and some frequently asked questions we think will help you decide the best way to move forward with this conversion. Please keep in mind that these changes only affect our clients who store their databases locally (on-premise).
So, what makes Progeny 11 different?
What’s Being Added
- Ability to export invite fields from invites module to text and/or Excel
- End-user administrator that will be able to create:
- Symbols
- Subtext
- Pedigree Fields
- Smart Headers/Footers
- Smart list management
- FHQ (Family History Questionnaire) email templates
- Ability to import via spreadsheets
- Move on Invite – questionnaires can move to folders automatically upon questionnaire invitation
- New Genetic Testing Results (GTR) fields for summarizing variants and test date fields
- Same-sex relationships, sperm/egg donor, and surrogate capabilities on pedigree canvas
- Sex and gender designations to reflect gender identify in addition to sex at birth
- Auto-update questionnaire invite status to inactive upon designated date/timing
- Only Probands viewing option in Individuals module
- Ability to toggler between Ambry organizations in Orders module
- Ability to view all clinic patients in addition to a specific user’s patients, mimicking Ambry Port functionality
- Pedigree undo/redo
- MFA (Multi-Factor Authentication) with email for secure logins
- Ability to run risk on selected individual
- Ability to batch send invitations
What’s Changing
- Backend database management system moved from Sybase on Progeny 10 to MySQL on Progeny 11
- Modules/functionality no longer supported in Progeny 11:
- LAB (including Genotypes, Analysis, Markers tabs)
- LIMS (includes Inventory, Containers, Workflows, Samples, Tasks)
- Sample Module
- LDAP (replaced with SAML SSO for authentication and permissions)
- Due to the changes in backend database management systems (Sybase to MySQL), custom functions, triggers, procedures, and events are no longer supported (these will not be included as part of the Progeny 10 to 11 conversion)
- Direct exporting of BOADICEA, CAGene, and BRCAPro risk formats
- Progeny 11 no longer has separate desktop and web applications; Progeny 11 is a web exclusive application, and the remaining supported desktop-only functionality has been folded into the web application.
Progeny 11 Upgrade Process and Information
How do we start?
Your Customer Success Manager will work with you to review any questions and details you need before you start this process. Once you are ready to move forward, we will coordinate with you to pull a copy of your database for scoping. Scoping will determine billing and any additional costs, and the copy of your database is purged once it is completed. Please keep in mind, once the initial scoping is completed, no additional customized work can be added to this project, and it will need to be discussed as its own, new project.
Overall, this process should take approximately one to two months from start to finish, but that may change due to reasonable delays like scheduling conflicts and additional meetings for questions. For more precise timelines, please speak with your Customer Success Manager.
Once everyone has agreed on the billing and scoping, we need to pull the database once again and provision the live server with the new database set-up. From there, we will convert the database to Progeny 11 and then re-insert it into your local environment, we will require a new server or VM at the time of provisioning. We will try to limit the number of meetings this takes to be considerate of everyone’s time, but depending on the set-up, that may not always be possible. We do know that we will need at least two meetings for the actual insertion of the Progeny 11 database. Once this change goes into effect, all users will need to create new passwords using the “Forgot Password” process. Admins also have the option to change user passwords manually.
Provisioning Meeting
This meeting is to prepare the server(s) that will be used for Progeny 11. Please keep in mind, any SSL or EMR integration requests will need to be communicated during scoping to prevent delays. The steps taken here are dependent upon the customer’s environment but will typically include the below:
- Installations
- Apache Tomcat 9 (latest available)
- Oracle Java (latest available)
- MySQL
- Workbench (latest available)
- Server (latest available)
- Firewall Permissions
- Creating an inbound rule for Apache Tomcat
- Opening ports on the network if external access is required (Optional)
Migration Meeting
The migration process will take place after an updated copy of the customer’s database has been acquired and it has been fully converted. Our Technical Support team will place it in the local environment with the client’s assistance. If the Technical Support Representative cannot complete the database insertion within a reasonable time limit, all changes to the server will be reverted using the scoped conversion time, please speak with your Customer Success Manager for details about what that time limit looks like for your specific set up. This is to make sure there are no prolonged disruptions to the Progeny service. From there, Technical Support will reconvene with appropriate internal and external contacts to find solutions to the issues discovered.
These steps are also dependent on the customer’s environment but will typically include the below:
- Configuring the Progeny 11 database
- Licensing and validating Progeny 11
- Optional Configurations
- SSL Certification
Frequently Asked Questions
Q: What’s the difference between Progeny On-premise and Progeny Cloud?
A: On-premise Customers have Progeny installed locally. They manage their own Progeny database including the maintenance and administration of the environment. Moving forward, our support teams will no longer be able to assist with any local versions of Progeny 9 and 10. Cloud Customers have the Progeny application installed and managed within our Ambry Data Center. We manage all working parts of their database, maintenance, and administration of their application. This communication is not applicable to our Cloud accounts as they are already on Progeny 11.
Q: Who are the Customer Success Managers (CSM) at Progeny?
A: Michelle Carangi ([email protected]) and Gisela Gollrad ([email protected]) are the Customer Success Managers here at Progeny. If you are unsure who directly handles your account, please reach out to both.
Q: If my institution won’t approve the increased cost, what will happen to our Progeny database?
A: An On-premise customer can continue to use Progeny locally. Previously, a Progeny Support Plan allowed On-premise clients to receive assistance from our technical teams but it was never required. Moving forward, our internal teams will no longer perform any maintenance or support for older versions of Progeny (i.e., 9 and 10). We are extending this support if the client has an active Progeny Support Plan until the plan expires. Please remember that even with Progeny 11, an annual Progeny Support Plan is required for continued service.
Q: If our institution decides to not upgrade to Progeny 11, what are the security risks for Progeny 9 and 10?
A: As there will be no further development, updates, patches, or testing on versions 9 and 10 of Progeny, the application may be at risk for new security vulnerabilities. There may be generalized security risks related to outdated dependent Progeny web application files, including Sybase 17, which has already reached end-of-life.
Q: How do I know if my institution qualifies to upgrade to Progeny 11?
A: All On-premise clients qualify for Progeny 11 conversion, however those that are utilizing LIMS/LABS or samples, may need to pursue other clinical options as these features are being discontinued. Please contact your Customer Success Manager to review any details or concerns about this change.
Q: What does it cost to upgrade to Progeny 11?
A: We are waiving the up-front cost of converting Progeny 10 to Progeny 11, additional hourly costs may apply after database scoping depending on how much work will be required to fully convert it. Please reach out to your Customer Success Manager to go over details.
Q: Can my institution move to the Cloud instead?
A: Yes! Cloud is another option for our On-Premise clients. We manage all the hard stuff, so you don’t have to. Say goodbye to worrying about maintenance! Cloud is also a popular cost savings option with many of our clients.
Q: Can we still email Progeny Support if we have any questions or issues with Progeny 9 or 10?
A: Yes, and we will do our best to address any outstanding questions! However, no further support (Customizations, Developer Support, Troubleshooting, Client Meetings, etc.) will be available for Progeny 9 or 10 after January 1, 2024, or your annual Progeny Support Plan expires.
Q: Can an institution upgrade to Progeny 11 without providing their database?
A: If a fresh database is preferred over scoping an existing database, that may be an option. Otherwise, without the database, scoping becomes impossible, and the Progeny 11 upgrade cannot proceed. If you would like a Business Associate Agreement (BAA) in place prior to disclosing a copy of your database, please speak with your Customer Success Manager for assistance.
Q: If an institution has multiple databases to migrate, does that complicate the conversion?
A: If there are multiple databases, each database can be migrated individually with an associated cost. However, if all the databases originated from the same source (with matching fields), there may be ways to avoid the additional costs, although we cannot determine that until we are able to fully scope out the project. Please make sure your Customer Success Manager knows about the multiple databases and how you