Änderung in gemSpec_Aktensystem_ePAfueralle

Neue Anforderung und Hinweis in Kapitel 3.15 Email Management:

Hinweis: Die Beschränkung auf die maximale Anzahl gilt sowohl bei der direkten Hinterlegung neuer E-Mail Adressen, als auch bei der indirekten Hinterlegung im Kontext der Befugnisersteilung für einen Vertreter.

Änderung in gemSpec_ePA_FdV

Änderung in Kapitel 6.2.11 Verwaltung von E-Mail-Adressen

Ergänzung im einleitenden Abschnitt.

Ein Nutzer kann bis zu 10 (maximale Anzahl) unterschiedliche E-Mail-Adressen in einem Aktensystem verwalten.

Änderung der Anforderung A_25721

alt:

neu:

Änderung in I_Email_Management.yaml

Änderung in Operation setEmail (description):

.....

       **Provider**:</br>
       A new email address associated to the kvnr of the requestor shall be created with:
       - timestamp _createdAt_ set to current system time.
       The maximum of 10 different mail addresses in total shall not be exceeded. The operation shall fail
       in case this limit  can not be kept.
       Provision of an already existing mail address (case-insensitive) is a success case but no new address is created.
       A notification mail shall be send to the new and all other stored mail addresses of the user.

.
       | Conditions | Status code | Error code | Remarks |
       |------------|-------------|------------|---------|
       | Successful operation | 201 |||
       | Request does not match schema | 400 | malformedRequest ||
       | Requestor role is not _oid_versicherter_ | 403 | invalidOid ||
       | Device registration does not exist |403 | unregisteredDevice ||
       | Missing _x-insurantid_ | 403 | invalidParam | _oid_kostentraeger_ (only) requires _x-insurantid_ |
       | Requestor is not insurant itself or insurant hosted by insurance | 409 | requestMismatch ||
       | Provided mail address violates maximum limit | 409 | limitExceeded | if new mail address exeeds the limit of 10 different mail addresses |
       | Any other error | 500 | internalError | (see 'Retry interval') |
.......

Änderung in I_Entitlement_Management.yaml

Änderung in Operation setEntitlement (description):

...

       Representative Entitlement:</br>
       A request for representative entitlement shall provide (mandatory) a notification mail address
       of the representative.
       This notification mail address shall be associated to the representatives identification (kvnr) an kept for
       a subsequent device registration of the representative on first access to the insurant's health record
       (hand over to Device Management).</br>
       Additionally a notification mail shall be send to the representative using this mail address
       for information about the new established representative role for the insurant's health record, including
       kvnr and name of the insurant. This notification is obsolete in case the new entitlement replaces an existing
       entitlement of the representative.<br>
       The entitlement of a representative shall fail in case the provided notification mail address is not yet
       associated to the representative's kvnr (case-insensitive comparison) and exceeds the
       mail address limit (maximum: 10) of the representative.

       | Conditions | Status code | Error code | Remarks |
       |------------|-------------|------------|---------|
       | Successful operation | 201 |||
       | Request does not match schema | 400 | malformedRequest ||
       | Requestor has no valid entitlement | 403 | notEntitled ||
       | Requestor role is not _oid_versicherter_ | 403 | invalidOid ||
       | HSM verification failed | 403 | invalidToken ||
       | Health record does not exist | 404 | noHealthRecord | _insurantid_ unknown |
       | Health record is not in state ACTIVATED | 409 | statusMismatch | (see 'Retry interval') |
       | request claims _actorId_ which is _actorId_ of a static entitlement | 409 | invalidActorId ||
       | request claims _actorId_ == kvnr (_oid_ == oid_versicherter) and _validTo_ is not equal 9999-12-31T00:00:00Z | 409 | requestMismatch ||
       | request claims _oid_ == oid_diga and _validTo_ is not equal 9999-12-31T00:00:00Z | 409 | requestMismatch ||
       | request claims _actorId_ and _actorId_ is referenced by a Blocked User Policy assignment | 409 | blockedActorId ||
       | request claims  _actorId_ == kvnr (_oid_ == oid_versicherter) and requestor is not insurant| 409 | requestMismatch ||
       | request claims  _actorId_ == kvnr (_oid_ == oid_versicherter) and _email_ is not in request| 409 | noMail ||
       | request claims  _validTo_ which is not equal or in the future of current date| 409 | requestMismatch ||
       | representatives mail address exceeds representatives mail address limit | 409 | limitExceeded | if already 10 or more different mail addresses are stored for the representative |
       | Any other error | 500 | internalError | (see 'Retry interval') |

...