DicomConfig

Specifies the parameters needed for de-identification of DICOM stores.

HealthcareFHIRHL7v2DICOMMedical ImagingDe-IdentificationInteroperabilityCloud

Properties

Name Type Description
filterProfile string Tag filtering profile that determines which tags to keep/remove.
keepList object List of tags to keep. Remove all other tags.
removeList object List of tags to remove. Keep all other tags.
skipIdRedaction boolean If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based o
View JSON Schema on GitHub

JSON Schema

DicomConfig.json Raw ↑
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "DicomConfig",
  "description": "Specifies the parameters needed for de-identification of DICOM stores.",
  "properties": {
    "filterProfile": {
      "description": "Tag filtering profile that determines which tags to keep/remove.",
      "enum": [
        "TAG_FILTER_PROFILE_UNSPECIFIED",
        "MINIMAL_KEEP_LIST_PROFILE",
        "ATTRIBUTE_CONFIDENTIALITY_BASIC_PROFILE",
        "KEEP_ALL_PROFILE",
        "DEIDENTIFY_TAG_CONTENTS"
      ],
      "type": "string"
    },
    "keepList": {
      "$ref": "#/components/schemas/TagFilterList",
      "description": "List of tags to keep. Remove all other tags."
    },
    "removeList": {
      "$ref": "#/components/schemas/TagFilterList",
      "description": "List of tags to remove. Keep all other tags."
    },
    "skipIdRedaction": {
      "description": "If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: \"Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity.\" http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html",
      "type": "boolean"
    }
  },
  "type": "object"
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/DicomConfig"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.