This article covers the technical requirements that need to be met for the installation of Mjog.
Introduction
The Mjog Messaging System (system) provides Short Message Service (SMS) and other messaging services.
This document describes the PC software and hardware requirements for a successful installation of the Mjog system.
Mjog’s Deployment Team will assist in determining your exact requirements and will work with your technical teams to agree the best approach and method.
Basics
The Mjog system consists of services which interface with an SQLite database which will be installed on a desktop PC or server (physical or virtual), which is referred to as the host.
An Apache web server, with PHP installed, is used to host/serve the Mjog system web-based user interface (web UI).
All clients then access and use the Mjog system through a web browser using the web UI via a unique URL, which can only be accessed across the local area network (LAN).
On this page:
- Host Requirements
- Firewall Exceptions
- Web UI Requirements
- Clinical System Connection
- Software Updates
- Installation and Support
- SMS Messaging Providers
- Data Protection
Host Requirements
The Mjog system runs as a collection of three services on the host and utilises the SQLite database engine and Apache web server; both are installed on the host as part of the standalone installation by our Deployment Team.
Technical Specification Requirements
- Microsoft Windows 10 Pro or later operating system
- Quad core multi-threaded processor or better
- 8GB RAM or more
- 20GB available space
- Solid state storage recommended for performance reasons
Backups
The Mjog system only performs a local backup of the database. It is recommended that an external copy of the local backup is taken regularly. The default location of the local backup is the following folder:
C:\Program Files (x86)\Soft Option Technologies Ltd\Mjog\Restore
Local Administrator Rights
Both for the installation and ongoing support, it will be necessary for a user account with local administration rights on the host to be made available to the Deployment and Support Teams when required. The account name and password should be entrusted to a full-time user that can grant access to the Support/Deployment Team when needed.
Service Internet Access
By default, the Mjog system services are run as the built-in Local System (SYSTEM) account. If you have deployed a proxy server to provide internet access or the SYSTEM account has restricted internet access. Then the services will need to run as a different account/user that has internet access. The account/user must have the same level of access as the SYSTEM account and the password must not expire.
Firewall Exceptions
For management, support, and operational reasons, the Mjog services also connect automatically with our own servers which are held within an Amazon Virtual Private Cloud (VPC).
The following URLs must be accessible by the host. Please note these domains have dynamic IP addresses so IP addresses cannot be used when configuring your firewall exceptions:
- https://*.Mjog.com
- https://*.Mjog.net
The host must also be able to access our VPC public IP addresses:
- 13.248.152.73
- 76.223.18.185
All traffic between the Mjog services and our VPC is secured (TLS 1.2) and uses the standard HTTPS port 443.
Web UI Requirements
Web Browser
All users access the web UI via a web browser and can be accessed from any PC on the same LAN as the host. The web UI is compatible with the following web browsers:
- Microsoft Internet Explorer 11
- Microsoft Edge
- Google Chrome
- Mozilla Firefox 25 and above
Mjog recommends using the most up-to-date vendor supported browsers.
Clinical System Connection
The Mjog service will need to connect to the practice’s clinical system.
EMIS Web
The Mjog service will need access to the EMIS partner API through the Health and Social Care Network (HSCN). Mjog has its own DNS address to connect to the EMIS partner API which is different to the usual address used by other third-party software:
Mjog.spine.emis.thirdparty.nhs.uk
If the DNS address can’t be used, then EMIS support will need to be contacted to obtain the IP address ranges. You can find their contact information at the end of this document.
Microtest Evolution
The service will need to access the Microtest database via the practice’s LAN. Microtest support will set up the access the Mjog service will need.
TPP SystmOne
Due to the integration requirements of TPP SystmOne, all third-party solutions, including Mjog, have to connect to a physical computer running on site. This machine must be switched on and logged into SystmOne Gateway so that Mjog is able to communicate with it and read appointment information and write back read codes.
TPP require that your “Gateway” computer is a dedicated machine running in a server room or back office. It is not recommended to be used as a terminal by end-users. This is to ensure that the computer is available 24/7 and to facilitate the technical requirements of SystmOne and third-party product architecture.
Should the machine be switched off, all Mjog services will cease to function. This may lead to IG and Clinical Safety incidents occurring.
Please refer to your ICB IT Lead, or TPP representative for assistance on changing “Gateway” machines.
If there is an active local firewall on the gateway host, inbound traffic on TCP port 49984 needs to be allowed, so that the Mjog service can connect to the gateway.
Further information regarding the specific settings and system requirements for TPP SystmOne deployments can be found here.
Software Updates
Updates to the Mjog system are also released and applied automatically. All updates are issued as small EXE or SQL statement files (text files with a file extension of SQL).
It may also be necessary for any proxy and firewall settings to be configured to allow these EXE and SQL files to be downloaded.
We will never release software that has not been tested, and only release software for the purposes of updating and maintaining or enhancing the Mjog system.
Installation and Support
For both installation and ongoing product support it will be necessary to pre-approve and agree the technical arrangements that allows remote access to the Mjog host. Some CCGs already have their own solution in place for third party suppliers and this can be discussed with the Mjog Team.
We have our own preferred solution, Away From My Desk (AFMD). This is a commercial application that allows the remote user (a user at the CCG or Health Board) to invite us to remotely connect to a PC for the sole purpose of support or maintenance. This access is granted on a per-use basis and is always under the control of the remote user at the practice. There is no way we can connect without the direct involvement and approval of the practice each time.
We recommend AFMD for the following reasons:
- 256-bit encryption
- It is an attended remote connection
- Web based access over port 80 and 443
- A system already widely used within the NHS and Government bodies
- Adheres to rules defined in Connecting for Health Information Governance toolkit
We are already successfully using this proven solution in many CCGs and Health Boards across England, Scotland, and Northern Ireland.
Mjog also has a Health and Social Care Network (HSCN) connection which can also be used.
SMS Messaging Providers
The Mjog system works with four SMS messaging providers; NHSmail, BT/EE, FireText and Mjog.
NHSmail
The Mjog service will need direct access to the NHSmail POP and SMTP services.
Best practice should be that any services connecting to NHSmail should resolve to the DNS address as opposed to specific IP addresses. The use of Host Files is not supported by NHSmail.
Below is a table listing the DNS addresses, ports and protocols and IP address ranges as specified by NHS Digital.
|
DNS Address |
TCP Port (Protocol) |
IP Address Ranges |
|
send.nhs.net |
587 (SMTP) |
155.231.210.192/26 |
|
pop.nhs.net |
995 (POP3) |
10.222.62.0/24 |
BT/EE or FireText
Messages sent using BT/EE or FireText are despatched via the sender that has been chosen (BT/EE or FireText). All configuration will be undertaken by the Mjog Deployment Team at the time of installation whereby the details provided from BT/EE or FireText will be added to the accounts.
SMS messages dispatched via BT/EE or FireText are charged by the provider. Reply messages are charged to the sender (patient) at their standard network rate.
Mjog
Messages sent using Mjog are despatched via our own SMS gateway so there is no need for any additional accounts to be setup. All configuration will be undertaken by the Mjog Deployment Team at the time of installation and forms part of your account with us.
SMS messages dispatched via Mjog charged by us. Reply messages are charged to the sender (patient) at their standard network rate.
Data Protection
As with all messaging services, Mjog requires at least the minimum information to perform message delivery, but the content of all messages is entirely within the discretion and control of each practice. Minimal personal identifiable information (PII), specifically, first name, last name, date of birth, mobile/email/home number and patient ID, is held within the Mjog database on the host. The Mjog database holds no clinical information. Please see our Privacy Policy for more information. We are registered with the Information Commissioner’s Office (ICO), reference number Z109053X.