Prepare the visit summary
Gather the patient's stated concern, history, and relevant records into a reviewable summary.
General practice / records, letters, and follow-up
General practice runs on records, letters, and follow-up, with clinical judgment in every decision.
We deploy private workflows that prepare patient intake summaries, referral letters, follow-up lists, and review packs from approved practice records. Clinicians own every clinical decision and patient communication.
Intake summariesReferral lettersFollow-up listsReview packs
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where general practice time goes
The consultation is short. The surrounding work is not.
Every patient visit creates the same surrounding work: history, letters, referrals, and follow-up that all need a clinician's review.
Draft the referral letter
Prepare a referral draft from approved notes and patient records for the clinician to complete.
Keep the list current
Organize follow-up notes, open results, and next steps into a review pack for the team.
The clinical boundary
The system prepares the file. The clinician makes the call.
No diagnosis or triage
The workflow drafts administrative and record material. Clinical decisions, triage, and patient care stay with clinicians.
Patient records stay scoped
Permissions and confidentiality are agreed before patient material enters the workflow.
Every output is a draft
Summaries, letters, and follow-ups are reviewed, corrected, and signed by the responsible clinician.
A first general practice workflow
Start with the document the team rebuilds.
Choose the artifact
Pick intake summaries, referral letters, follow-up lists, or review packs.
Scope the approved sources
Define the records, templates, and letters the workflow may use and who can access them.
Test with real patients
Run the workflow against recent visits and check the draft, citations, and boundaries.
Hand over the review route
Document the source map, permissions, and the clinician responsible for each output.
General practice gets more time for patients when the letters and lists are ready for review, not built from scratch.
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 make clinical decisions?
No. It prepares records, letters, and lists. Diagnosis, triage, and patient care stay with clinicians.
Can it send patient letters automatically?
No. It drafts the material. Review, signing, and patient communication stay with the clinician.
How is this different from the clinics page?
That page covers clinics and HMOs broadly. This page is general practice specific: intake, letters, and follow-up.
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 document
Which general practice document takes the most time?
Tell us the artifact, the approved records, and the review clinician. We will scope the first workflow around the practice's own workload.