SCOOP Design

SCOOP is designed as a distributed research network for primary care. By that we mean that instead of aggregating data in a central repository, we keep patient data distributed near the point of care systems (e.g. near the EMR, in the physician offices). Data is replicated from the EMR to the end point and that application sits behind the clinical firewall. It can be queried to provide answers to reflective questions from a trusted Network Hub.

T he practitioner has control over what questions are responded to by the end point and can use a “Local Reflector” component to perform queries on their own end point. The local reflector can use existing / shared queries from the hubs or ad hoc queries can be generated. A key difference of the local reflector is that the practitioner can also get list of patients – this is not possible from the Hub.

Simple Architecture Sketch

There will be multiple End Points and one or more network hubs in a given network. A network hub can ask multiple questions and support multiple questioners (not shown). Questioners can also be practitioners, of course.

In a more fulsome picture, the whole network could look like:

Where we have multiple, nested hubs and end points (the Xs) that can be connected to the hubs in various ways based on the preferences of the end points.

Leave a Reply

Your email address will not be published.