Publish appointments-short-data-report

[inglesp]

From Seb:

This is a short data report about Appointments. We link to it from our documentation. However, it is not published.

Given our "working in the open" principle, it is something of a smell to publish a link to a non-public document.

We should publish the report, with a disclaimer added at the top. This Database Coverage report has good text we could copy as frontmatter:

This report displays the historical coverage of the OpenSAFELY-TPP database. It is part of the OpenSAFELY platform's technical documentation and is published at https://reports.opensafely.org/.

This report should not be used for inference about any aspect of the pandemic, public health, or health service activity. For the avoidance of doubt, any clinical or epidemiological interpretation of this report is likely to be a misinterpretation.

If you would like to use the OpenSAFELY platform, then you should read our documentation, our principles, and our process for onboarding new users. If you would like to see the code we used to create this report, then you can view it on GitHub.

[inglesp]

See opensafely/appointments-short-data-report#43 for implementation notes.

[iaindillingham]

TODO

• Suppress counts. (The disclosure control guidance was updated.)
• Ask an output reviewer to look at analysis/reports/report.ipynb (For the same reason. Would they make a small exception?)¹
• Fix failure when run locally (and presumably in CI)
• Handle T1OOs
• Check Operations Group approval
• Check NHSE approval
• Update jobserver permissions
• Run on OS Jobs
• Request outputs are checked

Footnotes

1. https://bennettoxford.slack.com/archives/C01UJLWNZJT/p1699884698368099 ↩

[iaindillingham]

I've moved this to "blocked" because:

• It's unclear whether this report has Operations Group approval.¹
• It's unclear whether this report is exempt from NHSE approval.² Amir has argued that short data reports are exempt, but that we should nevertheless contact NHSE as a courtesy.
• The project that's associated with this workspace doesn't have permission to run SQL Runner actions. A member of the IG team must grant this permission.³

Footnotes

1. https://bennettoxford.slack.com/archives/C01UJLWNZJT/p1699885642360359 ↩

2. https://bennettoxford.slack.com/archives/C31D62X5X/p1686742702816139?thread_ts=1686669958.929239&cid=C31D62X5X ↩

3. https://bennettoxford.slack.com/archives/C63UXGB8E/p1699887531231189 ↩