Timeline

Data Conversion Waves

IRB Module Transition Timeline

Do you have additional questions? Please visit our FAQs page for more information.

IRB Submission Planning Guide
(IRAP → myUABResearch Transition)

Continuing Review (CR) Submission Deadlines

• Submit continuing reviews (CRs) 6–8 weeks before protocol expiration.
• Only fully approved protocols migrate in each conversion wave.
• Wave 1 cutoff: August 20.
• Wave 2 cutoff: October 2 (assumed).

Key Planning Takeaways

• Back-plan from August 10: All submissions intended for Wave 1 must be fully approved by August 20, not just submitted.
• Work backwards from typical review times (often 1–3 months depending on study type) to set submission targets.
• Avoid "last-minute" amendments or continuing review submissions before either conversion wave, as these may prevent migration.
• Expect dual-system work (IRAP and myUABResearch) between August 24 and October 2.
• There is only one submission freeze (August 10–23), but Wave 2 still carries risk if submissions are in progress at the cutoff.

myUABResearch Notices

Featured

Important Notice

MyUABResearch Reports

Archive

myUABResearch Development Plan

Huron’s Huron Research Suite implementation approach is based on a methodology that includes all components of a successful system implementation of each module. Our methodology is organized into stages (Onboarding, Iteration, Test, Deploy and Support) that guide the order of the implementation work. Implementation threads (Project Management, Information Technology, Business Transformation and Delivery Management) are included in the work of each stage. Certain deliverables of each stage can be completed by Huron or the client affording flexibility in the resourcing model for the project.

Jump to a section...

1. Onboarding
2. Iteration
3. Test
4. Deploy
5. Support

1. Onboarding

The purpose of the onboarding stage is to provide the core project team, central office teams and departmental administrators with hands-on, in-depth training on the Huron Research Suite solution’s functionality and configuration capabilities. During these sessions, we will document feedback and identify gaps between your business processes and the Huron Research Suite solution. This will allow us to come to a mutually agreed upon scope for the configuration of the Huron Research Suite solution and align our business process with Huron' In parallel, key project management documents will be drafted and roles and responsibilities will be refined as necessary. Major decisions that will drive the direction of the project will also be determined (e.g., requirements definition, change leadership, and rollout strategy).

Key tasks in the Onboarding stage of the project include:

• Identify Stakeholders and define their roles & responsibilities
• Kickoff meeting to present the Onboarding schedule, confirm project scope and objectives
• Conduct Onboarding through in-person training and Learning Lab modules
• Gap analysis based on feedback during Onboarding sessions
• Gather and review existing project planning information and supporting documentation
• Collect Pre-implementation metrics (if applicable) to define measurements for success
• Establish project timeline & resource requirements
• Establish deadlines and milestones for various stages of work as well as key deliverables
• Establish project governance, approach, and change control
• Identify risks and formulate risk management strategies
• Establish progress reporting procedures
• Develop deliverable documentation standards and templates
• Document training needs
• Develop communication plans

Back to top...

2. Iteration

The Iteration stage consists of multiple cycles of detailing requirements, planning, configuring, process testing, and acceptance tasks. By completing this portion of the implementation in iterations, users are able to incorporate adjustments made in early iterations with future iterations in a more effective and cost-efficient manner.

Key tasks in this stage include:

• Prepare for and execute “future state” design workshops
• Design and document “future state” system setup configuration
• Prototype and mockup solutions as required.
• Develop functional specifications for interfaces, modifications, and reports
• Define security requirements based upon roles and responsibilities
• Finalize system test plan
• Develop end user training plan
• Finalize data mapping and conversion plan
• Establish test, development, and training environments

Back to top...

3. Test

The key objectives of the Test stage are to pilot “future state” business processes in the new system and to verify that all components are working as designed to support the Client’s implementation goals.

Key tasks in this stage include:

• Conduct system testing sessions
• Conduct user-acceptance testing sessions
• Perform mock conversions
• Logging issues found during testing for resolution
• Resolve issues found during testing for resolution
• Develop and deliver training courses and materials
• Draft system deployment communications
• Cutover approach

Back to top...

4. Deploy

The objective of the Deploy stage is to successfully transition the new system to the end-user community.

Key tasks in this stage include:

• Migrate interfaces and reports to production environment
• Migrate security to production environment
• Load system configuration
• Execute data conversion and verify results
• Perform security test

Back to top...

5. Support

During the new system’s stabilization period, the Huron team will work to transition all project roles and responsibilities to the Client team.

Key tasks in this stage include:

• Support end users as they transact business using the new system
• Conduct post go-live assessment
• Monitor and tune production environment
• Resolve software bugs and other issues
• stage out project team roles into prior or new Client positions
• Confirm ongoing plan to support and maintain the system
• Provide support to help desk personnel as needed

Back to top...