Testing Methodology: SIT, UAT & CRP

February 2026 · 16 min

The Testing Pyramid for Hospital ERP

Hospital ERP testing has unique requirements because errors can impact patient safety, not just business convenience. A billing error is fixable; a wrong medication dose displayed to a nurse is not.

The FC is responsible for functional testing -- verifying that the configured system behaves correctly for all business scenarios. Technical testing (performance, security, load) is the engineering team's domain, but the FC defines the test scenarios.

Writing Effective Test Scripts

A test script is a step-by-step instruction that any tester can follow:

The 21 FC Scenarios in the FC Scenarios section are your test scenario templates. Each scenario must be expanded into 5-15 individual test cases covering happy path, edge cases, and error conditions.

SIT (System Integration Testing)

SIT validates that data flows correctly across module boundaries:

What to test:

1. OPD to Lab -- Doctor orders test -> Lab receives order -> Lab enters result -> Doctor sees result in OPD
2. OPD to Pharmacy -- Doctor prescribes -> Pharmacy receives Rx -> Pharmacist dispenses -> Stock deducted -> Billing updated
3. Registration to Billing -- Patient registered -> Services availed -> All charges appear on bill -> Payment recorded -> Receipt generated
4. IPD Admission to Discharge -- Admit -> Room charges auto-accrue daily -> Procedures billed -> Medications dispensed -> Discharge summary -> Final bill
5. Lab to Billing -- Lab order -> Sample collected -> Result entered -> Lab charge appears on patient bill
6. Insurance Flow -- Pre-auth submitted -> Approved -> Services rendered -> Claim prepared -> Submitted -> Settled

SIT execution approach:

• FC executes all SIT test cases personally (not delegated to hospital staff)
• Use a dedicated SIT environment with known test data
• Execute in sequence: start with module-level tests, then cross-module integration tests
• Log every defect immediately with screenshot, steps to reproduce, expected vs actual
• Retest after fix; do not proceed to UAT until all Critical and High defects are resolved

UAT (User Acceptance Testing)

UAT is when hospital staff test the system using their own real-world scenarios:

FC's role during UAT:

1. Prepare -- Create UAT test data that mirrors real hospital data (realistic patient names, actual drug names, real service charges)
2. Brief Users -- Conduct a 30-minute orientation for each user group explaining what UAT is, why it matters, and what they need to do
3. Observe -- Sit next to users silently. Watch where they hesitate, where they make errors, where they get confused. These are training gaps
4. Record -- Document every issue the user raises, classify as: Bug (system error), Configuration (needs setting change), Training (user needs instruction), Enhancement (out of scope)
5. Resolve -- Fix configuration issues same day. Escalate bugs to technical team. Provide on-the-spot training for confusion
6. Sign-Off -- Get each department head to sign UAT acceptance: 'I have tested the system and it meets my department's requirements for go-live'

Common UAT challenges:

• Users test only the happy path and skip error scenarios
• Senior staff delegate UAT to junior staff who cannot make approval decisions
• Users raise enhancement requests disguised as bugs
• Department heads are too busy to attend UAT sessions

FC counter-strategies:

• Prepare specific edge-case scenarios for users to test (not just 'test the system')
• Insist on HOD participation for at least 2 critical scenarios per department
• Maintain a clear 'Bug vs Enhancement' classification with the Project Sponsor as arbiter
• Schedule UAT during low-patient-volume hours (2-5 PM weekdays or Saturday mornings)

CRP (Conference Room Pilot)

The CRP is a full-day simulation of a hospital working day using Bio Ecko:

Setup:

• One large conference room with workstations for each role
• Representative from every department (minimum: Registration, Doctor, Nurse, Pharmacist, Lab Tech, Billing Cashier, Accounts)
• FC facilitates and observes; Technical team on standby for issues
• Pre-prepared scenario script that simulates a typical day:

Sample CRP Script (Morning Shift Simulation):

1. 8:00 AM -- Receptionist registers 3 new patients and 2 follow-ups
2. 8:15 AM -- Doctor starts OPD; sees first patient, prescribes meds + orders lab test
3. 8:20 AM -- Patient goes to pharmacy; pharmacist dispenses medication
4. 8:20 AM -- Lab tech receives lab order; collects sample; enters result
5. 8:30 AM -- Doctor reviews lab result; adjusts treatment
6. 8:45 AM -- Emergency patient arrives; triage, assessment, admission to IPD
7. 9:00 AM -- IPD nurse records vitals; administers medication
8. 9:15 AM -- Surgeon schedules OT procedure for admitted patient
9. 9:30 AM -- Patient from morning OPD goes to billing; cashier generates bill; patient pays (cash + UPI split)
10. 10:00 AM -- Insurance patient arrives; pre-auth submitted; billing processed
11. 10:30 AM -- Discharge for a different IPD patient; discharge summary; final bill; payment; receipt
12. 11:00 AM -- Review: What worked? What broke? What needs more training?

CRP success criteria: All 12 steps complete without system-blocking issues. Users can navigate their workflows with minimal FC assistance.

Defect Management

Every defect discovered during testing must be tracked systematically:

Defect resolution SLAs:

• Critical: Fix within 24 hours (blocks go-live)
• High: Fix within 3 days
• Medium: Fix within 1 week
• Low: Fix post-go-live (add to backlog)

Regression Testing

When a defect is fixed, the fix might break something else. Regression testing catches this:

1. After every defect fix, retest the original defect (verification)
2. Also retest 3-5 related test cases that touch the same module or data flow (regression)
3. Before go-live, execute a full regression suite -- all Critical and High test cases from SIT
4. Automate where possible: Bio Ecko's API endpoints can be tested with scripts to verify calculations, data flows, and validations

Regression checklist before go-live:

• All SIT test cases re-executed after final configuration
• All UAT defects fixed and verified
• CRP completed successfully
• No open Critical or High defects
• All Medium defects have documented workarounds
• Performance acceptable (page loads < 3 seconds on hospital network)
• Data migration validated in production environment
• Backup and restore tested

Notes

Related topics