-
Notifications
You must be signed in to change notification settings - Fork 1
/
IRPQ.Rmd
executable file
·1233 lines (714 loc) · 58.9 KB
/
IRPQ.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
---
title: "Information Requests & Parliamentary Questions"
output:
learnr::tutorial:
css: "css/style.css"
progressive: true
allow_skip: true
runtime: shiny_prerendered
---
```{r setup, include=FALSE}
# Author: Vay Ly
# Original Date: February 2024
library(learnr)
library(gradethis)
library(stringr)
library(readr)
library(haven)
library(dplyr)
library(purrr)
library(ggplot2)
knitr::opts_chunk$set(echo = FALSE)
tutorial_options(
exercise.checker = gradethis::grade_learnr
)
```
```{r phs-logo, echo=FALSE, fig.align='right', out.width="40%", fig.alt = "Public Health Scotland logo"}
knitr::include_graphics("images/phs-logo.png")
```
## Introduction
Welcome to the Information Requests & Parliamentary Questions course. This course is designed to provide an overview of the Information Request (IR) and Parliamentary Question (PQ) process.
<div class="info_box">
<h4>Course Info</h4>
1. This course is separated into two main sections: **Information Requests** followed by **Parliamentary Questions**
2. Most sections have multiple parts to them. Navigate the course by using the buttons at the bottom of the screen to Continue or go to the Next Topic.
3. The Navigation Pane on the left hand side of this page contains all the sections of this course.
3. If you are comfortable with the content and are looking for specific information or guidance, feel free to navigate through to the appropriate section located in the navigation banner.
4. If this is your first exposure to PQs and IRs, it is highly recommended to work through the course from beginning till end.
5. Should you have any difficulties whilst navigating the course please contact the Statistical Governance team at phs.statsgov@phs.scot.
</div>
</br>
<div class="info_box">
<h4>Course Structure</h4>
1. By the end of the first half of the course, which focuses on **Information Requests**, you will have learned the following:
* What is an IR?
* How long do I have to respond to an IR?
* How do I work with my team to deal with an IR?
* How do I log, retrieve and answer an IR?
* What factors should I consider when answering an IR?
* How do I close an IR?
</br>
2. By the end of the second half of the course, which focuses on **Parliamentary Questions**, you will have learned the following:
* What is a PQ?
* How are PQs created, retrieved and allocated to PHS teams?
* What do I do if a PQ has been allocated to my team?
* What considerations should I bear in mind when answering a PQ?
* How do I answer a PQ?
* How do I sign off a PQ answer?
* How do I submit a PQ answer?
There will be a checklist at the end of the course with the above learning outcomes - take some time to reflect whether you have fully learned all the above outcomes by the end of the course.
</div>
</br>
<div class="info_box">
<h4>Reset</h4>
If you wish to reset all the quizzes and start over from the beginning, locate and press the *Start Over* button beneath the navigation banner on the left hand side.
</div>
## Information Requests
In the following sections, we will cover what Information Requests are, and how to process them.
In later sections, we will move on to PQs, which are a type of Information Request from MSPs.
Information Requests are requests for bespoke analysis of information and data which PHS holds.
IRs can be requested by anyone, so long as the requests are made in line with legislation, agreed principles, and public expectations regarding access to statistical information under which public bodies operate.
<div class="info_box">
<h4>Important</h4>
* Freedom of Information Requests and Environmental Information Regulation Requests are dealt with by the FOI team to ensure all FOI obligations are met under the Freedom Of Information Act 2002. Guidance can be found on [The Spark](https://spark.publichealthscotland.org/corporate-guidance/information-governance/data-protection/data-protection-handbook/freedom-of-information-foi/).
* Information Requests from the media should be directed to PHS Comms at phs.comms@phs.scot.
* All responses made to IR are subject to PHS overarching rules regarding [statistical governance](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/releasing-statistics/), which includes [data protection](https://spark.publichealthscotland.org/corporate-guidance/information-governance/data-protection/), [statistical disclosure control](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/statistical-disclosure-control/overview-of-disclosure-control-protocol/) and [Code of Practise for Statistics](https://code.statisticsauthority.gov.uk/)obligations.
* PHS generally aims to answer IRs within 20 working days from the point where the specification is agreed with the customer.
</div>
</br>
### When PHS will provide analysis
PHS will provide a bespoke analysis in response to an IR, subject to resource,
priority assessment and potentially a charge, provided that:
* The user is able to justify that other information already published or held as
unpublished analysis by PHS is not suitable;
* The user has stated clearly what they want to find out and if possible why, to
enable PHS staff to understand the request;
* PHS’s statistical governance rules are met.
### When PHS will not provide analysis
**PHS will not provide information in response to an IR if said information is due to be released in a publication within 12 weeks.**
Exceptions to this are where data is made available for the following purposes:
* In compliance with Pre-Release Access legislation on Official Statistics
* Early Access for Quality Assurance
* Early Access for Management Information
<div class="info_box">
<h4>Important</h4>
* Stats Gov (phs.statsgov@phs.scot) can be contacted in the first instance, should there be any concerns whether or not an IR should be answered.
</div>
</br>
## IR - Workflow
While individual teams may have their own local protocols for responding to IRs, the following is a general workflow which PHS users may use:
1. Team receives IR.
2. IR is logged in the IRS (see section [IR - Form & Service](https://scotland.shinyapps.io/phs-learn-irpq/#section-ir---form-service)) and given a reference number.
3. IR is assessed by the team (see section [IR - Assessing the Request](https://scotland.shinyapps.io/phs-learn-irpq/#section-ir---assessing-the-request)).
4. If the request has not been made via the **Information Request Form** (see section [IR - Form & Service](https://scotland.shinyapps.io/phs-learn-irpq/#section-ir---form-service)), teams are encouraged to send this form to the customer and request it be filled out and returned. Proceed to the next stage once it has been returned.
5. Team makes contact with the customer to discuss the IR, and communicate what is being provided, the timescale required, and any applicable charges.
6. Once all parties are in agreement, analysis can be performed. **Note: If a charge is applicable, payment must be received before proceeding.**
7. Once complete, a second team member should check the work.
8. Complete [Disclosure Risk Assessment form](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/statistical-disclosure-control/overview-of-disclosure-control-protocol/) and apply Statistical Disclosure Control as required.
9. The analysis must be approved by an appropriate member of the team (e.g. Principal Analyst or Service Manager).
10. If this is the first time the information is being released, it should be sent to preview 48 hours before it is released to the customer as follow:
1. Analysis relating to specific Health Board: Email PHS preview mailbox. Request that the IR is sent to the Chief Executive and Communications Manager at that specific board.
2. Analysis at national level: Email the IR to your policy contact at the Scottish Government using the e-mail templates in Appendix 1 of the [Information Request Protocol](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/information-requests/).
11. Send the IR to the customer.
12. Close the IR on the IRS.
In the next section, we will cover the first few stages of the IR workflow.
## IR - Form & Service
### Information Request Form
While teams may have their own local procedures in dealing with Information Requests, it is encouraged to have customers fill in and return an [Information Request Form](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/information-requests/) after the request has been assessed and deemed feasible. We have provided an example form for teams to adapt for their purposes.
This form not only aids in the team assessment stage of dealing with IRs, but also directs customers to relevant policies and protocols concerning data and statistical governance.
A screen grab of the form can be seen below. The attachable document file (with working hyperlinks) can be found in the [Useful Documentation & Links](https://scotland.shinyapps.io/phs-learn-irpq/#section-useful-documentation-links) section of this course, as well as on [Spark](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/information-requests/).
**Please ensure you enter an appropriate team email address where prompted in the document.**
```{r echo=FALSE, fig.align='center', out.width="80%", fig.alt="IR Form image"}
knitr::include_graphics("images/irpq/ir-IRForm.png")
```
<div class="info_box">
<h4>Important</h4>
* The 20 working day deadline to fulfil the IR will begin from when the specification has been agreed with the customer, following the team's assessment of the IR Form.
* The use of the **Information Request Form** is a suggestion only, and may not be appropriate for all cases (such as when requested data is complex and requires detailed discussion). Individual teams should operate by their own discretion.
</div>
</br>
### Information Request Service
The Information Request Service is where all Information Request should be logged.
By doing so, users are able to be allocated to Information Requests, the time spent on the requests are able to be logged, and Information Request reference numbers are able to be generated.
Users who require access to the IRS should contacts the Stats Gov team (phs.statsgov@phs.scot) via email to request access.
Below is a step by step tutorial of how to log and close IRs in the system.
1) Log on and select *New Record*
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Image showing selecting new record in the IRS"}
knitr::include_graphics("images/irpq/ir-UsingIRS1.png")
```
2) **Summary** - Select *Information Request (Non ISD)* as the Request Type, and fill in relevant information as shown below.
*Note: The default deadline is 20 working days from when IR is received. This should be updated after discussion with the customer.*
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Filling in the relevant information in the new request form"}
knitr::include_graphics("images/irpq/ir-UsingIRS2.png")
```
3) **Customer** - As a minimum, fill in the name, telephone and email.
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Filling in the customer section"}
knitr::include_graphics("images/irpq/ir-UsingIRS3.png")
```
4) **Time Log** - Click *Define New Role* and select a Lead Analyst (this can initially be the individual logging the request, and can be changed later).
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Filling in the time log"}
knitr::include_graphics("images/irpq/ir-UsingIRS4.png")
```
5) Once the Lead Analyst has been found and chosen, click *Submit Record*.
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Filling in the lead analyst information"}
knitr::include_graphics("images/irpq/ir-UsingIRS5.png")
```
6) **Closing Record** - Click *Search* and find the IR using the IR number. Once found, click *edit* to proceed.
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Closing the record"}
knitr::include_graphics("images/irpq/ir-UsingIRS6.png")
```
7) **Update Time Log** - You must update the amount of time worked in order to close the request. At this stage, you can also re-assign who is the lead analyst.
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Updating the time log"}
knitr::include_graphics("images/irpq/ir-UsingIRS7.png")
```
8) **Complete and Close** - Back in the *Summary* screen, fill in the *Completion Date* and click *Submit Record* and confirm. You can then log off.
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt = "Complete and closing the IR"}
knitr::include_graphics("images/irpq/ir-UsingIRS8.png")
```
Next, we will move onto the guidelines surrounding Charges.
## IR - Charging
### Core / Non-Core Customers
There are two types of customers who will make IRs to PHS - **Core Customers** and **Non-Core Customers**.
It is important to distinguish between the two, as charging principles will differ depending on the customer.
Below are the two categories, as well as what certain organisations/individuals would fall under:
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="2 tables showing the core and non-core customers for charging purposes"}
knitr::include_graphics("images/irpq/IR-CustomerType.png")
```
### Charging
IRs should be charged if PHS is required to carry out new work in fulfilling the request.
Customers are charged based on their type, and only if the work required exceeds a certain estimated timescale.
**Core Customers** are charged when the estimated work time exceeds 2 days.
**Non-Core Customers** are charged when the estimated work time exceeds 3.5 hours.
If a customer is to be charged, a fees notice and explanation of the fees must be sent when the specification of the IR is being discussed.
From the issuance of the fees notice, the customer will have 3 months to decide whether or not to pay the charge to obtain the information.
Below is a table of Estimated Day Rates, dependent on the Type of Analysis required in responding to an IR.
| Types of Analysis| Description | Estimated Day Rate (incl. VAT)|
|:-----------------|:--------------------|:--------------------|
| Standard Analysis|Basic tabulations or data extracts that require a certain level of skilled statistical expertise in order to extrapolate, manipulate and format the data to meet the customer requirements|Band 5 - Band 6|
| Complex Analysis |Higher level of skilled statistical expertise is required. For example the need for record linkage and/or the application of advanced statistical methodologies e.g. the use of modelling techniques, standardisation rates.|Band 7 - Band 8a|
| Highly Complex Analysis|Similar to the above, though with additional complex analysis requiring senior management staff to complete the statistical analysis.|Band 8b - Band 9 |
| Consultant Requirement|Consultant staff are required to complete the statistical analysis.|Actual cost of named individual|
<div class="info_box">
<h4>Important</h4>
* Do not charge for IRs where the data is already available.
* Do not charge when work is part of our normal business activity i.e. part of a planned programme of work, funded project, etc.
* Do not charge for discussing specification.
* For further information on Charging and the fees notice, consult the PHS Charging Mechanism and your respective teams.
* The most up to date details on charging rates are available via Service Now 'Finance and Procurement'.
</div>
</br>
## IR - Assessing the Request
Once you have received the IR Form from the customer and logged the IR within the IRS, you should then assess the request with your team.
Each team will have their own local methods to assess the request.
Below are some general considerations which should be understood and discussed with your team before proceeding to agree the specifications of the request with the customer.
### Considerations
Please work through the following checklist when assessing the IR with your team.
<input type="checkbox" unchecked> Is the request clear? Do we need further clarification from the customer or specialists?
<input type="checkbox" unchecked> Do we have the resources available to respond to the IR?</input>
<input type="checkbox" unchecked> Is the information readily available?</input>
<input type="checkbox" unchecked> Does responding to the IR impact on any Statistical Governance or Data Protection principles?</input>
<input type="checkbox" unchecked> Can the IR be responded to within 20 working days from the specification being agreed with the customer?</input>
<input type="checkbox" unchecked> Is this a repeat or similar request?</input>
<input type="checkbox" unchecked> Is this request chargeable?</input>
<input type="checkbox" unchecked> Who will be the Lead Analyst?</input>
<div class="info_box">
<h4>Important</h4>
* Avoid releasing confidential data, where possible. Ensure appropriate sign-off processes have been followed.
* Data relating to own treated patients can be released to consultants, so long as a [Data Release and Linkage Form](https://spark.publichealthscotland.org/corporate-guidance/information-governance/data-protection/data-protection-handbook/data-release-and-linkage-form/) is filled out and approved by the Data Protection Team (phs.dataprotection@phs.scot).
* Information Requests from the media should be directed to PHS Comms at phs.comms@phs.scot.
</div>
</br>
### Completing the IR
Once an agreement of the specifications has been made with customer, and any necessary Charges have been paid, the work can be carried out.
Teams will have their own methods and resources in carrying out the work necessary to fulfill an Information Request.
Users should apply [Statistical Disclosure Control](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/statistical-disclosure-control/overview-of-disclosure-control-protocol/) as required (e.g. If there are small figures, etc.).
### Sending and Closing the IR
If this is the first release of the information, the IR should be sent for preview 48 hours before it is released to the customer, using the templates contained within the Appendix of the [Information Request Protocol](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/information-requests/).
Once all the appropriate works and checks have been completed and the preview of the answer is sent off (if necessary) then the IR can be sent to the customer.
The IRS file should then be updated and closed.
## IR - Example
The below is a well-answered IR, and may be used as an example of how teams may tackle such requests.
### Example
A PHS team received an IR via email, requesting the **list size of patients aged 18-74 per practice in NHS Tayside**.
In discussion with the customer, the team were able to clarify the following:
* What the requirements were.
* If existing data was sufficient to answer the question.
* Confirmation customer would like to proceed with the IR.
* Confirmation of IR Number and Deadline, which was conveyed to the customer.
Following this discussion, the team outputted the following spreadsheet to the customer via email:
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Example IR response first page"}
knitr::include_graphics("images/irpq/ir-example1.png")
```
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Example IR response second page"}
knitr::include_graphics("images/irpq/ir-example2.png")
```
<div class="info_box">
<h4>Important</h4>
* This section only shows one example of how an IR has been answered. Individual teams will be able to provide their own examples of how they have answered IRs in the past.
* Unlike with PQs, there is no standardised template to be used when answering an IR, as teams will have their own methods, and each IR may be different in their requirements to eachother.
</div>
</br>
## IR - Knowledge Check
```{r final_IR_knowledge_check}
quiz(
question("Only specific people and organisations are permitted to submit an IR to PHS.",
answer("TRUE", correct = FALSE),
answer("FALSE", correct = TRUE),
incorrect = "Not quite, have another go!",
correct = "Anyone is allowed to submit an IR to PHS.",
allow_retry = TRUE,
random_answer_order = TRUE
),
question("The customer is making an IR which specifically requires small numbers to be disclosed. What should you do? (select all that apply)",
answer("Contact Stats Gov and seek guidance.", correct = TRUE),
answer("Release the information. It is only going to one customer, so it is fine.", message = "The information should not be released without consulting Stats Gov, and discussing the issue with the customer."),
answer("Have a discussion with the customer regarding the issues with supplying the information.", correct = TRUE),
incorrect = "Not quite, have another go!",
correct = "A discussion should be had with the Stats Gov and the customer (seperately) to discuss the issue and find a way forward.",
allow_retry = TRUE,
random_answer_order = TRUE
),
question("All work must be approved by an appropriate member of the team (e.g. Service Manager/Principal Analyst) prior to being sent to the customer.",
answer("TRUE", correct = TRUE),
answer("FALSE", correct = FALSE),
incorrect = "Not quite, have another go!",
correct = "Well done!",
allow_retry = TRUE,
random_answer_order = TRUE
),
question("An IR has been sent to your team from a researcher in a Private Company. They have asked for national level information which has not been released before. What additional stages would you have to do when processing this IR?",
answer("It must be sent for preview to your policy contact at SG using the template in Appendix 1 of the IR Protocol, at least 48 hours before being released to the customer.", correct = TRUE),
answer("Nothing. As this is new information, it is fine to pass it on to the customer.", message = "If this is new information, it should not be passed on to the customer."),
answer("It should be checked very thoroughly by a member of the team.", message = "Having a member of the team check the IR is not an additional measure."),
incorrect = "Not quite, have another go!",
correct = "First release of information should be sent to preview 48 hours before being released to the customer. Details can be found in the IR - Workflow section of this course",
allow_retry = TRUE,
random_answer_order = TRUE
)
)
```
### Conclusion
You have reached the end of the Information Request section of the IRPQ course.
The next half of the course will focus on Parliamentary Questions.
## Parliamentary Questions
PQs are questions posted by MSPs to the Scottish Government (SG), or the Scottish Parliamentary Corporate Body. They serve as a mechanism for MSPs to obtain factual and statistical information.
The nature and themes of the questions may change to reflect the ever changing social and political climate in Scotland at the time.
For instance, during the flu seasons SG may receive a number of PQs such as:
**To ask the Scottish Government how many vaccinations took place in Glasgow this year, and how it compares to the amount of vaccinations which took place last year.**
**To ask the Scottish Government how many vaccines are available in preparation for the 2024 Flu season.**
While topical questions are not certain to be asked, it is a good idea for teams to be aware of possible trends and topics they may be faced with.
PQs (both answered and unanswered) can be found on the [Scottish Parliament's Questions and Answers page](https://www.parliament.scot/chamber-and-committees/questions-and-answers).
In the next few sections, we will cover how a Parliamentary Question is created, information concerning the deadlines, and how the Statistical Governance team at PHS handle the PQs so that they (hopefully) reach the appropriate teams.
### About PQs
PQs can be asked in two ways:
**Oral Questions** are asked in Parliament during First Minister's Questions, and are submitted on a Wednesday, one week before they are to be asked in Parliament. The timescale to respond to the MSP is 5 working days.
**Written Questions** are submitted daily. The timescale to respond to the MSP is 10 working days, and 20 working days during a recess.
An overview of the PQ process can be seen below:
```{r PQ-process, echo=FALSE, fig.align='center', out.width="80%", fig.alt="Flow chart of IR process"}
knitr::include_graphics("images/irpq/irpq-pq-sg-process.png")
```
<div class="info_box">
<h4>Important</h4>
* While it is true that there is a short turnaround time in responding to PQs, the timeframe in which PHS should respond to SG (this will be known as our *Policy Deadline Date*) can be negotiated with SG.
* All attempts should be made to adhere to the above timeline.
</div>
</br>
## PQ - Workflow
The following section contains a general workflow for PHS Users to understand the PQ process.
More detailed breakdowns of each stage of the process can be found in later sections of this course.
1. PQs are made available.
2. The PHS Statistical Governance Team (phs.statsgov@phs.scot) retrieves and assigns the PQs to the appropriate PHS teams (see section [PQ - Retrieving & Assigning PQs](https://scotland.shinyapps.io/phs-learn-irpq/#section-pq---retrieving-assigning-pqs)).
3. Teams receive and assess the PQ.
4. If correctly assigned and the team are able to answer, contact SG to enquire whether a response is required (see section [PQ - Processing & Responding](https://scotland.shinyapps.io/phs-learn-irpq/#section-pq---processing-responding) for further information on the process at this stage, including for instances where PQs have been incorrectly assigned, or unable to be answered).
5. If a response is required, log the PQ in the IRS. (see section [IR - Form & Service](https://scotland.shinyapps.io/phs-learn-irpq/#section-ir---form-service))
6. Discuss the PQ with SG, gaining clarification as necessary, establishing deadlines, and conveying all relevant information.
7. Once all is agreed, proceed with answering the PQ. **Follow the [PHS Statistical Disclosure Control flowchart](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/statistical-disclosure-control/overview-of-disclosure-control-protocol/). ** If required, contact Stats Gov for assistance.
8. Produce draft answer in accordance with style guidelines, using the appropriate template. (see section [PQ - Processing & Responding](https://scotland.shinyapps.io/phs-learn-irpq/#section-pq---processing-responding))
9. Complete the sign-off procedure. (see section [PQ - Sign Off](https://scotland.shinyapps.io/phs-learn-irpq/#section-pq---sign-off))
10. Send the draft answer to the SG contact.
11. Update IRS and close the record.
12. Review the answer once it has been published at the [Scottish Parliament's Questions and Answers page](https://www.parliament.scot/chamber-and-committees/questions-and-answers)</a>.
<div class="info_box">
<h4>Important</h4>
* PHS Teams may, at times, receive PQs directly from Scottish Government contacts. In this instance, teams should carry out the PQ process above as normal proceeding from the **Teams receive and assess the PQ** of the above list.
</div>
</br>
Next, we will cover the first stages of the above workflow - how PQs are retrieved and assigned by Stats Gov.
## PQ - Retrieving & Assigning PQs
In this section, we will look at how the PHS Statistical Governance Team (phs.statsgov@phs.scot) retrieves the PQs from the Parliament website, and assigns them to teams within PHS.
### Retrieving new PQs
Every Tuesday and Thursday morning, Stats Gov runs a script which scrapes **all** the PQs from the Parliamentary website, until midnight of the previous day.
Questions which hit certain keywords relating to health (NHS, blood, etc.) are flagged in order to aid Stats Gov by highlighting important health-related questions.
Through the retrieval process, all questions (flagged and non-flagged) are retrieved and are manually reviewed by Stats Gov.
Throughout the year, there may be times where Stats Gov will increase the frequency of these retrievals if necessary due to large volumes.
```{r pq-review-quiz, results='asis'}
quiz(
question("Which of the following PQ's have Stats Gov reviewed? 'To ask the Scottish Government... (select ALL that apply)",
answer("how many stoats have there been in Orkney in each of the last seven years, and what it estimates the figure will be for 2019?", correct = TRUE),
answer("what plans it has to reduce the working week for public sector staff", correct = TRUE),
answer("whether guidance on flying flags from its buildings changed in 2021; what any such changes were, and what the reasons were for any changes made.", correct = TRUE),
answer("to ask the Scottish Government how many full-time equivalent British Sign Language tutors are currently employed by each local authority.", correct = TRUE),
incorrect = "There are a few more!",
allow_retry = TRUE,
random_answer_order = TRUE
)
)
```
### Assigning PQs
PQs are manually reviewed by Stats Gov, who decide the following:
#### Topic Area
The team will decide what topic areas the question corresponds to, and to which teams it should be assigned to.
The following is an excerpt from the topic area/team allocation guide which Stats Gov uses to allocated the PQs to the appropriate team. It includes what topics should be allocated to the team (in this case, Quality Indicators) and what should not.
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Excerpt from Allocations Guide document"}
knitr::include_graphics("images/irpq/irpq-pqallocation.png")
```
It is important to note that questions may pertain to multiple teams. If this is the case, it will be allocated to all related teams, and such an allocation be detailed in the *Notes* section explained below.
#### Action
Assigned PQs are given one of two actions:
* **For Information** - this indicates that the question is of interest to your service area. While there is no expectation to reply, be prepared should SG contact you to request any relevant assistance.
* **For Review** - this indicates that the question may require you to take action.
Regardless of the action assigned to the PQ, the recipients should read said PQ and make a decision whether any further action is necessary (we will discuss this later in the course).
#### Notes
Any relevant notes (such as previously answered PQs relating to this PQ, and to what other teams this PQ has been allocated to, including the action).
If the question has been assigned to multiple teams, it is expected that the teams will make contact with one another when processing the PQ.
<div class="info_box">
<h4>Important</h4>
* Stats Gov are not specialists within the individual topic areas, and may occasionally assign a PQ’s Topic Area or Action in error. Teams are expected to read through all PQs assigned to them. If incorrectly reassigned please contact Stats Gov and, where possible, cc the correct team who may be able to respond to the PQ. Stats Gov will update their allocation guide and process to mitigate future incorrect allocation.
* Stats Gov (phs.statsgov@phs.scot) welcomes any and all corrections in order to improve their services.
</div>
</br>
### Assigned PQ
Once the PQ has been assigned by Stats Gov, it is then sent out to the relevant teams, relating to the topic areas. Each topic area will generate one email containing all the PQs for that allocation session.
The email contains information on how to proceed, the SG contact email, as well as the deadline dates.
**The 'Answer expected' date is for when the question will need to be sent to the relevant MSP. It is not the deadline for PHS to respond to the SG.**
#### Example
```{r echo=FALSE, fig.align='center', out.width="100%", fig.alt="Example PQ allocation email"}
knitr::include_graphics("images/irpq/irpq-allocatedTeamEmail.png")
```
### Knowledge Check
```{r PQ-AllocationsQuiz}
quiz(
question("You have received a PQ which is not related to your service area, and has only been sent to your team. What should you do? (select ALL that apply)",
answer("Contact Stats Gov and inform them of the error.", correct = TRUE),
answer("If possible, forward the answer to the appropriate PHS team.", correct = TRUE),
answer("Contact Scottish Government, and tell them PHS cannot assist", message="You should not contact Scottish Government, as this PQ has been incorrectly assigned to your team."),
answer("Do nothing and wait for Scottish Government to ask for assistance", message="You should make every effort to ensure the PQ is received by the correct team, and that Stats Gov are informed of this error."),
allow_retry = TRUE,
random_answer_order = TRUE
),
question("If you receive a PQ with Action 'For Information', you can ignore it as you will not need to provide a response.",
answer("TRUE", message = "Teams should still read the PQs and take further action if necessary."),
answer("FALSE", correct = TRUE),
allow_retry = TRUE,
random_answer_order = TRUE
)
)
```
In the next section, we will cover what you should consider when you receive a PQ.
## PQ - Types & Considerations
The template used to respond to a PQ can be found in Appendix 3 of the [Parliamentary Questions Protocol Guide](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/parliamentary-questions/).
Within this template, you can see two key sections:
* **Draft Answer** - this is where you will supply your answer to the PQ.
* **Background Note** - this is additional/background information which could provide greater understanding or references.
Before you start to respond to the PQ, there are a number of considerations to bear in mind.
### Considerations
In the event you receive a PQ, you should carefully consider whether or not you are able to provide a response, what it may involve, and what you may need to discuss with your, or another, team.
The following are a list of considerations which you should discuss with your team:
### <blank>
#### Is your team able to answer the question?
* If your team is unable to answer the question, why is that? Did you incorrectly receive the PQ, and that error needs to be fed back to the Stats Gov team?
* Is input from a specialist (medic/HOP/Clinical Coding Helpdesk) required?
* Perhaps there is another team or organisation better suited with the appropriate data? For example, questions about Deaths would be more suited to NRS.
* If the question is being answered by multiple sources, who is taking the lead?
* Should the PQ require considerable resource and/or new analytical input please ensure this has been discussed with senior management.
### <blank>
#### Is the deadline achievable?
* If the deadline is not achievable, discuss the matter with the SG contact contained in the PQ email.
**It is often possible to negotiate deadlines with SG, especially when further analysis is required.**
### <blank>
#### Other considerations
* If the question cannot be answered, what background information should be considered? (If any)
* Can the question be interpreted in more than one way? If yes, how can you get clarification?
* Has a similar question been answered before? (This could be searched for on the [Scottish Parliament's Questions and Answers page](https://www.parliament.scot/chamber-and-committees/questions-and-answers))
* Is there a published source, which they can be referred to?
* What data completeness/quality issues may arise?
Hopefully, after spending some time on the above considerations, you will have decided on whether it is appropriate for your team to respond to the PQ.
Next we will discuss the 3 types of PQs you could receive, and provide some guidance on how best to answer them.
### PQs which can be answered with a specific answer
These are answers which are relatively straightforward PQs, such as when a table of figures would be enough to answer the PQ.
Some interpretation or explanation may still be required to give the MSP a clear understanding of the provided statistics.
**To ask the Scottish Government how many patients have received care or treatment at the (a) Vale of Leven and (b) Inverclyde Maternity unit in each year since May 2007**
**Draft answer example:**
*The information is provided in the table below:*
*Table 1: Number of patients recorded as having received care or treatment at the Vale of Leven and Inverclyde maternity unit*
**If the data is available on a website a standard reply should be used.**
**Draft answer Example:**
*The information is published on the PHS website under (insert section of website and link).*
Relevant background notes should be provided. Keep it brief, but provide enough information to ensure the question is answered and understood.
### PQs which require interpretation
A question may seem straightforward, but might not map to a specific available data source, or if it does, it may require interpretation of how to answer it. You may need to get specialist advice, or be flexible with your response in order to cover multiple interpretations of the same question.
Below are some examples of PQs which require interpretation.
```{r interpretationQuestions}
quiz(caption = "What information might you need to interpret in order to fully answer the question?",
question("To ask the Scottish Government how many (A) adults and (B) children have been registered with a dentist in each year since 2005. (select ALL that apply)",
answer("Definition of Adult and Children - Over 16 or over 18? Under 16 or under 18?", correct = TRUE),
answer("NHS or Private Dentist", correct = TRUE),
answer("Calendar year or financial year?", correct = TRUE),
answer("Reason for visiting the dentist", message = "There is no need to know the reason for visiting the dentist. Try again."),
allow_retry = TRUE,
random_answer_order = TRUE
),
question("To ask the Scottish Government how many people have been prescribed drugs for depression in each year since 2005, broken down into (A) children, (B) adolescents, (C) adults and (D) elderly people in each NHS board area. (select ALL that apply)",
answer("Time Period - since Jan 2005 or April 2005? (calendar year or financial year)", correct = TRUE),
answer("Definition of adult, child, elderly?", correct = TRUE),
answer("Could the prescribed drug also be prescribed to treat other conditions? Do we need specialist advice?", correct = TRUE),
answer("Is it possible for us to differ between the number of people, and the number of prescriptions?", correct = TRUE),
answer("How long have the individuals been on the prescribed drugs?", message = "There is no need to know how long an individual has been prescribed drugs. Try again."),
allow_retry = TRUE,
random_answer_order = TRUE
)
)
```
### <blank>
**To ask the Scottish Government how many attendances at GP surgeries by prostate cancer patients there have been in each year since 1997-98, also broken down by (a) NHS Board and (b) parliamentary constituency.**
For this question, the data is not collected by PHS, but a similar data set may be available. It may also require some advice from Medical Colleagues and will need to be checked by an appropriate Service Manager.
**Example Draft Answer:**
*This information is not available centrally. However estimates based on data from a small sample of general practices in Scotland, which are representative of Scotland, is presented in Table 1.*
*Table 1 shows the estimated numbers of patients attending consultations at Scottish GP Practices for prostate cancer related conditions during financial years 2003/04 to 2008/09.*
### Policy focussed questions where background data is helpful for the SG
These are questions which do not specifically ask for statistical information but for which data held by PHS could provide useful background context.
The data would be provided to the SG as a background note.
**To ask the Scottish Government whether it plans to review beta blocker prescribing recommendations following a study recently published in The Journal of the American Medical Association suggesting that beta blockers did not prolong the lives of patients.**
**Example Draft Answer:**
*The question relating to whether the Scottish Government plans to review beta blocker prescribing cannot be answered from data held centrally by PHS.*
**Background Note**
*Information on the number of items dispensed and the gross ingredient cost for beta blockers for financial years 2010/11 and 2011/12 by NHS board can be found in the table 1 below…*
## PQ - Guiding Principles
When you are in a position where you are required to provide a response, there are certain Guiding Principles which you should adhere to, in order to provide an answer that is clear and effective.
Below are some guiding principles which draft answer producers should consider and adhere to.
It is important to remember that PHS staff should know best about the quality of the data that we are providing. As such, we should not be leaving those who receive the PHS draft answer to interpret the data for themselves.
```{r echo=FALSE, fig.align='center', out.width="75%", fig.alt="Image of guiding principles"}
knitr::include_graphics("images/irpq/irpq-guidelines.png")
```
#### Background Notes
Background notes are provided to give additional contextual information.
This could include:
* Explain why the question has been answered in a certain way
* Explain issues with data used within the draft answer
* Sources and other useful briefings
**SG will most likely leave Background Notes out of their final response.**
<div class="info_box">
<h4>Important</h4>
* The SG may change the response provided by the PHS when preparing the final answer for the MSP. Such changes are often checked with PHS, but not always.
* For particularly hot topics, PHS staff should request they be consulted of any proposed changes to the content or wording of the PQ by the SG.
* If there are any issues with the process, please get in touch with Stats Gov and your Service Manager in the first instance.
* The above considerations and guiding principles provide an advisory basis for how you should tackle the PQs posed to you. Teams will have their own methods in responding effectively.
* For further guidance on releasing information in line with the Code of Practise, the [Scenarios on Code of Practise](https://spark.publichealthscotland.org/downloads/scenarios-on-code-of-practice/) document on Spark provides a number of appropriate examples.
</div>
</br>
### Knowledge Check
```{r PQ-GuidingPrinciples}
quiz(
question("You have received a PQ which you have been asked to respond to by the SG. The data you have access to is not clear, and as such, you cannot fully answer the question. What do you do? (select ALL that apply)",
answer("Do not pass on the data that is not clear.", correct = TRUE),
answer("Contact Scottish Government, and explain why you cannot assist.", correct = TRUE),
answer("Send the SG the data, and explain why you cannot answer it.", message = "You should not be sending unclear data to SG."),
answer("Contact specialists on the data to gain clarity, to assist in answering.", correct = TRUE),
answer("Do nothing. You cannot answer the question so it is better not to confuse anyone.", message = "You have been asked to respond by SG, and you should provide a response of some kind."),
correct = "That is correct! You should be open and transparent about your capabilities in answering a PQ, and specialist assistance should be sought in helping to answer a question.",
allow_retry = TRUE,
random_answer_order = TRUE
),
question("Your response to a question will include data that is contained in a publication due to be released in 12 weeks. You should release the answer with the data since PQs are important, and should be answered as soon as possible.",
answer("TRUE"),
answer("FALSE", correct = TRUE),
incorrect = "You should not be releasing data that is due to to be released within the next 12 weeks of an official release.",
allow_retry = TRUE,
random_answer_order = TRUE
)
)
```
## PQ - Processing & Responding
The following is the workflow when processing and responding to a PQ:
### Assess the PQ
Upon receiving a PQ, assess if it is:
* **Incorrectly assigned** - Stats Gov will have assigned the PQ according to their existing team allocation guide therefore if the correct team is known please forward the question to the appropriate team, copying Stats Gov for future reference and allocation processes will be updated to mitigate this in future. If there are no appropriate teams, contact Stats Gov and make them aware. No further action is required.
* **Correctly assigned, For Information** - No further action required, unless SG makes contact to request input.
* **Correctly assigned, For Review, Unable to Answer** - Inform SG that this data is not held.
* **Correctly assigned, For Review, Able to Answer** - Follow the steps below.
<div class="info_box">
<h4>Important</h4>
* If multiple teams have been assigned to the PQ, it is expected for teams to liaise with other teams when processing the PQs.
</div>
</br>
#### Contact the SG
**Contact SG** using the contact details within the PQ email, and find out if a response is required.
If no response is required, no further action is needed.
#### Response Required
Should a response be required, a discussion should be had with SG:
* Obtain SG's contact details from the PQ allocation email from Stats Gov.
* Record PQ in IRS (refer to later section on 'IR - Form & Service').
* Clarify SG understanding of PQ.
* Advise if Background notes will be provided.
* Establish/negotiate deadlines.
* If SG suggests a response that is not consistent with intended PHS response: discuss with Head of Service/Service Manager
### Checks Before Responding
Once a response is determined to be required, then the following should be undertaken:
* Check [Scottish Parliament's Questions and Answers page](https://www.parliament.scot/chamber-and-committees/questions-and-answers) for previous responses, consistency in codes/definitions, etc.
* If a previous response contains statistics based on methodology that has changed, this should be explained either in the answer itself, or the background note.
* If further expertise is required, this should be sought after immediately.
* If data is available on a website, a standard reply should be used. For example, ‘The information is published on PHS’s website under (insert section of website and link).’ Where relevant, background notes should be provided.
* Information should not be the first public release of the data.
* **Follow [PHS Statistical Disclosure Control flowchart](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/statistical-disclosure-control/overview-of-disclosure-control-protocol/). ** If required, contact Stats Gov for assistance.
### Producing Draft Answer
All answers should be produced using Appendix 3 of the [Parliamentary Questions Protocol Guide](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/parliamentary-questions/).
The following style guidelines checklist should be applied:
<input type="checkbox" unchecked> Font should be Arial size 12 for text and tables.</input>
<input type="checkbox" unchecked> Only Word tables should be included in the answer.</input>
<input type="checkbox" unchecked> All tables should be portrait.</input>
<input type="checkbox" unchecked> The left hand column in a table should be left justified, including the heading.</input>
<input type="checkbox" unchecked> The table rows containing information/figures should be right justified.</input>
<input type="checkbox" unchecked> Table headings and titles should not be in bold.</input>
<input type="checkbox" unchecked> Very large tables should not be included in the answer. Instead, save these as separate Excel sheets and include that with the answer.</input>
Check draft answer for accuracy, typing mistakes, etc. *Best practise is to have a colleague check the answer.*
Once checks are done, and the answer is produced in accordance with the above, it can proceed to the sign-off stage.
## PQ - Example
In this section, we will consider a case study as an example of how to create a draft answer for the PQs.
Further examples can be found in Appendix 4 of the [Parliamentary Questions Protocol](https://spark.publichealthscotland.org/corporate-guidance/statistical-governance/parliamentary-questions/).
### Example Scenario
Your team has received the following PQ and have been asked by SG to respond to it: