https://github.com/nhsdigital/core-gp-contract

Repository for code related to the Core GP Contract GPES extract
https://github.com/nhsdigital/core-gp-contract

nhs-digital-cgpc nhs-digital-gpes nhs-digital-publication

Last synced: 28 days ago
JSON representation

Repository for code related to the Core GP Contract GPES extract

• Host: GitHub
• URL: https://github.com/nhsdigital/core-gp-contract
• Owner: NHSDigital
• License: mit
• Created: 2023-10-17T10:53:22.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-10-20T08:29:21.000Z (over 1 year ago)
• Last Synced: 2024-04-13T07:14:14.533Z (9 months ago)
• Topics: nhs-digital-cgpc, nhs-digital-gpes, nhs-digital-publication
• Language: Jupyter Notebook
• Homepage: https://digital.nhs.uk/data-and-information/publications/statistical/gp-contract-services
• Size: 18.6 KB
• Stars: 0
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# core-gp-contract

Repository for code related to the Core GP Contract GPES extract

# ALCOHOL AND GMS/PMS PUBLICATION JOB

This job outputs four quarterly CSVs for the entire financial year after suppression applied 

## How to run

The main file to run is 'main.ipynb'. The code contains databrick widgets to display report times.

## Installations

The required python packages to run this publication job are:  pyspark, pandas, unittests, typing & functools.

## Parameters

The file "parameters.ipynb" contains date parameters which can be changed to fit the dates required for your personalised report. They are also various SQL database inputs required to put in in pre-processing and checks.

## Functions folder

The functions folder contains various functions used in the job which have been conveniently split into different sections. The "run_functions.ipynb" runs all the files in the functions in the functions file. This is done for ease of access in the "main.ipynb" file.

## Tests folder

The tests folder contains various normal tests and unittests for each function of the code to check whether they are functioning correctly.

## Spot checking

As the code is throughly checked and tested, the spot checking part of the code is done to manually assess the output for any errors the job did not catch.

 

## Contact details

Contact Details		

Author: Primary Care Domain, NHS England		

Lead Analyst Rob Danks		

Public Enquiries: Telephone: 0300 303 5678		

Email: [email protected]		

Press enquiries should be made to: Media Relations Manager: Telephone: 0300 303 3888		

## Copyright

Published by NHS England, part of the Government Statistical Service		

Copyright © 2023, NHS England.				

You may re-use this document/publication (not including logos) free of charge in any format or medium, under the  terms of the		

Open Government Licence v3.0		

or write to the Information Policy Team, The National Archives,		

Kew, Richmond, Surrey, TW9 4DU;		

or email: [email protected]