+91 9944844991 · [email protected] · Rajendramani
- Male, born in 1989
- Role: Associate Consultant
- Work experience: 7+ years
- Working as Associate Consultant at Virtusa | Polaris.
- Previously worked at Ebullitent Info Systems LLP.
- ★★★ Java, J2EE
- ★★☆ Spring MVC, Spring AOP, Spring Boot, Spring Data, Hibernate, Mybatis
- ★★★ SQL,PL-SQL
- ★★★ JMS, Activemq
- ★★☆ Tomcat, Weblogic, Websphere, JBoss
- ★☆☆ AngularJS
- ★★☆ JavaScript
-
CareDiscovery Electronic Quality Measures (CDeQM)
Java/J2EE, Spring, Mybatis, REST, Tomcat, IBM liberty
CDeQM provides a comprehensive data-submission manual that defines the data elements needed for calculation of eCQMs. CDeQM accepts patient data from disparate EHR systems and generates actionable insights. The solution assists hospitals in understanding data element definitions, associated value sets, and the likely sources where those data elements may be available within electronic systems. It also assists in performing a gap analysis to identify data elements that are not currently available in the EHR system. To overcome the challenges of eCQM submissions, CDeQM provides dedicated operations support to make submissions to the CMS and TJC on behalf of the hospital. Measuring and reporting eCQMs allows hospitals to deliver effective, safe, efficient, patient-centric, equitable and timely care
-
SAD (suspicious activity detection)
Java/J2EE, SOAP Web services, Weblogic12C
This system is used to analyse and detect the suspicious customer activities. At the time of customer login we took a following information e.g. device id, ip, geo locations etc., and these details need to be send to citi security systems team, where they already have a history of the customer’s geo location, device id, and IP. They will analyse the data and make a risk score. Based on the score we have to decide the following status (DENY, CHALLENGE, ALLOW). If the status is ALLOW, there will be no restriction. If it is DENY, we restrict the customer to proceed further. If it is CHALLENGE, we will allow the customer to proceed further process with some restriction
-
VERIFICATION CHANGES
Struts 1.x, EJB, SOAP Web services, Weblogic12C.
As per BRD, modified the verification process and also added the new feature for offline banking system (PHONE BANKING). Levels of verification are grouped and converted as three level verification namely LOW RISK, HIGH RISK, and SUPER HIGH RISK. If a customer request us to transfer his funds, it should be done with high risk or super risk and should not be LOW RISK. OTP verification feature is added in SUPER HIGH RISK level
-
TNC Maintenance Tool(Content Management Tool)
Java/J2EE, Struts 1.x, Struts2, Hibernate, Weblogic12C.
TNC is a standalone tool. This tool help us to maintain static text in Citibank online. Here we migrated this tool from struts 1.x to struts 2.x. This tool is working based on two criteria (MAKER, AUTH). For every message/contents they maintain a unique TNC id. To make use of these contents in various files we require this TNC id. Because this Id plays a major role. If the MAKER create/modify the content, it will affect the table Work Bean. Once the Maker finish his changes, AUTH will have a control. AUTH is responsible to verify the presence of data in Master Bean. If the data already present, It automatically move that particular data to History Bean. Now it will do the new change of moving the data from Work Bean to Master Bean
-
SLS (service logging system)
Java/J2EE, Struts 1.x, EJB, Weblogic12C.
This service logging system is used internally for tracking the bugs. For e.g. if citi phone officer finds the bug, he need to raise it as a bug and assign it to the respective teams. The team heads validates the bug and assign it to the respective resource, he is responsible for resolving and closing the bug. Based on the BRD, new features like grouping of teams, target date etc. are added
-
SNAPSHOT
Java/J2EE, Weblogic12C
It is an ADDON which helps the customer to see his Account Summary without his credentials but by one time registration. We handled 6 various cases during Registration.
- B.E, Dr.Sivanthi Aditanar College of Engineering, Computer Science, 2007~2010
- Diploma, Arulmigu kalasalingam polytechnic college, ECE, 2004~2007
- SSLC, P.A.C.M School 75%, 2004