Using UN/CEFACT'S Modelling Methodology in e-health projects

504 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
504
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Using UN/CEFACT'S Modelling Methodology in e-health projects

  1. 1. Using UN/CEFACTs Modelling Methodology in e-health projects Pablo García Sánchez , J. González, P.A. Castillo and A. Prieto Dept. of Computer Architecture and Computer Technology University of Granada IWANN 2009
  2. 2. Index <ul><li>Introduction and state of the art </li></ul><ul><li>Introduction to UMM </li></ul><ul><li>How to use it in a big e-health project? </li></ul><ul><li>Conclusions </li></ul>
  3. 3. Technologies <ul><li>Simply WS </li></ul><ul><li>Simply interaction </li></ul><ul><li>Consumer oriented </li></ul><ul><li>“ Light” processes </li></ul><ul><li>Not business collaboration </li></ul><ul><li>Not partner profile </li></ul><ul><li>Not secure, not reliable </li></ul><ul><li>Non-repudiation unsopported </li></ul><ul><li>Not repository support </li></ul><ul><li>Service approach </li></ul><ul><li>Bottom-up modelling </li></ul><ul><li>B2B collaboration (ebXML)‏ </li></ul><ul><li>Complex interaction </li></ul><ul><li>Business oriented </li></ul><ul><li>“ Heavy” processes </li></ul><ul><li>Business collaboration </li></ul><ul><li>Partner profile </li></ul><ul><li>Secure, reliable </li></ul><ul><li>Non-repudiation support </li></ul><ul><li>Registry and repository </li></ul><ul><li>Contract-based approac h </li></ul><ul><li>Top-down modelling </li></ul>
  4. 4. Methodologies <ul><li>BCM (Business-Centric Methodology)‏ </li></ul><ul><li>Developed by OASIS (creators of BPEL or UDDI)‏ </li></ul><ul><li>It is a set of model layers, a step-guide process, and an information pyramid to align the semantic information of partners. </li></ul><ul><li>It has a very large learning curve and it is not very extended yet. </li></ul><ul><li>SOMA </li></ul><ul><li>Proposed by IBM </li></ul><ul><li>It lets the identification, specification and implementation of services inside the SOA paradigm. </li></ul><ul><li>Top-down modelling oriented to intra-enterprise services (service-oriented instead of business-oriented). </li></ul>
  5. 5. UMM <ul><li>UN/CEFACTs Modelling Methodology (UMM) models the business services that each partner must provide in order to perform a B2B collaboration. </li></ul><ul><li>Developed by the United Nations Centre for Trade Facilitation and Electronic Business </li></ul><ul><li>Independent of the underlying implementation technology (ebXML, Web Services, CORBA or EDI). </li></ul><ul><li>Extends UML: more easily adaptable, due to the high development, acceptance and maturity of UML. </li></ul>
  6. 6. Using UMM in a big e-health project (AmIVital)‏ <ul><li>Objective : develop a new generation of technology and information tools to model, design and implement an Ambient Intelligence (AmI) platform to support the independent life, welfare and health of its users. </li></ul><ul><li>Funded by the Spanish Ministry of Commerce, inside the CENIT program, with a grant of more than 20 million euro. </li></ul><ul><li>Several institutions creates functional services that have to be choreographed, and many different technologies must be integrated, so UMM is proposed. </li></ul>
  7. 7. UMM Views <ul><li>Business Domain View: discover collaborative business processes using interviews and worksheets </li></ul><ul><li>Business Requirements View: identify the workflow of the business processes, business entities and their lifecycles and transactions. </li></ul><ul><li>Business Transaction View: describes the whole choreography, the interactions and the exchanged information between business partners. </li></ul><ul><li>Business Service View: details the composed services, the agents, and the necessary data interchange in the language and technical concepts of the software developers (i.e. BPEL or BPSS). </li></ul>
  8. 8. Business Requirements View (Business Process View)‏
  9. 9. Business Requirements View (II) <ul><li>Entity view </li></ul>Transaction requirements view
  10. 10. Business Transaction View (I)‏ <ul><li>Business Choreograpy View </li></ul>
  11. 11. Business Transaction View (II)‏ <ul><li>Business Interaction View </li></ul>
  12. 12. Conclusions and future work <ul><li>A common modelling methodology is mandatory within a wide inter-organizational research project. </li></ul><ul><li>As a proof of concept, UMM has been used to model a simple e-health business process, where several systems collaborate in an intelligent way with the user. </li></ul><ul><li>We have used UMM due to: </li></ul><ul><ul><li>Its growing usage in the development of B2B applications </li></ul></ul><ul><ul><li>Its learning curve is not very large </li></ul></ul><ul><ul><li>There exist completely functional tools to create and validate the models. </li></ul></ul><ul><li>UMM is not only diagrams! </li></ul><ul><li>Future work: </li></ul><ul><ul><li>Addapt to the new UMM 2.0 specification... </li></ul></ul><ul><ul><li>... and extending its usage to other e-health services, as telecare, medication management and domotic services among others. </li></ul></ul>
  13. 13. <ul><li>Thank you! </li></ul><ul><li>[email_address] </li></ul>

×