QIPP Digital Technology and ITK Care Co-Ordination: Interoperability WebEx4. 8 th November 2012

1. QIPP Digital Technology and ITKCare Co-Ordination: Interoperability WebEx4. 8th November 2012

2. WebEx • Overview of the Notification message scope • Example of a Notification use case • Event Types for Notification messages • There will then be time for questions and comments at the end. • During the WebEx all participants will be muted to avoid background noise • Discussion on this WebEx – either: • Use the “raise hand” and I will un-mute you so you can speak, or • Use the “chat” box to ask a question or make a comment • Please ensure you send it to “all” and not just the host! • The WebEx is being recorded, and a recording will be made available on the ITK NHS networks site after the session. http://www.networks.nhs.uk/nhs-networks/interoperability-toolkit-itk

3. Use cases for Notification Messages • Notification messages will be sent from the Author to the Recipients identified to inform them an Event has happened: • Document has been created/ updated • Patient has attended A&E • Patients address has been changed/updated • Patient has passed away • Notification messages should not be used for the following: • A transfer of care responsibility • Sharing clinical information regarding the patient • Receiving systems can be configured to handle these notifications: • Adding a flag or note against the patient's record • Adding a task to a user or team's work list or inbox • Actively notifying the user (either in the system or via SMS/email)

4. Notification Message Content

5. Scope of Notification Messages • High Level scope: • All recipients of the notification will be listed in the message • Recipient systems will be configurable to allow for different behaviours when a notification is received based on locally defined criteria. • Behaviours may include adding a flag, adding a note to a patient record, creating an item on a work list, or directly notifying a user. • The criteria used may include the event type, sender, or patient – allowing for notifications relating to different cohorts of patients to be treated differently. • An additional flag can be included in the message to indicate that the sender requires acknowledgement when a recipient has seen the notification. • This should only be used when absolutely necessary, and the exact criteria for this acknowledgement would need to be locally defined as there is insufficient clarity to define national requirements for this at this stage.

6. Use cases for Notification Messages • Example of the creation of a Record Recipient Systems EPaCCS System GP System Community System Ambulance System Acute System OOH System GP Care Preferences Notification Clinician John • The GP creates John’s EPaCCS record. Note: This is only an example!

7. Use cases for Notification Messages Note: This is only an example!

8. Event Types for Notification Messages • Event Types: • Notifying creation of a document • Notifying updates to a document • Notifying A&E attendance • Notifying change of address • Death notification • Sub Types, for example, Documents: • End of Life Care Coordination Information & Preferences • Long Term Conditions Personalised Care Plan

9. Notification Message • What we Propose: • Event types listed in this presentation will be rolled out for release 1- Any additional Event Types required will need to be requested by the 14th November 2012. • Acknowledgement flag- This will be subject to the author and the receiver having a prior agreement in place- the receiver will be given the option of sending an error if they are unable to verify receipt. • Get document- the Document Set ID can be used to retrieve the latest document available.