Update references to database refresh frequency

docs/data-sources/cpns.md

@@ -10,10 +10,10 @@ Initially this was lab-confirmed covid deaths only, but also includes suspected
 : In-hospital covid-related deaths in England.
 
 **Update frequency in OpenSAFELY**
-: Weekly.
+: Every four weeks.
 
 **Delay between event occurring and event appearing in OpenSAFELY**
-: Within 2 weeks.
+: Within 2 to 5 weeks.
 
 **Available from**
 : 24/03/2020 onwards (all test-positive deaths); 28/04/2020 onwards (test-positive and covid documented as underlying cause).

docs/data-sources/icnarc.md

@@ -26,10 +26,10 @@ Specialist units (eg neuro / cardiac) also participate. covid-19 admissions only
 : ICUs and HDUs
 
 **Update frequency in OpenSAFELY**
-: Approximately weekly.
+: Approximately every four weeks.
 
 **Delay between event occurring and event appearing in OpenSAFELY**
-: Approximately 1-2 weeks.
+: Approximately 1-5 weeks.
 
 **Collected information**
 : Admission, discharge and transfer dates; reason for admission; clinical support/interventions; clinical findings

docs/data-sources/onsdeaths.md

@@ -12,13 +12,13 @@ Date and cause of death based on information recorded when deaths are certified
 : General Register Office.
 
 **Update frequency in OpenSAFELY**
-: Approximately weeekly.
+: Approximately every four weeks.
 
 **Available from**
 : deaths recorded from February 2019 onwards.
 
 **Delay between event occurring and event appearing in OpenSAFELY**
-: Approximately 1-2 weeks.
+: Approximately 1-5 weeks.
 
 **Collected information**
 : Date of death, causes of death, age, sex, place of death.

docs/data-sources/sgsscovid.md

@@ -18,7 +18,7 @@ Some SARS-CoV-2 testing info also flows directly into the primary care record fr
 : Approximately monthly
 
 **Delay between event occurring and event appearing in OpenSAFELY**
-: Approximately 1-2 weeks.
+: Approximately 1-5 weeks.
 
 **Collected information**
 : Earliest specimen date, lab report date, age, sex, county, test result, source ("pillar 2" or "other")

docs/data-sources/systmone.md

@@ -110,7 +110,7 @@ When TPP receive data from external data sources (eg ONS), the tables are comple
 
 ## OpenSAFELY-TPP database builds
 
-The OpenSAFELY-TPP database is typically built once per week.
+The OpenSAFELY-TPP database is typically built every four weeks.
 In essence, this involves refreshing the database records so that the following groups are available for analysis:
 
 1. All patients currently registered[^1] at a TPP practice

docs/data-sources/therapeutics.md

@@ -12,10 +12,10 @@ The Therapeutics dataset contains information on COVID treatments used in inpati
 : Data sourced largely from BlueTeq system (forms completed by clinicians)
 
 **Update frequency in OpenSAFELY**
-: Approximately weekly
+: Approximately every four weeks
 
 **Delay between event occurring and event appearing in OpenSAFELY**
-: Approximately 2-9 days
+: Approximately 2 days + (0 - 4 weeks)
 
 **Collected information**
 : Treatment start date; therapeutic intervention; COVID indication, current status, risk group, region

docs/security-levels.md

@@ -6,7 +6,7 @@ Each stage is generated from the preceding stage — at each step, data priv
 This is the most restrictive level and includes the complete, raw, fully-identifiable, event-level patient data.
 EHR vendor data engineers store data at an identifiable level as part of their business-as-usual; they are instructed to process this data by the GPs (who are in routine practice the data controllers) in order to manage and store this information.
 
-This identifiable data is further processed by the EHR vendor to create a database of pseudonymised coded event-level GP data which the OpenSAFELY service can access to run study queries against. The pseudonymised GP data can be refreshed at regular intervals, for example, it is currently refreshed weekly by TPP.
+This identifiable data is further processed by the EHR vendor to create a database of pseudonymised coded event-level GP data which the OpenSAFELY service can access to run study queries against. The pseudonymised GP data can be refreshed at regular intervals, for example, it is currently refreshed every four weeks by TPP.
 
 ### Where is this data held?
 Data is held within the EHR vendor's secure environment.