Child pages
  • New 2013 Architecture Initiatives with RWIT
Skip to end of metadata
Go to start of metadata

The following is a list of six new initiatives for collaboration between RWIT and OIT Architecture identified by Tim Morris and Steve Wheat in February 2013. This list should be reordered with the highest priority items first and a detailed overview and design page should be provided for each initiative.

Lab Specimen Integration (priority: high)

RWIT needs to replace batch imports of instrument data that presently do not work well. Presently there are some batch processes provided with the Nautilus LIMS that pick up instrument feeds and process them to create [describe what they create] in the LIMS. [Someone describe the problems with the existing batch feeds].

The planned replacement is a web application that allows lab staff to upload instrument feeds and then submit them to the the LIMS using Emory's ESB/SOA infrastructure.

Vocabulary Service (priority: high)

The Lab Specimen Integration mentioned above and others require data from the the RWIT vocabulary service to validate data and present valid values to users. This data exists and is managed in a central database, but this database has not been exposed to other applications using Emory's ESB/SOA infrastructure. We need to expose this data as an ESB service.

Jasper Report Service (priority: high)

Emory needs a report development library and service for its applications. Given Emory's commitment to Java, the open-source, java-based Jasper Reports is a prime candidate for a relatively low-cost and manageable reporting library and service. Most urgently, RWIT needs a report service for [Tim, describe the most urgent application need with some details and timeline].

One important question to consider is why not use the Oracle reporting tools Emory has licensed as part of its Business Intelligence (BI) project. The short-term answer is that Emory is not licensed to use these Oracle tools for many of the applications for which we need reports and that using these tools is often unwieldy for smaller project at least until an organization becomes experienced and proficient with them. The long-term answer is that if Emory implements Jasper Reports as a reporting service and accesses it from within its applications using Emory's ESB/SOA infrastructure, there is no reason why Emory could not use both Jasper Report and Oracle tools to develop and provide these reports.

HIPAA Audit Logging for Reports (priority: medium)

The HIPAA Audit Logging Service presently supports creation of a single HIPAA Audit Log Entry in request/reply or pub/sub modality. In order to effectively log ePHI access for reports that return thousands of records, the auditing application will either have to provide a single entry describing the requested report (which may not be reproducible) or create thousands of HIPAA Audit Log Entries. We should add support to the HIPAA Audit Logging Service to accept a list of any number of HIPAA Audit Log Entries at once in request/reply or pub/sub modality and test for performance.

Subject Registration Service (priority: ?)

Receive a file from and external resource consortium to create master patient participant identities (MPPI Service) and research subjects in Emory systems (such as Redcap and LIMS). We should discuss whether or not receiving a file is the only modality the research consortium can support or if they can interact with web service facades we provide. Either way, we should be able to implement this with Emory's ESB/SOA infrastructure.

Yerkes Data Export (priority: ?)

The University of Georgia needs a way to request data sets from a combined data source (such as LIMS, Redcap, and instrument analysis). We will have more collaborations like this in the future.

This sounds like a web service, perhaps even the reporting service described above, in which UGA is granted access to request specific reports with specific parameters. If this meets the requirements, we could develop a Jasper report to meet this need and handle the requests and deliver the reports using the same reporting service described above. Alternately, we could create an ESB service specific to this report and these data sources and expose it to UGA as a web service.

  • No labels