Validate your NBS 7 deployment
Before go-live, confirm that all deployed components are functioning correctly and that data flows as expected from ingestion through to the NBS interface. Work through validation in sequence: start with core microservices, then confirm ingestion and notification pipelines, then run system-level checks across the NBS UI.
On this page
Before you validate
Confirm the following before starting:
- Deployment of all required microservices is complete for your chosen configuration
- A development or staging environment is available with representative test data
- You have admin credentials to access the NBS UI
- Your NBS 6 database refresh is complete and accessible from the test environment
Validation sequence
Work through the areas in this table in order. Resolve failures before moving to the next area.
| Validation area | What it confirms | Documentation |
|---|---|---|
| Elasticsearch, Modernization API, and NiFi (manual validation) | Name resolution is working; routing between NBS 6 and NBS 7 subsystems is correct; database connectivity from NBS 7 components is working; search indices are created and populated | Manual validation |
| Modernization API smoke test | API endpoints respond and return expected results | API smoke test |
| NBS UI and patient search smoke test | The NBS interface is accessible and patient search returns results | Web UI smoke test |
| Data ingestion smoke test | Individual ELR and eCR messages are accepted and routed correctly | Smoke test |
| Data ingestion API testing | Data ingestion API endpoints are reachable and functioning | API testing |
| Data processing RTI integration | Real Time Ingestion processes ELR data correctly and returns expected status codes | API testing and integration |
| Case notification API testing | Case notification service is processing and routing notifications correctly | API testing |
| NND service API endpoints | Data sync API endpoints are reachable and credentials are valid | Validate API endpoints |
| RTR pipeline validation (if deployed) | Streaming updates flow from ingestion through to reporting datamart tables | Pipeline validation |
System-level checks
After all component-level validation passes, confirm overall system behavior before proceeding to go-live:
- Log in to the NBS UI (for example,
https://app.example.com/nbs/login). - Verify that patient search returns results using test records.
- Create a test investigation and confirm it appears correctly in the UI.
- Confirm that ELR data ingested during testing is visible and correctly attributed.
- Review application logs across services for unexpected errors or warnings.
- Confirm that monitoring and alerting are configured and capturing baseline metrics.
Next steps
When all validation areas pass, finalize your cutover checklist and launch NBS 7 in production.