Skip to content

The Story

Tiago edited this page Oct 15, 2023 · 2 revisions

This is a Minimum Viable Product of a software to manage a Psychology Clinic. There are many features that could be implemented towards making such product, as:

  • Appointments system with configurable notifications for both client and psychologist.
  • Data encryption of sensitive data, with only the responsible professional having access to such data.
  • Report generation
  • Payment system
  • And so on, and so forth

But, considering restrictions such as manpower and time, the scope of the software will be limited to two essential domain of features.

1 - The main Software Users: Psychologists

I am a Psychologist as well a software developer, so I'm capable of writing about this domain. The most important, and essential feature, of a simple software for healthcare professionals is the capacity to register each session's Therapy Progress Notes. They should be persistent, secure and be connected to a Therapist, a Client and a date + time.

Ideally, the Therapy Notes should be encrypted to prevent data breaches, as many of these documents contain sensitive sensitive data. But currently this feature is beyond me with my current resources.

Psychologists should be able to create and maintain data from Clients. But data deletion should be reserved for the following role of Software Users, the Administrators.

2 - The system's Administrators

They should be able to create, update and delete new Psychologists in the system. Their role towards Clients can be a little tricky to define. Maybe they should only be able to Delete User's data as if required by e-mail. But, again, thinking of such complexities can be a case of over-engineering.

So, for the sake of simplicity, System's Administrators will have, initially, complete control over all creating, retrieval, updating, and deleting of all data, and roles. The previous paragraph was necessary to make the point that this decision is one made in the context of limited resources, to facilitate the process of software development, but it is incorrect to build a System Admin role like this, in this kind of software. Any step beyond this should address this issue.

Clone this wiki locally