How RXCopilot works
From the first word to continuing care.
A practical consultation journey showing how information can be captured, contextualised, developed into reviewable support and carried forward without transferring clinical authority.
The consultation journey
Eleven connected stages, each with a visible review boundary.
The sequence is illustrative; actual behaviour depends on authorised capability and workflow.
1. Consultation starts
The encounter purpose, participant, setting and authorised context are established.
2. RXCopilot listens
Clinically meaningful information may be captured from the authorised consultation source.
3. Information evolves
Patient report, professional observation, prior context and uncertainty remain distinguishable.
4. Questions develop
Potential clarification needs are organised by purpose for clinician review.
5. Examination is recorded
Findings and their observer, time and context are represented separately.
6. Reasoning is supported
Possible explanations, evidence, contradictions and missing information are made inspectable.
7. Investigations are connected
Tests can be related to clinical purpose, timing and expected follow-up.
8. Management is organised
Options, monitoring, referral and follow-up items remain proposals until professionally determined.
9. Documentation is drafted
Structured draft records preserve source and uncertainty.
10. Clinician reviews
The professional verifies, edits, accepts, rejects or defers material outputs.
11. Care continues
Approved documentation, actions and unresolved matters support follow-up across time.
Information boundaries
The system should show what is known—and how it is known.
Reported, observed, measured, historical, inferred and drafted material retain distinct meaning.
Source remains visible
Speaker, observer, system, record, measurement and knowledge source are not collapsed.
Uncertainty remains visible
Unknown, conflicting, incomplete and provisional information is not presented as established fact.
Professional review
Nothing material becomes approved merely because it was generated.
The review loop preserves authority and correction.
Inspect
See the source, reasoning context and status.
Edit
Correct wording, structure or meaning.
Accept
Approve material for the authorised workflow.
Reject
Prevent unsuitable material from continuing.
Defer
Leave an unresolved item visible for later review.
Continuing care
The consultation ends; the clinical journey does not.
Approved information can support communication, monitoring and follow-up while historical currency remains explicit.
Documentation
Clinician-reviewed records communicate what happened.
Actions
Decisions, responsibilities and timing remain explicit.
Monitoring
Expected change and review conditions can remain connected.
Follow-up
Unresolved matters and planned next steps can be carried forward.
Correction
Later information can update or supersede earlier understanding traceably.
Controls throughout
Safety and governance are part of every stage.
Controls do not sit only at the end of the workflow.
Purpose
Why the information or action is in scope.
Provenance
Where it came from and when.
Uncertainty
What remains unknown or disputed.
Authority
Who may review, decide and approve.
Status
What capability, version and release boundary applies.
Escalation
What requires professional attention or controlled restriction.
Questions and boundaries
Frequently asked questions
Does RXCopilot act without clinician review?
No. The design keeps material outputs subject to professional inspection and acceptance before approved use.
Does listening mean unrestricted recording?
No. Capture requires an authorised purpose, appropriate consent and privacy controls for the applicable setting.
Are suggested questions or actions instructions?
No. They remain reviewable support within the relevant capability boundary; the professional determines appropriate care.
What happens after the consultation?
Clinician-approved records, actions and unresolved matters can support communication, monitoring and follow-up.
Does the workflow prove current availability?
No. It is a design model. The capability-status page is the source for approved public availability.
This journey is an explanatory model, not a promise of current workflow coverage or performance. Professional Judgement and local governance remain required.
See the consultation model in context.
Explore a controlled fictional illustration or discuss your organisation's workflow and governance requirements.