RFP for Documentation and Development of Governance Process for Services Oriented Architecture

Transcription

1 RFP for Documentation and Development of Governance Process for Services Oriented Architecture Section I RFP Process Introduction The University of Texas M. D. Anderson Cancer Center (M. D. Anderson) in Houston, Texas, celebrating six decades of Making Cancer History, is one of the world s most respected institutions devoted exclusively to cancer patient care, research, education and prevention. Created by the Texas Legislature in 1941 as a component of The University of Texas System, M. D. Anderson continues to rank among the nations top cancer hospitals in U. S. News and World Reports America s Best Hospitals survey since its inception 15 years ago. One of the fundamental challenges in healthcare information technology is based on the fact that patients, clinicians and the clinical and research data that links them can be widely dispersed and difficult to access when care is required. Even within a single hospital setting, the clinical data needed for care, including data stored electronically which is increasingly the case may reside in a variety of physical locations, and be further confined by proprietary data and application architectures. Not only is it difficult (and in many cases, impossible) to access data across these boundaries, but this lack of accessibility challenges the clinicians ability to deliver high quality care and the researcher s ability to conduct studies. In response to this challenge, MDACC has developed an approach utilizing a virtual clinical data repository that is a conceptual model reaching across a variety of physical data bases, is physically located in a variety of places, and is inclusive of a variety of data models. (In many ways, the Internet itself is the model for a virtual data repository, consisting of an interwoven complex of data stores in literally millions of physical data bases throughout the world, tied together through standardized methods of access, data definition and communication.) MDACC believes that this virtual data base concept can in fact be utilized all the way down to the level of a healthcare provider organization which may have numerous physical stores of clinical data. The challenge is how to make this data available to the clinician and the researcher using the commonly used, standard and familiar tools of the Internet for access, data definition and communication. At MDACC, our virtual clinical repository is currently accessed through an application suite we call ClinicStation. ClinicStation was developed initially by the Informatics team in MDACC s Division of Diagnostic Imaging as a tool to facilitate radiologist access to clinical data managed within a filmless Picture Archive and Communications System (PACS) environment. ClinicStation has subsequently been extended throughout MDACC and is now used by virtually all of the clinicians who practice here. RFP for IT Professional Services Page 1

2 The initial development of ClinicStation was based on extensions of Microsoft s original Component Object Model (COM+), which predated currently defined services protocols that are now incorporated into Microsoft s.net framework. COM+ serves both as an object-oriented programming architecture and as a set of operating system services. The use of this componentbased framework permits the development of reusable program components which speeds up the development of new applications since there is no separate code compiling process. Client access to the middleware tier is via SOAP (Web Services) protocols. Each data source, query or transaction is a separate component and each data source component implements the same component interface, one of the significant advantages of the Web Services architecture. The data source component returns XML data, which is sent to the client via the SOAP web services component. In effect, ClinicStation embraced a services oriented architectural model before the term SOA became popularized in the literature With the assistance of consulting resources and tools from Avanade, Inc., ClinicStation has recently been migrated to Microsoft s (more current).net environment. MDACC believes that this major infrastructure and architectural transition now positions us to focus more clearly on our evolving services model and how to manage it going forward. The new SOA-based ClinicStation architecture implements WSE 3.0 and a SAML-based security token service (STS) for security and to provide a means of enforcement of a SOA Governance Process. The security infrastructure provides both user and application authentication (i.e. the request must be coming from an approved user and an approved application). The security infrastructure supports method level security by application, role and user. All service requests are logged to a database to assist with HIPAA compliance, and all services are instrumented for performance monitoring. The ClinicStation client is implemented as a.net smart client, which consumes the services published by the SOA. The client provides a display framework and the capability for a multithreaded asynchronous web services implementation. Figure 1 illustrates the overall ClinicStation architecture. Once authenticated, a clinician can then select from patients on his/her patient list and review data in any of forty five current applications in which clinic data is electronically collected and stored at MDACC. From the standpoint of the clinician, with a consistent user interface across multiple legacy applications, there is no indication that the data presented is from other than a single application. RFP for IT Professional Services Page 2

3 Virtual Clinical Data Repository Figure 1 Current ClinicStation architecture, showing the Client Tier, the Services Middleware Tier and the Virtual Clinical Data Repository MDACC s development of a services-oriented approach for ClinicStation, while intentional, has been driven largely by the specific needs of the application itself. Legacy systems have been wrapped with a services framework, and where those applications have not been up to the volume of queries ClinicStation can generate, a separate Operational Data Store (ODS) has been developed, also within a services framework. At this point MDACC recognizes the need to extend the services model to applications and data stores beyond the initial ClinicStation application suite. In addition, as more data stores and systems are added to our clinical and research systems environment, we recognize the need to develop a more formal governance model for managing both the conduct of our current services environment and the introduction of new services. Purpose of the RFP M. D. Anderson has prepared this Request for Proposal (RFP) to facilitate the selection of a company to provide the following services: 1. Documentation of the current services environment, including descriptions of all currently utilized services; RFP for IT Professional Services Page 3

4 2. Development of a formal governance model for all services currently being utilized and developed; 3. Implementation of a Services Governance Model, consistent with MDACC s current IS Governance structure and processes, to assure appropriate decisions regarding services definition, authentication, and management going forward. Scope of Activities M. D. Anderson is seeking a consulting professional services company to provide specialized expertise or personnel for purposes of documenting the current services environment and developing and implementing a services governing model going forward. Activities included within this scope, among others, include: Documentation of all services currently being utilized within M. D. Anderson s clinical environment; Providing recommendations on requirements for publishing and consuming services, and recommendations on processes to evaluate and enforce the requirements; Configuring, deploying, and maintaining an environment appropriate for services governance; Configuring, deploying, and managing such tools in order to support services governance going forward; Development of process for transferring in-depth technical knowledge about services documentation, management and governance to M. D. Anderson staff. Professional services must be available to all information technology groups at M. D. Anderson, both within the (central) Division of Information Services as well as several other (distributed) teams. Response Format Responses to this RFP should include appropriate responses to the Proposal Requirements presented in Section II of this document. Bidders should limit their proposals to a maximum of 25 single-sided 8½ by 11 pages (excluding resumes and sample reports). In replying to this RFP, vendor shall make best effort to comply with the guidelines as follows: Provide appropriate narrative responses and understands that a yes only response to a narrative question may be considered as a no response. Follow the below RFP sections and numbering schema in responding to the items Vendor shall prepare a response to the RFP with supporting materials and documentation and submit as follows: o Four bound hard copies of response and supporting material and documentation RFP for IT Professional Services Page 4

5 o An electronic copy in MS Word or PDF format Vendor acknowledges that responses received after July 2, 2007 at 2:00 p.m. will not be considered. Decision Criteria The final selection of a vendor for this engagement will be made by the decision making team based on the following criteria: Cost of the proposal; Firm experience with large-scale services documentation and governance implementation engagements within the healthcare industry, and preferably at large, diverse academic medical centers and/or other similar enterprises; Firm and individual expertise in Services Oriented Architectures; Demonstrated understanding of relationships among IT Governance, SOA Governance and overall data governance issues and processes; Firm and individual experience with (1) the current M. D. Anderson enterprise infrastructure and application environment, and (2) some of the most key clinical applications in use at M. D. Anderson; Demonstrated experience with defining and implementing technical standards for building and displaying services, with particular focus on security, registration and release of services within an overall governance process; Project management methodology and it s integration with the established M. D. Anderson IT governance process; Other items which may benefit M. D. Anderson that will be provided through the proposed methodology that have not been specifically requested by the Institution. Acceptance or Rejection of Proposals The RFP is not an offer to contract. Acceptance of a proposal neither commits M. D. Anderson to award a contract to any Service Provider nor limits M. D. Anderson s rights to negotiate terms in its best interest. M. D. Anderson reserves the right to accept or reject any or all proposals in part or whole. M. D. Anderson reserves the right to request clarification on any specific responses, omissions, or claims made in responses to the RFP. M. D. Anderson further reserves the right to request modification to a bidder s proposal in order to provide the optimum solution for strategic teaming services. RFP for IT Professional Services Page 5

6 Vendors submitting a proposal does so with the understanding that M. D. Anderson reserves the right to select a vendor of choice based solely on the response to the RFP or to evaluate one or more vendors via additional interviews, site visits, reference checks, and other additional evaluations. M. D. Anderson will notify vendor of the results of the selection process as soon as a final award decision has been made. Statement of Confidentiality The information contained in this RFP and its attachments is confidential and proprietary. It is not to be copied, displayed or distributed to any person or persons not associated directly with M. D. Anderson or your respective firm. RFP for IT Professional Services Page 6

7 Section II Requirements of Respondents Response Requirements 1. Corporate a. Provide an overview of your firm s services both in general and specific to Services Oriented Architectures b. Provide a list of applicable references regarding engagements of this type c. Provide an overview of your firm s experience with the governmental, academic and healthcare sectors d. Provide an overview of your firm s experience and expertise in the following key activities of this engagement: i. Configuring, deploying, and maintaining a Services Oriented Architecture environment ii. Establishing a formal governance environment for a Services Oriented Architectural model iii. Transferring in-depth technical knowledge about Microsoft enterprise infrastructure and application environment tools to M. D. Anderson technical staff e. Provide a listing of health care, academic, and governmental organizations with which your firm has previously engaged for purposes of Services Oriented Architectural analyses, with particular attention to governance processes and procedures f. List any certifications your firm has been granted, related to the (evolving) M. D. Anderson enterprise infrastructure and application environments as well as overall project management 2. Service Team a. Describe how your firm will staff the project, both in terms of the individual key engagement phases, as well as the overall SOA project. Address the use of any use of subcontractors to fulfill this engagement. b. Provide an organizational chart showing the structure and specific personnel for the team that you propose will serve M. D. Anderson. Include the resumes of these team members in an appendix to your response. Resumes should include a brief discussion of each individual s proposed responsibilities at M. D. Anderson, the estimated percentage of their time dedicated to M. D. Anderson, and any RFP for IT Professional Services Page 7

8 unique skills they bring to the engagement. (Note: Only provide resumes for personnel who will be active on the engagement.) c. Describe the proposed staff s specific experience in working within (1) large academic healthcare organizations; (2) successful Services Oriented Architectural engagements; d. Describe any certifications held by the proposed staffing team. 3. Process and Delivery a. Describe your firm s approach for monitoring and controlling an SOA project of this type so that specified budget, scope and schedule are achieved b. Describe the policies and practices your firm utilizes in order to ensure accuracy, consistency and confidentiality of the work performed c. Describe the process for identification and resolution of any issues encountered during the course of the engagement d. Describe your firm s project management methodology including goal-setting, process flows, measurements, milestones deliverables, etc. 4. Documentation a. Provide documentation of one or more IT professional services engagements related to Services Oriented Architecture b. Provide documentation about direct and specific experience with one or more applications built within the Microsoft.NET and Enterprise Library, as well as the Service Oriented Architecture (SOA) framework, as delivered during another engagement of this type. Include such sample documentation in an appendix to your response. c. Provide documentation about one or more large deployment of an SOA Governance structure and process. Include such sample documentation in an appendix to your response. d. Provide cost hourly rates for the following levels of personnel, or equivalent, from your organization: i. Senior project manager ii. Project manager iii. Technical lead software development iv. Developer RFP for IT Professional Services Page 8

9 v. Technical lead - infrastructure vi. Infrastructure support vii. Training viii. Consultant ix. Project Coordinator x. Content Coordinator RFP for IT Professional Services Page 9