A consultation begins before the call and continues after it.
Appointments, patient context and clinical notes belong to the same encounter. The software should preserve that connection.
Thalenor developed a custom virtual clinic platform bringing appointment scheduling, integrated video consultations, a unified patient timeline and AI-assisted documentation into one application.
Clinicians can prepare for an encounter, conduct the visit and complete its documentation within a connected workflow. Patients access appointments through a dedicated portal suited to their part in the consultation.
The central AI capability prepares a draft clinical note from a consultation transcript. The treating clinician reviews, edits and approves that draft before it proceeds to the saved patient record.
- Solution
- Custom virtual clinic web application
- Primary users
- Clinicians, patients and clinic staff
- Consultation delivery
- Integrated video visits
- Scheduling
- Central appointment management
- Patient context
- Unified consultation timeline
- AI capability
- Transcript-based clinical note drafting
- Documentation control
- Mandatory clinician review and approval
- Services
- Custom software development · AI engineering · Healthcare workflow automation · Web application development · UI/UX design
The work between systems becomes work for the clinician.
A schedule identifies the next appointment. A video tool hosts the conversation. Previous notes sit elsewhere, and the clinician may need another application to document the encounter.
The difficulty lies in the transitions. Patient information must be located, the consultation context re-established and the resulting note correctly associated with its encounter. Completing documentation later can also require the clinician to reconstruct the conversation.
Five requirements shaped the platform:
A connected encounter
Keep patient, clinician, appointment, consultation and documentation associated throughout the workflow.
Relevant history within reach
Make earlier encounters and their notes accessible through the patient timeline.
Less repetitive note composition
Use the available transcript to prepare a draft for the clinician to review.
An explicit approval boundary
Distinguish generated working text from the note authorised for saving.
A clear patient experience
Give patients appointment information and consultation access without internal documentation controls.
Keep the context connected.
Keep the clinician in control.
Research context: documentation burden
A 2025 quality-improvement study in JAMA Network Open examined ambient AI documentation among 263 clinicians across six US health systems. Preintervention and 30-day follow-up surveys found improvements in reported documentation burden and clinician experience.
Those findings concern that study and its particular system. They are background to the problem, rather than measured results for this virtual clinic platform.
Move from the appointment into the right patient encounter.
The appointment establishes who is meeting, when the encounter takes place and which patient record provides its context. Scheduling is therefore the beginning of the consultation workflow.
Clinicians can start with the clinic schedule and open the relevant consultation. The video visit remains associated with that appointment, while patient history and documentation belong to the same wider encounter.
Video is one part of the clinic workflow.
The integrated video consultation supports the clinician-patient conversation. Preparation comes before it, and note completion follows it. Connecting those activities reduces the need to move between independent scheduling, calling and documentation tools.
The patient portal presents appointment information and consultation access through a dedicated interface. The clinician workspace provides the additional context needed to prepare for and document the visit.
Every encounter adds context to the next one.
Previous consultations are more useful when their notes remain attached to the encounters they describe.
The unified patient timeline organises consultation history into one view. A clinician preparing for a follow-up can revisit an earlier encounter and examine its associated documentation.
This gives the current appointment a place within the patient's broader history. Once its note has been reviewed, approved and saved, that documentation is connected to the consultation for subsequent reference.
The timeline supports continuity through accessible records. It does not turn every historical statement into a finding from the current visit; the encounter and its documentation retain their own context.
Turn the transcript into a draft the clinician can inspect.
The transcript is source material. The generated note is a proposal. The approved version is the clinical record.
A consultation conversation can contain repetition, incomplete statements, corrections and information discussed out of sequence. Preparing documentation involves organising that material while preserving its meaning.
Once a transcript is available, the AI workflow uses it to prepare a draft note associated with the consultation. The clinician receives text to examine and refine, reducing the amount they need to compose from the beginning.
The workspace uses deterministic, source-linked local drafting without an external AI or automatic transcription integration.
Consultation transcript
The available conversation providing source material for documentation
Source informationAI-generated draft
A proposed note that organises the transcript for clinician review
Unapproved working textApproved note
The version the clinician has reviewed, corrected and authorised
Ready for the saved recordPreserve what the source actually supports.
The draft should reflect the encounter without filling gaps with invented information. An uncertain statement should remain uncertain. A possibility discussed during the consultation should not become a confirmed finding merely because it appears in a generated summary.
These are quality requirements for documentation assistance. AI does not independently verify clinical facts or establish medical conclusions; the treating clinician assesses the proposed note.
A generated draft does not authorise its own saving.
The platform requires clinical review before an AI-prepared note proceeds to the saved record. The clinician can examine the draft, correct it and decide whether it accurately represents the encounter.
Check the content
Examine whether the note preserves the relevant information discussed and established during the consultation.
Correct omissions or errors
Revise inaccurate wording and restore relevant details missing from the proposed documentation.
Preserve clinical certainty
Keep a discussed possibility distinct from a conclusion the clinician actually reached.
Approve the final version
Authorise the reviewed text before it becomes part of the saved consultation record.
The review is a substantive part of documentation. It gives the treating professional the opportunity to change the note before approval, rather than treating generated text as an already completed record.
AI prepares the draft.
The clinician approves the record.
Clinical decisions remain with the qualified professional. Documentation assistance does not independently diagnose conditions, authorise prescriptions or determine the patient's care plan.
Give patients a clear path to their virtual appointment.
Patients need to understand their appointment and access the consultation. The portal provides a dedicated experience connected to the clinic's scheduling and video capabilities.
Its information architecture differs from the clinician workspace. Patients are not asked to navigate internal documentation tools, and an AI draft is not presented as final clinical information before the appropriate review.
Both experiences belong to the same encounter. Each presents the information and actions relevant to the person using it.
One encounter, from the schedule to the approved note.
Explore how the appointment, relevant history, consultation and documentation stages connect. Each stage includes a relevant application screen; enlarge it to inspect the interface details.
Establish the appointment and encounter context.
The scheduled appointment connects the patient, clinician and consultation. Patients access their appointment information through the portal, while clinicians begin from the clinic schedule.
- Shared context
- Patient, clinician and appointment
- Clinician experience
- Central appointment schedule
- Patient experience
- Dedicated portal and consultation access
Scheduling establishes the encounter that later documentation must belong to.
Each stage refers to the same patient and encounter. The clinician can follow the documentation from its source through review to the approved record without recreating that association in another tool.
Connect responsibilities without collapsing their boundaries.
The engineering challenge is more than producing a conversation summary. Scheduling, consultation delivery, patient context, draft preparation and approval must work together while keeping their responsibilities clear.
Encounter context
The appointment, patient, clinician, video visit and relevant historical records
Scheduling & consultationDocumentation assistance
The available transcript and the proposed note associated with its encounter
Source & draftClinical authorisation
Clinician corrections, approval and the documentation retained in the patient history
Review & saved recordKeep documentation associated with the correct encounter
The appointment connects patient and clinician. The consultation transcript and its draft note retain that context, and the approved version is saved to the relevant encounter. The workflow should not depend on manually matching an unrelated transcript to a patient later.
Draft preparation and final saving are separate operations
Producing a draft is the documentation-assistance task. Clinical review determines whether the proposed text is accurate, and approval authorises the version that proceeds to the saved record. Generation does not bypass that boundary.
Build around the clinic's actual workflow
The architecture connects established capabilities without requiring a particular AI provider, transcription service or application framework to explain its value. Each implementation choice needs to support the encounter context and review process.
This approach to custom software development places AI-powered workflow automation inside the work clinicians already need to complete.
Approval protects the record's integrity. Data handling needs its own controls.
Patient histories, consultation transcripts and clinical notes contain sensitive information. Their collection, processing, access and retention need to be considered across the actual clinic deployment.
The US HHS telehealth privacy and security guidance identifies considerations including authentication, patient consent, protected transmission and the handling of consultation recordings. Applicable obligations depend on the clinic's jurisdiction and operating arrangements.
Source and consent
Establish how consultation content is obtained and what patients are told about recording, transcription and processing.
Access and role boundaries
Limit sensitive information and internal documentation functions to appropriately authorised people.
Processing and retention
Understand which systems handle transcripts and notes, including external providers and retention arrangements.
Clinical accountability
Maintain a clear distinction between assistance with note preparation and the clinician's responsibility for the approved record.
Review before saving is a documentation control. It does not by itself establish regulatory compliance, a security certification or the adequacy of the deployment's infrastructure and operating policies.
Less fragmented administration around the patient encounter.
The platform brings related activities together and gives AI assistance a defined role within documentation preparation.
Connected consultation management
Scheduling and video visits share the same clinic workflow and patient encounter context.
Accessible historical context
The timeline gives clinicians a consistent route to previous consultations and notes.
A starting point for documentation
Transcript-based drafts reduce the amount of text clinicians need to compose from the beginning.
Clear documentation states
Source material, generated drafts and approved notes have distinct meanings.
A dedicated patient experience
The portal focuses on appointments and consultation access without internal documentation complexity.
Clinical control over the final note
Review, corrections and approval remain part of the workflow before saving.
These are workflow benefits rather than measured claims of time saved, reduced burnout or improved patient outcomes for this platform.
Support the consultation.
Preserve clinical responsibility.
For Thalenor, the project shows how healthcare software solutions can connect encounters, context and documentation while keeping final clinical records under human control.
A few practical questions.
What is an AI-assisted virtual clinic platform?
It connects appointment scheduling, video consultations and patient records with AI-supported documentation. In this platform, consultation transcripts support draft note preparation, with clinician review and approval required before the note is saved.
How does AI-assisted clinical documentation work?
A consultation transcript provides source material for a proposed clinical note. The clinician reviews and edits the draft, then approves the final documentation before it proceeds to the saved patient record.
Can AI automatically write medical consultation notes?
AI can prepare a draft from consultation information, but generated text can contain errors, omissions or unsupported statements. This platform requires clinician review and approval; a generated draft is not treated as an independently verified clinical record.
What is the benefit of integrating video consultations with patient records?
Clinicians can access the appointment and relevant history within the same workflow used for the consultation. The resulting documentation stays associated with the correct encounter, reducing the need to transfer context between separate tools.
Why is human approval important in healthcare AI?
It gives the treating clinician the opportunity to check and correct proposed documentation before it becomes part of the record. The AI supports preparation, while clinical accuracy and medical decisions remain the responsibility of the qualified professional.
How does custom virtual clinic software differ from a video-calling application?
It connects remote communication to healthcare-specific responsibilities: scheduling, patient context, consultation history, documentation and clinician approval. The patient portal and clinician workspace serve different roles within the same encounter workflow.