Workspace

Represents distinct groupings of principals, resources and related data

Workspaces represent distinct groupings of principals, resources, and related data on the SafeCDx platform. As every resource request to SafeCDx requires a Workspace to be part of its context, Workspaces play a critical role in ensuring that all requests are routed to the right resources. Organizations can create Workspaces and nest them under each other as needed to support any clinical or CDx-related workflows. The platform provides flexibility for organizations to determine their own ways to place boundaries around workspaces, such as due to geographic or regulatory jurisdictions.

A Workspace is hosted inside a JAN. That also means that all requests relating to a specific Workspace will be routed to that JAN. Following the example above the request for the “big-us-pharmacy” Workspace will probably be routed to the US JAN.

All Entities that exist within the context of a Tenant are inside the “workspace” namespace. I.e.: /v2/workspaces/big-us-pharmacy/connected-test/1234

Sub-Workspaces

A Workspace can be part of another Workspace. I.e.: “big-us-pharmacy” may have the following Workspaces:

big-us-pharmacy US
- big-us-pharmacy California
- big-us-pharmacy Georgia

This hierarchy can be at most 5 levels deep.

This is mostly useful for configuration. In the example above the Workspaces for California and Georgia will inherit all the configuration form the Workspace US, where California and Georgia can each make their own overrides.

For the URIs this hierarchy is irrelevant. Following the examples above, these workspaces can be accessed using: