Starting from the design of the simplest appointment registration function in the Internet medical field, all complex function collections are composed of simple products.
Having mastered the core underlying logic, most future product iterations will have relatively stable ideas.
In the past, this work would also be done, and it was naturally produced, and there was no concept.
Asked some product experts in the industry and they said it's what product architects do, well, how to be a product architect.
Analysis and design country email list of appointment registration function
1. Routine general medical procedures
Registration is the general process for routine hospital visits and treatment, and this is the case for most routine outpatient clinics.
In the past, the process of going to the hospital to see a doctor basically started from the registration, and finally, the patient went to the hospital to go to the hospital for the process of picking up the number—checking in—waiting for a doctor—calling the number.
Finally, in the outpatient room of each department, the doctor conducts diagnosis and treatment.
Even if there is an inspection on the day, it is based on the order issued by the doctor's outpatient diagnosis.
Of course, emergency and first aid will be different, so I won't do too much description here.
Registration is the beginning of all behaviors of going to the hospital to see a doctor. Going to the hospital to see a doctor starts from the registration, and the patient can only seek medical treatment after registering at the hospital.
Internet medical treatment starts from registration, and then you can go to the hospital to pick up the number. After the outpatient service, the doctor will make a diagnosis, and then you will know what to do next.