A patient management system is the client file: who they are, what they consented to, what has been done and what was written about it. In a therapy practice the word patient often means client and the product is the same. This page is what belongs in it, what does not, and how to judge one when every vendor's screenshot looks alike. On the worked example the file covers 2,794 sessions a year across three clinicians, each with a note the practice must be able to produce.
What a patient management system should hold
Identity and contact details, the intake form as submitted, consent with its date and version, the sessions with their status, the notes with their history, and the documents issued. That is the file. Everything else is either the diary or the accounts, and mixing them in is what makes a record hard to produce later.
What it should not hold
Card numbers, more health history than the practice needs, and free-text fields where anybody can type anything. Data minimisation is a duty rather than a preference: on the worked example a 34-field intake form is already long, and every extra field is one more thing to justify holding.
How to judge one in ten minutes
Ask for one real client's file to be produced from a standing start, then ask what happens when a note is amended, then ask what the export contains. Three questions and ten minutes separate patient manager software from a nicely designed diary faster than any feature list.
Questions people ask about patient management software
Is patient management the same as practice management?
The patient file is one part of practice management. A practice management product includes the diary and the money as well.
Can clients see their own record?
They have a right to a copy. Whether they get a portal is a product choice; the right of access does not depend on one.
Who should see a whole caseload?
The clinician who holds it and whoever is clinically responsible. Everyone else needs a reason, and the system should be able to express that.