Integration of information systems
Topics <ul><li>Here we explore practices of national level system integration. Also explore differences between internatio...
Cross-organizational  work-flow
Legacy problems <ul><li>Not just a different data and formats: </li></ul><ul><ul><li>Unfamiliar platforms -> lack of devel...
Integration nightmare
Options for integration <ul><li>Network level – Secured channels: </li></ul><ul><ul><li>VPNs, sTESTA  </li></ul></ul><ul><...
Technical aspects <ul><li>Technological issues: </li></ul><ul><ul><li>Architecture of integration framework </li></ul></ul...
Common Data models <ul><li>In the process, system interfaces account for 25% to 70% of the development and support costs. ...
Enterprise Service Bus
Organizational aspects <ul><li>Legal requirements (national level) </li></ul><ul><li>Obligations and responsibilities of I...
National level Case: Estonia 13 April 2010 www.ega.ee 550 org. 5  110 DB  ~ 400 000 ~ 45 000 500 DB 1,100,000
International level (epSOS) <ul><li>Smart Open Services for European Patients </li></ul><ul><ul><li>Project aimed to devel...
epSOS <ul><li>Analysis of MS technical solutions, legal requirements </li></ul><ul><li>Defined epSOS system technical requ...
epSOS
 
epSOS – semantic content workflow
Pains <ul><li>International regulations </li></ul><ul><li>Missing technical standards </li></ul><ul><li>Time consuming pro...
Upcoming SlideShare
Loading in...5
×

Integration of information systems

361

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
361
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Integration of information systems

  1. 1. Integration of information systems
  2. 2. Topics <ul><li>Here we explore practices of national level system integration. Also explore differences between international level system integration and national (local) system integration. </li></ul>
  3. 3. Cross-organizational work-flow
  4. 4. Legacy problems <ul><li>Not just a different data and formats: </li></ul><ul><ul><li>Unfamiliar platforms -> lack of development competence </li></ul></ul><ul><ul><li>Strange interfaces / protocols </li></ul></ul><ul><ul><li>Business rules hard-coded to UI level </li></ul></ul><ul><ul><li>Missing documentation </li></ul></ul><ul><li>High integration expenses – every time when something must be fixed. </li></ul>
  5. 5. Integration nightmare
  6. 6. Options for integration <ul><li>Network level – Secured channels: </li></ul><ul><ul><li>VPNs, sTESTA </li></ul></ul><ul><ul><li>+ secure communication between authenticated parties </li></ul></ul><ul><ul><li>? Multiple protocols, data formats, point-to-point integration </li></ul></ul><ul><li>Protocol level – all parties use standard protocols: SOAP, XML, or as agreed. </li></ul><ul><li>Message/data level – standardized data formats and classification, interactions. </li></ul>
  7. 7. Technical aspects <ul><li>Technological issues: </li></ul><ul><ul><li>Architecture of integration framework </li></ul></ul><ul><ul><ul><li>Interfaces </li></ul></ul></ul><ul><ul><ul><ul><li>Protocols </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Interactions </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Message formats and transformations </li></ul></ul></ul></ul><ul><ul><ul><li>Routing </li></ul></ul></ul><ul><ul><ul><li>Transformation </li></ul></ul></ul><ul><ul><ul><li>Services repository – addresses, descriptions </li></ul></ul></ul><ul><ul><li>Semantic integration </li></ul></ul><ul><ul><ul><li>Semantic descriptions of services </li></ul></ul></ul><ul><ul><ul><li>Use of common data models </li></ul></ul></ul>
  8. 8. Common Data models <ul><li>In the process, system interfaces account for 25% to 70% of the development and support costs. </li></ul><ul><ul><li>The primary reason for this cost is that these systems do not share a common data model. </li></ul></ul><ul><li>Some common data models in use: </li></ul><ul><ul><li>Health: HL7 (Health Level 7) </li></ul></ul><ul><ul><ul><li>Differences between v2 and v3.! </li></ul></ul></ul><ul><ul><li>Retail: ARTS </li></ul></ul><ul><ul><li>Telecom.: SID </li></ul></ul><ul><ul><li>Human resources: HR-XML </li></ul></ul>
  9. 9. Enterprise Service Bus
  10. 10. Organizational aspects <ul><li>Legal requirements (national level) </li></ul><ul><li>Obligations and responsibilities of IS owners (between e-services providers and users) </li></ul><ul><li>Change of work processes </li></ul><ul><li>Standards to be used </li></ul><ul><li>Importance of co-ordination bodies, responsible for: </li></ul><ul><ul><li>Development of standards </li></ul></ul><ul><ul><li>Coordination of tests </li></ul></ul><ul><ul><li>Support of developers </li></ul></ul>
  11. 11. National level Case: Estonia 13 April 2010 www.ega.ee 550 org. 5 110 DB ~ 400 000 ~ 45 000 500 DB 1,100,000
  12. 12. International level (epSOS) <ul><li>Smart Open Services for European Patients </li></ul><ul><ul><li>Project aimed to develop a practical eHealth framework and an Information & Communication Technology (ICT) infrastructure that will </li></ul></ul><ul><ul><ul><li>enable secure access to patient health information, </li></ul></ul></ul><ul><ul><ul><li>Exchange of Patient Summaries and </li></ul></ul></ul><ul><ul><ul><li>ePrescriptions between different European healthcare systems. </li></ul></ul></ul><ul><li>http://www.epsos.eu </li></ul>
  13. 13. epSOS <ul><li>Analysis of MS technical solutions, legal requirements </li></ul><ul><li>Defined epSOS system technical requirements for exchange of prescriptions and Patient Summaries (interoperability) </li></ul><ul><li>Semantic services – common document structures, translations (SNOMED-CT, ICD10 classifications) preserving content and structure of original documents </li></ul><ul><li>Tests and pilots </li></ul>
  14. 14. epSOS
  15. 16. epSOS – semantic content workflow
  16. 17. Pains <ul><li>International regulations </li></ul><ul><li>Missing technical standards </li></ul><ul><li>Time consuming process to reach a mutual agreements. </li></ul><ul><li>Importance of central body, responsible for development of standards and technical support for developers </li></ul><ul><li>Testing period might take a x5 longer. </li></ul>

×