Another requirement is that the Private Link configuration isn't enabled. One requirement is that the two subscriptions must be part of the same Azure Active Directory (Azure AD) tenant. However, when the move operation is supported and enabled, workspaces and its child resources can be moved from one subscription to another subscription if certain requirements are met. Workspace names can be reused in the same Azure subscription, but not in a different Azure subscription, after deletion. However, when a workspace resource group is deleted, all the workspaces and child service instances within the workspace resource group get deleted. This feature helps prevent any accidental deletion of service instances. An Azure Health Data Services workspace, as a parent item in the hierarchical service tree, must be created first before one or more child service instances can be created.Ī workspace can't be deleted unless all child service instances within the workspace have been deleted. One or more workspaces can be created in a resource group from the Azure portal, or using deployment scripts. With the workspace, you can organize all your Azure Health Data Services instances and manage certain configuration settings that are shared among all the underlying datasets and services where it's applicable. You can provision multiple data services within a workspace, and by design, they work seamlessly with one another. The workspace also creates a compliance boundary (HIPAA, HITRUST) within which protected health information can travel. The Azure Health Data Services workspace is a logical container for all your healthcare service instances such as Fast Healthcare Interoperability Resources (FHIR®) services, Digital Imaging and Communications in Medicine (DICOM®) services, and MedTech service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |