The model on screen is a clinic application. The patient sees the appointment, the active prescription and the tests. The practice works on the same file. The same build applies wherever a status is updated from a phone and must return to the register, including without a signal. For a site that is only read on a phone, the website page remains the right channel.
Application model · medicine
The appointment, the prescription and the result on the phone
The patient sees the consultation, the active prescription and the tests. The practice sees the same file, with the status updated.
We establish who signs in: the patient, the doctor or reception. We establish what is visible on the phone and what stays only in the practice file. Test results and the prescription do not remain on the device after the session closes.
The day's appointments come from the practice register. Confirmation, postponement and the message are written on the same appointment. When the network is absent, the status stays on the phone and syncs on return, with the history of the person who confirmed.
An appointment confirmed on the phone enters the register. A prescription issued at the practice appears in the application. Tests attach to the file, not to a separate message. In the evening nobody recopies the status into a sheet.
Appointment, active prescription and test result, on the same screen.
The file updates when the patient confirms or postpones.
The day's list and the consultation status, without a parallel register.
Yes, when both platforms are used by the people who run the process. If the team works on one kind of device, the application is built for that device.
Yes, when the data and the accounts are clear enough to become working documents. If the current site is only a presentation, we say so before treating it as the base of the application.