Merge pull request #204342 from mcevoy-building7/dicom-oss-02

add details about dicom server

Author: PRMerger12

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

@@ -1,12 +1,12 @@
 ---
 title:  Overview of the DICOM service - Azure Health Data Services
 description: In this article, you'll learn concepts of DICOM and the DICOM service.
-author: stevewohl
+author: mcevoy-building7
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 06/03/2022
-ms.author: aersoy
+ms.date: 07/11/2022
+ms.author: v-smcevoy
 ---
 
 # Overview of the DICOM service
@@ -50,6 +50,10 @@ FHIR™ is becoming an important standard for clinical data and provides ext
 
 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. For each instance of DICOM service, we create a combination of isolated and multi-tenant resource.
 
+## DICOM server
+
+The Medical Imaging Server for DICOM (hereby known as DICOM server) is an open source DICOM server that is easily deployed on Azure. It allows standards-based communication with any DICOMweb™ enabled systems, and injects DICOM metadata into a FHIR server to create a holistic view of patient data. See [DICOM server](https://github.com/microsoft/dicom-server).
+
 ## Summary
 
 This conceptual article provided you with an overview of DICOM and the DICOM service.