UCSF Integration Update

Transcription

1 UCSF Integration Update Technology Forum 09/09/15

2 Agenda Integration Services Overview Medical Center Integration HL7 Enterprise Service Bus Overview Pilot Projects Intake Questions 2

3 UCSF Integration Services UCSF IT Integration Services is the central group that provides integration solutions across the UCSF enterprise and beyond. We provide the integration platforms and expertise in order to build robust, reusable and cost efficient interfaces for reliable data sharing and exchange between applications, platforms and services. 3

4 Our Service Overview Tools Cloverleaf A robust integration engine exclusively for HL7 messaging in healthcare integration solutions Mule ESB Enterprise Service Bus to handle general integration solutions Mule API Manager API management to expose reusable data services and enforce data governance Services PaaS Platform as a service, the Mule ESB and API Manager are available to UCSF developers to build and solve their own integration needs Implementation and Consulting Services the Integration Services team is available to build new integrations from scratch, enhance existing integrations, or provide consulting to help you achieve your integration needs 4

5 Medical Center -Interface Engine Overview Integration tool for UCSF Medical Center and beyond Solves the problem of sharing and exchange data HL7 de facto format/language for healthcare applications Clinical Apps Affiliates APeX Interface Engine Lab Rad Normalizes data Dietary Pharmacy Connects both modern and legacy applications Registry Cardiology 5

6 Systems We Connect Through HL7 6

7 What problem do we hope to solve? Many point to point connections Different protocols Mismatch version Expensive and hard to maintain Incompatible data Diverse connectivity Lack of flexibility 7

8 ESB Solution - Future Routing Filtering Transformation Alerts Extensible Powerful Flexible Reliable

9 ESB Pilot Think BIG, start small, prove value then scale up!!!

10 Current Integration Projects - Campus University Development and Alumni Relations (UDAR) Phase I - Currently in development phase Created a REST API to expose certain data in EDS Piloting a process model for Platform as a Service (PaaS) to allow UDAR developers direct access to the Mule platform to perform their own development for additional integrations. UCSF Student Information System (SIS) Currently in design phase Exposure of SIS API s through API Manager i.e. enrollment and curriculum data Archibus Currently in requirements/design phase Provide organization, employee and employee location to Archibus from ODS/EDS via JMS Receive employee location from Archibus via JMS, map JSON data and update CLS Proxy API from Archibus with building metadata for other systems to consume Benefit fields to Salesforce ExactTarget marketing cloud platform Went live end of August Providing 5 benefit-related fields that are not in EDS. 10

11 Project Intake Process DISCOVER Define scope and requirements Receive integration project request Acknowledge and record request in Innotas (<5 minutes) Setup discovery meeting to identify high-level scope and introduce our process (~30 minutes) Requestor to complete intake form and provide documented requirements and scope Discuss feasibility based on needs and timing (<10 minutes) ASSESS Solution design, Roles and responsibilities Setup detailed assessment meeting to (~60 minutes) Collect requirements: functional, technical, testing, security, resource, governance Discuss high-level design options and integration patterns Identify team roles and responsibilities, and other team dependencies (security, testing etc ) PLAN Timeline and Funding If project is approved and funded, then Integration team assigns prioritization Negotiate timeline: phases, milestones and start date Allocate resources Schedule integration project kick-off 11

12 Contact us integrationservices.ucsf.edu 12

13