FHIRNotificationService should emit event for patch update

[fsa1803]

Describe the bug
When patch a Patient resource no websocket event is triggered.

Environment
IBM FHIR Server : 4.9
Windows: 10
JVM: JRE 1.8.0_251

To Reproduce
Steps to reproduce the behavior:

1. Enable websocket notification
2. Open ws channel, I use Chrome Extension: "Web Socket Client"
3. Insert Patient resource
4. WS console show me the event:
   {"lastUpdated":"2021-08-17T11:01:15.307Z","location":"Patient/MPI0000000017/_history/1","operationType":"create","resourceId":"MPI0000000017","datasourceId":"default","tenantId":"default"}
5. Update gender:
   curl -s -H "Content-Type: application/json-patch+json;charset=UTF-8" -XPATCH https://localhost:9443/fhir-server/api/v4/Patient/MPI0000000017 -u fhiruser:fhiruser --insecure -d '
   [{ "op": "replace", "path": "/gender", "value": "male" }]
   '

Expected behavior
A notification for Patient update

[prb112]

Thank you for opening this @fsa1803

The default behavior is to do nothing with this notification.

    /**
     * This method is called during the processing of an 'patch' REST API invocation, immediately after the updated
     * resource has been stored by the persistence layer.
     * 
     * @param event
     *            information about the 'patch' event
     * @throws FHIRPersistenceInterceptorException
     */
    default void afterPatch(FHIRPersistenceEvent event) throws FHIRPersistenceInterceptorException {
    }

If this helps your use case, we'll implement these in the corresponding classes as outlined below.

FYI - this is a one pointer and needs minor updates. after the development team agrees to the appropriate behavior

[fsa1803]

Fine, this help my use case.

Thanks

[prb112]

Fine, this help my use case.

Thanks

OK, thanks, just testing the change now and will review with Lee

[d0roppe]

Tested this fully with the FHIRPath Patch path and seems to be issuing the correct notifications.