Query HealthTechnical WG Update

1/12/2011

Agenda

Topic Time Slot

Administrative stuff and reminders 2:00 – 2:05 pm

Specification Updates• QRDA• HQMF• Query Envelope

2:05 – 2:30 pm

RI Updates and Plugin Design Discussion

2:30 – 3:00 pm

Administrative Reminders

• None

QRDA++ Specification Update

• Srinivas Velamuri has volunteered to help us with the QRDA Specification

• Has worked with the QRDA spec as part of the CMS Activities

• Has published article in the Journal for Health Information Management

• http://www.himss.org/content/files/jhim/24-3/11_VELAMURI.pdf

• Examine the existing standard

• Represent sample query results in QRDA standard

• Start Identifying changes or modifications required for the existing standard to represent results for Query Health

HQMF++ Specification Update• HL7 Project Scope statement drafted

• Collected the changes Identified by Keith Boone and Marc Hadley

• Coordination with NQF / CMS ongoing

• Presenting the information to HL7 to get project approved for balloting the next version with changes required for Query Health

• Proposed HQMF Changes • http://wiki.siframework.org/Query+Health+-+Query+Format

• Please provide comments on the proposed changes.

• Keith B continuing work on HL7 schema updates for the changes

Query Envelope Specification Update • Query Envelope Specification

• PopMedNet reviewed the Plug-in design with hQuery and i2B2

• Starting point for the Query Envelope specification• Planning to have more focused deep dives on the internal PopMedNet Portal to

Data Client communication to document the meta data.

RI Update• Plugin design review completed

• Plugin document to be published tomorrow for consumption

• Working out the details of integration between hQuery / i2B2 and PopMedNet based on the Plug-in design

• PopMedNet v2.0 uploaded to repository• File > 220 MB and is causing download problems with regular synchronization of the

Trunk

• Planning to make it available through the downloads tab (There is a file limit of 200 MB) • Working on splitting it up and uploading the version.

Reference Implementation Top Level Components

PMN Request / Response Workflow Pipeline

Model Plugin Host

InternetHTTPS

PMN Web Portal Application PMN DataMart

Model Data Store

ModelPluginWeb

Services

RequestLibrary

DataMartSelector

RequestApproval

DataMartRouter

DataMartWeb

Services

ModelPluginWeb

Services

ResponseLibrary

ResponseApproval

DataMartStatus

DataMartResponseHandler

DataMartWeb

Services

PMN Web Server Request

QueueRequestApproval

Request Processor

ResponseUpload

ResponseApproval

ResponseProcessor

PMN DataMart ClientModel

ProcessorInterface

RequestDeserializer

RequestProtocol

Translator

RequestProcessor

ModelProcessorInterface

ResponseSerializer

ResponseProtocol

Translator

ResponseGenerator

PMN Plugin Model Processor

PMN Data Store

InternetHTTPS Firewall

REQUEST TUNNEL

REQUEST TUNNEL

RequestBuilder

DataMartFilter

Request Serializer

ResponseViewer

ResponseAggregator

ResponseDeserializer

Model Plugin Host

PMN Request / Response Workflow Pipeline

Model Plugin Host

InternetHTTPS

PMN Web Portal Application PMN DataMart

Model Data Store

ModelPluginWeb

Services

RequestLibrary

DataMartSelector

RequestApproval

DataMartRouter

DataMartWeb

Services

ModelPluginWeb

Services

ResponseLibrary

ResponseApproval

DataMartStatus

DataMartResponseHandler

DataMartWeb

Services

PMN Web Server Request

QueueRequestApproval

Request Processor

ResponseUpload

ResponseApproval

ResponseProcessor

PMN DataMart ClientModel

ProcessorInterface

RequestDeserializer

RequestProtocol

Translator

RequestProcessor

ModelProcessorInterface

ResponseSerializer

ResponseProtocol

Translator

ResponseGenerator

PMN Plugin Model Processor

PMN Data Store

InternetHTTPS Firewall

REQUEST TUNNEL

REQUEST TUNNEL

RequestBuilder

DataMartFilter

Request Serializer

ResponseViewer

ResponseAggregator

ResponseDeserializer

Model Plugin Host

Plugin Web Service /

Registration

Plugin IModelProcessor

Develop Website Components

• Compose web pages that encapsulate the query building process• Add logic to decrypt PMN authentication tokens• Subscribe and implement PMN plugin web service API• Optionally add logic to filter DataMarts based on metadata• Format plugin registration XML

Develop DataMart Components

• Create a .NET project that produces a DLL using .NET 4• Implement the IModelProcessor interface used to process requests and return responses• Optionally create a response document that be used to display the response to the user (DataMart Administrators, Investigators, Group Administrators, etc.)• Create a deployment project to install the model processor at DataMarts

Register Plugin with PMN

• Create a plugin registration XML file containing the following items• “Create Request” URL that contains a substitution parameter to be inserted for the PMN Request Token• “Retrieve Response” URL that contains a substitution parameter to be inserted for the PMN Response Token• Public key of your asymmetric cryptographic key (the private key remains at the plugin’s site)• An entry for each Request Types, each having a user-friendly name and a unique identifier within the plug• Optionally designate one of the Request Types as a metadata request used to filter DataMarts• Metadata (such as plugin name, website, e-mail, etc.)

Next Steps

• Continue with the RI and Specification Activities• Soliciting volunteers who are experienced in R-MIM’s and XML/XSLT to help with

some of the upcoming tasks

• Volunteers who can represent queries using the proposed HQMF

• Provide comments on the Proposed changes for HQMF

• Soliciting volunteers for the QRDA Work stream

• Volunteers requiring access to the code repository• Please sign up for a google account at http://code.google.com• Project Repository - http://code.google.com/p/query-health/ • Sign up for the RI at http://

wiki.siframework.org/Query+Health+Reference+Implementation