What are environments?

Last updated: Oct 2, 2025
PRODUCT OWNER
HEALTH TECH VENDOR
HCO

If a Redox organization is like your company’s secure office, a Redox environment is an isolated space inside the office building. These isolated spaces are ideal for safely setting up, testing, then going live with your implementation.

Types of environments

By default, a Redox organization comes with three environments with specific purposes:

  • Develop safely: Use the development environment to build your integrations and test new features without any risk of breaking things in production. This is your sandbox to play with and test.
  • Test thoroughly: Use the staging environment to test your integration to ensure everything works as expected. This environment serves as a mirror of your production setup. Think of it like your “pre-flight check” before deploying changes to production.
  • Operate securely: Go live in a stable, secure production environment and start sending and receiving real patient data. Access to this environment is typically the most restricted.

Switching between environments

If a user has access to more than one environment, they can switch between them using the environment selector in the Redox dashboard. If you don’t see this selector, it means you only have access to one environment.

Environment drop-down
Environment drop-down

Permission to access an environment

Not every user has the same access to every environment. Organization owners and admins can assign users to different environments based on their job functions. This helps keep confidential data secure. Learn about user roles.

Confidential data

Personal health information (PHI) shouldn’t be visible to just anyone in your organization. The ability to view log payloads—which may contain PHI—is restricted based on a user role assignment. Learn about roles. We recommend assigning user access as though all log payloads contain confidential data.

Although we build all environment types with the same level of security, you should never send PHI to development or staging environments. Users in staging or development don’t expect to interact with confidential data and may not treat it with sensitivity. We also can’t guarantee that one of your connections won’t include PHI by accident, so being preemptive about user access is the safest bet.

To find out which environments you can access, get a list of environments via the Redox Platform API.

Unique assets in an environment

Each environment has a defined set of assets. Learn about assets.

Assets are exclusive to one environment and can only be shared in the case of promoting a staging asset to production. Learn about promoting assets.

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.