Service-oriented architectures (SOA) and their application and usage in healthcareOutlineIntroduction and Motivation (Complexity)Introduction and Motivation (Outcome)Introduction and Motivation (Solutions)Role of SOARole of SOA (healthcare)Slide 8Service Oriented ArchitectureSOA MotivationSOA ExamplesSOA ComponentsSlide 13Slide 14Slide 15Slide 16SOA ManagementSlide 18Web ServicesWeb Service componentsSlide 21Slide 22Web Service Performance and ReliabilitySlide 24Web Service SecurityWeb Service Security considerationsSlide 27Connected HealthSlide 29Slide 30Slide 31Connected Health Framework-MicrosoftSlide 33Slide 34Slide 35Slide 36Slide 37Slide 38Slide 39Health Research Data Network (HRDN)Slide 41Slide 42Slide 43Slide 44Slide 45Slide 46Slide 47Slide 48Slide 49Slide 50Modeling Medical e-servicesSlide 52Modeling Medical e-services-RequirementsSlide 54Slide 55Slide 56Mobile Healthcare Information SupportSlide 58Slide 59Slide 60Slide 61BottlenecksSlide 63Slide 64Slide 651CSE 300 Service-oriented architectures (SOA) and Service-oriented architectures (SOA) and their application and usage in healthcaretheir application and usage in healthcareHerak SenCSE300: Topics in Biomedical [email protected] Science & Engineering DepartmentThe University of Connecticut371 Fairfield Road, Box U-255Storrs, CT 06269-21552CSE 300 OutlineOutlineIntroduction and MotivationIntroduction and MotivationRole of SOARole of SOABackground on SOABackground on SOASOA in healthcare:SOA in healthcare:Connected HealthConnected Health Framework – MicrosoftHealth Research Data Network (HRDN)Modeling Medical e-servicesMobileBottlenecksBottlenecks3CSE 300 Introduction and Motivation (Complexity)Introduction and Motivation (Complexity)Operate in different environmentOperate in different environmentEntity focused i.e. built specifically for providers, Entity focused i.e. built specifically for providers, patient ,insurance companies etcpatient ,insurance companies etcMinimum information sharingMinimum information sharingHardly any interactionHardly any interactionComplicated business, legal and ethical rules Complicated business, legal and ethical rules4CSE 300 Introduction and Motivation (Outcome)Introduction and Motivation (Outcome)Patient suffersPatient suffersRepeats information to different kinds of entityNo simple way to find information in times of emergencyQuality Quality 8th leading cause of death in US in medical errorsDuplicate patient information may be lead to repeated testing due to conflicts1/3 spending on healthcare goes to fix the duplication$2.7 trillion estimated expenditure by 2010 but not number 1 in health care services5CSE 300 Introduction and Motivation (Solutions)Introduction and Motivation (Solutions)TechnologyTechnologyGive the entities especially patients to choose health servicesAdoption of connected computer systems could reduce error and moneyInternet can be used to deliver health information quicklyStandardize health data exchangeUse the current systems instead of making new onesCreate a non-proprietary “network of networks” that will support rapid health information flow6CSE 300 Role of SOARole of SOASignificant work in independent healthcare areaSignificant work in independent healthcare areaPHREMRMedication Management toolChronic disease management toolsNeed to connect various systemsNeed to connect various systemsService Oriented ArchitectureService Oriented ArchitectureProvides ways to connect disparate systemsConnect at edge of one system7CSE 300 Role of SOA (healthcare)Role of SOA (healthcare)Common Framework of standards at National LevelCommon Framework of standards at National LevelData ExchangeSecurity and AuthorizationData IntegrityAll built as servicesAll built as servicesUsing such services to integrate various existing Using such services to integrate various existing systemssystemsNo redesigning of existing systemsSecure integration without jeopardizing patients and providers confidential data8CSE 300 Service Oriented ArchitectureService Oriented ArchitectureService Oriented ArchitectureService Oriented Architecture9CSE 300 Service Oriented ArchitectureService Oriented ArchitectureDefinitionDefinitionThe policies, practices, frameworks that enable application functionality to be provided and consumed as sets of services published at a granularity relevant to the service consumer.Services can published, discovered and invokedAbstracted away from the implementation using standards-based form of interfaces.One can think “functions” in a program as services1.Hides the implementation2.Discoverable by the library it belongs3.Can be invoked to get results4.Publishable through a libraryOne can think “functions” in a program as services1.Hides the implementation2.Discoverable by the library it belongs3.Can be invoked to get results4.Publishable through a library10CSE 300 SOA MotivationSOA MotivationPresent systems are across different architectures Present systems are across different architectures networks and even between organizationsnetworks and even between organizationsChallenge is to find extendible, flexible that fits into Challenge is to find extendible, flexible that fits into legacy systemslegacy systemsNeed to adapt to changing business models without Need to adapt to changing business models without effecting other parts of systemseffecting other parts of systemsIntegrationIntegrationProvide existing business functionalities as services Provide existing business functionalities as services that can be reused that can be reused11CSE 300 SOA ExamplesSOA ExamplesYahooYahooFlickrTravelGoogleGoogleSOAP search APIAmazonAmazonAmazon Associates Web Service exposes Amazon's product data and e-commerce functionalityAmazon DevPay is a simple-to-use billing and account management service12CSE 300 SOA ComponentsSOA ComponentsServicesServicesThe contract defined between one or more “published” interfaces exposing well-defined functionalitiesInterfacesInterfacesDefining services , like header files in C++ContractsPublished ServicesPublished ServicesPublished services are exposed through networkPublic services are exposed within a system13CSE 300 SOA ComponentsSOA ComponentsService provider Service provider The software
View Full Document