Browse and search developer information

Store and Notify

Pattern Description


When a new or updated piece of information (or document) is created, the Document Source sends the document into a Document Repository. The Document Repository then sends out notifications to inform other parties that new or updated information is available.

Document Consumers would then be able to store a “pointer” to the information, and add a flag to the appropriate patient record to indicate that the information is available. The Document Consumer may then retrieve the document electronically, either immediately or at some point in the future when it is required to display to a user. Where a Document Consumer cannot request the document from the repository for some reason, a click-through could be used to facilitate access to the information in the Document Repository.

In some cases the Document Source and Document Repository may be the same system. Subscriptions for notifications may be simple configuration in the Document Repository, but a more sophisticated subscription mechanism (e.g. allowing Document Consumers to directly subscribe to specific “topics”) would allow more flexible use and management of notifications.


  • Proactive: Systems subscribed for updates find out immediately when information changes
  • Allows for varying levels of maturity in Document Consumers – at its most basic a consumer could simply add a flag to indicate information exists with contact details. Migration to click-through, and electronic retrieval can follow.


  • In order to scale beyond a few systems, some form of subscription mechanism would need to be put in place.
  • Would only scale beyond a single health community if subscriptions were managed nationally (no national solution at present for this).
  • Does not provide a mechanism to find information for those not already subscribed to notifications.