>What is a context change? Is this context as in scratchpath in Smart Messaging? FHIRcast is explicitly designed to be a healthcare context synchronization specification. The vast majority of the real-world use-cases for context synchronization in healthcare revolve around multiple, disparate applications showing the same patient to the same user at the same time. A context change is, for example, the user selecting a different patient than what's currently shown.  First and foremost, this is the need that FHIRcast should solve. SMART Messaging's concept of a scratchpad is more akin to exposing a CRUD API through web messaging, than context sync.  Further, web messaging is an inherently limited communication protocol designed explicitly for web apps.