Gather the patient context
Extract the reason for referral, relevant history, and current notes from approved records.
Clinical workflow / referral letters
A referral letter should carry the relevant facts, not start from a blank page.
We deploy private workflows that draft referral letters from approved patient records and practitioner notes, with a review step for the clinician who signs it.
Patient factsReferral draftOpen questionsClinician review
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where referral letters lose time
The facts exist. The letter is rebuilt every time.
Each referral needs the same assembly: patient context, reason, relevant history, and the next step the receiving clinician should know.
Write the letter skeleton
Prepare the referral draft with patient facts, clinical context, and the requested next step.
The clinician completes it
Return the draft and open questions for the clinician to correct, sign, and send.
The clinical boundary
The system drafts the letter. The clinician owns the referral.
No clinical recommendation
The workflow drafts from existing notes. The reason for referral and clinical content stay with the clinician.
Use approved records
Patient facts and clinical context remain connected to the letter that uses them.
No automatic sending
The clinician reviews, corrects, signs, and sends the letter through the practice's normal route.
A first referral letter workflow
Build the letter the clinician already writes.
Choose the letter type
Pick the specialty, clinic, or recurring referral format the practice sends most.
Define the required sections
List the patient facts, history, reason, and next steps the receiving clinician needs.
Test with real referrals
Compare the draft with recent letters and fix gaps, wording, or access issues.
Hand over the sign-off
Deliver the draft to the clinician and document the sending route.
A referral letter is better when the relevant facts are assembled and the clinical reason is clearly the clinician's.
Why trust Pristine3D?
We build and operate production software.
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
We already run live products
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
We start with the actual workflow
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
The boundary stays visible
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Pricing / fixed scope
Know the starting numbers before you ask.
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One Workflow
Starting from$3,500 / ₦2.5m
2 to 3 weeksOne workflow for a small team, with training and handover.
See the one-workflow packageFirm-wide
Starting from$7,500 / ₦8m
4 to 6 weeksMultiple sources, roles, integrations, and admin handover.
See the deploymentAnnual support
Starting from$3,000 / ₦1.5m
per yearStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Straight answers
Common questions.
Can it decide what to write clinically?
No. It drafts from approved notes. The clinician writes, corrects, and owns the clinical content.
Can it send the letter automatically?
No. Review, signing, and sending stay with the clinician and the practice's normal process.
How is this different from clinical notes?
That page prepares the visit record. This page prepares the referral letter with a different output and review route.
Own your knowledge base
The model is not the product. The knowledge base is.
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
Your corpus, your index
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Models are swappable parts
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
The knowledge base is the alpha
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Related setups.
Start with the letter type
Which referral letter takes the most time?
Tell us the letter format, the approved records, and the signing clinician. We will scope a workflow around the practice's own referrals.