High Level Design Document

This document provides an overview of the TMS Insight (Data Capture) Ltd. Prescription Tracking System technical specifications and requirements to assist with the planning and implementation of the Prescription Tracking System.

Technical Architecture

On Premise Hosting

On Premise hosting allows the hosting of all Prescription Tracking System components within your own data centre. In this set-up you would need to consider backup and resilience options specific to your individual needs. The SQL Database can co-reside in an existing SQL instance / Cluster.

TMS Cloud Hosting

TMS Cloud hosting allows the hosting of the Prescription Tracking System components on our Azure VM Infrastructure.

Electronic Prescribing Interface

For customers using on-premise hosting, PTS can be configured to interface with Electronic Prescribing (ePrescribing) Systems to facilitate Prescription data being entered into PTS automatically so that data-entry is not duplicated.

Use of an ePrescribing interface can be used alongside manual entry of Prescription Data. The ODBC Query &/or ePrescribing service is configured by TMSi to process only the requests that the Pharmacy are interested in tracking.

The ePrescribing interface is a one-way feed, i.e. any amendments to Prescription data within PTS are not sent back to the ePrescribing system. PTS can be configured to send HL7 messages when activities are recorded against a Prescription (such as Dispense, Final Check etc.) or when a Prescriptions status changes (when Completed, Collected, Delivered etc.).

EMail & SMS messaging

PTS can be configured to send SMS &/or Emails to Pharmacy Staff, Ward Staff or Patients in response to notes being recorded. If this service is used, then the following configuration is required:

System Server and Client Requirements

The following are the minimum system requirements for each component along with the recommended specifications.

Component	Minimum requirements
IIS Application Server	Windows Server 2012 (Windows server 2016+ recommended). Physical or Virtual Servers are supported. 2.0 GHz dual core processor (3.0 GHz+ dual or quad core recommended). 8GB Ram. If the Application server is also the SQL Server, then a minimum of 16GB Ram is recommended. .NET Framework 4.6+ SSL Certificate if HTTPS connections are required (recommended). The following Server Roles & Features must be Installed: Web Server: Common HTTP Features: Default Document HTTP Errors Static Content Health and Diagnostics HTTP Logging Request Monitor (recommended not essential) Performance Static Content Compression Security Windows Authentication Application Development ASP.NET 4.6 (and associated components) Application Initialisation (recommended not essential) Management Tools IIS Management Console .Net Framework 4.6 Features .NET Framework 4.6 (4.6.2 minimum) ASP.NET 4.6 .NET Framework 3.5 Features .NET Framework 3.5 (This is required so that the Installer can use the RS.exe SSRS tool to set the data source for the PTS Reports. If SSRS is not installed on the server then this part of the installation will need to be completed manually. If connecting to a third-party system for patient demographics (such as CMM) the relevant 64-BIT ODBC drivers will need to be installed. In most instances TMSi can provide these drivers. If connecting to CMM (or other system) TMSi will require connection details (user, password, server name, database name / namespace, stored procedure, or query to be run etc.) Barcode label printer setup: Label Printers that PTS will use will need to be connected directly to the network and a TCP_IP port used from the server to connect to them. Alternatively, printers can be shared and a local port with the share address created on the server. 64bit printer drivers will be required for the make/model of the Printers being used. The following folders should be excluded from Antivirus scanning: %SystemRoot%\IIS Temporary Compressed Files %SystemDrive%\inetpub\temp\IIS Temporary Compressed Files %SystemDrive%\inetpub\temp\ASP Compiled Templates %systemDrive%\inetpub\logs %systemDrive%\inetpub\wwwroot The following processes should be excluded from Antivirus scanning: %SystemRoot%\system32\inetsrv\w3wp.exe %SystemRoot%\SysWOW64\inetsrv\w3wp.exe %SystemDrive%\PHP5433\php-cgi.exe
SQL Server	SQL Server 2014 (SQL Server 2016+ recommended). 2.0 GHz dual core processor (3.0 GHz+ dual or quad core recommended). 8GB Ram. If the Application server is also the SQL Server, then a minimum of 16GB Ram is recommended. SQL Server and Windows authentication enabled on the server (Mixed mode authentication). SQL Server Management Studio and SQL Reporting services configuration manager will need to be available on the server hosting the database or a separate PC that can connect to the SQL/SSRS server(s). Initial database size is approx. 2GB. The database will consume approximately 500MB-1GB of disk space per annum. The actual figure is dependent on numerous factors (number of dispensaries, number and type of prescriptions being tracked, number of stages being tracked etc.). Simple recovery model recommended. Overnight backup recommended.
SSRS Server	SQL Server Reporting Services (SSRS) 2014 (2016+ recommended). This can be the same SQL server that is hosting the PTS database or a separate SQL server instance if SSRS is not available on the PTS database host server.
Client PC Web Browser	Clients viewing the web application should use Chromium Edge, Chrome, Firefox Quantum or IE11. PTS 5 is NOT Compatible with versions of IE earlier than IE10. Chromium Edge is the recommended browser. JavaScript must be enabled on client browsers accessing PTS.
‘PTS Communications’ Desktop client for PCs with attached Barcode Scanners.	Windows 7 (Windows 10 or 11 recommended). .NET Framework 4.8+ Ability to communicate with Webservice on IIS Application server over HTTP (Port 80) or HTTPS (Port 443).
Android / iOS Delivery Application	The minimum supported operating systems are: Android – Lollipop (5.1). Apple – iOS 13. Both OS versions will be tested for compatibility with the latest version of Android/iOS and use of the most up-to-date version of the OS is recommended.