Sexual Health Tariff Grouper - Local Tariff Configuration
The integrated Sexual Health Tariff Grouper Local Tariff Configuration Service enables public health commissioners of sexual health services to specify locally agreed tariffs based on activity.
- Reliable implementation of complex tariff rubrics using activity triggers
- Application of provider MFFs or Geo-Weightings based on clinic location
- Use of supplementary local codes to trigger currencies
- Use of zero value currencies to monitor non chargeable activity
- Always charge host option only charges the host commissioner
- Publically available ruleset
- In year adjustments and configuration changes are included
- Centrally managed change management process keeps you in control
- Issue resolution support is included
- Rapid implementation of a local tariff configuration
- Step-by-step support to help iron out any issues
- Tariff configuration available for out of area commissioners to review
- Local charges are universally applied to out of area activity
£600 per user per year
6 0 3 0 9 0 6 4 3 9 4 3 0 7 6
|Software add-on or extension||Yes, but can also be used as a standalone service|
|What software services is the service an extension to||Integrated Sexual Health Tariff Grouper - Local Tariff Configuration|
|Cloud deployment model||Private cloud|
We require that the data we receive from providers is fully anonymised.
We require that healthcare providers have the consent of patients to process their anonymised data through 3rd parties for the purposes of public health and commissioning.
The service is designed for use with all modern browsers such as Chrome, Firefox, Edge, Safari, Opera and all modern devices such as IOS 7+, Android 4.0+ and Windows Mobile 8.1+. Internet Explorer, starting with version 8, is also supported, but with some limitations.
|Email or online ticketing support||Email or online ticketing|
|Support response times||Tickets responded to immediately with resolution target within 48hrs during working hours m-f 9-5.|
|User can manage status and priority of support tickets||No|
|Web chat support||No|
1st Line support firstname.lastname@example.org issues aimed to be addressed within 24hrs during the working week.
2nd Line support may escalate to telephone call back or desktop sharing to support the issue resolution.
Telephone support is limited to call back at 2nd line support, there is no inbound telephone support.
|Support available to third parties||Yes|
Onboarding and offboarding
|Getting started||We provide an introductory email with links to screencasts. In addition we offer an optional desktop sharing session to help new users get started.|
|End-of-contract data extraction||It is a subscriber's responsibility to extract from the service any data they want to retain using the embedded data extract features using MS Excel data extracts directly from the application.|
|End-of-contract process||At the end of the contract subscriber accounts are archived. It is a subscriber's responsibility to extract from the service any data they want to retain using the embedded data extract features.|
Using the service
|Web browser interface||Yes|
|Application to install||No|
|Designed for use on mobile devices||No|
|Independence of resources||We monitor server resources and dynamically optimise platform performance as required.|
|Service usage metrics||Yes|
|Metrics types||Hosted provider data submission activity|
|Supplier type||Not a reseller|
|Staff security clearance||Conforms to BS7858:2012|
|Government security clearance||Up to Baseline Personnel Security Standard (BPSS)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||United Kingdom|
|User control over data storage and processing locations||No|
|Datacentre security standards||Complies with a recognised standard (for example CSA CCM version 3.0)|
|Penetration testing frequency||At least once a year|
|Penetration testing approach||‘IT Health Check’ performed by a CHECK service provider|
|Protecting data at rest||
|Data sanitisation process||Yes|
|Data sanitisation type||Deleted data can’t be directly accessed|
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Data importing and exporting
|Data export approach||
The service is designed to import and export data.
Subscribers can use the embedded export to MS Excel buttons to export specific data sets
|Data export formats||Other|
|Other data export formats||MS Excel (xls)|
|Data import formats||
|Other data import formats||
|Data protection between buyer and supplier networks||
|Data protection within supplier network||
|Other protection within supplier network||
IP and Port restrictions
Availability and resilience
|Guaranteed availability||99.9% during working hours m-f, 9-5 excluding outside planned maintenance. In the event we do not meet this commitment we will issue a a service credit.|
|Approach to resilience||Available on request|
|Outage reporting||A public dashboard|
Identity and authentication
|User authentication needed||Yes|
|Other user authentication||A subscriber will need to make an initial subscription request using an email with a suitable known domain such as 'gov.uk' or 'nhs.net' supported by a valid purchase order.|
|Access restrictions in management interfaces and support channels||
SSH tunnels using certificates to management consoles;
User ID and password;
2 factor authentication;
IP address white lists;
Other monitoring and prevention measures
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||
|Description of management access authentication||.|
Audit information for users
|Access to user activity audit information||Users have access to real-time audit information|
|How long user audit data is stored for||At least 12 months|
|Access to supplier activity audit information||Users have access to real-time audit information|
|How long supplier audit data is stored for||At least 12 months|
|How long system logs are stored for||At least 12 months|
Standards and certifications
|ISO/IEC 27001 certification||No|
|ISO 28000:2007 certification||No|
|CSA STAR certification||No|
|Other security certifications||Yes|
|Any other security certifications||Cyber Essentials PLUS (IASME-A-09427)|
|Named board-level person responsible for service security||Yes|
|Security governance certified||No|
|Security governance approach||Other security governance standards in process of applying for ISO 27001|
|Information security policies and processes||We have an automated security regime that monitors and tracks all infrastructure changes as well as data access. Alerts are sent in real time to allow immediate remedial action to be taken.|
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||
For infrastructure we use an infrastructure as code approach, where changes are coded in configuration files and then applied. This provides a non-repudiable audit trail of changes.
For the software platform, we use agile development and continuous deployment techniques to create, test and deploy changes onto the live service without down time.
|Vulnerability management type||Supplier-defined controls|
|Vulnerability management approach||We rely on third parties to disseminate threat alerts, we deploy non-critical patches on a weekly basis. Critical patches will receive more immediate attention commensurate with the risk.|
|Protective monitoring type||Supplier-defined controls|
|Protective monitoring approach||We use 3rd party active threat monitoring tools that use machine learning and known threat IP addresses to assess a wide range of threats. Responses to alerts will depend on the threat severity and may if necessary, result in immediate suspension of the service.|
|Incident management type||Supplier-defined controls|
|Incident management approach||
We continually identify, assess, mitigate, report, and monitor risks. Management reviews and evaluates the risks identified following this procedure:
1. Identify – Identify technical and business risks to the organisation and operations.
2. Assess – Evaluates the potential impact(s) of identified risks, the likelihood of occurrence, and control effectiveness and maturity.
3. Mitigate – Control or reduce risk where needed, including the implementation of controls, processes, and other physical and virtual safeguards.
4. Report – Reporting and communication is performed to ensure that senior leadership, have visibility into risks.
5. Monitor – Identified and assessed risks are periodically reviewed.
|Approach to secure software development best practice||Supplier-defined process|
Public sector networks
|Connection to public sector networks||No|
|Price||£600 per user per year|
|Discount for educational organisations||No|
|Free trial available||No|