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" through an EMR Adaptor. A Local Reflector would allow the practitioner the ability to query their own End Point, leveraging the data design to ask more complex questions than could be asked through the EMR. Those components sit behind the clinical firewall. It can be queried to provide answers to reflective questions from a trusted Network Hub. The key differences between the Local Reflector and the Network Hub are:

• the hub cannot access / respond with patient specific information where as the Local Reflector can provide patient specific lists TO THE PRACTIONER ONLY.
• the hub can query multiple pracitces, the Local Reflector can only query its own local end point.

Visually, it could look like this:

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

In a more fulsome picture, a 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.

see also system architecture.