CLINIC ACCESS & PATIENT DATA
Patient information should be available to the people who need it for their work. Watson uses assigned roles, location scope and separate clinical permissions to control access within the clinic workflow.
The member and their assigned role
The business or location they can access
The areas and actions they are permitted to use
ACCESS IN THE CLINIC WORKFLOW
A job title alone should not decide what someone can see or change. Set the location assignment and permitted actions for the work that person performs.
Access is resolved from the user's current assignments. Group views limit operational records to the locations the person can access, and clinical requests check the relevant business scope.
Reading clinical records and editing diagnosis, prescription and lab sections are controlled separately. The saved clinical entry identifies its author and last update.
DIFFERENT VIEWS FOR DIFFERENT PURPOSES
Reception, the consultation room, pharmacy and group oversight use different information. Review what each workspace exposes as part of the clinic setup.
The configured patient-facing display communicates queue ticket and room information. It is separate from the clinical notes and staff workspace used to manage the visit.
Group operational views use selected record summaries and assigned locations. They do not automatically expose the full clinical chart across a group.
Authorised team members can take over a conversation and pause Watson in that thread. Clinical questions and decisions should follow the clinic's care process, with the right person handling the response.
REVIEW BEFORE ONBOARDING
Review the clinic's requirements with the processing terms and the actual setup, including the clinical records it will hold.
BEFORE YOUR DEMO
No. Reading clinical records and editing diagnosis, prescriptions or lab sections require the relevant permissions within the assigned business or location. Review each role during setup and when staff responsibilities change.
The HQ records view uses selected operational summaries. Clinical access is separate and remains subject to business or location scope and the relevant permissions.
The Privacy Policy explains personal-data handling, and the Data Processing Agreement sets out the published processing terms and sub-processor information. For this clinic offering, confirm the specific clinical-record data scope and operating details before onboarding.
No. The published DPA identifies engine and database hosting in AWS Kuala Lumpur and also lists connected providers that process data outside Malaysia. The clinic should review the services and transfers that apply to its configured channels and workflows.
Yes. Bring the clinic's required data types, retention needs, export formats and recovery expectations to the review. These need to be confirmed against the specific setup and processing terms rather than inferred from a general security statement.
Use illustrative examples or a representative sample with identifying patient details removed. Agree the data scope, authorised access and secure transfer process before sharing real clinic records.
SEE IT IN YOUR CLINIC
Bring your clinic's access, data-handling and recovery requirements. We will map them to the current workflow and the details that need to be agreed.
