Successful implementation of the Life Sciences Functionality Extension requires structured planning and strict adherence to Bonterra’s standards. This process ensures functional alignment with your program goals, minimizes risk, and supports long-term maintainability.
The following steps will guide you through the implementation process for this extension, from initial planning through post-implementation management best practices.
Pre-implementation planning
Step 1: Define business and functional requirements
Clearly outline what your program needs from each feature of the extension:
- What proposal types will be used?
- Which registration fields should be customized?
- How will payment statuses be tracked internally?
Identify any internal business rules that will impact these configurations.
Step 2: Engage stakeholders
Include legal, compliance, IT, and program teams to confirm alignment on system behavior, terminology, and data handling procedures.
Step 3: Prepare technical resources
Ensure that your internal IT team or a designated technical contact is available to:
- Assist with requirements validation
- Provide access to patient data fields
- Support User Acceptance Testing (UAT) coordination efforts
Step 4: Allocate solution credits
Confirm that your organization has the necessary solution credits to:
Implementation process
Step 5: Participate in the requirements workshop
Collaborate with Bonterra’s Implementation team to finalize scope, workflows, and extension configurations. The team will guide you using our standard methodology.
Step 6: Approve final functional specifications
Review and approve the extension’s documented functionality. Changes after this point may result in delays or cost adjustments.
Step 7: Complete development and conduct User Acceptance Testing (UAT)
Bonterra will configure the extension in a test environment. During UAT, validate that the system meets expectations, including:
- Portlet data displays correctly and completely
- Resupply links activate appropriately
- Registration fields reflect healthcare language
- Payment sub-statuses appear based on the criteria
Step 8: Provide formal UAT sign-off
No functionality will be moved to production without full written UAT approval from your team.
Post-implementation management
Step 9: Monitor extension behavior regularly
Assign a system administrator to monitor extension usage and confirm expected behaviors, as well as output. Review metrics for ongoing program performance.
Step 10: Request scoped changes thoughtfully
Each extension includes one permitted change per calendar year. When planning changes:
- Prioritize based on business value
- Consider timing to avoid program disruption
Step 11: Maintain documentation and knowledge transfer
Ensure internal teams have access to:
- Training documentation
- Configuration guides
- Support escalation procedures
Step 12: Engage Bonterra support when needed
If new requirements emerge, consult your Bonterra team to explore additional advisory services and determine whether a change order is needed.
What else do you need help with?
Not what you’re looking for? Navigate to Life Sciences Functionality Extension Overview
Looking for training?
Explore this feature at your own pace - access training video content or watch a recorded webinar by clicking the link below.
