PackagesCanonicalsLogsProblems
    Packages
    de.gematik.isik-terminplanung@3.0.4
    https://gematik.de/fhir/isik/v3/Terminplanung/StructureDefinition/ISiKTerminblock
{
  "description": null,
  "_filename": "StructureDefinition-ISiKTerminblock.json",
  "package_name": "de.gematik.isik-terminplanung",
  "date": "2024-05-07",
  "derivation": "constraint",
  "publisher": "gematik GmbH",
  "fhirVersion": "4.0.1",
  "name": "ISiKTerminblock",
  "abstract": false,
  "type": "Slot",
  "experimental": "false",
  "resourceType": "StructureDefinition",
  "title": null,
  "package_version": "3.0.4",
  "status": "active",
  "id": "15b0ad87-d2ba-48d0-9731-3339b2016ca5",
  "kind": "resource",
  "url": "https://gematik.de/fhir/isik/v3/Terminplanung/StructureDefinition/ISiKTerminblock",
  "version": "3.0.4",
  "differential": {
    "element": [ {
      "id": "Slot",
      "path": "Slot",
      "constraint": [ {
        "key": "ISiK-slot-1",
        "human": "Der Endzeitpunkt eines Terminsblocks MUSS nach dem Startzeitpunkt liegen",
        "source": "https://gematik.de/fhir/isik/v3/Terminplanung/StructureDefinition/ISiKTerminblock",
        "severity": "error",
        "expression": "start <= end"
      } ]
    }, {
      "id": "Slot.schedule",
      "path": "Slot.schedule",
      "comment": "Zur Referenzierung auf eine Schedule-Ressource MUSS eine Reference.reference mit einer URL verwendet werden. Das Termin-Repository muss so gestaltet sein, dass es aus Perspektive des Clients nur eine Service-BaseUrl gibt.",
      "mustSupport": true
    }, {
      "id": "Slot.schedule.reference",
      "min": 1,
      "path": "Slot.schedule.reference",
      "mustSupport": true
    }, {
      "id": "Slot.status",
      "path": "Slot.status",
      "mustSupport": true
    }, {
      "id": "Slot.start",
      "path": "Slot.start",
      "mustSupport": true
    }, {
      "id": "Slot.end",
      "path": "Slot.end",
      "mustSupport": true
    } ]
  },
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Slot"
}