# 3. Notify afleveren

## Relevante TA Notified Pull hoofdstukken

* 2.2 Notification message
* 3.3 Authorization base

## Inhoud van de Notify

### FHIR Task resource

De Notify voor de uiteindelijke Pull wordt aangeleverd in de vorm van een FHIR STU3 [*Task*](https://hl7.org/fhir/stu3/task.html) resource.

Voor de aflevering van de Notify dient de ontvangende partij een endpoint van diens FHIR server aan te leveren aan VIPLive. Zie [1. Koppeling leggen](/viplive-notified-pull/notified-pull/1.-koppeling-leggen.md).

De inhoud van de *Task* resource staat gelijk aan de vulling volgens de TA Notified Pull. Echter, voor onderstaande velden zullen er afspraken gemaakt moeten worden tussen VIPLive en de ontvangende partij.

<table><thead><tr><th width="278">Veld</th><th> Vulling VIPLive</th></tr></thead><tbody><tr><td>owner.identifier</td><td><strong>Ontvanger is een zorgaanbieder binnen het systeem:</strong>  OID van de AGB-code van de ontvangende zorgaanbieder.<br><br><strong>Ontvanger is het systeem:</strong> Veld wordt weggelaten.</td></tr><tr><td>requester.agent.identifier</td><td><strong>Test:</strong> 2.16.840.1.113883.2.4.3.164.2.1<br><strong>Acceptatie:</strong> 2.16.840.1.113883.2.4.3.164.2.2<br><strong>Productie:</strong> 2.16.840.1.113883.2.4.3.164.2.3</td></tr><tr><td>requester.onBehalfOf.identifier</td><td>Een OID van een AGB-code van de verzendende zorgorganisatie</td></tr></tbody></table>

### Authorization base

Zoals aangegeven in [2. Token request verzender](/viplive-notified-pull/notified-pull/2.-token-request-verzender.md) zal VIPLive een authorization base meesturen als onderdeel van de Notify. Deze dient bij de aanvraag van het token voor de uiteindelijke Pull weer mee terug gestuurd te worden in het `authorization_base` veld (zie [4. Token request ontvanger](/viplive-notified-pull/notified-pull/4.-token-request-ontvanger.md)).

## Voorbeeldbericht

#### Ontvanger is zorgaanbieder binnen het systeem

<details>

<summary>Klik hier om uit te breiden...</summary>

```json
{
  "resourceType": "Task",
  "id": "ee34f62d-0eaa-4655-8cd0-190889e43244",
  "identifier": [ {
    "system": "https://tools.ietf.org/html/rfc4122",
    "value": "3a016790-0b09-4a7f-b316-f4e16448625d"
  } ],
  "groupIdentifier": {
    "system": "https://tools.ietf.org/html/rfc4122",
    "value": "c9d59f3c-449a-478c-bb9c-39bb14843503"
  },
  "status": "requested",
  "intent": "proposal",
  "code": {
    "coding": [ {
      "system": "http://fhir.nl/fhir/NamingSystem/TaskParameter",
      "code": "pull-notification"
    } ]
  },
  "for": {
    "identifier": {
      "system": "http://fhir.nl/fhir/NamingSystem/bsn",
      "value": "123456782"
    }
  },
  "requester": {
    "agent": {
      "identifier": {
        "system": "urn:ietf:rfc:3986",
        "value": "2.16.840.1.113883.2.4.3.164.4"
      }
    },
    "onBehalfOf": {
      "identifier": {
        "system": "http://fhir.nl/fhir/NamingSystem/agb-z",
        "value": "01051234"
      }
    }
  },
  "owner": {
    "identifier": {
      "system": "http://fhir.nl/fhir/NamingSystem/agb-z",
      "value": "24654321"
    }
  },
  "input": [ {
    "type": {
      "coding": [ {
        "system": "http://fhir.nl/fhir/NamingSystem/TaskParameter",
        "code": "authorization-base"
      } ]
    },
    "valueString": "example-Topicus-authorizationBase"
  }, {
    "type": {
      "coding": [ {
        "system": "http://snomed.info/sct",
        "code": "3457005",
        "display": "Patient referral"
      } ]
    },
    "valueString": "ReferralRequest?identifier=https%3A%2F%2Ftopicus.nl%2Fen%2Fsectors%2Fhealthcare%2Ffhir%2FNamingSystem%2Fviplive-regiozorg-verwijzing-identifier%7Cc9d59f3c-449a-478c-bb9c-39bb14843503&type=http%3A%2F%2Fsnomed.info%2Fsct%7C3457005"
  } ]
}
```

</details>

#### Ontvanger is het systeem

<details>

<summary>Klik hier om uit te breiden...</summary>

```json
{
  "resourceType": "Task",
  "id": "ee34f62d-0eaa-4655-8cd0-190889e43244",
  "identifier": [ {
    "system": "https://tools.ietf.org/html/rfc4122",
    "value": "3a016790-0b09-4a7f-b316-f4e16448625d"
  } ],
  "groupIdentifier": {
    "system": "https://tools.ietf.org/html/rfc4122",
    "value": "c9d59f3c-449a-478c-bb9c-39bb14843503"
  },
  "status": "requested",
  "intent": "proposal",
  "code": {
    "coding": [ {
      "system": "http://fhir.nl/fhir/NamingSystem/TaskParameter",
      "code": "pull-notification"
    } ]
  },
  "for": {
    "identifier": {
      "system": "http://fhir.nl/fhir/NamingSystem/bsn",
      "value": "123456782"
    }
  },
  "requester": {
    "agent": {
      "identifier": {
        "system": "urn:ietf:rfc:3986",
        "value": "2.16.840.1.113883.2.4.3.164.4"
      }
    },
    "onBehalfOf": {
      "identifier": {
        "system": "http://fhir.nl/fhir/NamingSystem/agb-z",
        "value": "01051234"
      }
    }
  },
  "input": [ {
    "type": {
      "coding": [ {
        "system": "http://fhir.nl/fhir/NamingSystem/TaskParameter",
        "code": "authorization-base"
      } ]
    },
    "valueString": "example-Topicus-authorizationBase"
  }, {
    "type": {
      "coding": [ {
        "system": "http://snomed.info/sct",
        "code": "3457005",
        "display": "Patient referral"
      } ]
    },
    "valueString": "ReferralRequest?identifier=https%3A%2F%2Ftopicus.nl%2Fen%2Fsectors%2Fhealthcare%2Ffhir%2FNamingSystem%2Fviplive-regiozorg-verwijzing-identifier%7Cc9d59f3c-449a-478c-bb9c-39bb14843503&type=http%3A%2F%2Fsnomed.info%2Fsct%7C3457005"
  } ]
}
```

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://viplive-interop.gitbook.io/viplive-notified-pull/notified-pull/3.-notify-afleveren.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.