When a Dubai operator commissions a telehealth product, the conversation almost always centres on the video call. How good is the video, how does the patient join, what does the waiting room look like. This is understandable, because the call is the part everyone sees, demonstrates, and judges the product on. It is also why so many telehealth builds disappoint in operation: the call is the thin, visible surface over a clinical workflow that is most of the actual build, and a product scoped around the call underbuilds everything the call sits on top of.
This piece is a perspective on what a compliant Dubai teleconsultation actually has to carry beneath the video. The argument is opinionated. We are not arguing that video quality does not matter, or that telehealth is unusually difficult. We are arguing that a teleconsultation is a clinical encounter that happens to be delivered remotely, carrying the same obligations as an in-person visit: verified identity and consent, a structured clinical record, proper e-prescribing, claim and exchange linkage, and continuity with the rest of care; that the video is the smallest of these layers; and that the common failure is building the visible surface well and the foundation thin. The product looks finished because the part you can see is finished, and fails in operation because the part you cannot see was treated as secondary.
The audience for this analysis is operators and product owners of UAE clinics and groups building or buying a teleconsultation capability who have seen the demo, been impressed by the call, and not yet pressure-tested what happens around it. The useful diagnostic question is not "how good is the video" but "does the remote consultation produce the same verified identity, consent, structured record, prescription provenance, claim, and exchange linkage as the equivalent physical visit, or only the call".
The Video Is the Top Layer
Below is a representation of a teleconsultation as a layered stack. The video call is the narrow layer at the top, the part that is visible. Beneath it the foundation widens: identity and consent, the structured clinical record, e-prescribing, claim and exchange linkage, and scheduling and follow-up. The point is not that the video is unimportant; it is that it is the smallest layer, and that the layers below it are where the clinical and regulatory weight actually sits. Tap any layer to see what it actually requires and what underbuilding it costs.
A teleconsultation as a stack: the call is the visible top, the workflow is the foundation
Tap any layer for what it requires and what underbuilding it costs
Why the Foundation Is Most of the Build
The reason the video is the small layer is that delivering a clinical encounter remotely does not remove any of the obligations of a clinical encounter; it only changes the channel. A structured teleconsultation pathway is expected to carry identity verification, consent appropriate to remote care, a clinical record to the same standard as a physical visit, prescribing through the proper electronic path, and the same recording and funding linkage as an in-person encounter. The call is the part that is different from an in-person visit. Almost everything else is the same as an in-person visit, which is precisely why almost everything else is the bulk of the build and the part a video-centred scope underweights.
The funding context in Dubai sharpens one of these layers in particular. Dubai's health expenditure was around AED 22.24 billion in 2023, with roughly 61 per cent privately financed. In a predominantly private market a consultation that is clinically sound but not tied to its claim and the health information exchange is unpaid, unrecorded work, and a teleconsultation built around the call commonly treats the claim and exchange linkage as something to sort out afterwards. The same structural point made about in-person claims applies here: the claim is decided in the encounter, and a remote encounter that does not carry it is leaking revenue while looking smooth.
This is why the failure is structural rather than a matter of poor execution. A team can build an excellent call and a thin foundation and the product will demonstrate beautifully, because demonstrations exercise the visible layer. It fails in operation, when the unverified identity, the free-text record, the bolted-on prescription, or the unlinked claim is relied on. The operator that is exposed here is not the one that built a bad video; it is the one that scoped the product as a video and discovered, in production, that the consultation was the part underneath.
The shift in one observation
A teleconsultation is not a video call with some clinical features attached. It is a clinical encounter with verified identity and consent, a structured record, proper prescribing, and claim and exchange linkage, that happens to be delivered over video. The video is the top of the stack. The product that is scoped as a call and not as a clinical workflow looks finished in the demo and reveals what was missing only once real consultations run through it.
Where the Video-Centred Build Breaks
The call-first model breaks in four predictable places once real consultations run through it.
Identity and consent left thin
When the scope is the call, identity verification and consent appropriate to remote care are easy to treat as a checkbox. Every consultation then sits on an unverified patient and an undocumented consent. Nothing about the call reveals this; it surfaces only when the record is relied on clinically or examined.
A record that is a note, not a record
A teleconsultation that produces a free-text note that the call happened, rather than a structured clinical record to the standard of a physical visit, has not produced a lighter encounter. It has produced an undocumented one. This is the layer most often underbuilt and the most expensive to discover late.
Prescribing bolted on after the call
When prescribing is handled as a message or an image after the consultation rather than through the proper electronic path within it, the clinical and regulatory provenance of the prescription breaks. The patient experience can look smooth while the prescription has no defensible origin.
Claim and continuity disconnected
A call disconnected from the claim, the exchange, and follow-up turns teleconsultation into an island: unpaid or unrecorded work with no continuity into the rest of care. The clinical value of remote consultation, continuity, is exactly what the disconnected build loses.
The Numbers
Two Ways to Scope a Teleconsultation
The difference between telehealth products that hold up in operation and those that disappoint is whether they were scoped as a call or as a clinical workflow.
| Layer | Scoped as a video call | Scoped as a clinical encounter |
|---|---|---|
| Identity and consent | A checkbox. Unverified patient, undocumented consent. | Verified identity and consent recorded to in-person standard. |
| Clinical record | A free-text note that the call happened. | A structured record to the standard of a physical visit. |
| Prescribing | A message or image sent after the call. | Proper e-prescribing within the consultation. |
| Claim and exchange | Sorted out afterwards, often leaking. | Tied to the encounter and linked to the exchange. |
| Continuity | A standalone island disconnected from care. | One pathway with scheduling, follow-up, and in-person care. |
A telehealth product that is scoped as a video call will demonstrate well and disappoint in operation, because demonstrations exercise the visible layer and operations exercise the foundation. A teleconsultation is a clinical encounter delivered over video; the call is the smallest part of building one, and the part that is left thin is always the part underneath.
What a Workflow-Scoped Teleconsultation Looks Like
The pattern in teleconsultation products that hold up is recognisable. The video is built well, because it is the patient-facing surface, but it is treated as the top of a stack rather than the product. Identity is verified and consent appropriate to remote care is recorded at the point it is given. The consultation produces a structured clinical record to the same standard as a physical visit. Prescribing happens within the consultation through the proper electronic path. The encounter is tied to its claim and linked to the health information exchange as a remote encounter. Booking, the consultation, follow-up, and continuity with in-person care are one pathway rather than a disconnected call. The product feels as good in operation as it does in the demo because the foundation was built to carry the weight the demo never puts on it.
This does not necessarily mean a single new platform replacing existing clinical systems. In many operations the teleconsultation pathway can be built around the clinical, prescribing, and exchange-linked systems already in place, with the video as one component rather than the centre. Replacement becomes the better option mainly where the existing systems cannot carry a remote encounter to in-person standard or cannot link it to prescribing, the claim, and the exchange. Which applies is specific to the systems in place, and is established in scoping before any build commitment.
How This Sits Alongside the Operator's Own Responsibilities
The configuration keeps a clear separation. The healthcare operator delivers the clinical care, employs and licenses the consulting clinicians, holds the relationship with the regulator, makes every clinical, consent, and prescribing determination, and is responsible for its own compliance with the applicable teleconsultation requirements. The software is the instrumentation: the call, the identity and consent capture, the structured record, the prescribing path, and the claim and exchange linkage.
This is the role BY BANKS is positioned for. We are an independent software engineering company based in the UAE. We design and build software and hand it over to the operator who runs it. We build to the published requirements for structured teleconsultation; we are not affiliated with, endorsed by, or acting on behalf of DHA or any authority, we do not deliver care or make clinical, consent, or prescribing determinations, and we are not a regulated healthcare entity. The operator owns the care, the determinations, and its own compliance; we build the system that lets a remote encounter carry the same weight as an in-person one. The accountable party leads and owns the obligations; we build to their direction.
Where This Analysis Is Useful
The conversations where this perspective is most useful tend to be at three moments: an operator evaluating a telehealth product that demonstrates well and wanting to know what it does beneath the call; a team whose existing teleconsultation works but produces thin records, bolted-on prescriptions, or unlinked claims; or a product owner scoping a build and deciding whether they are commissioning a video call or a remote clinical encounter. The honest answer is usually the same: the call is the top layer, the encounter is the foundation, and a product scoped as the former disappoints precisely where the latter would have held.
For broader related work, see our perspective on what exchange-mandated really means for UAE health records and our perspective on why claims in Dubai are decided at the point of care. The applied work sits across our telehealth platform development and patient portal development capabilities, within the broader healthcare software practice and our operational platforms work. Get in touch if a 45-minute conversation about a specific teleconsultation build would be useful.
Frequently Asked Questions
No. We are an independent software engineering company based in the UAE. We build software to the published requirements for structured teleconsultation, but we are not affiliated with, endorsed by, or acting on behalf of DHA or any authority, we do not deliver care, and we do not make clinical, consent, or prescribing determinations. References to teleconsultation requirements in our work are descriptive of publicly known frameworks. The operator remains responsible for its own compliance; we build the system to their direction.
No. A reliable, private, clinical-grade call is necessary, and it is the surface patients judge the product on. The argument is about proportion: the call is the smallest layer of a teleconsultation, and the common failure is building it well while leaving the foundation thin. Video quality matters; it just is not the part most likely to be underbuilt, because it is the part everyone can see.
A teleconsultation that works in the sense that calls connect can still be producing thin records, prescriptions with weak provenance, or unlinked claims, none of which is visible during the call. The question is not whether the call works but whether the encounter carries the same identity, consent, record, prescribing, and claim and exchange linkage as the equivalent in-person visit. Whether yours does is something only an assessment of the layers beneath the call can establish.
Often not. In many operations the teleconsultation pathway can be built around the clinical, prescribing, and exchange-linked systems already in place, with the video as one component rather than the centre. Replacement becomes the better option mainly where the existing systems cannot carry a remote encounter to in-person standard or cannot link it to prescribing, the claim, and the exchange. Which applies is specific to the systems in place and is established in scoping before any build commitment.
It is sequenced and does not require stopping the service. The usual starting point is the foundation layer with the largest current gap and the sharpest consequence, often the structured record and prescribing provenance, since those carry the clinical and regulatory weight. Identity and consent to in-person standard follow, then claim and exchange linkage, then continuity with scheduling and follow-up. The order is driven by where the current build is thinnest relative to what the encounter requires, which scoping establishes for the specific operation.
A Dubai teleconsultation is widely scoped as a video call and is in practice a clinical encounter delivered over video, carrying verified identity and consent, a structured record, proper e-prescribing, and claim and exchange linkage, with the call as its smallest layer. Products scoped around the call demonstrate well and disappoint in operation, because demonstrations exercise the surface and operations exercise the foundation. The builds that hold up are the ones that treated the video as the top of a stack and built the workflow beneath it to the standard a clinical encounter requires. The build is software work; the care, the clinical, consent, and prescribing determinations, and compliance with the applicable requirements remain entirely the operator's, and the system simply lets a remote encounter carry the same weight as an in-person one.
References to structured teleconsultation requirements and the UAE health information exchange are descriptive of publicly known frameworks. The funding figures cited (Dubai health expenditure of approximately AED 22.24 billion in 2023, around 61% privately financed) are drawn from public sources listed on our Sources and Data page; the stack and other patterns in this article are observational models rather than measured statistics, and represent no specific product, operator, or determination. BY BANKS is an independent software engineering company; we are not affiliated with, endorsed by, or acting on behalf of any authority, we do not deliver care or make clinical, consent, or prescribing determinations, and we are not a regulated healthcare entity. On any healthcare engagement, the operator owns the care, the clinical, consent, and prescribing determinations, and responsibility for its own compliance with the applicable teleconsultation requirements. This article is not regulatory, clinical, or legal advice; operators should obtain qualified advice for their specific obligations. Public sources used in this piece are listed on our Sources and Data page.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation