Skip to main content
Frequently asked questions

FAQ

A concise explanation of what MójDPS is, who it is for and which functional areas are available and which remain in development.
A care-home employee asks a question during a small staff information session.

MójDPS covers resident records, stay history, qualification, reservations, absences and selected historical information. The exact admission workflow can be reviewed during the system demo.

In practice, the team spends less time looking for basic information in several places or reconstructing the course of a case from memory.

Yes. MójDPS helps keep resident documents, consent records, attachments and signatures in order. This matters not only for staff convenience, but also for management, which can review available documents and notice items that require completion.

In a well-organised facility, a document should not live “somewhere in a binder” or in an old internal message. The system is meant to reduce exactly those situations.

Yes. Shift reporting and structured handover are already implemented parts of the system. This matters especially in facilities where tension does not come from a lack of work, but from the difficulty of passing information calmly between shifts.

Ordered reporting makes it easier to see what has already been done, which observations matter and which decisions still need to be taken. It shortens the distance between an event and a decision.

Yes. The family portal is already part of the implemented system. Its role is not just to show a few details outside the facility, but to organise communication so that families receive the right information without returning to the same questions through several channels.

For the facility, this means not only convenience, but also a clearer flow of information and less risk of misunderstandings caused by fragmented communication.

No. The strongest part today is the operational core: residents, stays, documents, care, reporting and the basic communication structure.

Documents and consent records already have lifecycle and retention support, while policy scope depends on rollout configuration. Further development includes visits, extending consistent retention rules to more data classes, broader integrations and further supervisory layers.

No. Local IT can continue to manage computers, networks, printers, operating systems and user support. MójDPS is a specialist application for care-home processes and can operate alongside existing IT support.

Yes. A facility can begin with a limited, agreed pilot to assess the system during real work before deciding on a full rollout. Terms and scope are agreed individually.

Yes. The conversation can cover standardisation, reporting and a possible pilot for an organisation responsible for one or more facilities. The exact multi-facility model and rollout terms must be confirmed for that organisation.

Yes. MójDPS is an existing product, and the rollout scope can be shaped around the real processes and needs of a facility. One organisation may prioritise resident and stay records; another may focus on documentation, reporting, family communication or inspection readiness.

The product is actively developed, so justified facility needs can be considered without promising arbitrary features on request.