KrishnaSaketh Joginapally

Company Overview: Eligibility Appeals Operations Support (EAOS) enables the business operations and IT needs of the Patient Protection and Affordable Care Act (ACA) Marketplace eligibility appeals adjudication process filed on Healthcare.gov. The CMS Office of Hearing and Inquiries (OHI) and the Marketplace Appeals Group (MAG) oversee the administrative adjudication process that was established for consumers and employers appealing eligibility determinations made by the Federally-Facilitated Exchange (FFE) and State-Based Exchanges (SBE). Approximately 1,000 EAOS users support the adjudication of up to 15,000 eligibility appeals per month from all 50 states, the District of Columbia, in the individual market, large employer, and Small Business Health Options Program (SHOP).

• Directed deployment of Case Management application supporting intake, adjudication, and hearing processes.
• Lead the implementation of the Customer Service application for inbound and outbound calls.
• The call center telephony has been successfully migrated to Amazon Connect.
• Lead the implementation of the Appellant portal for consumers to track the status of their appeal, file an appeal, and upload additional documents.
• Ingested 3,000 appeals from the channels of telephone, web, and DocuSign with no data loss on a daily basis.
• Identified areas for improvement in existing systems and worked with developers to implement solutions.
• Streamlined and built the Correspondence tool to automate the generation and disbursement of outbound communication through email, phone, letters, and SMS.
• Support Infrastructure as Code with the Pega platform. Instance build, upgrade, with zero downtime.
• Build and support Blue/Green deployments for the Pega platform.
• Build pipelines using Pega Deployment Manager for deployment automation.
• Implement AWS SNS, CloudWatch, IaC, Splunk automations, and Kibana using the ELK stack.
• Support the EACMS 2.0 build in Spring Boot, Camunda, and AWS environments.
• Designed the migration plan for the system to Spring Boot microservices on AWS ECS from Pega.
• Environment: Pega V8.3, 8.8, Infinity 24.1, PEGA, V8.5, AWS, Pega Deployment Manager 4.6, Jenkins.
• Projects: Appellant Portal, letter enhancements, system upgrades, electronic outbound correspondence, customer service application, online submission with DocuSign, RADV, Appellant Portal.

• Implement the Pega Upgrade from 7.3 to 8.3
• Fix the issues with the upgrade of the platform
• Redesign and develop the UI to adhere to Pega 8.3 standards
• Implement Pega pulse to support application messaging

• Support Infrastructure as Code with Pega platform
• Instance build, upgrade with zero downtime
• Build and support Blue/Green deployments for Pega platform
• Build Pipelines using Pega Deployment Manager for deployment automation
• Built Scenario tests, Automated unit tests for automating regression tests
• Remote execution of scenario tests using Selenium webdriver

• Leading the development team to adhere to project schedule
• Configured Rest Service to consume the DocuSign Payload
• Leading the development team to implement the Request for Incident Docusign Integration
• Secure integration with DocuSign emails for seamless communication with external stakeholders
• Proposed, Designed in conjunction with Technical Architect and Developed Standard Agents to handle the Payload in the background to handle errors via requeuing with minimal effect on business processing and no loss of customer data when errored
• Parsing the Payload Data to map it to Appeal Data
• Proposed and implemented an intermediate step to handle many errors the user enters from public forms to successfully overcome many validations which Docusign system can not handle
• Configured Connectors to communicate with Docusign to retrieve the Documents, Add Signers, Delete Signers and Purge, Void API’s
• Proposed and developed the solution for real time monitoring of Docusign queues on a periodic basis and requeue the DocuSign failures to reduce the manual maintenance of Failures from Docusign
• The functionality notifies the operations team so as the appeals will adhere to the business timelines
• OAuth Authentication has been implemented for the security of the API
• Project has been delivered on time with no major impact on production performance
• Project: Online Submission-DocuSign Integration

• Worked with 4 Development Teams, Admin Team, Release Management Team, PMO Team, Environments Team to analyze the Gaps and bottlenecks within the process
• Interviewing various teams to document the current state of the system and capture the recommendations for the future state
• Proposing solutions to mitigate the Gaps
• Proposed the Organization-wide Center of Excellence for 4 different applications to handle many organizational standards and reusable components
• Proposed measures to enhance the security of Application
• Implemented audit mechanism to capture changes to data instances(Operator ID and Access group) and trigger an alert to security groups
• Proposed utilization of Rest-enabled command-line tool PRPCServiceUtils instead of existing PRPCUtils for deployment
• In the current state CA Release Automation tool is used in conjunction with Jenkins and PRPCUtils to perform the importing of archives
• Proposed to utilize Pega Deployment Manager and also include exporting archives in the dev-ops model
• Worked closely with Principal Technical Lead to document solutions and develop guidelines for implementation
• Project: Release Management
• Environment: PRPC 7.2.2

• Worked on creating a public facing application which will handle major work flow for the Organization
• Created UI to match the wireframes for the Public Facing Application
• Developed SSO to authenticate with an existing application
• Worked with OneAmerica UI team for seamless integration of Pega Disbursement application from the existing public-facing website using Pega Web-mashup
• Integration using Rest Connector for the Inhouse Mule ESB to create Transactions
• Designing and modeling of the Case type for the Disbursement application
• Implemented Pega Automated Unit test cases and suites for the direction of moving towards Pega Dev-Ops model
• Worked in Agile Methodology
• Project: PegaSonics
• Environment: PRPC 7.3, Pega Cloud

• Proposed and Designed the technical solution for the project in conjunction with Technical Architect
• Configured the rest connectors to retrieve the content of Letter from Drupal
• Proposed the variable reusable paragraphs in drupal to reduce the effort of changing the content of letters
• Binding the data from Appeal into dynamic fields of retrieved content from Drupal
• Conversion of HTML to Pdf using Pd4ml API
• Case design with multi-level approval process for the Managers
• Automatic Conversion of Word to PDF using Apache POI
• Worked collaboratively with AWS and Java Teams to implement the solution
• Involved in Production Support
• Received Accolades from Client
• Project: Letters Automations
• Environment: PRPC 7.3 Oracle 10g, HTML, Drupal, Tomcat 7

• Build Multiple applications using the common framework layer for various business units
• Accolades from Client Manager, Principal architect and the Delivery Manager for the successful implementation of the project
• Project: Supply Chain Management
• Environment: PRPC 7.1, Oracle 10g, HTML, AWS, Tomcat 6,7