Ismt s-599 Capstone Seminar in Enterprise Systems Summer 2015 Team 3

Download 214.01 Kb.

Page	7/12
Date	08.01.2017
Size	214.01 Kb.
	#7835

1 2 3 4 5 6 7 8 9 ... 12

4IMPLEMENTATION PLAN

The proposed service implementation plan is provided with five sub-sections – solution development, deployment, operational readiness, user enablement, and success metrics assessment.

4.1Solution Development

The solution development plan creates a flexible architecture for the entire hospital system and is focused first on the Anywhere Healthcare implementation components. The individual components are constructed as microservices and will be developed and implemented using DevOps²² concepts.

Flexible Services for Hospital

The flexible architecture implementation for the entire hospital system is a multi-year program. A five-year transformation will be done with four phases of implementation. The following table shows the phases and expected delivery and possible outcome:

Phase	Scope	Outcome
Phase 1	Introduce Anywhere Healthcare services to expand the business	20% out-patient revenue improvement
Phase 2	Convert the monolithic Electronic Medical Record system to flexible microservices	Reducing operation cost by 10% and improving system integration
Phase 3	Interconnect old monolithic and new systems using RestAPI and AMQP	Easy integration with both existing and new systems for extending system boundary
Phase 4	Introduce Digital hospital - connects everything in the hospital	Improved patient care, reduce cost and extend services beyond their current application

Services Development

Proposed Agile Principles

1. Involve health care providers in every sprint

2. Use fixed 4 week time-boxes
3. Include lightweight & visual requirements by involving care providers.
4. Develop, integrate and release with iterations.
5. Complete each microservice before moving on to the next
6. Apply the 80/20 Pareto principle
7. Follow a test-driven development process with reduced QA.
8. Follow DevOps principles in each sprint.
An Agile methodology has been chosen to manage design, development, and perform continuous integration and delivery. Major activities are divided into two groups: the system will be developed and deployed using Scrum method; system supporting activities will follow traditional waterfall method. Project time line given below which shows both development and delivery schedule together with supporting activities schedule. For continuous planning, development, integration and deployment we will utilize DevOps principles which can be found at Appendix 4.

Figure : Timeline and Milestones

Each sprint will start with sprint planning to define the features of the microservices as backlogs. List of features will be distributed among the team members to deliver the output in a fixed time frame. It is assumed that project is initiated and recommended hardware is purchased before starting first sprint. Integration of the existing systems will constitute the first sprint. Subsequently, enrollment, monitoring, billing, notification, and initial analytics services will be developed and deployed in later sprints.

Following table summarizes the expected delivery of each sprint from both technology development and supporting services:

Sprints

Development Deliverables

Supporting Deliverables

Sprint 1:

Integration

1. Develop core features of the legacy interface, which includes HL7-based EMR integration and SQL based billing integration. DICOM based interface will be added in next phase.

2. Keep service open for billing system integration, which will be done at Sprint 4.

3. Deploy integration service.

1. Support team will provide IT assessment report which will state current infrastructure: IT hardware, software, and networking components

2. Infrastructure requirement review report

3. Validate low-level design document (LDD) for infrastructure.

Sprint 2:

Enrollment

1. Develop core features of Enrollment service, which includes both patient enrollment and provider enrollment.
2. System should have access to existing EMR system using integration services of Sprint 1.

3. Test and deliver the enrollment service to the Docker containers hosted locally.

1. Physical deployment of the hardware is completed.

2. Cabling and Networking are done.

3. Disks are mounted and partitions are created.

4. VMware installed every hosts and the SAN is integrated as the datastore.

5. vCloud is installed and connected to all 8 hosts.

6. All VMs are created and containers are installed on VMs.

Sprint 3:

Monitoring

1. Develop core features of data pulling from the HealthVault system. The system will have features to receive notification data from HealthVault.

2. Successful tests of sending requests and obtaining offline patient data from HealthVault PPE (Pre-Production Environment).

3. Successful tests of sending data to the AMQP message queue.

4. Successful tests of receiving a list of requests for data pulling from the message queue.

5. Successful tests of scaling the monitoring service depending on volume of requests.

1. Marketing plans including market segmentations, promotional strategies (advertising, sales incentives, discounts, etc.).

2. Partner management guidelines and strategies.

3. Partner meetings organized.

4. Partners are registered.

Sprint 4:

Billing

1. Develop core features of billing engine including billing structure, integrate existing hospital billing system for linking health insurance claims.

2. Test and deploy the system interfaced with hospital EMR and billing system.

3. Test the feature that billing system receives record after enrollment of a new AHC patient.

1. User manuals are developed for both internal users and external users.

2. Trial completed that a selected patient records are received by the system and recorded based on billing info.

Sprint 5:

Notifications

1. Notification service developed

2. Key business rules are captured for notifications.

3. Notifications tested for patient, nursing care providers, ambulatory care providers and hospital internal staffs member.

4. Developed notification dashboard for hospital service administration.

5. Interfaced notification system with at least two ambulatory care providers.

1. Pilot phase started.

2. Subscribers are registered.

3. Pilot results are captured and monitored and connections are made to improve the system.

Sprint 6:

1. Initial analytics services are ready for deployment.

1. Results of pilot are captured.

2. Known issues are fixed.

3. Business ready for go live is achieve.

Sprint DevOps Activities

In each sprint, features of the services will be developed and deployed using DevOps. In a non-DevOps environment, development teams need to wait for the infrastructure teams to deploy the services. In DevOps, development and deployment will be done together with continuous monitoring. The following figure shows DevOps activities for each sprint:

Figure : Proposed DevOps development and Deployment²³

Project Sponsor

GlocoHCP will need to provide an Executive project sponsor for the engagement. This person will be asked to ensure the company’s acceptance of project deliverables during execution and remove any organizational hurdles that will delay the project.

The sponsor will manage the overall GlocoHCP project manager (PM). The TIP project coordinator and PM will work together with the various TIP and GlocoHCP teams and report to the executive sponsor on project status and finances. The project team will then consist of representatives from the different supporting business units including Marketing and IT support. TIPS will manage the DevOps team.

Directory: docs
docs -> Application for acem
docs -> Observational Assessment of Teaching Practices Teaching Assessment Initiative Proposal Submitted to The Teachers for a New Era project
docs -> Traditional British values
docs -> From Warfighters to Crimefighters: The Origins of Domestic Police Militarization
docs -> Borzoi Club of America Register of Merit Program I. What is a Register Of Merit
docs -> Protecting the rights of the child in the context of migration
docs -> United Nations E/C. 12/Esp/5
docs -> 9th May 1950 the schuman declaration
docs -> Getting To Outcomes® in Services for Homeless Veterans 10 Steps for Achieving Accountability

Download 214.01 Kb.

Share with your friends:

1 2 3 4 5 6 7 8 9 ... 12