Statement of Work

Project Objectives and Approach:

Objectives

1. Provide Integrated work environment for different end users include CDS, CDS Auditors, Coders, Physicians, CFOS, CDS Managers, HIM
2. Provide CAC (Computer Assisted Coding) with clinical evidance, and Computer assisted query suggestions with clinical criteria in CDS process
3. Integrated DRG groupers with alliance with any third party DRG groupers
4. Inbuilt encoder for code search
5. Advanced search features over patient documents
6. Showing patient documents with NLP annotations which includes Medical keyword higligting, context finding (Either medical word is positive, negative or suspect), and History finder.
7. Work Queues, better communication channel between different type of users, and auto reminders over patient related information (on new document arrival, on user defined constraints over Labs, Medications, Vitals)
8. Integrated Physician query interface, using this CDS can easily create new queries with clinical evidence, and track the queries, and physicians can also directly respond to the queries.
9. Tracking of CDS query performance that include pre and post DRG impact over query and different other CDS and coder performance stats.
10. Different Reports based on User level and dashboards for seeing performance measures
11. Integrated Auditing interfaces, and auditors and CDS and Coders easily sort issues woth out any ambiguity and other work arounds like using mails, Excels.
12. Built on web, easy to connect and use from anywhere with HIPPA Standards security.

Approach

1. Have expertises in moderen NLP technology to process and get meaningful information from patient documents.
2. Real time patient information processing systems, so there is no delay between real information and end users
3. Relatime integration with HIM systems through standard HL7 protocol interface so data is available for users round the clock.
4. Advanced single page reactive client applications, easy to interact

In-Scope:

1. Providing CAC and patient document annotations
2. Providing Work Queues for different end users
3. Stream line the account processing between end users
4. Physician Query interfaces
5. CDI dashboard, Patient Document Dashboards
6. Reports and charts

Out-of-Scope:

1. No auto Principle Diagnosis Suggestion
2. Disease POA will not capture by the system.

Timelines:

We are expecting total time line of 5 months to develop and deliver the end product. Following are estimated epics and corresponding time lines.

Start Time: August 1st 2018 End Time: December 31st 2018

EPIC	EPIC Name	Required Time (Months)
Epic 1	User Authentication and Authorisation System	1
Epic 2	Work Queues	1
Epic 3	CDI Dashboard and Query Interface	1
Epic 4	Patient Document Dashboard	1
Epic 5	Reports and Charts	1

Governance Structure:

Who will manage the project:

Amar Chandrakanth (Project Manager) Krishna Reddy (Team Lead)

Risks and Issues Management: Risks and issues will discuss over stand up meetings and will take final decision by Team Lead and Project manager.

Communication plan: Every Team member will be using Taiga (Project Management Tool) for communication, and for official communication will be done through mail.

Escalation plan, Change Management (how will change requests be managed): Need to write

Executive Steering Committee :

Project Sponsor: Dr. Krishna Prasad Project Manager: Amar Chandrakanth Dev Lead: Krishna Reddy N

Roles and Responsibilities:

Roles

Employee	Team	Role 1	Role 2	Role 3	Role 4
Amar Chandrakanth	HCRCM	Project Manage
Krishna Reddy	KPAI	Team Lead	API Developer	UI Designer
Srinivas A	KPAI	Database Administrator
Rajesh B	KPAI	Front End Developer	UI Developer
Ramu J	KPAI	Front End Developer	UI Designer	UI Developer	Deployer
Naga Deep	KPAI	Front End Developer	Tester	UI Developer
Devi	KPAI	Front End Developer	UI Developer
Suresh	File Server	Data Integration Engineer
Rajini	KPMD	Network Admin

Responsibilities:

API Developer:

• Should Expertise in Spring Boot and Restful Services
• Communicate with Client Application and take requirements from clinet application developers
• RESTFul End points design for KPAI application, and follow industry standard guide lines over design
• Implementation of API End Points business logic
• Communicate with DBA regarding database requirements for End Points
• Testing of API End Points
• Write required Documentations for API End Points
• Should follow and update Project Management tool (Taiga) and should update work status daily

Database Administrator

• Should expertise in MS Sql Server 2008 R2
• Communicate with API developer and fulfil database related requirements
• Proper Schema development and procedure and queries creation
• Continuous testing and tuning of API end point related queries and procedures
• DB routine maintenance check include auto mail alerts over data inconsistency, DB backups and Disater management etc
• Documentation and db change log for every DB related Changes
• DB user access controles and Security management
• Should follow and update Project Management tool (Taiga) and should update work status daily

UI Designer

• Should expertise in Prototype building, photoshop etc
• Application prototype design and communicate with Frontend developers on requirements
• UI Related Colors,Images and Themes Selection
• Define project namings and typography and all frontend related standards and guidelines
• Should follow and update Project Management tool (Taiga) and should update work status daily

Front End Developer

• Should expertise in Angular 6 Frame Work
• Should follow Project specified coding guidelines, and DOS and DONTS
• Check assigned tasks and design components and services in Angular
• Should communicate with API Developer regarding service
• Should communicate with UI Developer regarding template design for components
• Build unit test cases for each component, and communicate with tester on Unit and E2E testing
• Should have knowledge over Code Versioning Softwares, and Continuous integration tools
• Should follow and update Project Management tool (Taiga) and should update work status daily
• On Completion of every feature or task it should be unit tested, E2E tested and documented

UI Developer

• Should have knowledge in HTML 5, CSS 3, Angular Material Design, Boot Strap 3
• Should communicate with UI Designer over Design and follow design guide lines
• Should communicate with Front end developer to work on component templates and corresponding data
• should check Application design compatability over mutiple screens and different browsers in continuous application development stages
• Should follow and update Project Management tool (Taiga) and should update work status daily

Tester

• Should have knowledge in Angular Application Unit and E2E Testing, RESTFul end points Testing, and Selenium technologies
• Should continuously communicate with Developers over changes in application and do robust testing over application
• Build automatic test cases and run test reports before every production build
• Responsible for not failing application in production environment
• Prepare test data for every use case in application dev and production environments
• Should follow and update Project Management tool (Taiga) and should update work status daily

Deployer

• Should have knowledge in Source code versioning tools like SVN, GIT and Continuous integration tool like Jenkins
• Should take proper commits from developers before server deployment
• Should Take pre approval from tester before production deployment
• Should check and back up current build in server
• Should log or document current version and corresponding changes and their impact
• Should run test cases after new deployment in production and make post approval from tester over application consistency
• Should able to revert build if anything goes wrong as earliest
• Should follow and update Project Management tool (Taiga) and should update work status daily

Data Integration Engineer

• Should have knowledge over health care data interoperability protocols like HL7, and interface design between HIM and HCRCM
• Should have predefined Message specification templates over required HIM provided data to KPAI
• Proper integration and testing over communication channel in initial steps
• Should have check points over missing information in established channel

Network Admin

• Should communicate with clients IT team in initial network setup stages
• Should have predefined network interfaces to communicate with client networks
• Need to have continuous check over net work channels
• Need to provide required hardware and systems according to project requirements
• Availability to team over any network related issues
• Should have proper Security mechanisms against Client related information and organisation systems
• Should have technology to recover disaster situations regarding net work related like system hackings, hard disk failures and data recovery

Constraints and Dependencies:

Dependencies:

1. CIRS (Clinical Information Retrieval System) : This is Core NLP system which process every patient related information in real time. Which will provide following features to KPAI application.

2. CAC Coding

3. Patient Document Annotations with Context

4. AQAS (Auto Query Alerts System): Will provide query suggestions to CDS based on patient information context, there around 70 inbuilt query logic available.

5. Mirth and HL7 Interface System: Will provide all patient related information from facility HIM

6. Need third party DRG groupers for both MS and APR DRG grouping.

Constraints:

1. It will impact project objectives and performance, if facility will not provide requested patient information and formats specified by the KPAI system.
2. There is proper communication channel between Facility and KPAI systems, otherwise and it will create data ambiguities.

Risks:

1. Ambiguity between HIM provided information, it will impact production.

Assumptions:

1. We are expecting same team members and other dependencies as mentioned in this documents.

Deliverables:

1. KPAI web application, will be accessible from browser with valid credentials.
2. KPAI Services, this is RESTFul API users can use these services to integrate with some other client tools with proper credentials.

Stakholder Register:

List the identified stakeholders in the project - what is their influence and interest levels

Change Control Process:

If there is any change occurred in the middle of process, that will be discussed with stake holders and will add to the process. If new change will impact existing timelines and resources, then final decision will be taken care by stake holders.