Healthcare Data Protection in the UAE: Smart Wearables, Consultation Recording and Clinical Governance

Privacy, Recording and Health Data Governance
A patient arrives for a consultation wearing camera-equipped glasses. Another brings several months of heart-rate and sleep data from a smartwatch. Both devices appear ordinary, and both may help the patient engage with their care. Yet they create different questions for a healthcare provider. One may capture a private conversation and people nearby. The other may introduce health information collected, interpreted and stored outside the clinic’s systems.
The distinction matters as smart wearables become easier to use without a visible phone or a deliberate act of recording. Camera glasses can capture sound and images hands-free; health wearables can turn continuous measurements into reports that patients want clinicians to review. A consultation can therefore involve data whose collection began before the appointment and whose onward use may be difficult for either party to see.
For UAE healthcare organisations, the decision is broader than whether to allow a particular device through the door. They must protect patients, staff and visitors; understand how information enters and leaves clinical systems; and give patients workable ways to remember advice or share useful measurements. Device makers and digital health founders face a corresponding question: whether a consumer product’s default data flows are suitable for a healthcare setting.
This article examines what smart wearables mean for healthcare data protection in the UAE, including how privacy and cybercrime law, health data requirements and clinical governance apply in practice.

Smart wearables in UAE healthcare create two distinct data pathways
Camera-equipped glasses and biometric wearables are often discussed together, but their immediate risks differ. Glasses may collect information about other people: a clinician’s voice, a patient visible through an open doorway, or a conversation in a waiting area. A watch or ring usually collects information about its wearer: heart rate, activity, sleep or related measurements. Both can generate identifiable information, and either can become part of a clinical decision.
The pathway matters as much as the sensor. Consider a patient who records a specialist explaining a diagnosis. The file may remain on the device, move to a phone, be backed up, be shared with a relative or be submitted to an AI service for a summary. Each step changes who can access it and how long it may persist. Meta says captures on its AI glasses remain on the glasses until the user moves them to a phone through its app; its description of AI features also explains that selected images and spoken requests can be sent for processing. Those functions should be assessed separately rather than assuming every capture follows the same route.
A wearable health report follows another route. A patient may show a chart during an appointment, email an export to the clinic, or authorise an application to connect with a service. Once the clinic receives and uses that information, questions arise about its clinical relevance, accuracy, retention and integration with the health record. The existence of a measurement does not itself establish that it is sufficiently reliable for diagnosis.
This is why a single policy stating that “wearables are allowed” is inadequate. A provider needs to distinguish passive wearing, active recording, the presentation of patient-held information, and the provider’s own collection or processing of that information.
UAE privacy law requires a more precise account than a blanket recording ban
A commonly repeated claim is that recording any doctor’s consultation without the doctor’s explicit permission is automatically a criminal offence carrying a fine of AED 150,000 to AED 500,000. It conveys a sensible practical warning, but it compresses the legal test.
Article 44 of Federal Decree-Law No. 34 of 2021 addresses the use of an information network, information system or information technology equipment with the intention of invading another person’s privacy or the sanctity of private or family life, without consent and outside cases authorised by law. Its listed conduct includes recording or transmitting conversations and capturing images in the circumstances the provision describes. The stated penalty is imprisonment of at least six months and/or a fine of AED 150,000 to AED 500,000. The provision should therefore be read with its elements and context, rather than presented as an automatic penalty for every recording made in a consultation. Other provisions of UAE law may also be relevant to recording private conversations.
In practice, a person should ask before recording a consultation. A patient’s wish to remember complex instructions is understandable, but it does not amount to permission from everyone whose voice or image might be captured. Equally, a camera’s indicator light establishes neither informed consent nor compliance with a facility’s policy. Meta describes an illuminated capture light as a way to alert people nearby when its glasses are taking photos or video. Alerting someone and obtaining their agreement are different acts.
A clinic can set conditions for recording on its premises and protect the confidentiality of other patients. It can ask a person to stop recording and follow an incident procedure if recording has occurred. Claims that staff have an unconditional legal right to inspect a personal device or compel immediate deletion should be avoided without a specific legal basis and appropriate advice. Where there is a suspected offence or data exposure, preserving an accurate account of what happened may be more important than an improvised confrontation over the file.
The practical position is clear even where the legal outcome depends on facts: disclose the proposed recording, explain its purpose, seek agreement before starting, and follow the facility’s rules. If agreement cannot be reached, the provider should offer another reasonable way for the patient to retain the information.
Consent to recording is specific to people, purpose and onward use
Healthcare discussions tend to treat consent as a single yes-or-no question. Recording requires a more exact account of what has been agreed. A clinician may be willing for a patient to make an audio record of instructions for personal reference while declining video. Permission for that use does not necessarily extend to publishing a clip, submitting it to an external AI tool, or capturing a nurse or another patient who did not participate in the discussion.
The setting also changes the risk. In a private consultation room, the principal question may concern the patient and clinician. In a shared treatment space or waiting area, a device can collect identifiable information about people who have no relationship with the wearer. A companion joining a consultation introduces another voice and potentially another set of expectations about sharing.
A workable recording agreement should therefore identify the device, whether audio or video will be captured, the intended recipients and the purpose. It should address whether any material will be uploaded to a third-party service. The clinic should document the decision and any limits it places on recording. These are governance measures, not a claim that one standard form resolves every legal issue.
Providers should also preserve a useful alternative for patients. A written summary, a patient-approved companion, or an agreed recording made through a controlled process may better serve someone facing a complex diagnosis or treatment choice. Recording policies are more likely to be followed when they recognise the reason patients ask.
Separate rules apply when a provider wants to use patient imagery or statements publicly. Dubai Health Authority guidance requires separate written and documented consent from a patient or individual whose pictures, images, videos or statements are used in social media advertising. Consent to treatment is not permission to use a consultation image in promotional content.
Biometric data becomes a clinical governance issue when it informs care
A consumer wearable can produce a large volume of apparently precise measurements. Precision of display, however, is different from clinical validity. A clinician reviewing a reported change in heart rate, sleep or activity needs to know what the device measured, how it estimated the result, whether the patient was using it correctly and what decision the information is expected to support.
The first governance question is purpose. Data shown briefly by a patient to explain symptoms is different from a dataset formally imported into a record and monitored over time. In the latter case, a provider may need a defined review process: who checks incoming information, at what frequency, which findings require escalation, and how the patient is told about the limits of monitoring. Without those decisions, an apparent service can create expectations that no team is equipped to meet.
The second question is provenance. A screenshot may lack the context needed to interpret an outlier, including the period covered, device settings or gaps in collection. If a measurement materially informs advice, the clinical record should make clear what information was considered and how much weight it carried. A consumer-generated trend may be useful evidence to investigate a concern without serving as a confirmed diagnosis.
Finally, information collected for personal wellness may become more sensitive when linked to a named patient, diagnosis or treatment plan. Founders offering wearable integrations to clinics should account for that change in use. Product consent screens, technical permissions and clinical consent serve related but different purposes; none should be assumed to substitute automatically for the others.
Healthcare data protection in the UAE: storage and cross-border sharing require a separate legal assessment
The UAE’s Federal Decree-Law No. 45 of 2021 provides a framework for personal data protection, including provisions concerning cross-border transfers. It is incomplete, however, to describe its transfer routes as a general permission for a healthcare provider to send UAE clinical data to an overseas cloud. The applicability of that law and its interaction with sector-specific rules must be assessed for the data and organisation concerned.
Federal Law No. 2 of 2019 governs the use of information and communications technology in UAE health fields, including free zones. Its Article 13 restricts storing, processing, generating or transforming outside the UAE health data and information related to health services provided inside the country, subject to the approval mechanism stated in the law. The existence of recognised cases for storage or transfer outside the country means the position should not be reduced to an assertion that all such transfers are impossible. Nor should a general personal-data transfer provision be treated as sufficient clearance for a clinical workflow.
This distinction has immediate product implications. A clinic evaluating an AI transcription service, a wearable dashboard or a camera-assisted consultation tool needs to establish what data is captured, where processing takes place, which vendors can access it, whether the service uses it for further product purposes, and what happens to copies and backups. “Stored locally” answers only part of the question if a feature transmits selected content elsewhere for analysis.
The assessment should also distinguish a consumer acting independently from a healthcare organisation collecting information as part of its service. Their roles and obligations may differ. A clinic should nevertheless avoid building a workflow around a patient’s consumer account without understanding how the resulting health information is handled.
Dubai Health Authority policies add operational requirements for organisations within their scope, including the protection and controlled sharing of health information. A provider working across emirates, regulators or free zones should identify the rules applicable to each service and location rather than assume one policy covers every setting.
Healthcare providers need a recording and wearable policy that staff can apply
Effective governance begins at the point of care. A policy should state where recording is prohibited, where a request can be considered, who can approve it, and how the decision is documented. Reception and clinical staff need a consistent way to explain the policy without implying that simply wearing glasses means someone is filming.
Facilities should separate three practical situations. The first is suspected active recording: staff should ask whether capture is taking place and apply the facility’s procedure while protecting the consultation and surrounding patients. The second is a patient request to record: the clinician and facility can consider the purpose, the people present, the recording method and a suitable alternative. The third is provider use of recording or wearable data: this requires an approved workflow for consent, access, security and retention.
Incident handling deserves particular care. If an unauthorised recording may include another patient, a screenshot of a record or a private clinical discussion, staff should report it through the facility’s privacy and security process. The response can then assess the facts, contain any continuing exposure and determine whether escalation is required. Staff should know whom to contact before an incident occurs.
Procurement should apply the same discipline upstream. Before adopting a device or software platform, a provider should obtain a clear account of capture modes, default settings, data destinations, subcontractors, deletion controls and audit capability. Clinical leadership, information security and legal or compliance teams should review the proposed use together. A consumer device may be useful in ordinary life yet unsuitable for a particular clinical task unless its settings and data flows can be governed.
For regulators and investors, the revealing question is whether the operating model is credible. A company that cannot explain where identifiable information travels, how consent is scoped, or how a provider responds to a recording incident has an unresolved implementation risk, regardless of the appeal of its hardware.
Strategic assessment: innovation depends on control of the data pathway
Smart wearables can help patients bring useful observations into care and preserve information they might otherwise forget. Camera glasses can also make collection less conspicuous, while connected applications can move sensitive material beyond the consultation room. The central governance task is to make those movements visible and controllable.
For clinicians and facilities, the near-term priority is an intelligible recording policy paired with patient-friendly alternatives, a defined process for reviewing wearable measurements, and an incident route staff can use. For founders, it is a product design and contracting question: capture settings, processing locations and onward uses must be clear enough for a healthcare customer to assess against UAE requirements. For investors and senior executives, the evidence of maturity lies in tested workflows and documented data flows, rather than a general assurance that a product is “privacy compliant.”
The legal analysis should remain precise. Article 44 of the cybercrime law is a serious privacy provision with stated penalties, but its elements matter. Personal data transfer rules do not displace the healthcare-specific framework. A visible recording light does not confer consent. Treating each of those propositions accurately gives decision-makers a sounder basis for adopting technology that can serve patients without weakening trust in the consultation.
Healthcare strategy, regulation and clinical governance at Pnyx Hill
Pnyx Hill Healthcare Advisors supports healthcare operators and healthtech businesses across the UAE and GCC with regulatory strategy, clinical governance and operating model design. If your organisation is introducing wearable technology or deciding how patient-generated data should be used in care, speak with our team about the governance and operational decisions involved.
Sources and references
UAE Federal Decree-Law No. 34 of 2021 on Countering Rumors and Cybercrimes - Article 44 covers invasion of privacy, including recording conversations and capturing images in the circumstances set out in the law.
UAE Federal Law No. 2 of 2019 on the Use of Information and Communications Technology in Health Fields - Article 13 addresses the storage and processing of UAE health data outside the country.
UAE Ministry of Health and Prevention, Ministerial Resolution No. 51 of 2021 - Specifies cases in which health data may be stored or transferred outside the UAE. Include this alongside Article 13 to support the article’s point about exceptions.
UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data - Article 2 sets out the scope and exclusions, including personal health data governed by specific legislation. Articles 22 and 23 address cross-border transfers of personal data.
Dubai Health Authority, Guidelines for Patient Consent - Section 5.4 is the exact reference for separate, documented written consent when a patient’s images, videos or statements are used in social media advertising.
Dubai Health Authority, Policy for Health Information Sharing - Covers the sharing of protected health information by organisations within the policy’s scope.
