Testing Considerations
Getting Started with b.well's Developer Portal
This guide provides an overview of the testing environments, resources, and tools b.well offers to support your development and QA processes. For detailed technical implementation guidance, refer to the specific workflow guides in the developer portal.
Access:
Testing environment access and test users are provided by b.well as part of active sales engagements or for existing customers. There is no self-service portal—access credentials and configuration details are provisioned directly by the b.well team when your testing environment is set up.
Testing Environment
client-sandbox
A dedicated non-production testing environment that mirrors production functionality. Use this environment to develop and validate your integration without affecting production systems.
Synthetic Test Users
b.well provides synthetic test users tailored to your product's data configuration. Depending on your integration, this may include users with clinical data (lab results, medications, conditions, etc.), payer data (claims, coverage), or both. Test users are configured to support:
- Test integration workflows end-to-end
- Validate health data retrieval from external sources
- Verify general application functionality.
b.well's Sandbox Patient Access API Server:
Part of the health.network product suite, b.well provides a simulated patient access server for testing external health system connections in a controlled environment. This server lets you:
To address this, b.well created the b.well Sandbox PROA Server—a simulated patient access server that provides realistic testing scenarios in a fully controlled environment. The PROA server allows you to:
- Simulate external health system connections without accessing real production systems.
- Manage test data updates to simulate providers updating patient records
- Control token expirations to accelerate testing or extend validity to avoid interruptions during testing sessions
This addresses a key testing challenge: production health systems cannot be accessed for testing due to HIPAA compliance and security requirements, and third-party vendor sandboxes have limited availability and control.
In addition to the above, b.well also provides access to select third-party vendor sandboxes (EHR systems, health plans) for additional testing scenarios.
Updated 8 days ago