interoperability between e-health systems ECIIS 2010 Stockholm

Transcription

1 interoperability between e-health systems ECIIS 2010 Stockholm

2 Interoperability What is interoperability or technological integration? Let s have a look at the digital ecosystem! Looking beyond the technological perspective Technically speaking we have done pretty good in sticking to standards and also providing them (due to routine design problems, realizing technologies, architectural styles and patterns applied when similar problems occur.) manual composition the workflow is designed by the user. Similar to Peristeras et al., (2008) argument on how the workflow models address technical considerations why it discards the non technical coordination problems. Automated composition of digital services, users defines goals which are achieved with software support. (Marinos & Krause, 2009). SOA Basic Principles (Erl, 2008) Service Contract- With high granularity, advocates reusability of DSs. Service Loose Coupling- DSs know about each other but are loose coupled. Service Abstraction- DSs hides logic from the outside world. Service Reusability- Logic is encapsulated within the DS why reusability is advocated. Service Autonomy- DSs have responsibility for the encapsulated logic. Service Statelessness- Temporary data from previous requests is not stored server side thus advocating reusability. Service Discoverability- DSs must be discoverable. Service Composability- DSs living in a SOA must be composable. Interoperability, Prerequisites and Effects Ontology, BOM, Term Fact. Physical separation of business logic, process logic and application specific code. High interoperability acceptance advocated by SOA Technical flexibility by dynamic implementations. Non procedural thinking. Thus, DSs are used when they are needed. High level interfaces advocating interoperability and inter organizational functionality.

3 A brief SOA The very basic picture of SOA where 3 actors communicate through a medium (a market or a digital ecosystem). A DS is requested by a Service Requestor (a user), the request is pointed to the Service Provider who publish the requested DS in the Service Directory. Some way from the Service Perspective in other disciplines i.e. SM, where no scaffold is provided for.

4 On realizing Technology WebServices as excellent example The relationship between SOA and a realizing technology, in this case WebServices. SOA encapsulate logic as a type of container. The logic is made of relations and communication corresponding to the realizing technology. In line with the basic principals for SOA. Structural Relationship (with use of Erl, 2005) To be used the DS/WS needs WebService Definition Language (WSDL) ( pronounced wusdel ). WSDL contains the necessary information for use and understanding of the WS. When the right WSDL definition is designed it is stored in the Universal Description, Discovery and Integration repository (UDDI-repository). The message as such is formatted according to Simple Object Access Protocol (SOAP). Thus the interpretation can be expressed accordingly: application of reusable architectural style or pattern as part of the realizing technology has been applied. The WSDL Definition (with use of Erl, 2005)

5 Interoperability and IS derived from Business, the silver bullet ;) SOA goes SOBP -the digital service becomes a component in the SOA. Derived from business and designed by business owners.

6 The problem Technical how or Business what? Enabling Interoperability is in need of some answers What is a child? What is fully vaccinated? What is basic vaccinated? i.e. Ontology nomenclatur vocabulary definitions differs From Malmoe to Lund Around the world minus 20 kilometers Important initiatives providing concretizing acronyms to a not perfect ontology SNOMED Systematized Nomenclature of Medicine, CT (The National Board of Health and Welfare, Socialstyrelsen) HL7 - Is an international organization that works to spread the use of standards to increase efficiency in health care. NPÖ - Coordinated development for safer, more effective health and social care (Nationell Patient Översikt) Coordinated use of IT in local health and social care - Sweden's Municipalities and Counties Swedish Strategy for E-health

7 Who are the users of interoperability between E-health IIS? In 2002 the World Health Organization estimated that 1.4milion children from around the world would die from preventable diseases (World Health Organization, 2010). Almost each country in the world has its own vaccination schedule which differs significantly. Thus each child from a specific country ought to be immunized according to its national immunization schedule. The vaccination schedule regulates i.e. doses, intervals and vaccines. Problems are significant on this matter and emerge as immigrant children move from one country to another, thus also fazed into another immunization schedule. Immunization practitioners are struggling with how to immunize immigrant children because of this. According to current vaccination schedules there is a substandard of orientation among policies and rules for how to inoculate immigrant children. In 2008, in Sweden, children lived who was born in another country (Ibid). The problem is thus quite evident in Sweden (Statistics Sweden, 2010). i.e. s etc... State authorities professionals professionals Immunization Immunization State authorities

8 Why do we care about SOA, Business Processes and Business Rules?

9 Why do we care about SOA, Business Processes and Business Rules? We don t However, the desired result is of interest! Back to basics with Ontology epistemology nomenclature vocabulary No one knows the business better than the business owners The need for the declarative paradigm of ISD as the third pillar of IS i.e. BRA Let the business owners provide the requirements for Immunization IS interoperability Let the business owners design the business rules in natural language using the context specific ontology (why the same is of importance) Let the business owners manage their business rules/business logic in natural language in i.e. word.doc (i.e. IBM ILog Rule Solution for Office) Etc. The digital Services knows how to communicate and have done for quite some time now. But how is the message interpreted, what does the objects, terms and fact types mean? (remember around the world ) Value add We all know this Loss prevent Even more value add comes from meta description. Thus there is a need for transparency provided by i.e. BRs / Business Logic and BPs / Process Logic Peripheral IS i.e. Surveillance Impacts Digital Service Composition / interoperability i.e. ERP/CRM ISD scale

10 Laws and regulations Can we do it like this (technical SOA)? Country 1 Country 1 Country 1 Country 1 Legacy IS Journal system Legacy IS Journal system Legacy IS Journal system Legacy IS Journal system Service Provider Interoperability, reusability, logics encapsulation API API API API new entrance new entrance new entrance new entrance DS DS DS DS Medium e.g. Internet Service Repository One entrance to information Service Requestor Making things better?

11 If { The only thing constant is change itself (Hράκλειτος (Herakleitos; Heraclitus of Ephesus), (c.535 BC BC)) a Greek philosopher Technological interoperability is no longer more than a question of competence. Thus the business owners must decide on a complete context specific ontology. That enables business driven ISD where interoperability can be realized by several different realizing technologies i.e. WebServices. Also, IS can be managed in close to real time making the distance between model an reality a bit smaller. To the best of my knowledge and from what I can see today in the IS and ISD discipline is that the business vocabulary becomes more and more important. A key to IS derived from business rather than vice versa. we know how } then { agree on what } : : public Ontology[] getconcretizingacronym() { // begin-user-code return (Ontology[]) concretizingacronym.toarray(new Ontology[concretizingAcronym.size()]); // end-user-code }