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