We Connect

Client: Avaunte Inc, USA(www.avaunte.com)
Environment: Ensemble, ZEN, Cache DB, Cache Object Script, IIS, HL7/HIPAA,Windows, Macintosh

CHC is a system consisting of, “a collection of systems”. Designed with the recognition that multiple systems are required to meet the many and evolving needs of the health care user community and yet the need for a unified underlying overall management system. It does so through a collection of systems that are categorized underlying as Vertical Systems & Horizontal Systems.
CHC Front-Office – Doctor's front-office could schedule and edit appointments, check-in patients and create encounters a sophisticated and yet user friendly interface.
CHC Rounds – This is very helpful modules for doctors who make rounds at different times at different facilities. The rounding system gives them the ability view their rounding schedule, input new diagnoses and procedures performed for each round made, bill for a round even forward a round for next visit.
CHC Referrals – Individual Providers or Hospitals can refer patients to Individual providers and/or Hospitals though the referral system. Notifications are triggered to the specified users and work flow tasks created to make sure the referral received is processed and duly routed .
CHC Revenue – Patient encounters information could be used to generate invoices and file claims to respective Insurance companies and Individuals and is communicated through protocols as required by the receiver of the claim. Upon receipt of payment the same is also posted on account.
CHC Directory – A central repository of all accounts and contacts for the client which serves a huge purpose in facilitating effective communication.
CHC Documents – Any document related to any entity including a payer, provider, patient, subscriber etc. is scanned and saved in document data base. It is then indexed accordingly to respective entities and also distributed and categorized into groups, categories and types.
CHC Entities – CHC serves as a central repository for clients for their Patients, Guarantors, Contacts, Payers, Subscribers etc. with their detailed information. CHC also makes available the entire national provider index database as an entity.
CHC Integration – CHC is integrated with different health care systems including PrognoCIS, GE, Cedars Sinai etc. to exchange data via various protocols and interfaces as required.
CHC Standards – CHC makes available Industry (ICD, HCPCS etc.) standards and lets client create and maintain codes and types as to their specific needs.

Client: Ceva Logistics, USA(www.cevalogistics.com)
Environment: JCAPS 5.3, Sun MQ, Solaris 10, EDI X12, JDK 5, Oracle, DB2, ISeries, HTTPEway, FTP Eway, JDBC Eway, WebServices,Sun Cluster

The goal of Ocean Booking And Shipping is to send Booking Requests and Shipping Instructions and receive a response back in terms of Booking Confirmations and Shipping Freights. Also functional acknowledgments are sent/received on all communications received/sent.
Ceva logistics acts as a Forwarder in most of the cases and thus we receive requests from multiple carriers and forward the same to multiple providers depending on different scenarios and factors. The same isdecided in the business logic.

Client: Sun Microsystems, USA(www.sun.com)
Environment: ICAN, JCAPS, Solaris, AIX, Windows, Oracle, SQL Server, Sun Java Integration Server, Sun JMS Grid, Sun MQ, Open LDAP,
Genisys eWays and IH, PL/SQL,Sun Cluster

The goal of the Genisys project is to consolidate all application integration in Sun IT onto Sun SeeBeyond JCAPS/JMS messaging platform products. In so doing applications will be migrated off the Enterprise Information Highway onto the Enterprise JMS Grid. While the two messaging infrastructures are running concurrently a gateway will connect the two, passing messages between them to enable a seamless transition of applications from IH to JCAPS over time. The EMI Genisys Software Package contain SeeBeyond JCAPS middle-tier product software and own developed value-add software packaged as
Solaris pkgadd files.

Client: Sun Microsystems, USA(www.sun.com)
Environment: ICAN, JCAPS, Sun MQ, Solaris, AIX, Windows, Oracle, Sun Java Integration Server, Sun JMS Grid, LDAP, FTP/SFTP/Oracle/File eWays, PL/SQL, JDBC, JDO, JPA,,Sun Cluster

DSF is a dynamic service execution architecture that allows for the execution of a series of re-usable atomic services that execute based on dynamically set properties configured in the Configuration tables. A typical example of this is a general use FTP Hub. This framework comes with some basic file services that allow for the construction of a FTP Hub. It is a middle-tier framework that allows the creation of atomic services that can have parameters dynamically set at runtime. It will then allow the chainingof these services together to execute an end to end business solution. Therefore the goal of service development within the framework is to create simple atomic services that may have maximum re-usability.

Client: Sun Microsystems, USA(www.sun.com)
Environment: ICAN, JCAPS, Sun MQ, Solaris, Windows, AIX, Oracle, SQL Server, DB2, PL/SQL,Sun Cluster

CSF includes a common platform and a number of CSF Services that can be invoked from client applications through any of the client interfaces including J2SE Applications, JMS Messages, and Web Services. All client requests are passed in the form of the universal Common Message Envelope (CME) which is routed to the appropriate service. This decouples services from each other and CSF interfaces, allowing independent development of new services, and new types of interfaces, such as .NET or SRE. The CSF fits seamlessly in the CAPS architecture leveraging the Service Oriented Architecture, Web Services and J2EE design patterns. CSF is an open platform and allows adding, removing and replacing services to meet specific client and project requirements. It is based on best practices and development standards and can meet most performance and scalability demands.

Client: Fidelity Investments, UK(www.fidelity.co.uk)
Environment: Windows Server 2003, NetIntegrity SiteMinder 6.0, Websphere Application Server 6.0, Sql Server 7.0, WSAD 5.1, Struts 1.2, Hibernate, Tiles, PL/SQL

Fidelity Investments wishes to diversify its site providing its clients and consultants a secured area to enable them to view various funds performance, portfolio, manage their savings among the various other functionalities. Fidelity follows CS503 Standard for user authentication. They also have their own
Corporate Pin Server integrated with NetIntegrity SiteMinder. The new site would use the following standard and use the existing pin server to authenticate user and provide the functionality as per the roles defined in that server. Also we defined resources which are protected and require authentication. Customauthentication code was embedded in siteminder which would handle page flow upon authentication

Client: Logitech Inc, USA(www.logitech.com)
Environment: Windows Server 2003, Autonomy 4.0, IBM Lotus Notes 6.3, Websphere Application Server 6.0, Sql Server 7.0, Eclipse 3.0, Tomcat 4.1, jdk 1.4, log4j

Logitech had Lotus Notes as its main repository of documents. It intended to have a search application, which could enable them to search for a particular set of documents easily and faster based on a keyword, which Notes could not do. Data was fetched from Lotus Notes via Notes Fetch into Autonomy and various search features were provided to search and view document to the granular level.