Liam Peyton – Researchlpeyton@uottawa .ca

A Framework for Instrumentation and Integration of Process Performance

Management

Objectives• enable data collection (via mobile forms, network aware

devices/sensors) to monitor business processes • Enable reporting (alerts, mobile, portal) to systems, managers and

workers so they can react to ensure quality, safety, security, compliance and improve business performance.

• Applications / Case Studies in healthcare (mostly) and Smart Cities (power management, next generation networks)

• Process Performance Management• Model• Architecture• Methodology

Projects• QuickForms Open Source Project

• https://code.google.com/p/quickforms3/wiki/QF3Introduction • AJAX controls, CSS Templating, Web-Based IDE, BI Integration, Rule Engine,

Complex Event Processing, RESTful DAO Service

• Build Applications for case study evaluation in organizations• Ottawa Hospital Family Health Team – Resident Practice Profile• Local Health Integration Network – Regional Palliative Care Dashboard• Community Care Access Center Ontario – port MS InfoPath forms• University of Ottawa

• Pregnancy Coach Application• Course Tracker

• Local Companies• Alternative Energy Power Manager (Smart FuseBox)• Electric Car – Charging Station Manager

Skills Needed

• Can do attitude, customer-oriented, agile prototype development• AJAX, Devices: Javascript, JSON, HTML 5, CSS, Cordova, Raspberry Pi• Business Intelligence

• Complex SQL Queries; Excel, Microsoft or Cognos BI reporting

• Qualitative / Quantitative Analysis - usability and case studies• Quality assurance – test plans and automation• Design Patterns, SOA, Virtualization and CEP

• C, Java or Python, RESTful and SOAP web services, message brokers, server administration, next generation virtualization

CASE Study I – Monitor Cardiac Patient Process

Application Snapshot

Enterprise Model

Performance Mode l

Process Model

-name-description-resourceAttributes

«Resource»

-name-description

«CareProcess»

-name : string-description : string-stateAttributes

«State»

-name-description-eventAttributes

«Event»

-name-description

«Source»

11..*

Generate4

-name-description

«Goal»

-name-description-computation-target

«Metric»*

1..*

3 Computed from1..*

*

3 Measured by

-name-description-condition

«Rule»

*

1..*

3 Computed from

1..*1..* 3 Has

1..*1Has4

1..*

1..* Has4

1..*

1

Has4

1

1..* 3 Has

-Subgoal*

1

-name-description-message

«Alert»

1

1..*

Current State4

0..1

1..* Next State4

1

0..*

Application Meta-Model

Case Study II – Mobile App for Family Medicine Residents

• Provide feedback to medical residents on their clinical experience• experience in all the types of patients and diagnoses covered by medical curriculum?

• Investigate the efficacy of mobile business intelligence (BI) apps• Would/could residents/doctors use them effectively?

• Traditional EMR• Does not have data that maps to curriculum

• Special populations (immigrant, mental health, homeless, first nations), • Diagnoses (OHIP code vs Family Health curriculum)• Self-Evaluation (more reading?, more cases?)

• Interoperability: technology, privacy issues, report creation & Delivery• Report creation and delivery?

• ** Develop QuickForms 3Framework to support lightweight Mobile app**• Dramatically reduce effort and skill level needed to create / maintain Business Process• “double entry” per patient visit limited to 30 second per visit, 10 minutes per day• Immediate relevant feedback in reporting• Who will build and maintain?

RPP Summary View

RPP Demographics Form and Related Report

Mapping Clinical Experience (Based on Medical Curriculum)

AppRule Engines

QuickForms 3 – Business Process Monitoring Framework

AppRules

AppTemplates

WidgetLibrary

Result• RPP Application

• Participatory Design – Action Research• Ottawa Hospital Family Health Team, 4 Medical Residents• Think Aloud Sessions

• Conceptualize family medicine diagnoses• Reporting feedback requirements• App complexity and ease of use <30 seconds

• QuickForms 3 Framework• J2EE 3,154 lines, complex, poor UI, form mapping• QuickForms 1.0, 4551 lines, Good UI, form mapping• QuickForms 3.0, 608 lines, Encapsulated controls, templates, configuration instead

of coding