pervasive software interoperability for the operating room of the future may 10, 2005

26
Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Upload: gwenda-wilcox

Post on 31-Dec-2015

218 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Pervasive software interoperability

for the Operating Room of the Future

Pervasive software interoperability

for the Operating Room of the Future

May 10, 2005May 10, 2005

Page 2: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

UMBC UMBC• The University of Maryland

Baltimore County • One of the three research campuses

in the University of Maryland System• Ranked in top tier of nation's research universities--

Doctoral/Research Universities-Extensive -- by the Carnegie Foundation

• Has 500 full time and 335 part time faculty, 10K undergraduate and 2K graduate students

• Located in suburban Baltimore County, between Baltimore and Washington DC.

• Special focus on science, engineering, information technology and public policy with ~$80M in external research funding in 2003

Page 3: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

IT @ UMBCIT @ UMBC• Information Technology has UMBC’s

largest concentration of faculty & students• Over 100 faculty and more than 2500 students

• College of Engineering and Information Technology• Degree programs (graduate and undergraduate)

• Computer Science, Computer Engineering, Information Systems, Electrical Engineering, Digital Imaging, and Systems Engineering

• Certificate and training programs (degree and non-degree)• Bioinformatics, Electronic Government, Information Security,

Web Development, Systems Administration, Oracle, CISCO, …

• Many institutes and centers• Center for Women and Information Technology, Center for

Information Security and Assurance, Bioinformatics Research Center, Center for Photonics, …

Page 4: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

UMBC Ebiquity Research Group

UMBC Ebiquity Research Group

IntelligentIntelligentInformationInformation

SystemsSystems

NetworkingNetworking& Systems& Systems SecuritySecurity

AIAIDBDB

semanticsemanticwebweb

mobilitymobility

pervasivepervasivecomputingcomputing

trusttrust

privacyprivacy

assuranceassurance

web services/SOCweb services/SOC

userusermodelingmodeling

wirelesswireless

data mining

machinemachinelearninglearning

knowledgeknowledgemanagementmanagement

KRKR

intrusionintrusiondetectiondetection

contextcontextawarenessawareness

policiespolicies

IRIR

wearable computingwearable computing

DRMDRM

HPCCHPCC

Page 5: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Building Building intelligent intelligent

systems in open, systems in open, heterogeneous,heterogeneous,

dynamic, dynamic, distributed distributed

environmentsenvironments

Building Building intelligent intelligent

systems in open, systems in open, heterogeneous,heterogeneous,

dynamic, dynamic, distributed distributed

environmentsenvironments

Page 6: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Human Evolution?Human Evolution?

ubiquitous, pervasive computing services must

adapt to homo sapiens and their environments

ubiquitous, pervasive computing services must

adapt to homo sapiens and their environments

Page 7: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Pervasive ComputingPervasive Computing““The most profound technologies are those The most profound technologies are those that disappear. They weave themselves that disappear. They weave themselves into the fabric of everyday life until they into the fabric of everyday life until they are indistinguishable from it are indistinguishable from it ” – Mark ” – Mark WeiserWeiser

Think: writing, central heating, electric lighting, plumbing, telephones …

Not: taking your laptop to the beach, sending SMS messages on your cell phone or immersing yourself into a virtual reality

Page 8: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Today life is still simpleToday life is still simple

Page 9: Pervasive software interoperability for the Operating Room of the Future May 10, 2005
Page 10: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

But it’s getting complicated!But it’s getting complicated!

Page 11: Pervasive software interoperability for the Operating Room of the Future May 10, 2005
Page 12: Pervasive software interoperability for the Operating Room of the Future May 10, 2005
Page 13: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Coordination can be automatic

Coordination can be automatic

Page 14: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

If systems become smarterIf systems become smarter

As complexity & expectations increase, As complexity & expectations increase, software & hardware systems must evolve to software & hardware systems must evolve to bebe•Self describing and self organizingSelf describing and self organizing•Able to negotiate for the services and Able to negotiate for the services and

resources Context aware and capable of resources Context aware and capable of adjusting their behavior as appropriateadjusting their behavior as appropriate

•Capable of adapting and learningCapable of adapting and learning•Able to communicate naturally with peopleAble to communicate naturally with people

Page 15: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

In the OR of the future, tooIn the OR of the future, too•Trauma Pod ‘06 will have arms and eyes but no brain•Trauma Pod ‘20 will need to be smarter and much

more aware

2005: da Vinci Surgical Robot 2005: da Vinci Surgical Robot 2005: da Vinci Surgical Robot 2005: da Vinci Surgical Robot 2020: Automated Trauma Pod treats wounded 2020: Automated Trauma Pod treats wounded

soldiers on the battlefield. soldiers on the battlefield. 2020: Automated Trauma Pod treats wounded 2020: Automated Trauma Pod treats wounded

soldiers on the battlefield. soldiers on the battlefield.

Page 16: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Three Key EnablersThree Key Enablers

Semantic interoperability

Greater context awareness and intelligence

Agents driven by policies and workflow

11

22

33

Page 17: Pervasive software interoperability for the Operating Room of the Future May 10, 2005
Page 18: Pervasive software interoperability for the Operating Room of the Future May 10, 2005
Page 19: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

How can we control such a system?

How can we control such a system?

•As we evolve to a system of semi-autonomous components, control is an issue•Self managing, self healing

•Norms of behavior can provide mechanisms for control (e.g. capture workflows, constraints, …)

•We need better ways of describing and using Policies which serve as norms of behavior

Page 20: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Policies Govern Autonomous Systems

Policies Govern Autonomous Systems

1 A robot may not injure a human being, or, through inaction, allow a human being to come to harm.

2 A robot must obey the orders given it by human beings except where such orders would conflict with the First Law.

3 A robot must protect its own existence as long as such protection does not conflict with the First or Second Law.- Handbook of Robotics, 56th Edition, 2058 A.D.

Page 21: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

It’s policies all the way downIt’s policies all the way down

•In Asimov’s world, the robots couldn’t always follow their policies•Unlike traditional “hard coded” rules like DB access control & OS file permissions

•We need policies about what happens when policies are not followed, …

•So, it’s natural to worry about …•How entities governed by multiple policies can resolve conflicts among them

•How to deal with failure to follow policies – sanctions, reputation, trust, etc.

•Whether policy engineering will be any easier than software engineering

1 A robot may not injure a human being, or, through inaction, allow a human being to come to harm.

2 A robot must obey the orders given it by hu-man beings except where such orderswould conflict with the First Law.

3 A robot must protect its own existence as long as such protection does not conflict with the First or Second Law.

- Handbook of Robotics, 56th Edition, 2058 A.D.

Page 22: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

An EasyMeeting ScenarioAn EasyMeeting Scenario

Alice enters a conference room

The broker detects Alice’s presence

B

Policy says, “can share with any agents in the room”

A

B

The broker buildsthe context model

Web

Alice “beams” her policy to the broker

B

Policy says, “inform my personal agent of my location”

AB .. isLocatedIn ..

Page 23: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

An EasyMeeting ScenarioAn EasyMeeting Scenario

Her agent informs the broker of her

role and intentions

+

The broker tells herlocation to her agent

A

The projector agent wants to help Alice

The projector agentasks slide show info.

B

The projector agent sets up the slides

The broker informsthe subscribed agents

B

Page 24: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

Enforcing Domain PoliciesEnforcing Domain Policies

Page 25: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

http://ebiquity.umbc.edu/http://ebiquity.umbc.edu/

Page 26: Pervasive software interoperability for the Operating Room of the Future May 10, 2005

http://ebiquity.umbc.edu/http://ebiquity.umbc.edu/