Polaris PDF API

The PDF API is part of the Polaris platform (formerly DHOS). This service is responsible for managing PDFs, largely for the purposes of business continuity (BCP). The PDFs are a printable representation of a product's information about a given patient.

This service is intended to wrap the Polaris PDF Engine.

Maintainers

The Polaris platform was created by Sensyne Health Ltd., and has now been made open-source. As a result, some of the instructions, setup and configuration will no longer be relevant to third party contributors. For example, some of the libraries used may not be publicly available, or docker images may not be accessible externally. In addition, CICD pipelines may no longer function.

For now, Sensyne Health Ltd. and its employees are the maintainers of this repository.

Setup

These setup instructions assume you are using out-of-the-box installations of:

• pre-commit (https://pre-commit.com/)
• pyenv (https://github.com/pyenv/pyenv)
• poetry (https://python-poetry.org/)

You can run the following commands locally:

make install  # Creates a virtual environment using pyenv and installs the dependencies using poetry
make lint  # Runs linting/quality tools including black, isort and mypy
make test  # Runs unit tests

You can also run the service locally using the script run_local.sh, or in dockerized form by running:

docker build . -t <tag>
docker run <tag>

Documentation

Endpoint	Method	Auth?	Description
/running	GET	No	Verifies that the service is running. Used for monitoring in kubernetes.
/version	GET	No	Get the version number, circleci build number, and git hash.
/dhos/v1/gdm_pdf	POST	Yes	Generate a PDF containing a summary of a GDM patient record. The request body contains details of the patient and their blood glucose readings. Responds with HTTP 201.
/dhos/v1/dbm_pdf	POST	Yes	Generate a PDF containing a summary of a DBM patient record. The request body contains details of the patient and their blood glucose readings. Responds with HTTP 201.
/dhos/v1/gdm_pdf/{patient_uuid}	GET	Yes	Get a care record PDF for a GDM patient with the provided patient UUID
/dhos/v1/dbm_pdf/{patient_uuid}	GET	Yes	Get a DBM care record PDF for a patient with the provided patient UUID
/dhos/v1/send_pdf	POST	Yes	Generate a PDF chart for a SEND patient, containing observations recorded during a particular encounter (hospital stay). This endpoint may also generate additional files depending on the trustomer configuration. The endpoint responds with an HTTP 201 on success.
/dhos/v1/patient/pdf/{encounter_uuid}	GET	Yes	Get a PDF chart for a SEND patient for the provided encounter (hospital stay) UUID.
/dhos/v1/ward_report	POST	Yes	Generate a SEND PDF ward report for a particular location, containing statistics on the observations taken for patients in that location. The endpoint responds with an HTTP 201 on success.
/dhos/v1/ward_report/{location_uuid}	GET	Yes	Get a SEND PDF ward report for the provided location UUID.

Requirements

At a minimum you require a system with Python 3.9. Tox 3.20 is required to run the unit tests, docker with docker-compose are required to run integration tests. See Development environment setup for a more detailed list of tools that should be installed.

Deployment

All development is done on a branch tagged with the relevant ticket identifier. Code may not be merged into develop unless it passes all CircleCI tests. :partly_sunny: After merging to develop tests will run again and if successful the code is built in a docker container and uploaded to our Azure container registry. It is then deployed to test environments controlled by Kubernetes.

Testing

Unit tests

🔬 Either use make or run tox directly.

tox : Running make test or tox with no arguments runs tox -e lint,default

make clean : Remove tox and pyenv virtual environments.

tox -e debug : Runs last failed unit tests only with debugger invoked on failure. Additional py.test command line arguments may given preceded by --, e.g. tox -e debug -- -k sometestname -vv

make default (or tox -e default) : Installs all dependencies, verifies that lint tools would not change the code, runs security check programs then runs unit tests with coverage. Running tox -e py39 does the same but without starting a database container.

tox -e flask : Runs flask within the tox environment. Pass arguments after --. e.g. tox -e flask -- --help for a list of commands. Use this to create database migrations.

make help : Show this help.

make lint (or tox -e lint) : Run black, isort, and mypy to clean up source files.

make openapi (or tox -e openapi) : Recreate API specification (openapi.yaml) from Flask blueprint

make pyenv : Create pyenv and install required packages (optional).

make readme (or tox -e readme) : Updates the README file with database diagram and commands. (Requires graphviz dot is installed)

make test : Test using tox

make update (or tox -e update) : Updates the poetry.lock file from pyproject.toml

Integration tests

🔩 Integration tests are located in the integration-tests sub-directory. After changing into this directory you can run the following commands:

Database migrations

Any changes affecting the database schema should be reflected in a database migration. Simple migrations may be created automatically:

$ tox -e flask -- db migrate -m "some description"

More complex migration may be handled by creating a migration file as above and editing it by hand. Don't forget to include the reverse migration to downgrade a database.

Configuration

• DATABASE_USER, DATABASE_PASSWORD, DATABASE_NAME, DATABASE_HOST, DATABASE_PORT configure the database connection.
• LOG_LEVEL=ERROR|WARN|INFO|DEBUG sets the log level
• LOG_FORMAT=colour|plain|json configure logging format. JSON is used for the running system but the others may be more useful during development.

Database

Records of PDFs are stored in a Postgres database.

GDM PDF Sections

• Summary - Summary of patient detail (incl. name, NHS number and BMI)
• Contact - Contact deatils for patient (incl. phone number, email and postcode)
• Management - Diagnosis management detail (incl. readings per day and management strategy)
• GDM details - Diagnosis specific test results (incl. date of diagnosis and first HbA1c result)
• Pregnancy details - Pregnancy related details (incl. estimated delivery date, parity and gravidity)
• Pregnancy outcomes - Pregnancy specific test results (incl. induced, pre-eclamsia and perineal trauma)
• Deliveries - Details on each delivery (incl. baby name, delivery date and birth weight)
• Blood glucose reading history - history of all blood glucose readings (incl. reading date/time, dose taken and patient comment)

GDM PDF Example

SEND PDF

The SEND PDF is a printable version of the chart displayed on SEND.