SSO Compliance Checklist

HEALTHNET/BC
SSO Compliance Checklist
Review this checklist prior to scheduling a compliance evaluation
This checklist is a guide for SSOs of the services, materials and requirements pertaining to a HealthNet/BC compliance evaluation.
1 Evaluation Location and Facilities
A compliance evaluation can have two components:
Application evaluation to ensure application compliance with the relevant HealthNet/BC compliance document; &
Security evaluation for applications that use the Ministry's security protocol, HNSecure.
Application evaluations can take place at either the vendor site, at the Ministry or remotely. These three options are not always
available for each application. Check with Quality Assurance.
Sufficient work space for 2 compliance team members and 1 observer is required.
The vendor is responsible for supplying all required hardware and software.
For PharmaNet related software, exclusive use of a printer must be available to print labels, receipts, fanouts or FDB monographs.
The compliance evaluation of the HNSecure protocol must be performed at the vendor site.
If the evaluation of the application takes place at the Ministry, a meeting room and access to the Internet (if req’d.) will be supplied.
2 Pre-compliance Assistance
Quality Assurance offers informal, pre-compliance assistance, by phone, where readiness is discussed (i.e.: review checklist items.)
Development test scenarios for SSOs developing Health Registry software describes how to test each of the Health Registry
transactions (See 'Documentation' below for more details).
3 Data and/or Software Required Prior to a Compliance Evaluation
Confirm With Pharmacare Quality Assurance:
Pharmacy ID and IP address to be used during the test.
Software Version Number.
Data (if needed) such as Patient, Practitioner & Drug is supplied. This data must be added to your local system prior to the
evaluation, otherwise it takes up time during the evaluation.
For applications using HNSecure, ensure you have registered and received the facility ID and domain to be used for the evaluation.
These are different from those used during development.
Security group identification (i.e., OP, IP, ED, MD, HNF etc.)
Confirm with HealthNet/BC Access Services:
Data such as PHN and person is supplied. It must be added to your local system prior to the evaluation, otherwise it takes up time
during the evaluation.
4 Documentation
The following documents are available on the HealthNet/BC Web Site, http://admin.moh.hnet.bc.ca. SSOs should be very familiar with
the document(s) pertaining to the software being evaluated.
HealthNet/BC Professional and Software Compliance Standards: These documents describe the HealthNet/BC standards and are
used as the basis for the compliance tests.
PharmaNet (includes HNSecure).
Health Registry (includes HNSecure).
Lab Test Standard (includes HNSecure).
Compliance Test Documents: These documents describe the compliance tests, as performed during the compliance evaluation.
Community pharmacy test cases.
Emergency department test cases.
Hospital admitting test cases.
Hospital in-patient test cases.
HNSecure test cases.
Health Registry - Client demographic &
eligibility test cases.
Development Test Scenarios: This document describes how to test each of the Health Registry transactions. This is particularly
helpful during the SSO test cycle prior to compliance evaluation.
5 Third Party Requirements (for Community Pharmacy only)
The SSO is responsible for coordinating the following with 3rd party adjudicators:
Ensure the third party test environments are available.
Ensure transaction security is in place on both the third party database and on the SSO's local software.
Ensure support from the third party is available during the evaluation.
6 SSO Technical Support Requirements During the Compliance
Ensure the operator of software being evaluated has the ability to:
Point to a compliance test environment by changing port numbers.
Change facility and domain to the compliance test environment, in the case of applications using HNSecure.
Change the system date to dates other than the current date.
Contact Information
Quality Assurance - PharmaNet:
Telephone Queue: Victoria 952-3508, elsewhere 1-888-918-8822 Compliance Evaluation Scheduling:[email protected]
Health Registry:
Pre-compliance Testing: Help Desk at 250-952-1234 Compliance Evaluation Scheduling: [email protected]