M POWER

1. M POWER Middleware platform for eM•POWERing cognitive disabled and elderly Ståle Walderhaug & Marius Mikalsen University in Tromsø & SINTEF ICT stalew@{cs.uit.no | sintef.no} & marius.mikalsen@sintef.no

2. The Successful Development of a Smart HomeCare System • Requires Standardisation • Interfaces • Operations • Messages • Reuse of Services and Components • Not reinvent the wheel • Share resources and save money • Development • Maintenance • Upgrade • Collaboration with End Users and Technology Experts • Do the right things right

3. Service Oriented Middleware • How can we identify which services that are needed? • From User-defined System FEATURES • How can we implement these services effectively and conform to standards? • Model-Driven Development • Integrate Standards in Transformation and Generation processes

4. The Challenge being Addressed • Increased number of older people • Increased number of cognitively disabled • Improved patient safety • Restricted information security regulations • Heterogeneous user groups • Increased care and treatment costs • Distributed family • Increased demands

5. Finding User Needs

6. Scenarios - UseCases - Features Middleware Services

7. Problem and Activity Scenario (example)

8. Use Case (calendar scenarios)

9. Features

10. Development of Information Systems for Smart-Home-Care • Common Problem: • Need to integrate/inter-connect (read and write access) several information sources • Individual Plan • Medication list • Automation devices (water, gas, doors, lighting, heating, motion detection,…) • Education material • No common ”application programming interface (API)” available • Syntactical and semantical interoperability issues

11. Common Solution: • Write adapter / wrappers to each ”information source” • Integration done in application / user session layer • Standards are not used – quick and dirty approach.

12. Common Solution Problem • Requires much resources • A change in underlying information source requires changes in many higher level services/components • Reusability (and documentation) is poor

13. Proposed Solution Model-Driven Development of Service-Oriented Standards-Based Middleware Components

14. Model-Driven Development • Use Formal Models to represent all artefacts • Use Model-Transformation to create Platform Models • Use Code Generation to create Executable Code

15. SOA (in MPOWER)

16. Standards • HL7v3 is the chosen messaging standard in MPOWER • All communcation will be based on HL7 v3 RIM • Service to Service • Business Service to Service • Application to Service • MPOWER Interoperability Services will transform from other standards • Pilot System: KITH Dialog messages to HL7

17. How can we develop services effectively and (still) adhere to standards? • Model-Driven Software Development • Use formal specifications in UML (SOA UML Profile) • User Scenarios, UseCase, Features • Specify Services in Platform Independent Models (PIM) • Interfaces, Operations, Messages • Transform to WSDL (Web Service Description Language) Models • Generate WSDL code • Generate Web Services • (Manually) Implement Web Service behavior • Deploy and Test WebServices

19. Service Modeling (from SOA4HL7)

20. Identify Service

21. Identify and Describe InterfacesIdentify and Describe Operations

22. Identify and Describe Messages (HL7) New Medication Request For Patient (POME_HD011000UV01)

23. Model-Transformation:Generate WSDL Model

24. Generate WSDL Code

25. Generate Web Service

26. Deploy and Generate Tests

27. The Successful Implementation of a Smart HomeCare System • Requires Standardisation • Interfaces • Operations • Messages • Reuse of Services and Components • Not reinvent the wheel • Share resources and save money • Development • Maintenance • Upgrade • Collaboration with End Users and Technology Experts • Do the right things right

28. The Consortium

29. Time and costs • The project runs from October 2006 – April 2009 (30 months) • The total budget of the project is 4.3 mill €

30. Project Objectives • M•POWER will create a middleware platform enabling rapid development and deployment of services for cognitive disabled and elderly. • Two proof-of-concept applications will be developed to guide and support the middleware platform development: • A collaborative environment for distributed and shared care, providing requirements for information security, information models, context awareness, usability and interoperability. • A SMART HOUSE environment, providing requirements for information security, information models and usability

31. Project approach • Combining Agile Software Development (ASD) and Model Driven Architectures (MDA) to facilitate high level of interaction between members of the development teams (middleware and proof-of-concept) and the end-users. • The approach includes the following elements: • MPOWER Framework for Service Development • MPOWER Platform for Service and System Integration • MPOWER Proof-of-Concept Applications • User trials

32. Norwegian Pilot • A collaborative environment for distributed and shared care, providing requirements for: • information security • information models • context awareness • Usability • interoperability

33. Polish pilot • Smart-house environment faciliating environment and patient monitoring and control • Heathing • Oven • Water • Doors • Light

34. Thank you for listening • Ståle Walderhaug: stalew@{cs.uit.no | sintef.no} • Tromsø, Norway • Marius Mikalsen (Project Leader): marius.mikalsen@sintef.no http://www.mpower-project.eu