NBRS Compliance Testing Script
Information Directorate
National Booking Reporting System
(NBRS)
PMS Compliance Test Scripts for District Health Boards
Organisation
Name: …………………………………………………..
This Compliance Test Scripts document supports the NBRS Compliance Testing Strategy and Approach Plan.
Prepared by: / Anne Goodwin, Richard LeeUpdate by / Richard Lee
Date / 11 August 2015
Version: / 1.0
Status: / Final
TEST SITE DETAILS FORM
In the space below please provide information about the environment in which the tests were conducted. This information is an integral part of the testing process.
Test site: ......
Software name:......
Software version being tested:......
Hardware platform details:......
Operating system and version:......
Are there any differences in the test environment or system from the production equivalent, other than the software being tested? If YES please provide a description:
(Y/N) ......
Please list any additional details required to fully define the test environment in the comments section below or in an accompanying letter.
OTHER COMMENTS:
TESTER:(To be completed by the person performing the tests)
Signed:...... Date: ...... /...... /..
Name:......
Title:......
Organisation:......
Address: * ......
......
Phone:…..………………………………………………………………
Email:……………………………………………………………………
Table of Contents
1 Introduction
1.1Overview
2 Test Methodology
2.1Test Process & Prerequisites
2.1.1 Overview of Test Process
2.1.2 Testing Prerequisites
2.1.3 Summary of Compliance Scenarios to be completed
2.1.4 About the test scripts
3 Data Extraction Compliance Tests
3.1Test Scenario 1a
3.1.1 Compliance Test Scenario 1
3.1.2 Compliance Test Steps
3.1.3 Assessment/Booking Entry Data (BE) Test Data
3.2Test Scenario 2a
3.2.1 Compliance Test Scenario 2
3.2.2 Compliance Test Steps
3.2.3 Assessment/Booking Entry Data (BE) Test Data
3.3Test Scenario 3a
3.3.1 Compliance Test Scenario 3
3.3.2 Assessment/Booking Entry Data (BE) Test Data
3.4Test Scenario 4a
3.4.1 Compliance Test Scenario 4
3.4.2 Compliance Test Steps
3.4.3 Assessment/Booking Entry Data (BE) Test Data
3.5Test Scenario 5a
3.5.1 Compliance Test Scenario 5
3.5.2 Compliance Test Steps
3.5.3 Assessment/Booking Entry Data (BE) Test Data
3.6Test Scenario 6a
3.6.1 Compliance Test Scenario 6
3.6.2 Compliance Test Steps
3.6.3 Assessment/Booking Entry Data (BE) Test Data
3.7Test Scenario 7a
3.7.1 Compliance Test Scenario 7
3.7.2 Compliance Test Steps
3.7.3 Assessment/Booking Entry Data (BE) Test Data
3.8Test Scenario 8a
3.8.1 Compliance Test Scenario 8
3.8.2 Compliance Test Steps
3.8.3 Assessment/Booking Entry Data (BE) Test Data
3.9Test Scenario 9a
3.9.1 Compliance Test Scenario 9
3.9.2 Compliance Test Steps
3.9.3 Assessment/Booking Entry Data (BE) Test Data
3.10Test Scenario 10a
3.10.1 Compliance Test Scenario 10
3.10.2 Compliance Test Steps
3.10.3 Assessment/Booking Entry Data (BE) Test Data
3.11Test Scenario 1b
3.11.1 Compliance Test Scenario 1
3.11.2 Assessment/Booking Entry Data (BE) Test Data
3.12Test Scenario 1b continued
3.12.1 Compliance Test Scenario 1 (b)
3.12.2 Assessment/Booking Entry Data (BE) Test Data
3.13Test Scenario 2b
3.13.1 Compliance Test Scenario 2
3.13.2 Assessment/Booking Entry Data (BE) Test Data
3.14Test Scenario 5b
3.14.1 Compliance Test Scenario 5
3.14.2 Assessment/Booking Entry Data (BE) Test Data
3.15Test Scenario 6b
3.15.1 Compliance Test Scenario 6
3.15.2 Assessment/Booking Entry Data (BE) Test Data
3.16Test Scenario 7b
3.16.1 Compliance Test Scenario 7
3.16.2 Assessment/Booking Entry Data (BE) Test Data
3.17Test Scenario 8b
3.17.1 Compliance Test Scenario 8
3.17.2 Assessment/Booking Entry Data (BE) Test Data
3.18Test Scenario 9b
3.18.1 Compliance Test Scenario 9
3.18.2 Assessment/Booking Entry Data (BE) Test Data
3.19Test Scenario 10b
3.19.1 Compliance Test Scenario 10
3.19.2 Assessment/Booking Entry Data (BE) Test Data
3.20Test Scenario 1c
3.20.1 Compliance Test Scenario 1
3.20.2 Assessment/Booking Entry Data (BE) Test Data
3.21Test Scenario 2c
3.21.1 Compliance Test Scenario 2
3.21.2 Assessment/Booking Entry Data (BE) Test Data
3.22Test Scenario 5c
3.22.1 Compliance Test Scenario 5
3.22.2 Assessment/Booking Entry Data (BE) Test Data
3.23Test Scenario 6c
3.23.1 Compliance Test Scenario 6
3.23.2 Assessment/Booking Entry Data (BE) Test Data
3.24Test Scenario 8c
3.24.1 Compliance Test Scenario 8
3.24.2 Assessment/Booking Entry Data (BE) Test Data
3.25Test Scenario 1d
3.25.1 Compliance Test Scenario 1
3.25.2 Assessment/Booking Entry Data (BE) Test Data
3.26Test Scenario 2d
3.26.1 Compliance Test Scenario 2
3.26.2 Assessment/Booking Entry Data (BE) Test Data
3.27Test Scenario 5d
3.27.1 Compliance Test Scenario 5
3.27.2 Assessment/Booking Entry Data (BE) Test Data
Test Scenario 6d
3.28.1 Compliance Test Scenario 6
3.28.2 Assessment/Booking Entry Data (BE) Test Data
4 Sending and Receiving files
4.1.1 Instructions for Transmitting a Test Extract File
4.1.2 Processing Return Files
Version Control
Version / Date released / Author / Details of Changes1.0 / May 2008 / C. Ross / First version
2.0 / October 2008 / A. Goodwin / Major changes following NCAMP July 2008
2.1 / 20 October 2008 / A. Goodwin / To correct errors in version 2.0
2.2 / 7 August 2009 / R. Lee / NCAMP 09 changes incorporated
2.3 / 24 Jan. 12 / U Singh / NCAMP 11 changes incorporated
2.4 / 11 August 2015 / R. Lee / 2015 Update
Date Last Saved 17 Aug 2015 / Version 2.1 / Page 1 of 51
NBRS Compliance Testing Script
Information Directorate
1Introduction
1.1Overview
The purpose of these compliance tests is to confirm that organisations’ data reporting requirements as documented in the National Booking Reporting System, File Specification Version 4.3(effective July 2011)can pass the Ministry’s NBRS Full Compliance Certification standard.Compliance testing would typically be required when an Organisation’s Patient Management system undergoes a significant change, whether the change originated with the DHB or the Ministry of Health.
If your compliancetest results meet the ‘pass’ requirements and your first production file also successfully passes through the Data Management Services (DMS) Compliance Environment, full NBRS Compliance Certification will be issued and file processing through the Production environment can be resumed.
If you have any queries relating to this Compliance Test Script or the test procedures please contact:
Standard Compliance Contact
Data Management ServicesTel: 0800 505 125
Escalation Contact
Angela PiddTel: 04 816 2805
2Test Methodology
2.1Test Process & Prerequisites
2.1.1Overview of Test Process
/- Data Management Services (DMS)have supplied this test script, which specifies the data we would expect to be supplied in the upload files.
- You will perform the tests using your test environment and PMS system. The data extracted from your system should match the expected data values. Your system must also be able to input and process the Return files produced by Data Management Services (DMS), if that is a function of your PMS.
- Once you have undertaken your own internal testing, you will need to follow the Test script. In doing so, you will be producing four NBRS extract files. Please send each extract file before continuing to the next.
- FTP the extract files as per the ‘DHB Compliance Procedures’that will be sent to you separately.
- Send a notification email to , attaching the completed portion of the Test Script document.
- Data Management Services (DMS) will load each extract file to the NBRS compliance environment and provide an Acknowledgement and Error Return file for each extract. If errors occur during the extract file processing we may require you to make changes to your PMS and/or the Test Scenario data and resend corrected booking events.
- After all extract files have been processed and all errors identified are corrected, you will be given Provisional NBRS Compliance. The next step of sending a production NBRS file for processing in the Compliance Test Environment may then commence.
2.1.2Testing Prerequisites
/- The system you use to perform the tests must be an exact copy of your production system in all structural and operational respects.
- You must be able to enter the test data into your system and generate an extract file containing the data entered.
- The system used for the test must be linked to the test NHI (to register a test patient). You will need to register 9 patients on the test NHI to complete these compliance scripts.
- The Summary on the next page describes the order in which NBRS records should be taken and when an NBRS Compliance extract should be created. It is estimated that all steps can be completed over 4 days. Each extract should contain only the specified records. If your PMS system requires that you generate a Production extract from your test system to clear any unsent messages, please do this,as resending records that have already been accepted may impact on compliance results.
- It is very important that you record the actual values you enter,or that the system generates, as you complete each Test Scenario. This information will be used by the DMS team when investigating problems that may arise during the test. This applies to Patient details entered on the NHI as well as all hospital event details.
- All test booking events should refer to dates on or after 01 July 2015
2.1.3Summary of Compliance Scenarios to be completed
Test Patient / Scenario steps to be completed / Extract 1 / Extract 2 / Extract 3 / Extract 41 / 1a, 1b, 1c, 1d / 1a
04 (Active Review) / 1b
07 (Reassess)
02 (Given Certainty) / 1c
01 (Booked) / 1d
20 (Exited)
2 / 2a, 2b, 2c, 2d / 2a
02 (Given Certainty) / 2b
01 (Booked) / 2c
20 (Exited) / 2d
Delete Record
2 / 3a / 3a
02(Given Certainty - Staged)
3 / 4a / 4a
02 (Given Certainty - Planned)
4 / 5a, 5b, 5c, 5d / 5a
02 (Given Certainty) / 5b
01 (Booked) / 5c
05 (Deferred) / 5d
20 (Exited)
5 / 6a, 6b, 6c, 6d / 6a
02 (Given Certainty) / 6b
01 (Booked) / 6c
06 (Rebooked) / 6d
20 (Exited)
6 / 7a, 7b / 7a
04 (Active Review) / 7b
20 (Exited)
Exit Category 14
7 / 8a, 8b, 8c / 8a
02 (Given Certainty) / 8b
20 (Exited) / 8c
Erase Record
8 / 9a, 9b / 9a
02 (Given Certainty) / 9b
Change Record (Given Certainty – Planned)
9 / 10a, 10b / 10a
04 (Active Review) / 10b
Change Record (Change Purchaser)
Extract / 1 / 2 / 3 / 4
2.1.4About the test scripts
/ ThisTest Script providesthe flexibility to enter procedures across specialties that are typically performed by your DHB. The “NBRS Record Requirement” column (associated with each Assessment/Booking Entry (BE) data in the record) states what is expected in an NBRS record of this booking status code.Where a column states that a field is mandatory or optional, you may enter any valid value you wish for the overall Scenario.
Where a column contains a dash (-), it is expected that any submitted values are consistent with data previously submitted for the booking event. Note that these fields are ignored by the NBRS load process.
We have provided sample Health specialty codes and Clinical codes, however if your DHB does not perform these procedures, please feel free to enter in cases more relevant to you.
You are encouraged to select procedures from across specialties as this demonstrates that CPAC Scoring tools are set up correctly on your system.
3Data Extraction Compliance Tests
3.1Test Scenario 1a
3.1.1Compliance Test Scenario 1
/ OverviewThe purpose of Test Scenario 1is to add a patient to your waiting listwith an Active Review Booking Status Code. The Scenario has 4 steps that would typically be associated with the patient exiting having received publicly funded elective treatment. (Refer to the summary on page 8 for details of which steps are submitted with each extract).
Scenario 1a
Select a surgical procedure that is commonly performed at your facility and take the necessary steps to ensure the patient is added toNBRS in Active Review at a date three months ago. (Please state if you are not able to back-date the addition of a patient to your waiting list and use the current date instead).
Please perform the following steps and enter the compliance test data into your system.
3.1.2Compliance Test Steps
/- Establish a connection to the compliance NHI and register a new patient on your system. Record the NHI number and patient details below.
Test patient 1
Test Patient # / #1
Surname / *SiteTest
First Names
Address
Date of Birth
Gender
Ethnicity
Ethnicity (2)
Ethnicity (3)
NZ Resident Status / Y
Returned Domicile Code
Returned NHI Number
*Site– please enter your site name
- Enter the information as specified in the Test Scenario step into your system.
- Enter the values you have entered for your test in the column labelled ‘Entered on your System’
3.1.3Assessment/Booking Entry Data (BE) Test Data
Field Name / NBRS Record Requirement / Entered on your SystemRecord type / BE
Action code / A
Facility code / Enter your facility code
Local booking system entry identifier / Enter your local booking entry ID
Booking status / 04
Booking status date / Date three months prior to today’s date
NHI number / Enter NHI for Test Patient #1
Date of referral / Date prior to Booking status date / Mandatory when the NBRS booking is first loaded & initialCPACAssessment Date is on or after 1 July 2010 booking source is public specialist (2)
or primary care provider (4).
Booking referral source / 2
Date first specialist assessment / Same date as booking status date
CPAC assessment date / Same date as booking status date
CPAC score / 48
CPAC scoring system identifier / 9081
Date Certainty given / -
Date Booking was made / -
Date booked for treatment or diagnostic test / -
Principal health service purchaser / 35
Contract agency / -
Treatment facility / -
Client system identifier / -
Health specialty code / M10
Booked procedure / -
Clinical code / 3830600
Clinical code type / O
Clinical coding system ID / 14
Deferred by / -
Date of exit category / -
Exit Category / -
Staged/planned procedure flag / 1
Event local id / Enter your event local id
Professional group code / A valid code for your DHB
Clinical responsibility code / A valid code for your DHB
Domicile Code / A valid domicile code
Assessor Code / A valid code for your DHB
Assessor Group Code / A valid code for your DHB
3.2Test Scenario 2a
3.2.1Compliance Test Scenario 2
/ OverviewThe purpose of Test Scenario 2 is to add a patient to your waiting list with a Given Certainty booking status code. The Scenario has 3 steps that would typically be associated with the patient exiting having received publicly funded elective treatment. In addition, (step 4), you will submit a ‘Delete’record. (Refer to the summary on page 8 for details of which steps are submitted with each extract).
Scenario 2a
Select a surgical procedure that is commonly performed at your facility and take the necessary steps to ensure the patient is added to NBRS with a Given Certainty booking status code.
Please perform the following steps and enter the compliance test data into your system.
3.2.2Compliance Test Steps
/- Establish a connection to the compliance NHI and register a new patient on your system. Record the NHI number and patient details below.
Test patient 2
Test Patient # / #2
Surname / *SiteTest
First Names
Address
Date of Birth
Gender
Ethnicity
Ethnicity (2)
Ethnicity (3)
NZ Resident Status / Y
Returned Domicile Code
Returned NHI Number
*Site– please enter your site name
- Enter the information as specified in the Test Scenario step into your system.
- Enter the values you have entered for your test in the column labelled ‘Entered on your System’.
3.2.3Assessment/Booking Entry Data (BE) Test Data
Field Name / NBRS Record Requirement / Entered on your SystemRecord type / BE
Action code / A
Facility code / Enter your facility code
Local booking system entry identifier / Enter your local booking entry ID
Booking status / 02
Booking status date / A date a month ago
NHI number / Enter NHI for Test Patient #2
Date of referral / A few days before Booking status date / Mandatory when the NBRS booking is first loaded & initialCPACAssessment Date is on or after 1 July 2010 booking source is public specialist (2)
or primary care provider (4).
Booking referral source / 2
Date first specialist assessment / Same as Booking status date
CPAC assessment date / Same as Booking status date
CPAC score / 87
CPAC scoring system identifier / 8013
Date certainty given / Same as Booking status date
Date Booking was made / -
Date booked for treatment or diagnostic test / -
Principal health service purchaser / 35
Contract agency / -
Treatment facility / -
Client system identifier / -
Health specialty code / S70
Booked procedure / -
Clinical code / 3720300
Clinical code type / O
Clinical coding system ID / 14
Deferred by / -
Date of exit category / -
Exit category / -
Staged/planned procedure flag / 1
Event local id / Enter your event local ID
Professional group code / A valid code for your DHB
Clinical responsibility code / A valid code for your DHB
Domicile Code / A valid domicile code
Assessor Code / A valid code for your DHB
Assessor Group Code / A valid code for your DHB
Please confirm the following:
Is a Certainty Given Date mandatory in your PMS
when entering a score or priority associated with a
Certainty Given booking status? Yes/No
Can you enter a Certainty Given Date that is before
the CPAC Assessment Date?Yes/No
Can you enter a Date of Referral that is after the
CPAC Assessment Date?Yes/No
Can you enter a Date First specialist assessment Yes/No
that is before the CPAC Assessment date?
3.3Test Scenario 3a
3.3.1Compliance Test Scenario 3
/ OverviewThe purpose of Test Scenario 3 is to add a procedure to a patient on your waiting list with a Staged Booking Status Code. You can use Test Patient 2, and add an additional procedure to that used for Scenario 2.
Scenario 3a
Select a surgical procedure that is commonly performed at your facility and take the necessary steps to ensure the patient is added to NBRS with a Staged booking status.
Please perform the following steps and enter the compliance test data into your system.
3.3.2Assessment/Booking Entry Data (BE) Test Data
Field Name / NBRS Record Requirement / Entered on your SystemRecord type / BE
Action code / A
Facility code / Enter your facility code
Local booking system entry identifier / Enter your local booking entry ID
Booking status / 02
Booking status date / A week before today’s date
NHI number / Enter NHI for Test Patient #2
Date of referral / Same Date of referral value for Scenario 2a / Mandatory when the NBRS booking is first loaded & initialCPACAssessment Date is on or after 1 July 2010 booking source is public specialist (2)
or primary care provider (4).
Booking referral source / 2
Date first specialist assessment / Same as Booking status date
CPAC assessment date / Same as Booking status date
CPAC score / 85
CPAC scoring system identifier / 9010
Date certainty given / Same as Booking status date
Date Booking was made / -
Date booked for treatment or diagnostic test / -
Principal health service purchaser / 35
Contract agency / -
Treatment facility / -
Client system identifier / -
Health specialty code / S45
Booked procedure / -
Clinical code / 5970000
Clinical code type / O
Clinical coding system ID / 14
Deferred by / -
Date of exit category / -
Exit category / -
Staged/planned procedure flag / 2
Event local id / Enter your event local ID
Professional group code / A valid code for your DHB
Clinical responsibility code / A valid code for your DHB
Domicile Code / A valid domicile code
Assessor Code / A valid code for your DHB
Assessor Group Code / A valid code for your DHB
3.4Test Scenario 4a
3.4.1Compliance Test Scenario 4
/ OverviewThe purpose of Test Scenario 4 is to add a procedure to a patient on your waiting list with a Planned Booking Status Code.
Scenario 4a
Select a surgical procedure that is commonly performed at your facility and take the necessary steps to ensure the patient is added to NBRS with a Planned booking status.
Please perform the following steps and enter the compliance test data into your system.
3.4.2Compliance Test Steps
/- Establish a connection to the compliance NHI and register a new patient on your system. Record the NHI number and patient details below.
Test patient 3
Test Patient # / #3
Surname / *SiteTest
First Names
Address
Date of Birth
Gender
Ethnicity
Ethnicity (2)
Ethnicity (3)
NZ Resident Status / Y
Returned Domicile Code
Returned NHI Number
*Site – please enter your site name
- Enter the information as specified in the Test Scenario step into your system.
- Enter the values you have entered for your test in the column labelled ‘Entered on your System’.
3.4.3Assessment/Booking Entry Data (BE) Test Data
Field Name / NBRS Record Requirement / Entered on your SystemRecord type / BE
Action code / A
Facility code / Enter your facility code
Local booking system entry identifier / Enter your local booking entry ID
Booking status / 02
Booking status date / Two weeks prior to today’s date
NHI number / Enter NHI for Test Patient #3
Date of referral / Three weeks before Booking status date / Mandatory when the NBRS booking is first loaded & initialCPACAssessment Date is on or after 1 July 2010 booking source is public specialist (2)
or primary care provider (4).
Booking referral source / 2
Date first specialist assessment / Same as Booking status date
CPAC assessment date / Same as Booking status date
CPAC score / 93
CPAC scoring system identifier / 9110
Date certainty given / Same as Booking status date
Date Booking was made / -
Date booked for treatment or diagnostic test / -
Principal health service purchaser / 35
Contract agency / -
Treatment facility / -
Client system identifier / -
Health specialty code / S35
Booked procedure / -
Clinical code / 3933101
Clinical code type / O
Clinical coding system ID / 14
Deferred by / -
Date of exit category / -
Exit category / -
Staged/planned procedure flag / 3
Event local id / Enter your event local ID
Professional group code / A valid code for your DHB
Clinical responsibility code / A valid code for your DHB
Domicile Code / A valid domicile code
Assessor Code / A valid code for your DHB
Assessor Group Code / A valid code for your DHB
3.5Test Scenario 5a
3.5.1Compliance Test Scenario 5
/ OverviewThe purpose of Test Scenario 5 is to add a patient to your waiting list with a Given Certainty Booking Status Code. The Scenario has 3 steps that would typically be associated with the patient exiting being booked, failing their pre-op assessment and being removed from the list because they are medically unfit. (Refer to the summary on page 8 for details of which steps are submitted with each extract).
Scenario 5a
Select a surgical procedure that is commonly performed at your facility and take the necessary steps to ensure the patient is added to NBRS with a Given Certainty booking status.
Please perform the following steps and enter the compliance test data into your system.
3.5.2Compliance Test Steps
/- Establish a connection to the compliance NHI and register a new patient on your system. Record the NHI number and patient details below.
Test patient 4
Test Patient # / #4
Surname / *SiteTest
First Names
Address
Date of Birth
Gender
Ethnicity
Ethnicity (2)
Ethnicity (3)
NZ Resident Status / Y
Returned Domicile Code
Returned NHI Number
*Site – please enter your site name
- Enter the information as specified in the Test Scenario step into your system.
- Enter the values you have entered for your test in the column labelled ‘Entered on your System’.
3.5.3Assessment/Booking Entry Data (BE) Test Data