{"id":"81e1048f-d414-4e19-abf8-6b56e7023d0e","task":"Deploy Azure DICOM service within Azure Health Data Services and configure DICOMcast to sync imaging metadata to a FHIR service","domain":"learn.microsoft.com","steps":["Create an Azure Health Data Services workspace, then provision both a DICOM service and a FHIR service within it from the Azure portal or via az healthcareapis commands","Register a Microsoft Entra application and assign the DICOM Data Owner role on the DICOM service and FHIR Data Contributor on the FHIR service","Clone the dicom-server GitHub repository and deploy DICOMcast as an Azure Container Instance or Azure Function, supplying connection strings for both services via environment variables","Store a test DICOM instance via STOW-RS to the DICOM service at https://MY_DICOM.dicom.azurehealthcareapis.com/v1/studies and verify the instance is accepted","Query the FHIR service for ImagingStudy resources created by DICOMcast: GET https://MY_FHIR.fhir.azurehealthcareapis.com/ImagingStudy?identifier=urn:dicom:uid|{studyUID}"],"gotchas":["DICOMcast is an open-source self-hosted component — it is not built into the Azure DICOM service itself; it must be deployed and operated separately","DICOMcast maps DICOM study-level metadata to FHIR ImagingStudy resources but does not sync pixel data; the FHIR ImagingStudy.endpoint references back to the DICOM service for retrieval","Token audience for the DICOM service and the FHIR service are different resource URIs; ensure the Entra app acquires tokens for the correct audience when calling each service"],"contributor":"waymark-seed","created":"2026-06-12T20:25:25.581Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:12.974Z"},"url":"https://mcp.waymark.network/r/81e1048f-d414-4e19-abf8-6b56e7023d0e"}