Iteration 0 Architecture

This wiki page describes the architecture for Iteration0 of the SCOOP project. The goal of this iteration is to explore the proposed components, familiarize ourselves with them, and ensure that they will work together.

Context

This iteration is being deployed to a laboratory environment (non production). All components reside "virtually" in the same location. Meaning we've abstracted certain security controls from the design (e.g. traversing firewalls).

There is only one practice being simulated in this iteration. (i.e. one endpoint).

Logical View

In the context of the system it is noteworthy that there are no new software applications being developed. Each component illustrated in this section is an existing Open Source product.

SCOOP Hub This is the application that the researcher uses to ask a "question" of the Research Network. Anticipated that this hQuery Composer will be this component.

SCOOP Gateway This application holds patient information in a structure that is able to be queried. It then receives, interprets, and responds to requests from the SCOOP Hub. Expected that hQuery Gateway will be this component.

ETL Tool On a nightly schedule, extracts information from the EMR, transforms it into a standard structure, and sends it to the SCOOP Gateway component. We are evaluating Mirth Connect for this purpose.

EMR The point of care system that the provider uses. For this and subsequent iterations this will be OSCAR.

Constraints

Privacy Individual information never leaves the practice. Early feedback from discussions with the faculty physicians UBC highlighted their stewardship of patient information as a serious matter. There’s a genuine concern that anonymous data collected may be used for unintended research purposes in the future. Several are concerned by the risks of data aggregation, even when the data is de-identified.

Open Source As SCOOP development is sponsored with public funds it will be released as open source for any one to use. In addition, SCOOP will only rely on free, open source components so that its use is accessible to any individual/group.

Design View

Data View

Technology Section

OSCAR An Open Source EMR system used by many private physicians. This is way that individual information is captured - and the user interface for the physician practitioner end user.

Mirth Mirth is an open source interfacing system. It acts as generic middleware between many healthcare software systems and connects them via HL7 messages (although several formats / protocols are supported).

Mirth Rest Adaptor This is an open source piece of middleware developeed by the SCOOP project. Mirth does not fully support restful web services. Specifically it does not allow naming of attachments to web service calls. For this reason, hQuery gateway cannot find the patient summary document when Mirth calls it directly. This component can be thought of as a restful web service relay that renames a single attachment (patient summary document) before forwarding the call.

hQuery Gateway The query gateway is a web based application that provides the back end for executing queries. The query gateway which exposes a query API, accepts queries, runs those queries against the patient data, and returns the results of the query back to the query composer.

hQuery Composer The query composer is a web based application that provides the front end for creating, managing, and executing queries. Those queries are executed against the query gateway which exposes a query API, accepts queries, runs those queries against the patient data, and returns the results of the query back to the query composer.

Scoop Endpoint refers to all the non-emr SCOOP software components that will reside at a practice in the future. This indludes hquery gateway, Mirth, and Mirth Rest adapter.

SCOOP Hub This is the application that the researcher uses to ask a "question" of the Research Network. This includes features for query management, policy enforcement, privacy management, and security. Currently, hQuery composer is the only software system in the hub - but more design and enhancements are needed.

• Libraries: template