# Recognising personal data in healthcare projects In healthcare projects, personal data could include: * Socio-economic data, such as household income, and ages and education levels of each household member. * Electronic health records, such as individual episodes of care including doctor visits, prescriptions supplied, or hospital or day care surgeries. * Health and wellness tracking from mobile phones, digital watches and other wearable technologies that measure, for example, heart rate, levels of physical activity and sleeping patterns. * Mobile phone numbers, which often have associated geo-location that could identify an individual. * Information about employees working in healthcare systems, for example name, address and bank details. ![](/files/SLotCMfkmV0vhBp8lEcm) **Key actions to take:** * Could the data in your project directly or indirectly identify individuals? If the answer is yes, refer to the section below on minimising risks. * Consider developing a [data protection impact assessment](https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/accountability-and-governance/data-protection-impact-assessments/) to keep a record of specific risks and mitigations. * Consider speaking to your data protection officer or seeking legal advice to confirm which data protection laws and regulations will need to be complied with. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://open-data-institute.gitbook.io/data-governance-playbook/play-eight-managing-risks-when-handling-personal-data/recognising-personal-data-in-healthcare-projects.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.