Merge pull request #235559 from mmitrik/mmitrik/dicom-cast-retire-notice

Adds retirement notice for DICOMcast.  Redirects to OSS repo.

Author: Court72

.openpublishing.redirection.json

@@ -22562,6 +22562,11 @@
           "source_path_from_root": "/articles/azure-monitor/app/java-standalone-arguments.md",
           "redirect_url": "/azure/azure-monitor/app/java-get-started-supplemental",
           "redirect_document_id": true
+        },
+        {
+          "source_path_from_root": "/articles/healthcare-apis/dicom/dicom-cast-access-request.md",
+          "redirect_url": "/azure/healthcare-apis/dicom/dicom-cast-overview",
+          "redirect_document_id": false
         }
     ]
 }

articles/healthcare-apis/dicom/dicom-cast-access-request.md

@@ -11,6 +11,9 @@ ms.author: mmitrik
 
 # DICOMcast overview
 
+> [!NOTE]
+> On **July 31, 2023** DICOMcast will be retired.  DICOMcast will continue to be available as an open-source component that can be self-hosted.  For more information about deploying the DICOMcast service, see the [migration guidance](https://aka.ms/dicomcast-migration).
+
 DICOMcast offers customers the ability to synchronize the data from a DICOM service to a [FHIR service](../../healthcare-apis/fhir/overview.md), which allows healthcare organizations to integrate clinical and imaging data. DICOMcast expands the use cases for health data by supporting both a streamlined view of longitudinal patient data and the ability to effectively create cohorts for medical studies, analytics, and machine learning.
 
 ## Architecture
@@ -87,7 +90,7 @@ DICOM has different date time VR types. Some tags (like Study and Series) have t
 
 ## Summary
 
-In this concept, we reviewed the architecture and mappings of DICOMcast. This feature is available on demand. To enable DICOMcast for your Azure subscription, please request access for DICOMcast by opening an [Azure support ticket](https://azure.microsoft.com/support/create-ticket/). For more information about requesting access to DICOMcast, see [DICOMcast request access](dicom-cast-access-request.md). 
+In this concept, we reviewed the architecture and mappings of DICOMcast. This feature is available as an open-source component that can be self-hosted.  For more information about deploying the DICOMcast service, see the [deployment instructions](https://github.com/microsoft/dicom-server/blob/main/docs/quickstarts/deploy-dicom-cast.md).
 
 > [!IMPORTANT]
 > Ensure that you include the **resource IDs** of your DICOM service and FHIR service when you submit a support ticket. 

articles/healthcare-apis/dicom/dicom-cast-overview.md

@@ -16,7 +16,7 @@ sections:
   - name: Ignored
     questions:
       - question: What is the DICOM service?
-        answer: The DICOM service is a managed service within [Azure Health Data Services](../healthcare-apis-overview.md) that ingests and persists DICOM objects at multiple thousands of images per second. It facilitates communication and transmission of imaging data with any DICOMweb™ enabled systems or applications via DICOMweb Standard APIs like [Store (STOW-RS)](dicom-services-conformance-statement.md#store-stow-rs), [Search (QIDO-RS)](dicom-services-conformance-statement.md#search-qido-rs), [Retrieve (WADO-RS)](dicom-services-conformance-statement.md#retrieve-wado-rs). It is backed by a managed Platform-as-a Service (PaaS) offering in the cloud with complete [PHI](https://www.hhs.gov/answers/hipaa/what-is-phi/index.html) compliance that you can upload PHI data to the DICOM service and exchange it through secure networks.
+        answer: The DICOM service is a managed service within [Azure Health Data Services](../healthcare-apis-overview.md) that ingests and persists DICOM objects at multiple thousands of images per second. It facilitates communication and transmission of imaging data with any DICOMweb™ enabled systems or applications via DICOMweb Standard APIs like [Store (STOW-RS)](dicom-services-conformance-statement.md#store-stow-rs), [Search (QIDO-RS)](dicom-services-conformance-statement.md#search-qido-rs), [Retrieve (WADO-RS)](dicom-services-conformance-statement.md#retrieve-wado-rs). It's backed by a managed Platform-as-a Service (PaaS) offering in the cloud with complete [PHI](https://www.hhs.gov/answers/hipaa/what-is-phi/index.html) compliance that you can upload PHI data to the DICOM service and exchange it through secure networks.
 
       - question: What are the key requirements to use the DICOM service?
         answer: The DICOM service needs an Azure subscription to configure and run the required components. These components are, by default, created inside of an existing or new Azure Resource Group to simplify management. Additionally, an Azure Active Directory account is required.
@@ -31,13 +31,13 @@ sections:
           
       - question: What data formats are compatible with the DICOM service?
         answer: |
-          The DICOM service exposes a REST API that is compatible with the [DICOMweb™ Standards](https://www.dicomstandard.org/using/dicomweb)specified and maintained by NEMA.
+          The DICOM service exposes a REST API that is compatible with the [DICOMweb™ Standards](https://www.dicomstandard.org/using/dicomweb) specified and maintained by NEMA.
           
-          The server does not support DICOM DIMSE, which works primarily over a local area network and is unsuited for modern internet-based APIs. DIMSE is an incredibly popular standard used by nearly all medical imaging devices to communicate with other components of a provider’s medical imaging solution, such as PACS (Picture Archiving and Communication Systems) and medical imaging viewers. However, many modern systems, especially PACS and viewers, have begun to also support the related (and compatible) DICOMweb™ Standard. For those systems which only speak DICOM DIMSE, there are adapters available which allow for seamless communication between the local DIMSE-supporting systems and the DICOM service.
+          The server doesn't support DICOM DIMSE, which works primarily over a local area network and is unsuited for modern internet-based APIs. DIMSE is an incredibly popular standard used by nearly all medical imaging devices to communicate with other components of a provider’s medical imaging solution, such as PACS (Picture Archiving and Communication Systems) and medical imaging viewers. However, many modern systems, especially PACS and viewers, have begun to also support the related (and compatible) DICOMweb™ Standard. For those systems which only speak DICOM DIMSE, there are adapters available which allow for seamless communication between the local DIMSE-supporting systems and the DICOM service.
           
       - question: What version of DICOM does the DICOM service support?
         answer: |
-          The DICOM standards has been fixed at version 3.0 since 1993. However, the standard continues to add both breaking and non-breaking changes through various workgroups.
+          The DICOM standard has been fixed at version 3.0 since 1993. However, the standard continues to add both breaking and non-breaking changes through various workgroups.
           
           No single product, including the DICOM service, fully supports the DICOM standard. Instead, each product includes a DICOM Conformance document that specifies exactly what is supported. (Unsupported features are traditionally not called out explicitly.) For more information, see [DICOM Conformance Statement](dicom-services-conformance-statement.md).
           
@@ -61,8 +61,4 @@ sections:
       
       - question: What is REST API versioning in the DICOM service?
         answer: |
-          DICOM service has versions for the REST API used to access the service. The version is specified as a URL path in the requests. For more information visit the [API Versioning for DICOM service Documentation](./api-versioning-dicom-service.md).
-          
-      - question: How can I get access and use DICOMcast?
-        answer: |
-          To enable DICOMcast for your Azure subscription, please request access for DICOMcast by opening an [Azure support ticket](https://azure.microsoft.com/support/create-ticket/). For more information about requesting access to DICOMcast, see [DICOMcast request access](dicom-cast-access-request.md). 
+          DICOM service has versions for the REST API used to access the service. The version is specified as a URL path in the requests. For more information, visit the [API Versioning for DICOM service Documentation](./api-versioning-dicom-service.md).

articles/healthcare-apis/dicom/dicom-services-faqs.yml

@@ -24,7 +24,7 @@ The DICOM service is a managed service within [Azure Health Data Services](../he
 - **PHI Compliant**: Protect your PHI with unparalleled security intelligence. Your data is isolated to a unique database per API instance and protected with multi-region failover. The DICOM service implements a layered, in-depth defense and advanced threat protection for your data.
 - **Extended Query Tags**: Additionally index DICOM studies, series, and instances on both standard and private DICOM tags by expanding list of tags that are already specified within [DICOM Conformance Statement](dicom-services-conformance-statement.md).
 - **Change Feed**: Access ordered, guaranteed, immutable, read-only logs of all the changes that occur in DICOM service. Client applications can read these logs at any time independently, in parallel and at their own pace.
-- **DICOMcast**: Via DICOMcast, DICOM service can inject DICOM metadata into a FHIR service, or FHIR server, as an imaging study resource allowing a single source of truth for both clinical data and imaging metadata. This feature is available on demand. To enable DICOMcast for your Azure subscription, please request access for DICOMcast via opening an [Azure Technical Support](https://azure.microsoft.com/support/create-ticket/) ticket.
+- **DICOMcast**: Via DICOMcast, the DICOM service can inject DICOM metadata into a FHIR service, or FHIR server, as an imaging study resource allowing a single source of truth for both clinical data and imaging metadata. This feature is available as an open-source feature that can be self-hosted in Azure.  Learn more about [deploying DICOMcast](https://github.com/microsoft/dicom-server/blob/main/docs/quickstarts/deploy-dicom-cast.md).
 - **Region availability**: DICOM service has wide-range of [availability across many regions](https://azure.microsoft.com/global-infrastructure/services/?products=azure-api-for-fhir&regions=all) with multi-region failover protection and continuously expanding.
 - **Scalability**: DICOM service is designed out-of-the-box to support different workload levels at a hospital, region, country and global scale without sacrificing any performance spec by using autoscaling features. 
 - **Role-based access**: You control your data. Role-based access control (RBAC) enables you to manage how your data is stored and accessed. Providing increased security and reducing administrative workload, you determine who has access to the datasets you create, based on role definitions you create for your environment.

articles/healthcare-apis/dicom/dicom-services-overview.md

@@ -69,7 +69,7 @@ You can find more details on DICOMweb standard APIs and change feed in the [DICO
 
 #### DICOMcast
 
-DICOMcast is currently available as an [open source](https://github.com/microsoft/dicom-server/blob/main/docs/concepts/dicom-cast.md) project, and it's under private preview as a managed service. To enable DICOMcast as a managed service for your Azure subscription, request access by creating an [Azure support ticket](https://azure.microsoft.com/support/create-ticket/) by following the guidance in the article [DICOMcast access request](dicom-cast-access-request.md).
+DICOMcast is currently available as an [open source](https://github.com/microsoft/dicom-server/blob/main/docs/concepts/dicom-cast.md) project.
 
 ## Next steps
 

articles/healthcare-apis/dicom/get-started-with-dicom.md

@@ -81,8 +81,6 @@ items:
   items:
     - name: DICOM service open-source projects
       href: references-for-dicom-service.md
-    - name: DICOMcast access request
-      href: dicom-cast-access-request.md