Helpers HMS Medical Workflow
This guide explains the typical patient journey through Helpers HMS.
The objective is to help users understand the business flow, not only individual menus.
Implementation note: The final published workflow must match the deployed Helpers HMS modules and configuration.
Workflow overview
Patient Registration
↓
Appointment
↓
Consultation
↓
Diagnosis / Clinical Notes
↓
Prescription / Treatment / Procedure
↓
Diagnostics, if enabled
↓
Billing / Invoicing
↓
Follow-up
Not every deployment uses every step.
1. Patient registration
The workflow starts with the patient record.
Reception or another authorized user searches for the patient first.
If no existing record is found, a new patient is created.
Recommended process:
Search patient
→ Open existing patient
or
Search patient
→ No match
→ Create new patient
Avoid duplicate patient records.
2. Appointment creation
An appointment links the patient to a planned healthcare visit.
Typical appointment data includes:
- Patient
- Physician
- Department or specialty
- Date and time
- Visit purpose
- Notes
TODO: Document the exact appointment form used in the current Helpers HMS demo.
3. Appointment management
Appointments may pass through different states during their lifecycle.
The implementation agent should verify:
- Appointment state field
- Available buttons
- Allowed state transitions
- Which role can perform each transition
- Whether cancellation or rescheduling is supported
- Whether appointment states affect billing or clinical records
Do not publish guessed states.
4. Consultation
During consultation, the doctor or authorized healthcare professional may:
- Review previous history
- Review previous appointments
- Record current complaints
- Record clinical notes
- Add diagnosis information
- Add vital or examination information where enabled
- Create prescriptions
- Add treatments or procedures
- Request diagnostic services
5. Medical history
The patient's history may include:
- Appointments
- Consultations
- Prescriptions
- Treatments
- Procedures
- Diagnostic requests or results
- Invoices
- Other installed healthcare records
TODO: Audit the patient form smart buttons and tabs in the deployed version and document the real ones.
6. Prescription workflow
The implementation agent should verify:
- Where prescriptions are created
- Required fields
- Prescription states
- Medication source
- Pharmacy integration
- Printing/report actions
Suggested conceptual flow:
Consultation
→ Create Prescription
→ Add Medicines
→ Dosage / Frequency / Duration
→ Confirm
→ Print or Process
Publish only after verification.
7. Treatment and procedures
The final documentation should answer:
- What is a treatment?
- What is a procedure?
- How are they created?
- Who can create them?
- Are they billable?
- Where are they shown on the patient record?
- Which states do they use?
8. Laboratory workflow
Show this section only when the laboratory module is installed and enabled.
Possible flow:
Consultation
→ Lab Request
→ Sample / Processing
→ Result
→ Doctor Review
Verify the real models, states, security groups, patient links, and billing integration.
9. Radiology workflow
Show this section only when radiology functionality is installed.
Possible flow:
Consultation
→ Imaging Request
→ Examination
→ Result / Report
→ Doctor Review
10. Pharmacy workflow
Show this section only if pharmacy functionality is enabled.
Document the difference between:
- Prescription creation
- Medication dispensing
- Stock movement
- Sales/invoicing
- Pharmacy user permissions
11. Hospitalization workflow
If inpatient functionality is enabled, cover:
- Admission
- Ward / Room / Bed
- Responsible physician
- Nursing activity
- Treatments
- Medication
- Discharge
- Billing
12. Billing and invoicing
The exact workflow must be verified.
The implementation agent should document:
- Which HMS records generate invoices
- Who can create invoices
- Whether invoices are created manually or automatically
- Invoice state
- Payment workflow
- Products/services used for billing
- Whether insurance workflows are installed
Conceptual flow:
Healthcare Service
→ Billable Item
→ Invoice
→ Payment
13. Follow-up visits
Recommended process:
Open Patient
→ Review History
→ Create Follow-up Appointment
→ Perform New Consultation
14. Role-based workflow
Conceptual responsibilities:
Reception
- Search patients
- Register patients
- Create appointments
- Update administrative information
Physician
- Review assigned patients
- Open appointments
- Record clinical information
- Create prescriptions
- Record diagnoses/treatments
Billing user
- Review billable services
- Create or process invoices
- Record payments where allowed
Administrator
- Manage users
- Configure access
- Maintain system configuration
The final documentation must map these to the real Helpers HMS access groups.
15. Suggested end-to-end demo scenario
Patient: Demo Patient
Visit: General Consultation
1. Register patient
2. Create appointment
3. Assign physician
4. Start consultation
5. Add clinical note
6. Add diagnosis
7. Create prescription
8. Complete appointment
9. Review patient history
10. Review billing action if enabled
16. Quick Demo integration
Suggested CTA:
Try this workflow in Quick Demo
Deep links should be implemented only after the demo routing and authentication flow can preserve them safely.
Next
Continue to: