Comment:

FHIR Messaging architecture doesn't define a publish subscribe model on top of resources, and should. Subscriptions should take one or more events to subscribe to, an additional set of criteria to filter events, and optionally, a callback URL to execute when events occurred. Servers could respond with a URL to query for notifications, if the POST-based framework isn't sustainable.