Uzbekistan Digital Health Platform, published by Ministry of Health of the Republic of Uzbekistan. This guide is not an authorized publication; it is the continuous build for version 0.12.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/uzinfocom-org/digital-health-ig/ and changes regularly. See the Directory of published versions

• Narrative Content
• JSON

: Detach a patient from the managing organization and the general practitioner

Draft as of 2026-10-22

Raw json | Download

{
  "resourceType" : "OperationDefinition",
  "id" : "patient-detach",
  "language" : "en",
  "text" : {
    "status" : "generated",
    "div" : "<div xml:lang=\"en\" lang=\"en\"><hr/><p><b>English</b></p><hr/><p class=\"res-header-id\"><b>Generated Narrative: OperationDefinition patient-detach</b></p><a name=\"patient-detach\"> </a><a name=\"hcpatient-detach\"> </a><p>URL: [base]/Patient/[id]/$detach</p><h3>Parameters</h3><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>reason</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R5/datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>Reason for detaching the patient. Must carry a non-empty text or at least one coding with a non-empty code, otherwise the request is rejected with 400 and issue code <code>value</code>. A missing reason is rejected with 400 and issue code <code>required</code>.</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R5/patient.html\">Patient</a></td><td/><td><div><p>The Patient resource after detachment, or the current resource when there was nothing to detach.</p>\n</div></td></tr></table><div><p>The update goes through the regular update path with the version of the read resource, so if the Patient was modified concurrently the operation fails with HTTP 412. If the patient has neither an organization, nor a practitioner, nor the attachment extension, no new version is created and the current resource is returned. The reason is validated and logged but is not stored in the Patient resource. Detaching only the organization or only the practitioner is not supported; use Patient/$attach to change one side of the attachment.</p>\n</div></div>"
  },
  "url" : "https://dhp.uz/fhir/core/OperationDefinition/patient-detach",
  "version" : "0.12.0",
  "name" : "PatientDetach",
  "title" : "Detach a patient from the managing organization and the general practitioner",
  "status" : "draft",
  "kind" : "operation",
  "experimental" : false,
  "date" : "2026-10-22",
  "publisher" : "Ministry of Health of the Republic of Uzbekistan",
  "contact" : [
    {
      "name" : "Ministry of Health of the Republic of Uzbekistan",
      "telecom" : [
        {
          "system" : "url",
          "value" : "https://gov.uz/en/ssv"
        },
        {
          "system" : "email",
          "value" : "info@ssv.uz"
        }
      ]
    }
  ],
  "description" : "Detaches the patient from both the managing organization and the general practitioner in one call. The server clears Patient.managingOrganization and Patient.generalPractitioner and removes the `https://dhp.uz/fhir/core/StructureDefinition/managing-organization-attachment` extension set by Patient/$attach; other extensions are kept. The operation is invoked at instance level only (Patient/[id]/$detach) with POST and a Parameters body. The response is the Patient resource, not Parameters.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "urn:iso:std:iso:3166",
          "code" : "UZ",
          "display" : "Uzbekistan"
        }
      ]
    }
  ],
  "purpose" : "The reverse of Patient/$attach: where $attach records the attachment, $detach removes it in one call, for example when the patient has applied to be detached.",
  "affectsState" : true,
  "code" : "detach",
  "comment" : "The update goes through the regular update path with the version of the read resource, so if the Patient was modified concurrently the operation fails with HTTP 412. If the patient has neither an organization, nor a practitioner, nor the attachment extension, no new version is created and the current resource is returned. The reason is validated and logged but is not stored in the Patient resource. Detaching only the organization or only the practitioner is not supported; use Patient/$attach to change one side of the attachment.",
  "resource" : [
    "Patient"
  ],
  "system" : false,
  "type" : false,
  "instance" : true,
  "parameter" : [
    {
      "name" : "reason",
      "use" : "in",
      "min" : 1,
      "max" : "1",
      "documentation" : "Reason for detaching the patient. Must carry a non-empty text or at least one coding with a non-empty code, otherwise the request is rejected with 400 and issue code `value`. A missing reason is rejected with 400 and issue code `required`.",
      "type" : "CodeableConcept"
    },
    {
      "name" : "return",
      "use" : "out",
      "min" : 1,
      "max" : "1",
      "documentation" : "The Patient resource after detachment, or the current resource when there was nothing to detach.",
      "type" : "Patient"
    }
  ]
}