Patient history · One patient · authorised context
Open the patient. Pick up where care left off.
Find the patient’s previous notes, images, tooth history, treatment, consent and balances together. Keep the record connected between visits without giving every team member the same access.
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected01Patient identity, contacts, preferences and emergency details
02Clinic links with per-clinic case-number support
03Clinical notes, attachments, gallery sharing and treatment history
04Privacy requests and a structured patient-data export workflow
Why this workflow matters
THE CLINIC MOMENT
One patient should not require five searches.
Patient 024’s medical alert is in a note, the crown image is in a phone gallery and the balance is in a spreadsheet. Every handoff begins with another search and another chance to miss context.
×When clinical history, contact details and balances live in separate files, every handoff begins with a search for context.
×The next owner and source record are unclear.
✓Find the patient’s previous notes, images, tooth history, treatment, consent and balances together. Keep the record connected between visits without giving every team member the same access.
✓Open the record you need without searching for the patient again.
HOW IT WORKS
Bring identity, care, files and money onto one patient spine.
Follow the task from its first entry to the next person who needs it.
- 01
Identify
Maintain contact, preferences, emergency details, clinic links and clinic-specific case context.
- 02
Connect
Reach notes, files, charting, treatment, consent and finance from the patient record.
- 03
Continue
Carry authorised context across visits and linked clinics instead of rebuilding the history.
ONE WORKFLOW · 4 CHECKPOINTS
Turn five searches into one patient spine.
Identity, care, files and money stay connected while clinic and role boundaries still apply.
The note, image, alert, plan and balance live apart.
Each handoff begins with another search and another chance to miss context.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedOne patient identity anchors the journey.
Clinic links and local case context sit around the shared patient record.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedAuthorised records become reachable together.
Open clinical notes, charting, treatment, documents and finance without rebuilding the patient story.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedThe next user opens the right source.
The record carries context forward without widening a user’s configured access.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedIdentity and access
Give the team the right context without flattening permissions
A patient record can include contact preferences, DND state, emergency contact, health identifiers, reference source, allergies and other configured master data.
Patients can be linked to multiple clinics while retaining clinic-specific case numbering. Staff access continues to follow their organisation, clinic and role permissions.
Longitudinal history
Keep visits, treatments and documents connected
Clinical notes, dental-chart findings, attachments, treatments, prescriptions, plans, consents and financial records can be reached from the patient context.
Clinical media may be selected for a generated gallery share, while access to public share routes is controlled through purpose-specific links.
Data requests
Support clinic-led privacy and export workflows
The product includes patient privacy-request records and a structured JSON export workflow. Clinics still need their own legal process for verifying a request, deciding what must be supplied and meeting applicable timelines.
Permissions and workflow boundaries
ROLES & PERMISSIONS
Connected context still respects clinic and role boundaries.
Patient context remains scoped by organisation, clinic assignment and module permissions. A linked multi-clinic patient does not give every user organisation-wide access.
WHERE IT STOPS
What your team still decides.
Accuracy depends on authorised clinic users maintaining the record. Export capability is not an ABDM integration or a legal-compliance determination.
Plan your trial
TRIAL PLAN
Test the handoff with two different roles.
Try these tasks with fictional patient details and the roles your team uses. Note any setup question or step that needs a different process.
- Create a patient linked to two clinics
- Add a note and attachment
- Review the patient with a restricted role
- Open treatment and finance from patient context
- Inspect the supported export workflow
QUESTIONS TO ASK
Can one patient be linked to more than one clinic?
Yes, with clinic-specific context and authorised access around the shared patient identity.
Is this an ABDM integration?
No ABDM integration is claimed. Any export description should be evaluated as an export workflow, not external-system connectivity.
YOUR CLINIC · YOUR EXCEPTION
Bring the handoff that keeps breaking.
Start free to test the workflow yourself, or book a guided demo when you want help mapping the exception.