Product and implementation guide
Confirm the administrative scope
Clinic Management is an ArcApps software application, not the patient-care department. People seeking physiotherapy should visit Frolsket Healthcare . Software requirements should identify the administrative tasks, staff roles and information involved before configuration. Confirm the capabilities included in your proposal; a general product page does not establish a certified clinical system or medical decision function.
Example: an appointment request
A person submits a preferred date through a website. Decide whether staff must review availability before confirming a booking. The acknowledgement should describe a request accurately and should not imply a guaranteed appointment. Identify how the administrative team receives the enquiry and how any integration is reconciled. The public website does not automatically write appointment requests into this application.
Handle information conservatively
Medical and identity information can be sensitive. Do not send patient records through an initial sales enquiry or use real clinical data in a public demonstration. Agree appropriate collection, access, retention and professional responsibilities with qualified owners. Administrative software should not be presented as a substitute for a clinician's assessment or judgment.
Test roles and corrections
Use synthetic examples to test an ordinary request, a changed appointment and a restricted action. Confirm which staff can view, amend or export information and how access is removed. Define a support route that does not require sending unnecessary patient details. The integration guide offers relevant questions about identifiers, failures and ownership when connecting approved systems.
Access, setup and support
Start with a confirmed subscription and implementation scope, then use the sign-in address supplied by the team. The public website does not provision accounts. Your organization should identify an administrator, approve each user's role, and confirm which locations and records belong in the setup. Use unique accounts and follow the approved recovery process rather than sharing passwords. Confirm the available controls in your configured environment before entering live information.
Validate before going live
Prepare synthetic examples covering an ordinary workflow, a correction and a restricted action. Reconcile imported records against the approved source and agree who resolves differences. Ask each intended role to complete its tasks, including on the devices they will actually use. Record issues with the expected outcome and the observed result. Do not use real customer or employee records in a public demonstration.
Daily operation and changes
Keep operational policies and responsibilities alongside the configured workflow. When a task fails, note the time, action and visible error without sending credentials or sensitive records. Contact the support route agreed in your service terms. Changes to modules, integrations, exports, retention or commercial scope require confirmation; they are not implied by this guide. For onboarding and troubleshooting specific to your deployment, request a walkthrough using your approved scenarios.
Open the product guide · Product FAQ · Implementation support