Exploiting Semantics of Web Services in e. Business Applications Asuman Dogac Middle East Technical University 06531 Ankara Turkey Asuman Dogac RIDE 2004, Boston, March 28, 2004 1/92
Outline n Why do we need the semantics of Web services? n Means of expressing semantics: Ontology and Ontology Description Languages n Semantic Support Available in UDDI Registries n Semantic Support Available in eb. XML Registries n Two approaches to exploiting semantics: Querying and Reasoning n Describing the semantics of Web services in two domains q q Healthcare Tourism Industry Asuman Dogac RIDE 2004, Boston, March 28, 2004 2
Why do we need the semantics of Web services? Asuman Dogac RIDE 2004, Boston, March 28, 2004 3/92
Why do we need Web Service Semantics? n WSDL only gives the technical specification of the Web services n In order to exploit services in their full potential their properties must be defined: q q q The methods of charging and payment The channels by which the service is requested and provided Constraints on temporal and spatial aspects Availability Service quality Security, trust and rights attached to a service Asuman Dogac RIDE 2004, Boston, March 28, 2004 4
Why do we need Web Service Semantics? n To be able to define the Web service functionality semantics n To be able to describe service properties and later search for services according to their properties n Defining Service Properties Through Ontology Languages This search needs to be done in a machine processable and interoperable manner Asuman Dogac RIDE 2004, Boston, March 28, 2004 5
Ontology Asuman Dogac RIDE 2004, Boston, March 28, 2004 6/92
What is an Ontology? “An explicit formal specification of the terms in the domain and relations among them. ” - Noy and Mc. Guinness, “Ontology Development 101” • The word ontology comes from the Greek ontos (being) and logos (word) Class • An ontology describes objects and concepts as classes Subclass • These classes are arranged in a hierarchy, and then class attributes and relationships are described with properties Subclass Asuman Dogac RIDE 2004, Boston, March 28, 2004 properties 7
Why use an ontology? • A common vocabulary • Ability to define relationships among classes, properties and instances • Automated Processing 1. Querying 2. Reasoning Asuman Dogac RIDE 2004, Boston, March 28, 2004 8
Resource Description Framework (RDF) n A W 3 C recommendation n RDF fixes the syntax and structure of describing metadata through RDF Syntax n It allows meaning to be defined and associated with data through RDF Schema n RDF Schema facilities to define domain specific ontologies Asuman Dogac RIDE 2004, Boston, March 28, 2004 9
Ontology Languages and OWL OIL: Ontology Inference Layer (European Commission Project) DAML: Darpa Agent Markup Language DAML+OIL RDF (Resource Description Framework) OWL: Web Ontology Language (Being Standardized by W 3 C) Asuman Dogac RIDE 2004, Boston, March 28, 2004 10
OWL Classes n n Ministry of Interior has defined ontologies for their information in OWL For example: <owl: Class rdf: ID=“Crimes"> </owl: Class> Crimes Robbery <owl: Class rdf: ID=“Robbery"> <rdfs: sub. Class. Of rdf: resource="#Crimes"/> </owl: Class> Asuman Dogac Speeding Terrorism … <owl: Class rdf: ID=“Terrorism"> <rdfs: sub. Class. Of rdf: resource="#Crimes"/> </owl: Class> RIDE 2004, Boston, March 28, 2004 11
OWL Properties <owl: Datatype. Property rdf: ID=“description"> <rdfs: domain rdf: resource="#Crime"/> <rdfs: range rdf: resource=“http: //www. w 3. org/2001/XMLSche description Crimes Literal ma#Literal"/> </owl: Datatype. Property > <owl: Object. Property rdf: ID=“suspect"> <rdfs: domain rdf: resource="#Robbery"/> <rdfs: range rdf: resource=“#Thief> </owl: Object. Property > <owl: Object. Property rdf: ID=“driver"> <rdfs: domain rdf: resource="#Speeding"/> <rdfs: range rdf: resource=“#Speeder"/> </owl: Object. Property > Asuman Dogac suspect Robbery Speeding RIDE 2004, Boston, March 28, 2004 Thief driver Speeder 12
An Example: e. Government n Finger prints from a robbery scene identified John Smith as the suspect n Here is the police report on the robbery: <Robbery rdf: ID="report-2003 -10 -23 -xyz"> <description>. . . </description> <suspect> <Thief rdf: about="http: //www. ministry. Of. Interior. gov/criminals#John_Smith"/ > </suspect> </Robbery> Asuman Dogac RIDE 2004, Boston, March 28, 2004 13
An Example: e. Government • Later in the day a police gives a person a ticket for speeding • The driver's license showed the name John Doe • Here is the police report on the speeder: <Speeding rdf: ID="report-2003 -10 -23 -abc"> <description>. . . </description> <driver> <Speeder rdf: about="http: //www. ministry. Of. Interior/criminals#John_Doe"/> </driver> </Speeding> Asuman Dogac RIDE 2004, Boston, March 28, 2004 14
Any Relationship between the Thief and the Speeder? Ministry of Interior keeps the OWL descriptions of their files: <Criminals rdf: about=" http: //www. ministry. Of. Interior/criminals#John_Doe "> <owl: same. As rdf: resource=" http: //www. ministry. Of. Interior. gov/criminals#John_Smith "/> </Criminals> Asuman Dogac RIDE 2004, Boston, March 28, 2004 15
How can this be achieved? owl: same. As property helps! Thief John Smith owl: same. As Speeder John Doe Inference: The Thief and the Speeder are one and the same! n OWL provides a property (owl: same. As) for indicating that two resources (e. g. , two people) are the same Asuman Dogac RIDE 2004, Boston, March 28, 2004 16
Semantic Support of Web Services in UDDI Registries Asuman Dogac RIDE 2004, Boston, March 28, 2004 17/92
UDDI Registry APIs n Inquiry API q Find n n q n q find_business find_service find_binding find_t. Model n n n Asuman Dogac Save n n Get Details n Publishers API q get_business. Detail get_service. Detail get_binding. Detail get_t. Model. Detail save_business save_service save_binding save_t. Model Delete n n delete_business delete_service delete_binding delete_t. Model RIDE 2004, Boston, March 28, 2004 18
Defining Service Semantics in UDDI Registries business. Entity n n By using standard taxonomies And by putting the corresponding t. Model keys in the category bags of services Asuman Dogac business. Key name URL description contacts business. Services identifier. Bag category. Bag keyed. Reference t. Model. Key key. Name key. Value RIDE 2004, Boston, March 28, 2004 Contact Phone Address Email business. Service service. Key t. Model. Key Name Description Binding. Templates keyed. Reference t. Model. Key key. Name key. Value 19
Business categories in UDDI n Three standard taxonomies in V 1 n Industry: NAICS - North American Industrial Classification Scheme (Industry codes - US Govt. ) n Product/Services: UN/SPSC - Universal Standard Products and Services Classification (ECMA) n Location: ISO 3166 Geographical taxonomy Asuman Dogac RIDE 2004, Boston, March 28, 2004 20
ISO 3166 Codes (Countries) (http: //www. iso. ch/iso/en/prods-services/iso 3166 ma/) Country A 2 A 3 Number ITALY IT ITA 380 TURKEY TR TUR 792 … … Asuman Dogac RIDE 2004, Boston, March 28, 2004 21
North American Industry Classification System (NAICS) Asuman Dogac RIDE 2004, Boston, March 28, 2004 22
United Nations Standard Products & Services Code® (UNSPSC) Asuman Dogac RIDE 2004, Boston, March 28, 2004 23
How can we find a service through its semantics in UDDI Registries? n Looking for a service to buy a Computer q q If a service puts the t. Model key corresponding to [43. 17. 18. 03] Workstations or desktop computers – commodity in its category bag THEN We know that this service is related with computers BUT: Is this service really selling computers? If so how about the properties of the product? Payment method? Memory, Speed? Asuman Dogac RIDE 2004, Boston, March 28, 2004 24
Taxonomies Define Only Class/Subclass Relationship: An Example Taxonomy: UNSPSC • UDDI uses taxonomies to describe the semantic of Web services by relating them to t. Models 43. 00. 00 Communications and Computer Equipment and Peripherals and Components and Supplies Through taxonomies: • It is not possible to define properties of services 43. 16. 17. 00 Business Transaction and Personal Business Software • It is not possible to relate service classes with one another 43. 16. 17. 02. 00 Tax Preparation Software Asuman Dogac RIDE 2004, Boston, March 28, 2004 25
Semantic Support of Web Services in eb. XML Registries Asuman Dogac RIDE 2004, Boston, March 28, 2004 26/92
Where to store the generic semantics of the services? n An eb. XML registry allows to define semantics basically through two mechanisms: q q It allows properties of registry objects to be defined through “slots” and, Metadata can be stored in the registry through a “classification” mechanism Asuman Dogac RIDE 2004, Boston, March 28, 2004 27
eb. XML Registry Information Model (RIM) Registry. Object Classification. Node Classification. Scheme Asuman Dogac Classification Registry. Entry Registry. Package Association Extrinsic. Object RIDE 2004, Boston, March 28, 2004 Service 28
Exploiting semantics Travel. Service Transportation Accommodation Entertainment Service Air. Transportation n In relating the semantics Reserve. AFlight Buy. ATicket with the services advertised in service registries, there originating. From destination. To payment. Method are two key issues: q Where to store the generic semantics of the Reserve. AFlight services: In eb. XML, metadata is stored in the registry originating. From destination. To payment. Method q How to relate the services advertised in the registry with the semantic defined through an ontology: In My. Service eb. XML through Classification objects ? ? Asuman Dogac RIDE 2004, Boston, March 28, 2004 29
Relating a Web service Advertised with Service Ontology in eb. XML Service. To. Industry. Classification: Classification classification. Node classsified. Object My. Service: Registry Entry Asuman Dogac Reserve. AFlight: Classification. Node RIDE 2004, Boston, March 28, 2004 30
How to relate services advertised with the generic ontology classes? n By relating a service advertised with a node in classification hierarchy, we make the service an explicit member of this node n The service also inherits the well-defined meaning associated with this node as well as the generic properties defined for this node n When we associate “My. Service” with “Reserve. AFlight. Service”, its meaning becomes clear; that this service is a flight reservation service n Assuming that the “Reserve. AFlight. Service” service has the generic properties such as “originating. From”, “destination. To” and “payment. Method”, “My. Service” also inherits these properties Asuman Dogac RIDE 2004, Boston, March 28, 2004 31
Querying vs. Reasoning Asuman Dogac RIDE 2004, Boston, March 28, 2004 32/92
Some Observations n Ontologies can play two major roles in the Web services area: Ø Ø One is to provide a source of shared and precisely defined terms which can be used to dynamically discover, compose and monitor services The other is to reason about the ontologies Asuman Dogac RIDE 2004, Boston, March 28, 2004 33
Some Observations n The fact is that we do not have industrial strength reasoners yet! n Semantic can also be taken advantage of through querying Asuman Dogac RIDE 2004, Boston, March 28, 2004 34
Exploiting Semantics through Querying n Once semantics is associated with Web services in eb. XML registries, it can be used to discover services simply through queries n Examples: q q q It is possible to find the properties of a Web service class It is possible to find all the advertised instances of a Web service class in the ontology It is possible to obtain the content files (WSDL and OWL) Asuman Dogac RIDE 2004, Boston, March 28, 2004 35
Querying eb. XML Registry through Query Templates n This can be achieved through predefined query templates which yields into automation: q q q A query template is used to obtain the properties of a generic class A query template is used for locating service instances of a given generic class node in the class hierarchy A template is a content retrieval query to obtain the original OWL and WSDL files through the identifiers of the OWL and WSDL files in the Specification. Links Asuman Dogac RIDE 2004, Boston, March 28, 2004 36
A query template to obtain the properties of a generic class eb. XML Registry Travel. Service Datatype. Property Transportation Accommodation Entertainment Service Air. Transportation Reserve. AFlight originating. From destination. To eb. XML Query Get Datatype Properties eb. XML Query Result Object. Property Buy. ATicket payment. Method 1 1 2 2 eb. XML Query Get Object Properties eb. XML Query Result payment. Method originating. From destination. To Asuman Dogac promotion RIDE 2004, Boston, March 28, 2004 37
An Example Query Retrieving all the Associations of Type “Datatype. Property” for “Reserve. AClass. Flight. Service” <Adhoc. Query. Request xmlns = "urn: oasis: names: tc: ebxml-regrep: query: xsd: 2. 0" xmlns: xsi = "http: //www. w 3. org/2001/XMLSchema-instance" xsi: schema. Location = "urn: oasis: names: tc: ebxml-regrep: query: xsd: 2. 0 query. xsd"> <Response. Option return. Type = "Leaf. Class" return. Composed. Objects = "true" /> <Filter. Query> <Classification. Node. Query> <Source. Association. Branch> <Association. Filter> <Clause> <Simple. Clause left. Argument = "association. Type"> <String. Clause string. Predicate = "Equal"> Datatype. Property</String. Clause> </Simple. Clause> </Association. Filter> <Classification. Node. Query> <Name. Branch> <Localized. String. Filter> <Clause> <Simple. Clause left. Argument = "value"> <String. Clause string. Predicate = "Contains"> Reserve. AFlight. Service</String. Clause> </Simple. Clause> </Localized. String. Filter> </Name. Branch> </Classification. Node. Query> </Source. Association. Branch> </Classification. Node. Query> </Filter. Query> </Adhoc. Query. Request> Asuman Dogac RIDE 2004, Boston, March 28, 2004 38
A query template to find all the advertised instances of a Web service class eb. XML Registry Travel. Service Accommodation Entertainment Service Transportation Service Air. Transportation Reserve. AFlight My. Service 1 Buy. ATicket My. Service 2 1 2 My. Service 3 eb. XML Query Get Extension of a Classification. Node eb. XML Query Result My. Service 1 My. Service 2 Asuman Dogac RIDE 2004, Boston, March 28, 2004 My. Service 3 39
An Example Query: Retrieving all the Services Classified with “Reserve. AFlight. Service” Classification. Node <Adhoc. Query. Request xmlns = "urn: oasis: names: tc: ebxml-regrep: query: xsd: 2. 0" xmlns: xsi = "http: //www. w 3. org/2001/XMLSchema-instance" xsi: schema. Location = "urn: oasis: names: tc: ebxml-regrep: query: xsd: 2. 0 query. xsd"> <Response. Option return. Type = "Leaf. Class" return. Composed. Objects = "true" /> <Filter. Query> <Service. Query> <Classified. By. Branch> <Classification. Node. Query> <Name. Branch> <Localized. String. Filter> <Clause> <Simple. Clause left. Argument = "value"> <String. Clause string. Predicate = "Equal"> Reserve. AFlight. Service </String. Clause> </Simple. Clause> </Localized. String. Filter> </Name. Branch> </Classification. Node. Query> </Classified. By. Branch> </Service. Query> </Filter. Query> </Adhoc. Query. Request> Asuman Dogac RIDE 2004, Boston, March 28, 2004 40
eb. XML Registry eb. XML Repository Travel. Service Transportation Service Accommodation Service WSDL of My. Service 1 Entertainment Service Air. Transportation Reserve. AFlight Extrinsic Object Buy. ATicket Specification. Link My. Service 1 1 2 Extrinsic Object eb. XML Query Get Specification. Link Content of a Service A Content Retrieval Query template eb. XML Query Result WSDL of My. Service 1 Asuman Dogac OWL-S of My. Service 1 RIDE 2004, Boston, March 28, 2004 41
Retrieving the WSDL Files <Get. Content. Request xmlns="urn: oasis: names: tc: ebxml-regrep: query: xsd: 2. 1" xmlns: rim="urn: oasis: names: tc: ebxml-regrep: rim: xsd: 2. 1" xmlns: xsi="http: //www. w 3. org/2001/XMLSchema-instance" xsi: schema. Location="urn: oasis: names: tc: ebxml-regrep: rim: xsd: 2. 1. . /schema/rim. xsd urn: oasis: names: tc: ebxml-regrep: query: xsd: 2. 1. . /schema/query. xsd"> <rim: Object. Ref. List> <--! The unique id of the WSDL file in the registry --> <rim: Object. Ref id="urn: uuid: 7 e 4397 db-916 a-490 f-bdc 7 -c 9 da"/> </rim: Object. Ref. List> </Get. Content. Request> Asuman Dogac RIDE 2004, Boston, March 28, 2004 42
OWL-S Asuman Dogac RIDE 2004, Boston, March 28, 2004 43/92
OWL-S: Defines an Upper Ontology for Web Services in OWL Resource Service. Profile presents: What it does provides Service. Grounding Asuman Dogac Supports: How to access it described. By: How it works Service. Model RIDE 2004, Boston, March 28, 2004 44
Web services and the Healthcare Domain Asuman Dogac RIDE 2004, Boston, March 28, 2004 45/92
Challenges of Healthcare Informatics n According to Jonathan Borden, M. D. of ASTM: q q q A disaster: 1. 1 Trillion $/year in the USA 30 -40 % overhead Mostly paper based Highly proprietary commercial systems Tens of thousands of people die each year due to poor information/errors Most of the information is rendered useless Asuman Dogac RIDE 2004, Boston, March 28, 2004 46
Asuman Dogac RIDE 2004, Boston, March 28, 2004 47
Challenges of Healthcare Informatics n Most of the health information systems today are proprietary n They often only serve one specific department within a healthcare institute n To complicate the matters worse, a patient's health information may be spread out over a number of different institutes which do not interoperate n This makes it very difficult for clinicians to capture a complete clinical history of a patient Asuman Dogac RIDE 2004, Boston, March 28, 2004 48
Patient Records: Problems n Content: too little, too much, or wrong n Format: poor organization of information n Access, availability, security n Linkages and integration Asuman Dogac RIDE 2004, Boston, March 28, 2004 49
Challenges of Healthcare Informatics The systems must interoperate for effectiveness For interoperability standards are needed However there are more than one standard in the health care domain Asuman Dogac RIDE 2004, Boston, March 28, 2004 50
EHR Architectures The nice thing about standards is that there are so many to choose from. Andrew Tanenbaum, Introduction to Computer Networks n „Candidates“ of EHR architectures: q q q q CEN ENV 13606 „EHR Communication“ Good Electronic Health Record (GEHR) Open. EHR CEN EN 13606 (draft) HL 7 Clinical Document Architecture HL 7 v 2 Information Model (implicit) HL 7 v 3 Reference Information Model (draft) Asuman Dogac RIDE 2004, Boston, March 28, 2004 51
Web Services in the Healthcare Domain n Web services provides the healthcare industry with an ideal platform to achieve the difficult interoperability problems n Web services are designed to wrap and expose existing resources and provide interoperability among diverse applications n It becomes possible to provide the interoperability of medical information systems through standardizing the access to data through WSDL and SOAP rather than standardizing documentation of electronic health records Asuman Dogac RIDE 2004, Boston, March 28, 2004 52
Introducing Web services to the healthcare domain brings many advantages q q q Medical information systems suffer from proliferation of standards to represent the same data; Web services allow for seamless integration of disparate applications representing different and, at times, competing standards Web services will extend the healthcare enterprises by making their own services available to others Web services will extend the life of the existing software by exposing previously proprietary functions as Web services Asuman Dogac RIDE 2004, Boston, March 28, 2004 53
Semantics of Web Services n In order to exploit Web services to their full potential, it is necessary to describe their semantics n An essential element in defining the semantic of Web services is the domain knowledge n Medicine is one of the few domains to have extensive domain knowledge defined through standards Asuman Dogac RIDE 2004, Boston, March 28, 2004 54
Domain Knowledge n n Some of the domain knowledge exists in controlled vocabularies, or terminologies: q Some vocabularies are rich semantic nets, such as SNOMED-CT while others such as ICD-10 (International Statistical Classification of Diseases and Related Health Problems) is little more than lexicons of terms q However, there also standards that expose the business logic in the healthcare domain such as HL 7 and Electronic Healthcare Record based standards such as CEN TC 251, ISO TC 215 and GEHR which define and classify clinical concepts These standards offer significant value in developing ontologies to express the semantics of Web services Asuman Dogac RIDE 2004, Boston, March 28, 2004 55
What kind of Semantics? n n Service Functionality Semantics: q HL 7 has categorized the events in healthcare domain by considering service functionality which reflects the business logic in this domain q This classification can be used as a basis for defining the service action semantics through a Service Functionality Ontology Service Message Semantics: q Electronic healthcare record (EHR) based standards like HL 7 CDA (Clinical Document Architecture), GOM (GEHR Object Model), and CEN TC 251's ENV 13606 define meaningful components of EHR so that when transferred, the receiving party can understand the record content better q The meaningful components defined by these standards can be used in developing service message ontologies Asuman Dogac RIDE 2004, Boston, March 28, 2004 56
HL 7 and Web Services n The primary goal of HL 7 is to provide standards for the exchange of data among healthcare computer applications n An event in the healthcare world, called the trigger event, causes exchange of messages between a pair of applications n When an event occurs in an HL 7 compliant system, an HL 7 message is prepared by collecting the necessary data from the underlying systems and it is passed to the requestor, usually as an EDI message n Mapping HL 7’s message based events directly into Web services may result in several inefficiencies Asuman Dogac RIDE 2004, Boston, March 28, 2004 57
HL 7 and Web Services n n n The input and output messages defined for HL 7 events are usually very complex containing innumerous segments of different types and optionality Furthermore, all the semantics about the business logic and the document structure are hard coded in the message This implies that, the party invoking the Web service must be HL 7 compliant to make any sense of the content of the output parameter(s) returned by the service Furthermore, the information contained in an HL 7 message may be coming from different systems either proprietary or complying to different standards Hence, in Web services terminology, HL 7 events correspond to Composite services, whereas more elementary services are needed Asuman Dogac RIDE 2004, Boston, March 28, 2004 58
HL 7 and Web Services n Since HL 7 has already been through an effort of categorizing the events in healthcare domain considering service functionality, it can be used as a basis for a service functionality ontology Asuman Dogac RIDE 2004, Boston, March 28, 2004 59
An Example Service Functionality Ontology Health. Care. Services Patient. Administration Patient. Care Patient. Referral. Request Patient. Referral Scheduling Patient. Info. Request Insurance. Information Clinical. Information Observation. Reporting Cancel. Patient. Referral Demographic. Data Get. Clinical. Information service. Quality Asuman Dogac location RIDE 2004, Boston, March 28, 2004 Properties of the Generic Service Class 60
Service Messages n n n A Web service in the healthcare domain usually accesses or updates a part of an electronic healthcare record, that is, parts of the EHR constitute the service parameters An electronic healthcare record may get very complex with data coming from diverse systems such as lab tests, diagnosis, prescription of drugs which may be in different formats Electronic healthcare record (EHR) based standards like HL 7 CDA, GOM and CEN's ENV 13606 aim to facilitate the interoperability between Medical Information Systems These standards provide conceptual building blocks or meaningful components We propose to use these standards as a basis for Service Message Ontology Asuman Dogac RIDE 2004, Boston, March 28, 2004 61
GEHR n n n EHR and Transaction level Navigation level Content (e. g. observation, subjective, instruction) level Data types (e. g. quantity, multimedia) level Clinical models are expressed outside the GOM in the form of archetypes Asuman Dogac RIDE 2004, Boston, March 28, 2004 62
CEN TC 251 ENV 13606 n Folder: High-level subdivisions of the entire EHR for a patient n Composition: A set of record entries relating to one time and place of care delivery; grouped contributions to an aspect of health care activity; composed reports and overviews of clinical progress n Headed Section: Sub-divisions used to group entries with a common theme or derived through a common healthcare process. n Cluster: Low-level aggregations of elementary entries (Record Items) to represent a compound clinical concept Asuman Dogac RIDE 2004, Boston, March 28, 2004 63
An example Service Message Ontology Concept Property Asuman Dogac RIDE 2004, Boston, March 28, 2004 64
Relating the services with the semantic defined through an ontology - UDDI Business Entities and Related Hacettepe. Hospital UDDI t. Models Observation. Reporting. Services Medical Services . . . Patient. Care Patient. Referral. Services Get. Clinical. Info get. Clinical. Info Observation Reporting Patient. Referral. Req Category. Bag reference Asuman Dogac RIDE 2004, Boston, March 28, 2004 65
Associating semantics to eb. XML Health. Care. Services subclass. Of Patient. Care Patient. Administration Observation. Reporting subclass. Of Patient. Referral. Request subclass. Of Patient. Info. Request Standards Conformed service. Quality eb. XML Classification Hierarchy eb. XML Classification. Nodes Asuman Dogac eb. XML associations eb. XMLslots RIDE 2004, Boston, March 28, 2004 66
The healthcare informatics industry has already started using Web services n An Example: Integrating the Healthcare Enterprise (IHE) n IHE defines a Web service based implementation framework Asuman Dogac RIDE 2004, Boston, March 28, 2004 67
Overview of IHE IT Infrastructure Integration Profiles IHE IT Infrastructure Technical Committee Charles Parisot, GE Medical Systems Information Technologies Asuman Dogac RIDE 2004, Boston, March 28, 2004 68/92
IHE IT Infrastructure 5 Integration Profiles Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Patient Synchronized Applications Enterprise User Authentication Synchronize multiple applications on a desktop to the same patient Patient Identifier Cross-referencing for MPI Consistent Time Map patient identifiers across independent identification domains Provide users a single name and centralized authentication process across all systems Coordinate time across networked systems Asuman Dogac RIDE 2004, Boston, March 28, 2004 69
An Example: Retrieve Information for Display Key Technical Properties: n Standards Used: q Web Services (WSDL for HTTP Get). q General purpose IT Presentation Formats: XHTML, PDF, JPEG plus CDA L 1. q Client may be off-the-shelf browser or display app. n Two services : q Retrieve of Specific Information: n n n q Patient centric: patient ID Type of Request Date, Time, n. Most. Recent Retrieve a Document n n n Asuman Dogac Object Unique Instance Identifier (OID) Type of Request Content Type Expected RIDE 2004, Boston, March 28, 2004 70
![Retrieve Information for Display Transaction Diagram Display Retrieve Specific Info for Display [11] Information](https://present5.com/presentation/8c83f28fce1d67a388d17627422a855a/image-71.jpg "Retrieve Information for Display Transaction Diagram Display Retrieve Specific Info for Display [11] Information")
Retrieve Information for Display Transaction Diagram Display Retrieve Specific Info for Display [11] Information Source Retrieve Document for Display [12] Types of Requests Summary of All Reports Summary of Laboratory Reports Summary of Radiology Reports Summary of Cardiology Reports Summary of Surgery Reports Summary of Intensive Care Reports Summary of Emergency Reports Summary of Discharge Reports List of Allergies List of Medications Persistent Document Asuman Dogac RIDE 2004, Boston, March 28, 2004 71
For Further Information… n IST-1 -002103 -STP Artemis Project: A Semantic Web Service-based P 2 P Infrastructure for the Interoperability of Medical Information Systems n http: //www. srdc. metu. edu. tr/artemis/ Asuman Dogac RIDE 2004, Boston, March 28, 2004 72
Web Services and the Travel Industry Asuman Dogac RIDE 2004, Boston, March 28, 2004 73/92
Overall Information Flow in Tourism Domain About 1000 companies About 100, 000 Hotels Hilton Ankara, Sofitel Paris. . . 4 major GDSs+ Hundreds Airline Companies 10 small Olympic, Air France … Of Chains XML Two companies Hotel Switching Chains Companies Hilton, BW, GDS Cryptic Pegasus, Utell, E-Rez, … Tens of Thousands Of agencies Rent-a-Car Agencies Asuman Dogac Worldres. Rent-a-Car Hundreds Chains Of Avis, Hertz, … Chains Amadeus, Galileo, Sabre, Worldspan … RIDE 2004, Boston, March 28, 2004 E-Comm. Site Travel Agency 74
Global Distribution Systems (GDS) n Provides connection to the airline, hotel and -a-car reservation systems from a single point n Leading GDSs: Amadeus, Sabre, Galileo, Worldspan n Travel Agency – GDS Connectivity q q rent Usually in the form of dedicated client terminals that accept GDS specific cryptic commands, connected to the GDS on a private network Special APIs provided for Client Application Developers Asuman Dogac RIDE 2004, Boston, March 28, 2004 75
Disadvantages of GDSs (I) n But GDSs suffer from: q q q Mostly they rely on their own private networks They have difficult to use cryptic languages Mainly for human use A request to the system usually involves more than one interaction with the person on the terminal GDSs have limited speed and search capabilities It is difficult to interoperate them with other systems and data sources Asuman Dogac RIDE 2004, Boston, March 28, 2004 76
Challenges of Travel Industry (II) n GDSs are legacy systems and suffer from: q q Classical problems with centralized architectures Among the millions of travel agents, only about 10 to 20% of all travel agents are in connection with the GDS companies Weak support for SMEs (major hotel chains and etc. . ) Do not support every type of services in travel industry (no support for tours) Asuman Dogac RIDE 2004, Boston, March 28, 2004 77
A Web service based architecture can bring several advantages to the industry q q q q Opening up the resources over the Internet Interoperability Ability to access legacy systems Better support for SMEs Ease in service discovery Machine processing Better accessibility Asuman Dogac RIDE 2004, Boston, March 28, 2004 78
Web Services in Travel Industry n A few early adopters in the travel industry have started developing Web Services Sabre and n Datalex are among the first companies to develop OTA based Web services n Sabre Web Services provide all the functionality needed to sell travel n Galileo also provides a Web service based solution and claims to have cut down the development time by 80% Asuman Dogac RIDE 2004, Boston, March 28, 2004 79
New Business Opportunities through Web Services in the Travel Domain (I) n GDS companies support only major travel products; q q q Airline ticketing, Hotel reservation and Car rental n Through Web services other types of specialized services can be made available n Especially different types of tour and transportation based travel products can be advertised and accessed Asuman Dogac RIDE 2004, Boston, March 28, 2004 80
New Business Opportunities through Web Services in the Travel Domain (II) n Among the millions of travel agents, only about 10 to 20% of all travel agents are in connection with the GDS companies n Most travel agencies and travel organization companies choose to manage travel services by themselves, due to reasons which may be q q n Technical, or Economical These companies generally suffer from the lack of advertising their services as well as publishing them electronically Asuman Dogac RIDE 2004, Boston, March 28, 2004 81
New Business Opportunities through Web Services in the Travel Domain (III) n Web services technology will provide a solution for all companies, especially for small-to-medium enterprises in the travel industry n The travel agencies and service providers will collaborate with each other on a new level n The companies will be able to provide every type of travel service; the service alternatives will be found on the fly Asuman Dogac RIDE 2004, Boston, March 28, 2004 82
Service Semantics in Travel Domain n Generic service semantics can be defined through DAML-S (later OWL-S) upper ontology n However some other properties of the services depend on the application domain n To facilitate the discovery of the Web services, there is a need for an ontology to describe service functionality in the domain Asuman Dogac RIDE 2004, Boston, March 28, 2004 83
Ontology Efforts in the Travel Domain n There are some efforts in this direction n There have been some efforts in defining the message ontologies in the travel domain such as the Harmonise project http: //www. harmonise. org/ n The Harmonise project have defined the Interoperability Minimum Harmonization Ontology (IMHO) Asuman Dogac RIDE 2004, Boston, March 28, 2004 84
Open Travel Alliance (OTA) n OTA exposes considerable amount of domain knowledge which can offer significant value in describing the semantics of travel Web services: q q q Generic messages Air messages Car message Hotel messages Golf Tee Times Insurance messages Package Tours/Holiday Bookings Travel Itinerary messages Rail information messages Loyalty messages Profile messages Asuman Dogac RIDE 2004, Boston, March 28, 2004 85
Service Functionality Ontology First Level Travel. Web. Services Vehicle. Services Hotel. Services Rail. Services . . Air. Services Insurance. Services. . Air. Details. Services . . Air. Booking. Services Air. Schedule. Services Checking. Availability. Services Request. Air. Avail Response. Air. Avail Asuman Dogac RIDE 2004, Boston, March 28, 2004 86
The advantages of Service Functionality Ontology n All sorts of Web services can be classified by using the nodes of such an ontology to make their meaning clear n Web service instance discovery is facilitated: All the services classified through a node in the ontology can be retrieved from service registries Asuman Dogac RIDE 2004, Boston, March 28, 2004 87
Message Ontologies n There is a need for message ontologies n It is also necessary to define the semantics of the messages exchanged so that the party receiving the message can interpret it n When ontologies are used to describe the messages, since the messages can refer to ontology concepts, it becomes possible to map one message instance into another through ontology mapping although they may be defined through different ontologies Asuman Dogac RIDE 2004, Boston, March 28, 2004 88
For Further Information… n IST-1 -002104 -STP Satine Project: Semantic-based Interoperability Infrastructure for Integrating Web Service Platforms to Peer-to-Peer Networks n http: //www. srdc. metu. edu. tr/satine/ Asuman Dogac RIDE 2004, Boston, March 28, 2004 89
Conclusions… n Semantic information about Web services can be made use of both q q through querying the service registries and through reasoners running over ontologies n Needless to say reasoning produces new information and hence is more powerful n But given that we do not have industrial strenth reasoners yet; through querying the we can get very useful semantics on Web services Asuman Dogac RIDE 2004, Boston, March 28, 2004 90
Conclusions… n The semantic efforts on the Web services area need to focus on application domains n Semantics is domain specific knowledge n Also different domains have evolved differently; and they have different needs n Web service technology can improve the interoperability and can introduce new business models in these domains Asuman Dogac RIDE 2004, Boston, March 28, 2004 91
Thank you for your attention! Asuman Dogac RIDE 2004, Boston, March 28, 2004 92
Скачать презентацию Exploiting Semantics of Web Services in e Business
8c83f28fce1d67a388d17627422a855a.ppt