My group needs to build a system architecture based off of this criteria. How do you think we should go about doing this within 2 months??

Nursing Management System: Background The Our County Health Care Agency (HCA) Community and Nursing Services Division (CNSD) provides home and community based public health nursing services to our residents who meet the criteria regardless of financial status. These services consist of Targeted Case Management (TCM), client advocacy, patient referrals, community resource information and health education in a variety of programs that target specific population of: 1. Pregnant and parenting women 2. Children 3. Adults, and older adults CNSD is responsible for providing over 15,000 public health nursing services to approximately 3,000 individuals annually, the majority being home visits. A comprehensive system is needed to provide effective and efficient solutions along with robust system capabilities. Objective To implement an integrated, secure and scalable web-based nursing case management system solution to support CNSD in conducting a continuum of public health nurse services, effectively, efficiently and support any applicable compliance regulations and requirements. Overall System Capability The system must support all functional activities of a nurse case management system including the ability to create internal business workflows, capture demographic information, produce daily work assignment and activity summary sheet and perform audits. The system shall also be capable of managing the following but not limited to: 1. Assessments 2. Nursing notes 3. Care plans 4. Referrals 5. Reports 6. TCM/MAA time surveys Functional Requirements The system shall have the ability to: 1. View, retrieve and centralize all patient care documents to provide easy access. 2. Monitor CNSD fee-based services using a calendar as a self-tracking tool. 3. Perform electronic documentation of CNSD activities for multiple programs at the individual, family and community level. 4. Create, manage and configure the data fields for CNSD programs within the system, whether they are TCM billable or not. 5. Generate unique identifiers to manage clients and family members comprehensive case management records. 6. Manage billing for comprehensive nurse case management services. 7. Create ad-hoc and customized metrics and have the ability to electronically submit data to the National Family Partnership (NFP) warehouse database if needed.

8. Provide accurate and consistent TCM/Medi Administrative Activities (MAA) reports for monitoring and reimbursement purposes. 9. Apply role-based access control limiting each identified user role with access to a subset of system functions, pages, tabs, fields and the ability to add, update, delete, or view data. 10. Electronically submit required data and outcomes measures to the County Children and Families Commission as a flat file if needed. 11. Create customizable dashboards to view and manage nursing staff workloads. 12. Provide document manageability (import, export, save and print documents) in all formats. 13. Perform data mining and analytics from system. 14. Interface with the State system to electronically submit TCM claims if needed. 15. Perform search using keywords and other criteria. 16. Create and send email notifications, alerts, and reminders for any activity being performed in the system. 17. Provide and capture an audit trail, status updates of all changes made in the system. 18. Be HIPAA compliant for all tiers required by the County. 19. Create and manage a Time Survey Component. The Time Survey component must produce a daily work assignment and activity summary sheet for all nurses and shall have the ability to perform the following: Edit the daily Time Survey activity sheet Prioritize the Time Survey sheet. Record time spent on general activities, mileage traveling to and from services. Bill by time spent on a service. Bill based on service performed. Capture daily activity of who performed the action against what record, against what program, what kind of action and how long the action took. Compute average time per program and generate a time value based on business rules. Automatically and manually schedule the next activity based on frequency, activity type, activity date, and program factoring in County working days. Non-Functional Requirements 1. The system shall be scalable to accommodate additional users and modules as needed. 2. The system shall comply with regulatory components. 3. The system shall be web-based and have a 99.9% up-time. 4. The system shall be accessible 24 hours a day, 7 days a week. 5. The system shall comply with Healthcare IT Security requirements. Reports This system shall have the ability to generate reports for all CNSD programs using a reporting wizard and shall have the ability to: 1. Create canned and ad-hoc reports. 2. Customize reports. 3. Export, print and save reports. 4. Ability to utilize County approved data visualization tools if needed.

Technology Requirements 1. The system shall be a Software as a Service model in the cloud accessible to suit HCA CNSD. 2. The system shall have the ability to support all browsers at their current version levels. 3. The system shall have a user login authentication process with SSO if needed. 4. The system shall have a high degree of usability and user-friendliness in terms of navigation, data-entry, reviewing data and running reports. 5. The system shall provide safeguards for referential integrity of all data. 6. All communications must be encrypted in-transit through the use of standard security protocols: SSH, SFTP, SCP, HTTPs. Data at rest must be encrypted. 7. Mobility Requirements: The system shall be device agnostic, i.e., performance shall be identical whether the end user is connecting from a desktop or a tablet or any mobile device. Menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation. The system shall be designed for optimal performance over slower or unreliable connections. The system shall be designed as the primary expected input methods through the use of drop-down lists, and context-specific fields Project Management 1. Provide a Project Charter and a consolidated Project, which identifies all Contractor and HCA tasks and responsibilities. The execution of the project tasks and activities shall be completed using an Agile approach. 2. Contractor and HCA shall be responsible for establishing an organization to manage and deliver the services defined in this Scope of Work. After being awarded the Contract, Contractor shall provide a project organization chart describing the project charter which shall be in place for the duration of this contract. Contractor shall designate a Contractor Project Manager who shall have the authority to commit Contractor resources necessary to satisfy all contractual requirements. 3. Contractor shall identify all relevant assumptions made in the development of the project charter and the project plan, and upon which the estimates have been calculated must be clearly documented. 4. Change management Contractor shall include a description of the change control management process that will be used in order to manage changes either requested by the County or mitigate any deviation from the plan. 5. Contractor shall develop performance metrics and deliver monthly written project status reports summarizing key activities, comparing plan vs actual and identifying any issues and provide resolutions for the preceding reporting period. The monthly project status reports shall be presented by Contractor's Project Manager to County's Project Manager at monthly project management meetings. This report shall be the basis for advising HCA on project progress and to identify issues with which HCA shall be made aware and work with Contractor to resolve. The

reporting frequency can increase during times where additional communication is needed or required. 6. Contractor shall utilize a comprehensive methodology for ongoing project risk management which addresses such issues as technical risk, resource issues, scheduling problems, and HCA readiness. Contractor shall define escalation procedures to address extended and unresolved problems to County Project Manager. Notification and emergency procedures shall be established in the event of system failure. The escalation procedures shall require approval of County Project Manager. The escalation procedures shall include, but not be limited to the following: Conditions warranting changes to the core team or requiring additional resources in meeting the milestones and/or resolving a problem/issue Time durations between escalating to next level of support A diagram depicting the various levels of response The names, titles, and phone numbers of Contractor personnel responsible for response at the various levels of support 7. Contractor shall make available, via secure FTP (SFTP), an unencrypted full Production backup from the first of every month, in MS SQL file format or XML (SQL preferred), of all county data, related metadata and associated database schema Development, Testing & Training Environments Contractor shall develop separate development, testing, and training environments for the system accessible to HCA IT staff. The project stakeholders shall also have access to these environments for monitoring Contractor work and performing validation. Contractor shall provide a detailed training plan to the County which must be approved by the County project manager. Support and Maintenance Procedures Contractor shall be responsible for establishing support and maintenance procedures for the SAAS system. Contractor shall provide all necessary documentation and procedures needed to support HCAs use of the system on a 24/7 basis. Contractor shall follow standard multi-tier support framework in terms of classifying and resolving issues based on severity and mutually acceptable service level expectations. The training shall be broken down into four (4) major groups: End User, Super User, Service Desk/Field Support, Administrator and Software Support. End Users End Users are the largest group in need of training. They could be further broken down into more specific groups based upon their job function. Super User A Super User will be a staff member that will assist other users with general computer and system problems and will be able to generally distinguish between hardware, operating system, network, and system errors. Service Desk/Field Support Service Desk/Field Support staff shall be trained at the Super User level and be able to accurately triage and record issues for escalation to higher levels of support, identify issues within the system as well and troubleshoot issues with bar

code printers and scanners. Service Desk staff shall also have rights to create and maintain user accounts. Administrative Staff Administrator staff shall be trained to support the front and back-end issues, generate reports and manage the database. Software Support Software Support staff shall be trained at the level of both super user and service desk staff in addition to some selected aspects of the administrative level training. Software Support shall be charged with testing of new releases and updates. User Acceptance Testing Contractor in junction with the HCA project team shall develop test scripts consistent with the requirements as described in the SOW. Contractor shall work with the project team to conduct a User Acceptance Test to ensure that HCA users are able to successfully use the system and that all modified workflows, policies and procedures are consistent with it. HCA users shall assist in the actual test and shall be responsible for final approval of user acceptance test recommendations