NTG Proposal To Medmark - v6

Proposal for Health
Insurance System
MedMark Health and Life
Proposal for Health Insurance System
Contents
1
Objective........................................................................................................................... 3
Introduction...................................................................................................................... 3
2.1
Purpose..................................................................................................................... 3
2.2
System overview....................................................................................................... 3
2.3
Glossary.................................................................................................................... 5
System scope.................................................................................................................... 6
3.1
System components.................................................................................................. 6
3.1.1 HCMS Administration App......................................................................................6

3.1.2 HCMS Service Provider App....................................................................................6
3.2
Operating Environment............................................................................................. 6
3.3
Functional requirements specifications......................................................................6
3.3.1 HCMS Administration App......................................................................................6

3.3.2 HCMS Service Provider App..................................................................................30
3.4
Main user scenarios.................................................................................................36
3.4.1 HCMS Administration App....................................................................................36

3.5
Assumptions and dependencies..............................................................................38
3.6
Out of Scope............................................................................................................ 39
3.6.1 HCMS Administration App....................................................................................39

4
Deliverables.................................................................................................................... 39
4.1
Obligation and responsibilities of NTG Egypt...........................................................39
4.2
Obligation and responsibilities of Medmark.............................................................39
Change control process................................................................................................... 39
Development Process...................................................................................................... 45
6.1
Integration Approach............................................................................................... 46
NTG EGYPT

6.1.1 Software Integration Definition............................................................................46
6.1.2 Software Integration Design.................................................................................47
6.1.3 Software Integration Development......................................................................47
7
Solution Delivery And Project Management....................................................................48

7.1
Delivery of the Platform...........................................................................................48
7.2
Migration strategy................................................................................................... 48
7.3
Integration and Testing............................................................................................48
7.4
Project Management................................................................................................49
8 Pricing................................................................................................................................ 52
7.5
Payment Terms........................................................................................................ 52
NTG EGYPT
PROPOSAL FOR HEALTH INSURANCE SYSTEM

1
OBJECTIVE
NTG Clarity is honored to be given the opportunity to propose our commercial

solution for the MedMark Health Insurance System.
2
INTRODUCTION
2.1 PURPOSE
The purpose of this document is to specify the requirements and preview some elements of the
analysis model of the application.
2.2 EXECUTIVE SUMMARY

HCMS is a comprehensive solution, which helps Medmark as a medical insurance company
to keep track its members, their plans and their services ceiling, and to avoid them any loss
that may be happened because of providing the medical services for uncovered members.
Additionally, to allow medical service providers to validate and maintain the member
services ceiling before providing any service for himhim/her, and help those service
providers to complete the cycle of providing any services in accurate and clear manner.
Medmark provides different insurance schemas and plans for its members, each schema or
plan defines a set of medical benefits that target different types of medical cares, and each
medical benefit defines a set of medical services that can be provided to the members.
The ceiling and cost of each service in a certain benefit depends on the benefit ceiling which
depends on the type of schema or plan that member join it.
NTG EGYPT
2.3 GLOSSARY
Term
Definition
Web application
Application software that runs in a Web browser.
Member
Any customer joins the medical insurance services.
Service provider
Any health care facility or medical practitioner as

Hospitals, pharmacies, labs, radiology centers, clinics.
Transaction
A process of providing medical services to certain member

by certain provider.
(MS.)
Abbreviation for Medmark staff.
(Sub.)
Abbreviation for member.
(SP.)
Abbreviation for service provider.
SYSTEM SCOPE
NTG EGYPT
3.1 SYSTEM COMPONENTS

3.1.1 HCMS ADMINISTRATION APP
It is a web application that will be used by Medmark staff and allow them to manage all
services and keep track all service providers, members, their plans and their services ceiling.
3.1.2 HCMS SERVICE PROVIDER APP

It is a web application that allows service providers to validate and check the member
services ceiling before providing any services for himhim/her.
3.2 OPERATING ENVIRONMENT

HCMS system applications must support the most common and popular internet browsers
such as:
o
o
o
o
IE.
Chrome.
Firefox.
Safari.
3.3 FUNCTIONAL REQUIREMENTS SPECIFICATIONS

REQ-1:
REQ-1: USERS AUTHENTICATION AND AUTHORIZATION

Description:
System must authenticate its users by validating their accounts, and authorize them
by verifying their permissions and privileges.
Functions:
FUN-1: System must authenticate the user by allowing himhim/her to login or sign in
through a valid predefined Medmark account, by typing his account username and
password.
NTG EGYPT
Fig.1. Login Screen
FUN-2: After success login, User can use and access the system functions and
screens according to his permissions and privileges.
FUN-3: System must allow user to terminate his current session and exit the system
at any time via a Logout option at the main header.
Fig.2. (Logout) option at screen header
REQ-2:
REQ-2: MANAGE USERS

Description:
System administrators will be able to manage other system users, users groups, and
define privileges of each users group.
Functions:
FUN-1: System must allow administrator to define new users group.

FUN-2: System must allow administrator to define privileges for certain users
group to determine which screens allowed for it and which functions allows for
it on the screen level.
FUN-3: System must allow administrator to define new user and create a
specific account for himhim/her.
NTG EGYPT

FUN-4: System must allow administrator to define the type of account , as the
new account belongs to Admin, Medmark staff member, or Service provider.
FUN-5: System must allow administrator to select certain user account and
assign himhim/her for certain group to take the same privileges of this group.
FUN-6: System must allow administrator to select certain user account and
modify his data as resetting his password, reassign himhim/her to different
group to take different privileges, or switching his status.
FUN-7: System must allow administrator to select certain users group and
remove or deactivate it, after checking its belonged users and their status.
FUN-8: System should have the log for any change in the users and their
privileges, either for the medmark staff or the providers.
FUN-9: System must allow administrator to select certain user and remove or
deactivate it.
FUN-10: System must have a master admin account by default; this master
account is a static and predefined account that will be used to define other
admins accounts
FUN-11: System must allow administrator to set a privilege on the claim size
for each user/user group , to have a limitation on claims handling based on its
total cost(i.e. there will be some users /user groups that have the authority to
handle any claim with total cost up to the permitted limit)
FUN-11: Each user must have privileges such as:
o Claim size limitation
FUN-12: System must support user groups and apply privileges by default on
users member of these groups
Note
The screen(s) layout will comply with the database relationship between users,
user groups and group privileges
REQ-3:
REQ-3: IMPORT BATCH OF TRANSACTIONS

Description:
About the transactions that were provided by a certain service provider manually
without using HCMS system then need to record and store it into the system.
System must allow user to import a bulk of transactions that executed by certain
service provider to record their data in the system, so this transactions must be
defined in Excel sheet in certain structure to be imported easily.
Functions:
FUN-1: System must allow user to import a bulk of transactions by browsing and
selecting the transactions batch file that was saved on the local directory as Excel
file.
Excel file contains transactions that was executed by one service provider, as all
transactions must belongs to the same service provider.
NTG EGYPT
Fig.3. Import a batch of provided transactions
FUN-2: System will open and view all file content as :

1- The service provider name and ID.
2- A list view of transactions , that represent each transaction as:
o Member ID.
o Schema ID
o Benefit id
o Current Benefit balance (from the DB & before this transaction)
o Service ID.
o Quantity
o Cost.
o Date.
NTG EGYPT
Fig.4. Display transactions list, and mark the invalid ones
FUN-3: System will support a paging mechanism while displaying the imported
transactions in case of the number of imported transaction exceeded the list
size, to facilitate the navigation between them.
Note
this means that the system will read after loading the data- a pre-deifined no.
of records from the database and display them on the screen ,and if the user
scrolling down many times ,then the system will fetch a gain another no.
records and display them.
FUN-4: System will validate all imported transactions and mark any invalid
ones, these invalid transactions may have invalid data or invalid business
rules like exceeding the member ceiling or unauthorized service for the
service provider, so system will mark it to be easy for recognizing and
reviewing.
FUN-5: System will allow user to submit all these viewed transactions into
system DB.
FUN-6: System will allow user to release the imported file and select another
file for certain service provider.
Notes:
The uploaded data will be the balance of each benefit per each scheme for
subscribermember as of a specific data/time regardless the providers
transactions.
Status for the service providers, subscribers, Schemes, and benefits, should
be uploaded if changed.
REQ-4:
IMPORT BATCH OF CHANGED STATUSES
NTG EGYPT

Description:
About the transactions that need to change the status of schema, benefit
,service ,member and service provider.
System must allow user to import bulk of statuses change for schema, benefit
,service ,member and service provider to update the new statuses in the system, so
this statuses change must be defined in Excel sheet in certain structure to be
imported easily.
Functions:
FUN-1: System must allow user to import a bulk of statuses change by browsing
and selecting the statuses change batch file that was saved on the local directory
as Excel file.
FUN-2: System will open and view all file content as :

A list view of statuses to be changed, could be represented as follow:
o Schema
o Benefit
o Service
o Member
o Service provider
o New status
So for each record there will be a value for schema , schema & Benefit , schema &
Benefit & Service ,member or service provider this is with a value for the new status
REQ-5:
MEMBERS TRANSACTIONS REPORTS

Description:
To track members and all their historical transactions, System must allow user to
generate reports about certain member and display a history of all his transactions
and its details through a certain period of time.
Functions:
FUN-1: System must allow user to specify the Member and determine the time
interval that he s/he want to generate a report about it.
NTG EGYPT
1
0
Fig.5. Specify the Member ID, and the time duration
FUN-2: The generated report must display the Member personal information in
addition to the following data about each transaction made by the specified
Member and during the specified time interval:
o Transaction ID.
o Transaction date, time stamp.
o Transaction cost.
o User ID
o Quantity of each item
o Description of each item
o Support meta data for each item through lookup table
NTG EGYPT
1
1
Fig.6. Report about Member transaction over certain duration
FUN-3: At the generated report, System must allow user to select any
transaction and view all its details as:
o The provided services.
o The services quantities.
o The services costs.
o For each service, the cost percentage that was covered by Medmark.
Fig.7. Services provided via certain transaction
FUN-4: At the generated report, System must allow user to select any
transaction and view its service provider and all his information, the provider
name and activity will be displayed for each transaction at the provider
column.
NTG EGYPT
1
2
Fig.8. Service providers of certain transactions
REQ-6:
REQ-5: MANAGE SCHEMAS

Description:
Medmark staff member will be able to manage all insurance schemas, as he s/he can
define new schema, list all of them, search on one of them by its data attributes,
view their details, modify or edit and delete any of them.
Functions:
FUN-1: System must allow user to define a new insurance schema into
system, by entering all its basic data attributes.
NTG EGYPT
1
3
Fig.9. Form of create new schema.
FUN-2: System must allow user to select a certain schema and define all
benefits that must be provided within this schema and the ceiling of each
benefit within this schema.
Then on the benefit level system must allow user to define all medical
services that must be provided within each benefit and the ceiling of each
service according to this schema.
FUN-3: System must allow user to view all defined schemas as a list.
FUN-4: System will support a paging mechanism while displaying the schemas
list in case of the number of defined schemas exceeded the list size, to
facilitate the navigation between them.
Fig.10. List of defined schemas
NTG EGYPT
1
4

FUN-5: System must allow user to search on any schema by its basic data
attributes or even allow himhim/her to filter the displayed list for specific
schemas which match the specified filter.
Fig.11. Filter schemas list
FUN-6: System must allow user to select any schema and view all its details.
FUN-7: System must allow user to select any schema and modify it.
FUN-8: System must allow user to select any schema and delete or deactivate
it, after checking all its dependencies and apply removing constraints.
Fig.12. Actions can be applied on certain schema
NTG EGYPT
1
5

Note
The schema will have a status that may be active or inactive, and the members
transactions will be done only on the active ones
REQ-7:
REQ-6: MANAGE BENEFITS

Description:
Medmark staff member will be able to manage all medical benefits, as s/he can
define new benefit, list all of them, search on one of them by its data attributes, view
their details, modify or edit and delete any of them.
Functions:
FUN-1: System must allow user to define a new medical benefit into system,
by entering all its basic data attributes.
Fig.13. Form of create new benefit
FUN-2: System must allow user to select a certain benefit and define all
medical services that belongs to the selected benefit.
FUN-3: System must allow user to view all defined medical benefits as a list.
FUN-4: System will support a paging mechanism while displaying the benefits
list in case of the number of defined benefits exceeded the list size, to
NTG EGYPT
1
6
Fig.14. List of defined benefits
FUN-5: System must allow user to search on any medical benefit by its basic
data attributes or even allow himhim/her to filter the displayed list for specific
benefits which match the specified filter.
Fig.15. Filter the benefits list
FUN-6: System must allow user to select any medical benefit and view all its
details.
FUN-7: System must allow user to select any medical benefit and modify it.
FUN-8: System must allow user to select any medical benefit and delete or
deactivate it.
NTG EGYPT
1
7
Fig.16. Actions can be applied on certain benefit
The Benifit will have a status that may be active or inactive, and the members
REQ-8:
REQ-7: MANAGE SERVICES

Description:
Medmark staff member will be able to manage all medical services, as he s/he can
define new medical service, list all of them, search on one of them by its data
attributes, view their details, modify or edit and delete any of them.
Functions:
FUN-1: System must allow user to define a new medical service into system,
by entering all its data attributes.
NTG EGYPT
1
8
Fig.17. Form of create new service
FUN-2: System must allow user to view all defined services as a list.
FUN-3: System will support a paging mechanism while displaying the services
list in case of the number of defined services exceeded the list size, to
Fig.18. List of defined services
FUN-4: System must allow user to search on any medical service by its data
services which match the specified filter.
NTG EGYPT
1
9
Fig.19. Filter the services list
FUN-5: System must allow user to select any medical service and view all its
details.
FUN-6: System must allow user to select any medical service and modify it.
FUN-7: System must allow user to select any medical service and delete or
deactivate it.
Fig.20. Actions can be applied on certain service
The Service will have a status that may be active or inactive, and the members
NTG EGYPT
2
0
REQ-9:
REQ-8: MANAGE SERVICES PROVIDERS

Description:
Medmark staff member will be able to manage the contracting service providers, as
s/he define new service provider, can list all of them, search of one of them by his
data attributes, view their details, modify or edit and delete any of them.
Functions:
FUN-1: System must allow user to define a new service provider into system,
by entering all his data attributes.
Fig.21. Form of create new service provider
FUN-2: System must allow user to view all defined service providers as a list.
FUN-3: System will support a paging mechanism while displaying the service
providers list in case of the number of defined providers exceeded the list
NTG EGYPT
2
1
Fig.22. List of defined services providers
FUN-4: System must allow user to search on any service provider by its data
attributes or even allow him/her to filter the displayed list for specific
providers who match the specified filter.
Fig.23. Filter the service providers list
FUN-5: System must allow user to select any service provider and view all his
details.
FUN-6: System must allow user to select any service provider and modify it.
FUN-7: System must allow user to select any service provider and delete or
deactivate it.
NTG EGYPT
2
2
Note
- Each service provider will have a list of authorized or allowed services that can
be provided to the members, and the members transactions provided by this
service provider will be done only on the allowed services for that service
provider
- The service provider will have a status that may be active or inactive, and the
members transactions will be done only on the active ones
REQ-10:
REQ-9: MANAGE SUBSCRIBED COMPANIES

Description:
Medmark staff member will be able to manage the contracting companies and their
groups, as he s/he can define new company or group, list all of them, search on one
of them by its data attributes, view their details, modify or edit and delete any of
them.
Functions:
FUN-1: System must allow user to define a new subscribed company or entity
into system, by entering all its data attributes.
Fig.24. Form of create new company
FUN-2: System must allow user to define super groups and groups of certain
company, plus he s/he can manage all this groups.
NTG EGYPT
2
3
Fig.25. Form of create new company super group
FUN-3: System must allow user to view all defined companies as a list.
FUN-4: System will support a paging mechanism while displaying the service
providers list in case of the number of defined companies exceeded the list
Fig.26. List of defined companies
FUN-5: System must allow user to search on any company by its data
companies which match the specified filter.
NTG EGYPT
2
4
Fig.27. Filter the companies list
REQ-11:
FUN-6: System must allow user to select any company and view all his details.
FUN-7: System must allow user to select any company and modify it.
FUN-8: System must allow user to select any company and delete or
deactivate it.
REQ-10: MANAGE MEMBERS OR CONSUMERS

Description:
Medmark staff member will be able to manage the members, as he s/he can define
new member, list all of them, search on one of them by his data attributes, view their
details, modify or edit and delete any of them.
Functions:
FUN-1: System must allow user to define a new member into system, by
entering all his basic data attributes.
This member must belong to a certain subscribed company or entity.
NTG EGYPT
2
5
Fig.28. Form of create new member
FUN-2: System must allow user to define and manage member dependents
and their ceilings.
FUN-3: System must allow user to view all defined members as a list.
FUN-4: System will support a paging mechanism while displaying the
members list in case of the number of defined members exceeded the list
Fig.29. List of defined members
FUN-5: System must allow user to search on any member by his data
members who match the specified filter.
NTG EGYPT
2
6
Fig.30. Filter the members list
FUN-6: System must allow user to select any member and view all his details.
FUN-7: System must allow user to select any member and modify himhim/her.
FUN-8: System must allow user to select any member and delete or
deactivate it.
Note
- The member will have a status that may be active or inactive, and the
members transactions will be done only on the active ones
- Each member will have only one schema ,so the ceiling of this schema will be
the ceiling of that member
- The system will support uploading the members balances from excel files and
update the members info by these balances and this update will not affect the
old transactions history.

REQ-1: USERS AUTHENTICATION
Description:
System must authenticate its users by validating their accounts.
Functions:
NTG EGYPT
2
7

FUN-1: System must authenticate the user by allowing himhim/her to login or
sign in through a valid predefined Medmark account, by typing his account
username and password.
FUN-2: After success login, User can use and access all system functions and
view all system screens.
FUN-3: System must allow user to terminate his current session and exit the
system at any time via a Logout option at the main header.
REQ-2: PROVIDE A SERVICE TO MEMBER

Description:
System will help service providers to complete the cycle of providing any services
easily and accurately, as medical service providers can validate and maintain the
member services ceiling before providing any service for himhim/her to avoid the
case where member exceeds the service ceiling.
Functions:
FUN-1: System must allow service providers to specify the member that need
the service, by entering member registration ID.
Fig.31. Enter member ID and search on himhim/her
FUN-2: System must validate the member registration ID and display his
name, avatar and his mobile phone number as semi-encrypted number.
NTG EGYPT
2
8
Fig.32. Member initial information
FUN-3: System must allow service provider to send a confirmation SMS with a
unique, secret, and auto-generated PIN code to the member using the
displayed mobile phone, to confirm that he s/he can access member system
data.
Then service provider will enter this PIN code after getting the member
permission to access all his system data.
The PIN code must be expired after a configurable time interval, after that the
service provider must resent a new one to the member again.
Fig.33. Enter PIN code and confirm
NTG EGYPT
2
9

FUN-4: System must allow service provider to view all member data and
assign the required services for himhim/her.
To assign a service for the member, system must allow service provider to
select a certain benefits category according to the member schema, and then
select a service according to the selected benefits category, then add this
selected service into the required services list after viewing its cost.
Fig.34. View a member data and request certain service for himhim/her
Note
The service quantity will be displayied in the above services list
FUN-5: System must allow service provider to check the selected service cost
against the service ceiling, total benefits ceiling and total schema ceiling, to
determine if the required service within the member ceiling and can be
covered or it exceeds his ceiling.
NTG EGYPT
3
0
Fig.35. Check the needed services and add it to required services list
FUN-7: After validating the member ceiling, System views the Medmark
coverage percentage for the selected service and will increment the total cost
of required services and view it.
FUN-8: System must allow service provider to remove any added service, and
recalculate the total cost after removing it.
FUN-9: System must allow service provider to send a second confirmation SMS
with a unique, secret, and auto-generated PIN code to the member using the
displayed mobile phone, to confirm that the member agreed on the service
and on any required payment actions.
Then service provider will enter this PIN code after getting the member
agreement.
The PIN code must be expired after a configurable time interval, after that the
service provider must resent a new one to the member again.
NTG EGYPT
3
1
Fig.36. Enter PIN cod to confirm all added services
FUN-10: System must allow service provider to cancel the confirmation

process and back to the required service list.
FUN-11: System will record this transaction into main DB, and clear the
services list.
FUN-12: System will allow the service provider to view the transactions done
by himself/herself, and he/she will be allowed to delete one or more services
from this transactions, and of course this operation will be logged and
recorded for any reporting.
Note
All the sent SMS messages will be logged on the system
3.3.3 GENERAL NOTES

1. System must support an interface for editing for each lookup table record by record
2. System must support to work with current access database by import and export with
standard raw format ( Access, Excel, Etc.) as intermediate files
2.1. Both systems will be working in parallel and Medmark will be responsible to maintain
integrity between two systems through import and export intermediate files
3. System must support logs for:
3.1. Each transaction on the system with record of time stamped and each user involved
3.2. SMS with status of the messages: sent, delivered or failed with timestamp; according
to the messaging gateway availability.
3.2.1. ZAK: Investigate the availability of SMS delivery reports
4. ZAK: Please add more details regarding how the system will prevent fraud.
5. ZAK: Add mobile web / app option
5.1. For service provider only
6. ZAK: Study hardware requirements with option of amazon cloud
NTG EGYPT
3
2

7.
3.4 MAIN USER SCENARIOS

Import transaction batch.
(MS.)
Login to system
(MS.)
Browse on transactions batch
execl file of certain service
provider, and select it
(MS.)
View and list all transactions
for reviewing
(MS.)
Release the batch file
(MS.)
Record and store transactions
in the system DB
NTG EGYPT
3
3
Generate member services report.
(MS.)
At the side menu, Select
"Repors" item, then select
"member transactions"
subitem.
(MS.)
Enter member ID , and time
interval .
(MS.)
Select one transactione, and
view its services details and its
service provider details.
(MS.)
Generate reports and view all
availabel transactions.
(MS.)
Login to system

Provide service to a member
NTG EGYPT
3
4
(Sub.)
Request certain service
form service provider
(SP.)
Login to system
(SP.)
Enter the subscriper
registeration ID
(SP.)
Check and send
confirmation SMS 1
(SP.)
Review the check result
with member, and send
send confirmation SMS
2
(SP.)
Check and validate the
member's services
ceiling, then the benifits
ceiling , then the schema
ceiling.
(SP.)
Select required benefit
and service, then add it
into the required
services list
(SP.)
Enter member PIN code,
and validate his
information
(SP.)
Enter service agreement
PIN code , and provide
the service
(Sub.)
Get the required service.
3.5 ASSUMPTIONS AND DEPENDENCIES
Medmark staff will be responsible for creating any number of accounts for certain service
provider according to his need, as service provider can request these separated accounts
and distribute them on his employees at its different branches.
User session time out should be configurable through the backend or control panel.
User pin code expiration duration is (2 min) by default, and should be configurable
through the backend or control panel.
Member can subscribe only in one schema at a time.
To import external transactions of certain service provider into HCMS, transactions must
be represented in an Excel sheet with specific structure as following:
o Service provider ID.
o Service ID.
o Member ID.
o Date.
o Cost.
The benefit ceiling will change based on the parent schema.
The service ceiling will change based on the parent benefit and schema.
The mentioned screenshots may have a little modifications and changes at the system
implementation phase to enhance its usability and user experience.
The Screens of the setups and Configurations will comply with the database relationship
between users, user groups , group priviliges, services, benefits, etc
NTG EGYPT
3
5
3.6 OUT OF SCOPE

System does not allow user to modify or edit any of external transaction that was
supported by each service provider as Excel sheet, the system will view information of
this imported transactions only, and store it into system DB.
System does not allow user to rollback any provided service or recorded transaction.
DELIVERABLES
4.1 OBLIGATION AND RESPONSIBILITIES OF NTG EGYPT
Deliver binary files of all system applications that provide all what mentioned in the
scope, as following:
o Binary files of HCMS administration application.
o Binary files of HCMS service provider application.
Deliver all requirements and design documents of solution, as following:
o Software Requirements Specification (SRS) Document.
o User guide document.
4.2 OBLIGATION AND RESPONSIBILITIES OF MEDMARK
Provide any needed business data.
CHANGE CONTROL PROCESS

a. The Change Control Process governs changes to the scope and deliverables during
the term of the Scope of Work.
b. The purpose of this process is to coordinate and properly document the development
and implementation of new responsibilities and services during the Scope of Work.
c. The process will apply to new service components and to enhancements of existing
services.
d. The Change Control Process will be implemented from the start of the project and will
continue throughout the project duration.
e. A Change Request will be the vehicle for communicating any desired changes. The
Change Request will describe the change, the reason for the change, and the effect
the change is expected to have on the project
f. The Project Manager/Coordinator of the requesting party will submit a written Change
Request to the Project Manager/Coordinator for the other party in the format
identified in Change Request Form as attached below.
g. Both NTG and Medmark will review the proposed Change Request. The amount and
payment of the costs of further study, if any, will be agreed upon by both NTG and
Medmark. The results of the study will be used to determine the effect that the
implementation of the Change Request will have on the project cost, duration, scope
and deliverables.
NTG EGYPT
3
6

h. Once the parties have evaluated the Change Request, NTG and Medmark will
complete and sign Change Request Evaluation Response Form as mentioned
below.
Agreed and accepted
Agreed and accepted
NTG Clarity Egypt
Medmark
By: ---------------------------------
By: ----------------------------------
Printed Name: ------------------
Printed Name: -------------------
Title: ------------------------------
Title: -------------------------------
Date:-------------------------------
Date: -------------------------------
NTG EGYPT
3
7
Change Request Form

Medmark HCMS
Requester Name: --------------------------------------------------------------
Requester Company Name: -------------------------------------------------
Date Requested: ---------------------------------------------------------------
Response Requested By: ----------------------------------------------------
Change Requested:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Benefits Of Making The Change:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NTG EGYPT
3
8

Estimated Project Schedule Impact:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Estimated Cost Impact:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Change Request Received:
By: --------------------------------------------Company: -----------------------------------Date: -----------------------------------------Change Request No.: ----------------------
NTG EGYPT
3
9
Change Request Evaluation Response Form

Medmark HCMS
Change Request No.: ----------------------
Requester Name: --------------------------------------------------------------
Requester Company Name: -------------------------------------------------
Review Date: ---------------------------------------------------------------
Request No.: ---------------------------------------------------Has been: ------------- [accepted without changes]

------------- [Accepted with modifications that mentioned below]
------------- [Rejected]
Modifications to Change Request:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Statement of Work Revision:
NTG EGYPT
4
0

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Cost Revision:
Additional Cost: -----------------------------------------------------Party Responsible for Cost: -----------------------------------------------------Additional Cost Payment Due Date: -----------------------------------------------------Acceptance Criteria/Deliverables: ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Agreed and Signed:
NTG Clarity Egypt
Medmark
By: ---------------------------------
By: ----------------------------------
Signature: ------------------------
Signature: -------------------------
Title: ------------------------------
Title: -------------------------------
Date:-------------------------------
Date: -------------------------------
NTG EGYPT
4
1
DEVELOPMENT PROCESS
A software development model is an organized strategy for carrying out the steps in
the life cycle of a software application program or system in a predictable, efficient,
and repeatable way.
Software development process generally follows defined steps, which are:
Specification or functional design, done by system analysts in consort with

the potential end users of the software to determine why to do this, what the
application will do, and for whom it will do it.
Architecture or technical design, done by system designers as the way to
achieve the goals of the functional design using the computer systems
available, or to be acquired, in the context of the enterprise as it now
operates. This is how the system will function.
Programming or implementation, done by computer programmers together
with the system designers.
Testing of new systems (or regression testing of modified systems) to ensure
that the goals of the functional design and technical design are met.
Documentation of the system, both intrinsically for its future maintainers, and
extrinsically for its future users. For large systems, this step may involve enduser training as well.
Maintenance of the application system over its typical 3-years life cycle,
employing the design document as the Technical Specification or System
Maintenance Document.
NTG EGYPT
4
2
6.1 INTEGRATION APPROACH

NTG takes a disciplined and systematic approach to software integration known as
the "4D Methodology". The Four D's encompass:
6.1.1 SOFTWARE INTEGRATION DEFINITION

Like in the construction industry, you have to know what you are building before
you can build it. Therefore, the first step in the 4D methodology is to define what
software will be integrated and define the best method for integration. Also known
as scope definition, this is the point in the software lifecycle where we meet with our
NTG EGYPT
4
3
customers to discuss the software integration needs. We also identify during this
stage whether the software will be able to directly integrate or middleware is
required.
6.1.2 SOFTWARE INTEGRATION DESIGN
This is another vital step in the software lifecycle. Before we begin writing any code,
we first create an integration design plan, which clearly explains in non-technical
terms the best method for integrating the software. In situations where middleware
is required to be developed, NTG will create a functional specification that describes
in detail the functions to be performed by the middleware. Customers will be
involved in every step of this process and actual development of the middleware
will not begin until customer approve on the functional specification. This ensures
that both parties are on the same page as to what will be developed and deployed.
6.1.3 SOFTWARE INTEGRATION DEVELOPMENT
Once all appropriate plans and specifications have been approved, the development
to integrate the software is started. The entire development process is overseen by
customer dedicated project manager who will be provided with scheduled updates
on the progress of development and deliverable timelines. We utilize trusted,
experience development resources with which we've had a working business
relationship for years.
NTG EGYPT
4
4
SOLUTION DELIVERY AND PROJECT MANAGEMENT
7.1 DELIVERY OF THE PLATFORM

NTG follows the standard delivery methodologies to each platform accordingly.
7.2 MIGRATION STRATEGY
NTG has a proven record of migration from one system to another with the following
proposed strategy:
Analyze phase
Migration plan, Design & Considerations
Acceptance test
Full backup
Deployment
Testing
7.3 INTEGRATION AND TESTING
CMMI Pre- Appraisal Level II
Tools: SOAP UI, Red Mine, JTrac, ITTS (Work Flow), JIRA
ITIL Certified
Telecom Engineering Testing (Equipment, Provisioning, Discovery, NMS,)
eTOM Implementation
White Box Testing
Good Knowledge of SQL (TOAD, SQL Developer, Scripts)
Good Knowledge of Environment Configuration (Application Server, SVN,

Database, Client Configuration)
Good Knowledge of Build Tools (ANT, MAVEN, HUDSON..)
Good Knowledge of Database Documentation Tools (ERWIN, Visio, )
Understanding Business Rules and Attending all Analysis Meetings
NTG EGYPT
4
5
Functional Testing (Unit Testing, Integration Testing, System Testing)
Non-Functional Testing (Performance Test, Stress Test, Load Test, Recoverability,

Usability, User Interface/GUI)
7.4 PROJECT MANAGEMENT

NTG Project Management approach is to assign a dedicated end-to-end Project
Manager that will interface with the MedMark Project Manager.
The Project Manager will provide the Project Charter, High Level Project Plan and
establish the kick off meeting with all stake holders
The NTG prime will develop the detailed Project Plan for WBS, as well as the detailed
items with team members assigned from NTG and MedMark.
The Project Manager will formulate the Steering Committee and establish regular
meetings with senior staff for updates on a regular basis
MedMark will identify key primes for the following areas:
o
System Interfaces
Integration Testing
Training (Primes from IT development and support team)
NTG EGYPT
4
6
Handover (to system prime)
Today, the most expensive resources of any project are the personnel. One of the
key challenges is the effective empowerment of these key resources to consistently
deliver quality results that meet the expectations of our clients. This
Implementation Project Life Cycle Methodology provides that capability as well as
establishing a common standard of communication about the project as it
progresses from inception to completion.
The methodology produces the following benefits:
Enhanced productivity
Reduction of scope creep
Reduced change management
Improved quality
The methodology emphasizes what has to be done during an Implementation

project life cycle, not how to do it. Although standard templates and samples are
provided, they serve to establish a standard and consistent means of
communication. They are not solutions in themselves. Rather, solutions to complex
business problems require the application of various best of breed tools and
concepts in order to meet the clients expectations and deliver the optimum results.
NTG EGYPT
4
7

User Documentation
Events/Activities
System Documentation
Conception/Start
Business Case
Feasibility & Approval
Project Plan
Project Kickoff
External Design
Document
Requirement
Analysis
Internal Design
Document
Design
Prototype Testing
Prototyping
System Code
Development
Change Requests
User Acceptance
Test Plan
Acceptance Testing
System Integration
& Training
Collateral
Implementation
Bugs/Changes
Acceptance Results
Post
Implementation
Project Closure
NTG EGYPT
4
8
PRICING
A total amount of 210,000 EGP will be charged to cover the analysis, design,
development any
Customization and testing aspects for agreed Solution, estimated duration for the
proposed scope
Delivery will be 8 weeks starting from Business Requirement Document sign off.
Module
Fraud and subscription
Ceiling management
Tool
Total
Price
210,000 EGP
Comments
210,000 EGP
Optional Remote 8
hours /5 days
Standard Support
In case of heavy
usage for the tool
NTG is offering a
Optional gold support
22%
Due next day after UAT

acceptance (in advance)
37%
Due next day after UAT

acceptance (in advance)
8.1 PAYMENT TERMS
Payments are associated with milestones as follows:
Task Description
% from Total cost
Initial payment upon signing contract
30%
Payment upon submitting design document
30%
Payment upon NTG delivery of tool
20%
UAT and Delivery of Solution
20%
NTG EGYPT
4
9
PAYMENT CONDITIONS AND QUALIFIERS:
Prices are in EGP
Prices quoted do not include third party licenses
Any additional new requirements (after acceptance) would follow change request
processes with additional prices.
Any H/W cost is not included.
NTG EGYPT
5
0

NTG Proposal To Medmark - v6

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NTG Proposal To Medmark - v6

Uploaded by

Copyright:

Available Formats

Proposal for Health

Proposal for Health Insurance System

3.1.1 HCMS Administration App......................................................................................6

Functional requirements specifications......................................................................6

3.3.1 HCMS Administration App......................................................................................6

Main user scenarios.................................................................................................36

3.4.1 HCMS Administration App....................................................................................36

Assumptions and dependencies..............................................................................38

3.6.1 HCMS Administration App....................................................................................39

Obligation and responsibilities of NTG Egypt...........................................................39

Obligation and responsibilities of Medmark.............................................................39

Change control process................................................................................................... 39

Proposal for Health Insurance System

Solution Delivery And Project Management....................................................................48

Delivery of the Platform...........................................................................................48

Integration and Testing............................................................................................48

Proposal for Health Insurance System

PROPOSAL FOR HEALTH INSURANCE SYSTEM

NTG Clarity is honored to be given the opportunity to propose our commercial

2.2 EXECUTIVE SUMMARY

Proposal for Health Insurance System

Application software that runs in a Web browser.

Any customer joins the medical insurance services.

Any health care facility or medical practitioner as

A process of providing medical services to certain member

Abbreviation for Medmark staff.

Abbreviation for member.

Abbreviation for service provider.

Proposal for Health Insurance System

3.1 SYSTEM COMPONENTS

3.1.2 HCMS SERVICE PROVIDER APP

3.2 OPERATING ENVIRONMENT

3.3 FUNCTIONAL REQUIREMENTS SPECIFICATIONS

REQ-1: USERS AUTHENTICATION AND AUTHORIZATION

Proposal for Health Insurance System

Fig.1. Login Screen

Fig.2. (Logout) option at screen header

REQ-2: MANAGE USERS

FUN-1: System must allow administrator to define new users group.

Proposal for Health Insurance System

REQ-3: IMPORT BATCH OF TRANSACTIONS

Proposal for Health Insurance System

Fig.3. Import a batch of provided transactions

FUN-2: System will open and view all file content as :

Proposal for Health Insurance System

Fig.4. Display transactions list, and mark the invalid ones

IMPORT BATCH OF CHANGED STATUSES

Proposal for Health Insurance System

FUN-2: System will open and view all file content as :

MEMBERS TRANSACTIONS REPORTS

Proposal for Health Insurance System

Fig.5. Specify the Member ID, and the time duration

Proposal for Health Insurance System

Fig.6. Report about Member transaction over certain duration

Fig.7. Services provided via certain transaction

Proposal for Health Insurance System

Fig.8. Service providers of certain transactions

REQ-5: MANAGE SCHEMAS

Proposal for Health Insurance System

Fig.9. Form of create new schema.

Fig.10. List of defined schemas

Proposal for Health Insurance System

Fig.11. Filter schemas list