Clinical Documentation Is a Thinking Problem
- Barry Nguyen

- 2 days ago
- 3 min read
Most conversations about AI in healthcare start with the same question:
How do we reduce administrative burden?
Faster notes.
Less typing.
Better templates.
These are real problems, and they matter.
But after building CliniScribe and working with clinics across the full spectrum of allied health, we’ve come to a different conclusion.
The Problem Isn’t Just Documentation
CliniScribe is used across a wide range of clinical environments:
high-volume, back-to-back physio services within GP clinics
specialist musculoskeletal and sports physiotherapy practices
multidisciplinary allied health teams
Each setting operates under different constraints, priorities, and workflows.
There is no single “right” way to practise.
However, one consistent pattern has emerged.
Two clinicians can assess the same condition, in the same clinic, with similar patients — and produce fundamentally different outputs.
Not just in how they document.
But in:
assessment
treatment planning
clarity of communication
underlying reasoning
At first glance, this appears to be a documentation issue.
In reality, it reflects something deeper.
Documentation Is a Reflection of Thinking
Clinical notes are not the work itself.
They are a representation of how a clinician:
structures a consult
interprets information
makes decisions
communicates a plan
This leads to an important realisation:
Documentation is not simply an administrative task. It is a reflection of clinical thinking.
The First Principle We Had to Solve
When we began building CliniScribe, our goal was to improve efficiency.
But very quickly, we encountered a more fundamental challenge:
How do we accurately capture clinical reasoning — exactly as it is — without distortion?
Not enhanced.
Not simplified.
Not over-interpreted.
Just a faithful representation of what occurred during the consult.
Because if this layer is inaccurate, any downstream use — whether for documentation, communication, or analysis — becomes unreliable.
Where Most AI Solutions Focus
Many AI tools in healthcare focus on optimising the output:
generating notes faster
reducing manual input
improving formatting
These improvements are valuable.
However, they operate at the surface level.
They do not address the underlying variability in how clinical decisions are made and expressed.
The Contrarian Perspective
Through our work, we’ve arrived at a different view:
Clinical documentation is one of the most under-utilised representations of clinical thinking in healthcare.
Every consult contains:
decisions
reasoning
patterns
judgement
Yet today, this information is typically:
recorded once
stored
and rarely used again
This represents a significant missed opportunity.
Why This Problem Is Hard
Capturing clinical thinking is not simply a user interface challenge.
It is fundamentally an intelligence problem.
It requires:
contextual understanding
consistency across clinicians
domain-specific nuance
reliability across varied scenarios
And this is where we encountered a key limitation.
The Infrastructure Constraint
General-purpose AI models are designed for:
broad applicability
rapid deployment
general language tasks
They are not optimised for:
the nuances of allied health
consistency across edge cases
long-term control over performance
If the goal is to accurately represent clinical reasoning, this creates a gap.
Our Approach
To address this, we made a deliberate decision:
To take full control of the AI infrastructure that powers CliniScribe.
This includes:
hosting our own models
running on dedicated GPU infrastructure
managing the end-to-end processing pipeline
Why This Matters
Owning the infrastructure allows us to:
iterate more precisely on model behaviour
fine-tune for allied health-specific contexts
improve consistency and reliability
reduce distortion in how clinical reasoning is captured
This is not about adding more features.
It is about improving the core intelligence of the system.
What This Unlocks
With this foundation, we can move beyond simple transcription.
We can begin to:
more faithfully represent clinician intent
reduce variation in outputs
improve the quality of documentation indirectly by improving its source
In other words:
Enhance how clinical thinking is captured — not just how notes are written.
Looking Ahead
The future of AI in allied health is unlikely to be defined by incremental improvements in documentation speed.
Instead, it will be shaped by systems that:
support clearer thinking
improve consistency across clinicians
enable better decision-making over time
Final Thought
CliniScribe began with a focus on documentation.
What we discovered is that the real opportunity lies one layer deeper.
We are not simply building an AI scribe. We are building infrastructure for better clinical thinking.
If you’re interested in how this evolves, or would like to explore how CliniScribe fits into your clinic, feel free to get in touch.

Comments