The purpose of the certification process is to enable your Organisation’s Laboratory Information System (LIS) to implement an existing certified BloodNet LIS interface into your production environment.
Once your Organisation’s BloodNet LIS interface is implemented your administrators and users will be able to enjoy the following full benefits of automated:
- Import of receipted items from BloodNet into your LIS System;
- Fate of received items from your LIS into BloodNet; and
- Regular updated inventory stock levels into BloodNet.
Through LIS interfaces the current manual processes of entering stock levels for orders, dual system receipting and separate entry of the fate discard, transfer and transfusion information in the system automated between BloodNet and your LIS.
To complete the Facility LIS certification process please complete the following three steps:
- Create a separate new user account for each LIS Administrator in the BloodPortal;
- Complete the LIS Interface Signup Form; and
- Verify that facility’s LIS Interface is correctly integrated with BloodNet LIS Web Services.
LIS Interface Verification
The goal of the BloodNet LIS Facility Interface integration verification process is to ensure that the already verified implementing LIS system can communicate successfully with the BloodNet LIS web services in the facility environment. To do this the NBA needs to assess the completeness of the implementation of the LIS web services in the local test environment before allowing access to the production environment.
This process provides assurances to the developer of the BloodNet LIS interface, the NBA and your pathology service that integration between the LIS and NBA LIS web services will operate locally as expected.
Once this process has been completed a formal sign off process is undertaken that confirms that the NBA is confident the BloodNet LIS interface will operate as intended for the facility and/or organisation, thereby reducing the risk of problems being discovered in production that would impact their own, others or the NBA’s ability to process LIS Interface transactions.
The process will require facilities to undertake the required Verification steps detailed below in the Verification Testing section to establish that testing of both function and connectivity has been undertaken by facilities. A report detailing the testing and quality assurance activities undertaken must then be provided to the NBA. Upon receipt of this report the NBA will undertake independent verification that has to be accepted before any LIS or Organisations will be issued with their production credentials.
The full set of BloodNet LIS web service functionality outlined in the BloodNet LIS Technical Specification (1.89 MB) is available in the LIS Testing environment at https://uat.blood.gov.au/BloodNet5/LISService/LISService.svc - corresponding BloodNet website is https://uat.blood.gov.au/BloodNet5/Web.
Facilities and LIS Software Providers however will only need to perform the integration verification testing process using the following minimal set of Web Service methods:
- AcknowledgeReceiptedIssueNotes – This web service method will send, every 5 minutes or via user initiation, an automatic acknowledgement to BloodNet indicating that the unit is now in stock at the facility.
- GetReceiptedIssueNotes – This web service method will return, every 5 minutes or via user initiation, an automatic list of receipted issue notes awaiting acknowledgement.
- UpdateRealTimeInventoryLevels – This web service method will send, every 15 minutes automatically, the up to date information of the facility’s stock levels.
- FateOfUnit– This web service method will send, every 5 minutes or via user initiation, an automatic unit status changes.
Environment, Timeframes, Availability and Support
The environment used for BloodNet LIS Interface verification is the BloodNet LIS Test environment. The environment is available all hours but only technically supported during standard business hours, Monday-Friday 9.00am-5.00pm AEST.
Any planned changes or outages to the environment will be communicated to LIS Administrators, LIS Developers and any designated contact officers via email. The NBA will maintain and make available this stable test environment keeping changes, where possible, to a minimum so that those accessing service can do so as and when required.
For any support enquiries please contact the NBA:
- Email email@example.com
- Call 13 000 BLOOD (13 000 25663) | +61 2 6151 5000
- Fax +61 2 6151 5210
The following scenarios detail the required functional and connectivity testing required to be undertaken by organisation or facilities that will then be verified by NBA. These three scenarios must be undertaken to the specified requirements.
Once completed, you will need to provide a report demonstrating that each Scenario and all necessary iterations were successful to the NBA for verification. Additionally a checklist has been included to help individual facilities perform the necessary testing steps required to achieve local verification.
1.Scenario A: (Acknowledging Issue Notes)
In this scenario the facility will acknowledge some receipted issue notes.
Step 1: The facility will call the GetReceiptedIssueNotes web service method to return a list of receipted issue notes awaiting acknowledgement.
Step 2: The facility then should call “AcknowledgeReceiptedIssueNotes” Web Service method to acknowledge the returned issue notes (from the GetReceiptedIssueNotes).
Verification: Is achieved when the Web Service method calls were successful; the LIS Log page in the BloodNet web site lists the acknowledged issue notes and the information on the Receipting web page reflects correctly the acknowledged Issue Notes. NBA then confirms these results on no less than 5 calls and 50 issue notes.
2.Scenario B: (Update Inventory Levels)
In this scenario the facility will send up to date information of their stock levels.
Step 1: The facility will call the UpdateRealTimeInventoryLevels web service method with their stock levels.
Verification: Is achieved when the Web Service method call was successful; the LIS Log page in the BloodNet web site lists the stock update details and the inventory update is shown on the LIS Inventory Dashboard web page. NBA then confirms these results on no less than 1 day of LIS inventory level updates.
3.Scenario C: (FateOfUnit)
In this scenario the facility will send a discard fate for a component and product.
Step 1: The facility will call the FateOfUnit web service method with a component discard payload.
Verification: Is achieved when the Web Service method call was successful; the LIS Log page in the BloodNet web site lists the fate details and the fate summary page reflects the new Component Discard. The user is also able to view the Component Discard fate details.
Nb. Scenario C must be repeated for all other Fate types and for Products
NBA then confirms these results on no less than 40 calls and 40 successful fate records.
Once the verification tests are completed successfully; the facility will be issued with the LIS production service account and credentials.
To complete the LIS Signoff and Production Credential Process please follow the next two steps detailed below. If the same user account credentials created for the Test environment are to be used for the Production environment please complete only Step 2 of the process providing this information:
- Create a new user account in the BloodPortal; and
- Complete the LIS Interface Signup Form.
- Step 1: BloodPortal account(s) need(s) to be created at https://portal.blood.gov.au.
- Step 2: Complete the LIS Interface Signup Form.
To complete the Facility Integration Certification Process please download and follow the steps detailed above using the following Verification Checklist and LIS Sign-up form as required: