Secondary Data Analysis
Uses statistics or operational records collected for another purpose in evaluation. Check fit of collection purpose, targets, definitions and timing to evaluation questions. [1]
- Difficulty
- Intermediate
- Cost
- Low
- Duration
- Illustrative planning durations, not common standards: finding/acquiring data 1–2 weeks, quality/preprocessing 1–2 weeks, analysis 2–4 weeks
How it works at a glance
Organize variables and periods before searching. Check metadata, missingness, revisions and use conditions and retain processing records. [1]
Available indicators may not measure intended outcomes. State population or definition mismatches and consider additional collection for unanswered questions. [1]
- Find secondary data
- Assess quality through metadata
- Access and acquire data
- Clean and preprocess
- Conduct analysis
- Describe limitations and interpretation cautions
When to use it and when it is unsuitable
When to use it
- Understand target-area/group backgrounds and trends without new collection
- Supplement outcomes using municipal records or statistics
- Build long-term trends or comparison-group baselines
- Obtain quantitative evidence with limited budgets
When it is unsuitable
- Necessary variables absent: primary collection is needed
- Substantially different collection times or targets invalidate comparison
- Access or use terms restrict evaluation use
Participants, roles, and deliverables
Participants and roles
1–2 data analysts; acquisition may require coordination with administration
Main deliverables
- Source list with metadata assessments
- Clean analytical dataset with code and procedures
- Quantitative report with limitations
Implementation steps
- Find secondary dataSystematically search e-Stat, government statistics, international agencies, municipal open-data portals and archives such as SSJDA. List variable, sample and timing fit.
- Assess quality through metadataCheck purpose, population, sampling, timing, missing-data treatment and definition history. Explicitly record coverage, timing and variable-definition mismatches.
- Access and acquire dataCheck terms, privacy and secondary-use permissions. Use appropriate microdata applications through SSJDA or statistical offices, APIs or downloads.
- Clean and preprocessCheck missing values, outliers and coding. For joins, align area codes/times and validate keys. Record every step in R, Python or Excel scripts for reproducibility.
- Conduct analysisUse methods suited to questions and data: descriptive statistics, trends, area or group comparisons. Incorporate target/non-target or before/after comparisons.
- Describe limitations and interpretation cautionsState collection purpose, times and target mismatches when reporting. Explain over/underinterpretation risks from constraints and points needing primary-data supplementation.
Strengths and limitations
Strengths
- Uses large longitudinal datasets without new collection costs or time
- Administrative records and censuses offer scale and coverage difficult in primary studies
- Strong for long time-series trends and comparison groups
- Reuse is expected in EBPM and evidence synthesis
Limitations
- Not designed for evaluation, so necessary variables may be absent
- Time, target and definition differences complicate comparisons
- Terms and privacy constraints may limit access
- Inadequate limitation assessment/reporting risks erroneous conclusions
Common pitfalls
- Do not derive questions from available data. Set questions first, then seek necessary data.
- Provider definition changes can distort trends. Always check metadata and annual reports' methodological-change sections.
- Do not hide limitations only at the end. State collection-purpose, definition, target differences and missingness relevant to conclusions alongside results.
Conditions of use and evidence
- Judge fit to purpose considering record gaps and post-creation changes. [1]
Distinguish consultation counts and people
A fictional illustration examining reach using a fictional consultation register.
Scroll horizontally to view the table
| Item | Fictional register value | Interpretation |
|---|---|---|
| Consultation count | 120 cases | Includes repeat consultations |
| Identifiable users | 80 people | Scope where duplicates could be checked |
| Records without identifiers | 10 cases | Further checks needed for person counts |
Common errors in judgment
Compare years without checking definitions
How to revise
Check aggregation and recording changes
ReasonApparent trends may arise from institutional or recording changes.
Freely join individual records because data are public
How to revise
Check terms and re-identification risks
ReasonAnonymous datasets may identify people when joined.
References and checked sections
- Existing documentsBetterEvaluation
- Section consulted
- Types of existing documents / Advice for using this method
- How it relates to the text
- Judge fit to purpose considering record gaps and post-creation changes.
Editorial and checking information
How to cite this page
Change history
- — Checked sources for definitions and conditions and added fictional examples, judgment rationales and completed entries for every field. Revised unsupported historical or uptake claims. Reviewed procedures and cautions, adjusting fixed counts, thresholds and institutional generalizations. Preserved field positions, types and counts while revising fixed conditions and thresholds.


