• To eradicate the inefficiencies and difficulties faced by the customers of the existing CareView product, which was proposed to rebuild the product with enhancements by using java development tool provided by SAP.
• In addition, the earlier system was built using non-SAP development platform and integrated with SAP components.
• To ease connections and make seamless integration with SAP components, the new version of CareView was proposed to be built purely using the SAP NW components.

MS SQL Server 2000

platform-independent, robust, and scalable Web services and business applications

supports ABAP, Java and Web services

application platform of the SAP NetWeaver, which is the basis for the other NetWeaver components

SAP NetWeaver Developer Studio (NWDS)

• single point of entry for all Java development tools and an integration point for all SAP infrastructure components
• supports in developing Web Dynpro and J2EE applications
• reduces the complexity of Solutions
• increases reusability by providing close support for the component model
• offers a highly flexible development process

• Client-independent programming model of the SAP NetWeaver technology platform for developing user interfaces for Web applications
• Enables a clear separation of processing logic and presentation logic
• Structured according to the Model View Controller (MVC) programming model
• BAPIs (Business APIs) are called from R/3 system using an interface created by the SAP Java Connector (SAP JCo)
• Encapsulation of the processing logic in Enterprise JavaBeans (EJBs) with subsequent use in the Web Dynpro application
• Use of Indigenous and Third party Web services

• Front-end component for SAP NetWeaver
• Platform independent (Windows/Unix installation)
• Multi-lingual support
• Single point of access to SAP and non-SAP information sources,
• Offers role based navigation environment for end users

• Roles: Employees of the health care institution are assigned to various roles depending on their nature of work. Eg. Physiotherapist, Cardiologist, Neurologist etc.
• Locations: Broadly classified into ‘Physical’ (WC) and ‘Organization’ (Org). Examples of Physical or Work Center Locations are bed, room, etc. Examples of Organizational Locations are Department, Unit etc.
• Clients: Clients (patients) are identified based on the physical locations to which they are attached.
• Authorization: The locations are assigned Role/Location based authorizations to restrict access to clients

• Client Registration
• Product Registration
• AZR
• Careplan
• Medication
• MIC
• Employee Registration
• Document Management
• Task Management
• Messages and Notifications
• Agenda
• BZO
• Report Generator

• Client Registration (Client Registratie): The sequence of steps in this application facilitates recording of various details of patients as said above.
• Client Location (Rollen en autorisaties): Clients are assigned physical location in the health care institution and authorizations are set for the Roles to access the locations.
• Personal Information (Personaliainzien): This enables end user to browse through all information pertaining to the selected client.
• The end users (employees) record details like personal data, additional information, locations, health providers and insurance messages in respect of patients
• Additional information on patients generated using Web Dynpro dynamic screens are stored in MS SQL database
• List Patients from R/3 using Adaptive RFC (more than 32 BAPIs are integrated in one transaction)
• Text files uploaded by Insurance Companies are read using XI middleware IDoc Adapter and converted to XML file for consumption in ABAP layer
• A third party web service is used to get complete postal address
• Indigenous web services are built to show Employee Roles, Locations, Labels and messages
• Present the complete transaction using Role based Authorizations

• Care Arrangement (Zorgarrangement)
• Hours per employee (Uren Registratie)
• Time Registration (Tijd Registratie)
• Manager Approval on Time/Hour Registration (Productie Fiaterring)
• Presentation List (Presentielijst)

• Care arrangement is designed to create an agreement with the clients
• Products (Services) are attached to the clients
• The products may be standard products or the prescribed products from the insurance company

• Using the Time registration module, Employees of the care institution can book time spent on different clients on daily basis
• Based on the manager’s approval, the employees can change the bookings.

• Using the Hour registration, Employees of the care institution book hours spent on different clients for a week.
• Based on the manager’s approval, the employees can alter the bookings made previously.

• Using this application, Managers can approve or disapprove the bookings made by the employees for both Time and hour registration
• It gives manager the provision to alter the bookings made by employees and it is designed in such a way to approve/ disapprove bookings for a week or month

• Its purpose is to display the availability of patients for treatment over a selected period along with their details
• It encompasses the employee and manager view of this info in a single point differentiated by their respective roles

• AZR is meant for sending client specific data from the Insurance Company to the care institutions to initiate care for a Client
• After care is initiated for a client, the care information is sent back to the Insurance company from the care institution
• XI plays a key role in this module
• Interfaces built in XI facilitate the inbound and outbound processes
• The AZR Inbound process is achieved by configuring a File to IDoc scenario in SAP XI
• In the Outbound process, ABAP proxy (in SAP R/3) is used to send the information to an outbound file with the help of SAP XI

AZR is made up of following applications,

• AW 33/34
• AW 35/36
• AW39/310

• As the name suggests, this module is aimed at defining health plan for the clients based on initial diagnosis.
• This module processes information from R/3 as well as SQL Server Database
• Dynamic UI Element programming is applied here
• The Careplan is trifurcated into,

• Careplan Definition (Zorgplan Definieren)
• Careplan Regulation ( Acties Zorgplan )
• Careplan Report (Rapporteren Zorgplan)

• Creating agreement between the client and care institution
• Defining care questions to diagnose the problems
• Setting goals and sub goals based on the diagnosis

• Defining actions for the goals and sub goals set in Careplan definition
• Creating questions of various types to get the feedback of the actions imposed on the clients

• Create Recipe: To start medication for a patient, the details of medicines and duration with time intervals are stored
• Stop Recipe: To manually stop the medication prescribed to a client in the previous  application
• Distribution List: The medicines to be distributed to the clients can be seen for a selected period
• Recipe recurrence: To cancel repetition of recipe created through the application ‘Create Recipe’

• Using XML, XSLT and PDF, reports are generated in PDF format

• Employee Registration (Medewerker Registratie) is meant for registering the details of Employees (Health Service Providers like Doctors, Nurses, etc)
• The interfaces made available in this application enable filling up and storing of employee details such as, personal information, assignment of Roles and Locations in the backend R/3 and SQL Database

• Create Task (Taak aanmaken): Several tasks related to clients are created through this application. 
• Task Assignment (Taak Toekennen): Tasks are selected and assigned to employees.
• Monitor progress (Monitoren voortgang): Users monitor the progress made in the tasks

• Create Message: It is meant for creating messages and assigning them to roles
• Display Message : Whenever an employee logs on, he can view the messages assigned to his roles