Scribd
Upload
21 views

HealthCare Domain Testing

The document discusses healthcare domain testing and describes a data migration project from source to target systems. It outlines the data flow through different staging layers and validations performed, including checking for duplicates, schema validation, and comparing data in the target and reporting layers.

Uploaded by

subhabirajdar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
21 views

HealthCare Domain Testing

The document discusses healthcare domain testing and describes a data migration project from source to target systems. It outlines the data flow through different staging layers and validations performed, including checking for duplicates, schema validation, and comparing data in the target and reporting layers.

Uploaded by

subhabirajdar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

 HealthCare Domain Testing

 We can’t use the low performance of system because that applications effect on all the health
care system so in this project we check the quality of the applications.

 Healthcare Domain Testing is a process to test healthcare application for various factors like
standards, safety, compliance, cross dependency with other entities, etc.
 The purpose of healthcare domain testing is to ensure quality, reliability,
performance, safety and efficiency of the Healthcare application.
 We can’t use the low performance of system because the that effect on all the health care
system

 Basic knowledge of Health Care Domain

 The entire health care system is weaved with each other by the single body that is
hospital or provider (doctor).

 While the other entities include-

1. Insurance company: Medicare, Medicaid, BCBS, etc.


2. Patient/Consumers: Patient Enrolled
3. Regulatory Authority: HIPAA, OASIS assessment, HCFA 1500 and UB92, etc.
4. Health-care and Life-Science solution Vendors

 Basic Terminology of Health Care System:

A. Provider: A health care professional (doctor), medical group, clinic, lab, hospital, etc.
licensed by health care services
B. Claim: A request to your health insurance company to pay a bill for health care
service (Who pay or give the money for hospital )
C. Broker: An insurance professional, who negotiates, procures insurance on behalf of
insured or prospective insured
D. Finance: Insurance bodies that pay for medical expenses, it could be government
(Medicare or Medicaid) or commercial (BCBS)
E. Medicare: A federal health insurance program for senior citizen and permanently
disabled people
F. Medicaid: A joint and state program that helps low-income families and individuals
pay for the cost associated with medical care
G. CPT code: A current procedural terminology code is a medical code set to describe
medical, surgical and diagnostic services(It is code to describe the procedure how to survice
and describe all the terminology in that)
H. HIPAA: It is a set of rules and regulations which doctors, hospitals, healthcare
providers and health plan must follow in order to provide their services.
Introduction of project

Johnson data migration AIA


 In this project basically there is data flow from source to target with different changes that are
given in requirement

Source: Source is basically the data which is coming from Source. We are calling it as SPC source which
includes about the information about Medical equipment. There are available in views

 Columns available like a) name of instrument, b) supplied date c) warranty date d)


warranty start date e) warranty end date f) net rate etc.
 Eg. In source table data coming from diffrenet different branches and different
euipements of hospitals in the form of above formate.

 Source contains the data which is in raw condition which is not good for presenting
in front of clients or business users. That data is cleaning by applying different types of
functions like

1. Joints
2. Aggregations
3. Case
4. Set operations
5. Like
6. Other different functions

 In source Development team involved so by using , aggregates different data and they

are creating views(virtual table) for that The views are considers as a containers for

flow and names as

 Suppose data from different hospitals and by using the joins we create the one set

for that hospitals.

1. Medical installation equipment’s


2. Case related equipment’s
3. Service Related equipment’s

These all data flows in different layer in data staging which are having different nomenclature

1. fine
2. very fine
3. super fine

1. Fine: Fine is first staging area of data where data from source is kept as it is.
Sometime if any type of changes requires in data that we are doing from fine to very
fine. In this we use the azur/pipline .
2. Very fine: very fine is second stage of staging area where aggregations are used on
data for minimizing the uncleanliness in data. sometime some other data is merged in
very fine stages. In this layer data store in from like nulls ,duplicates ,some blanks so we
should clear it.
3. Super fine stage: In super fine stage we are placing all data in very fine conditions. in
this stage data columns are reduced by applying certain conditions. In this stage, data
consist of information about all data that is coming from source but in limited
columns.

Data flows for staging area is done in Azure SQL

We will make change according to requirement in different layers


Checks that are used for testing
1. Check for duplicates
2. Count match
3. Sample data matching
4. Schema validation
5. Table name
6. Table structure
7. Calculations validation
8. Validating data with reporting layer

Reporting tool:

Qlik view
Key Performance Indicators

20
feb

OX

40

206

* 106
' Mexnco

 In reporting we use the Qlik view tool used.


 So,In this we compaire data in target table and reporting layer by using excel ,We copy the data
from target table i.e super fine layer and export the data from reporting layer and compair it.
 Defect tracking
For defect tracking, we are using azure devOps

You might also like