# CliniqueRx — Pharmacy Owner or Manager Guide ## Document control | Field | Value | | --- | --- | | Document version | Controlled Global-mode document 1.0 | | Date | August 20, 2026 | | Local workflow revision | October 16, 2026: network admission section reconciled with the current implementation. Source-only correction; PDF and publication not updated in this revision. | | Targeted security revision | October 27, 2026 - initial MFA, browser remembrance and session duration; PDF export not updated | | Team workflow reconciliation | October 28, 2026 - individual email, activation and MFA reconciled with Direct34; PDF export not updated | | Audience | Authorized owner or manager of a pharmacy linked to a contracted organization | | Software target | Global production mode; verify the deployed release identity before use | | Data schema | Verify the migration reported by the deployed release before use | | Screenshots | Use synthetic accounts only | | Real-world use | **Governed by the active Global release binding and workspace access controls** | > This guide describes Global-mode functions. It is not, by itself, an authorization to use CliniqueRx with real patients, a certification, regulatory approval, or legal advice. Commercial terms are governed by the contract between the organization and CliniqueRx; the application does not sell individual pharmacist seats to pharmacies. ## 1. The owner’s role in CliniqueRx The owner or manager configures the pharmacy workspace. This role manages named team access, available services, appointment windows, and the complaints the pharmacy chooses to offer. It can also review operational statistics. This role does not automatically grant permissions reserved for the organization administrator or platform manager. A pharmacy-manager account cannot alter the organization contract, invite another owner on behalf of the chain, modify clinical rules, or access APEx functions. The owner account is administrative. It does not show complaint search, care cases, clinical Travel health, the Inbox, or the shared Agenda. If the owner also practises as a pharmacist, they must create a separate named account under **Team**. That clinical account remains linked to the same pharmacy and requires no seat purchase. ## 2. Before the first sign-in Prepare the following information: - the pharmacy’s legal name and contact information; - the manager’s identity and professional email address; - the single-use, email-bound invitation sent by the organization’s authorized administrator; - the services the pharmacy expects to offer; - opening hours and appointment windows; - the team member list, with one individual username per person. Every user must have a named account. Never share the manager account, a password, or a verification code sent by email. ## 3. Create the pharmacy workspace and secure the account After creation, sign-in continues with the password just chosen and presents any remaining verification, including the owner's email code. If it cannot complete, ordinary sign-in remains available. The dashboard shows **Set up your pharmacy**: establishment, first pharmacist and licence, network and workstation, clinical pathways, appointment services and first team use. The states reflect saved data; **Continue** opens the relevant section directly. Completed steps remain available for review. These indicators do not replace clinical authorizations. 1. Open the named invitation link received from the organization administrator and enter the requested information for the one physical pharmacy it identifies. 2. Create the primary manager account. Only one person should use this account. 3. Confirm the email address if prompted. 4. Replace any temporary password at first sign-in. 5. At sign-in, enter the single-use verification code sent to the manager’s confirmed professional email address after the password when prompted. This role uses email verification; if access is lost, follow only the recovery process provided by CliniqueRx. 6. Before performing any administration, confirm that the pharmacy name in the header identifies the correct workspace. Named professional accounts, pharmacy owners or managers, organization managers and patients require initial MFA using a code sent to their confirmed email address. Platform governance accounts use an authenticator app. A personal shift PIN complements the professional’s sign-in on a shared workstation. After successful verification, the remember option recognizes your account on this browser for up to 90 days. It does not automatically extend to other browsers, accounts or workstations sharing the same IP address. Revocation, a security change or loss of the proof may require verification again. Sessions remain limited to a maximum of 24 hours and may end earlier because of inactivity or revocation. Use a pharmacy-managed workstation with automatic locking, encryption, and current security software. Sign out when leaving the workstation. The administrative owner account may be used outside the pharmacy’s approved network, including from home. Remote administration grants no clinical permission: it cannot open a patient case, the clinical Inbox, or the shared Agenda. If the owner also practises as a pharmacist, their separate team account remains limited to the pharmacy’s approved network like every other professional account. ### Authorize the pharmacy network and use team workstations From the pharmacy network being authorized, sign in with the pharmacy owner or manager account and complete its required authentication. Confirm the exact public IPv4 address displayed by CliniqueRx. Repeat from each additional pharmacy network that the team is authorized to use. Adding an address preserves existing network authorizations; remove authorizations that are no longer needed. Team members then use their named accounts. After the team password is verified, CliniqueRx creates or validates a technical browser session bound to the workspace and a currently authorized pharmacy network. The owner approves the network, not each browser individually. A browser session credential does not permit access outside the currently authorized network. Review the authorized network and workstation inventory at least monthly. Keep the existing revocation procedure for lost, retired or suspicious devices and sessions. Do not treat an automatic technical browser session as verification of the device's local security configuration. Use a pharmacy-managed workstation with automatic locking, encryption and current security software. Never use the public IP address as the sole proof that a device belongs to the internal pharmacy network. Maintain the approved local controls, including a staff-only network, managed browser profiles, disk encryption, patching and automatic locking. Remote owner administration grants no clinical permission; the separate professional account remains subject to the pharmacy network boundary. ## 4. Organization access and contract state Pharmacy access depends on an exact link to an active organization and a contract that is effective and unexpired. The owner then creates as many named professional accounts as the real team requires; no seat quota grants or removes access. ### Suspension or lack of access If the organization contract is future, suspended, expired, or the pharmacy link is revoked, the application blocks the clinical workspace and shows **Enterprise access required**. Do not attempt to bypass this control. Contact the organization’s named administrator or the platform and use the pharmacy’s normal approved process in the meantime. The owner’s separate regulatory-retention workspace remains subject to recent authentication with the password and single-use email code. ## 5. Separate administration from clinical care The owner account is used only to administer the pharmacy. It must not be used to search for a complaint, open a patient case, process a submitted form, sign a prescription, or manage a clinical appointment. If the owner also provides care: 1. create a separate named account for them under **Team**; 2. complete the professional name and licence number in that team profile; no handwritten-signature image is collected; 3. validate the licence as the owner under the approved procedure and the regulator for the province where the physical pharmacy is located; 4. always use the account that matches the task: owner for administration and pharmacist for care. The two accounts remain distinct even when they belong to the same person. Do not share passwords, the manager’s emailed verification codes, shift PINs, or sessions between them. ## 6. Create and manage the team ### Add a pharmacist or nurse 1. Open **Team and professional licences**, then **Add a team member**, and select the pharmacist or nurse role. 2. Enter the person’s identity and an email address the member can access. This address must not already belong to another CliniqueRx account. The member will use their email to sign in; the account remains linked to this pharmacy. 3. Complete the professional profile. Clinical signing uses the named professional, licence, exact content, and cryptographic shift-PIN proof; it does not use an uploaded handwritten-signature image. 4. Create the named account. Licence verification opens automatically in the member’s profile on the same page. 5. Consult the official register provided for the member’s role, record the evidence reference and next review date, then confirm the attestation. For an existing member, click **Verify professional licence** in their profile. The status updates after saving. Pharmacy technicians do not have this step. 6. Give the **activation code** to the named member through a secure channel. The code is single-use and expires after 48 hours. If needed, generate a new code in the member's profile: it replaces the previous one. You can also revoke an unused code. 7. From the pharmacy's authorized network, the member opens **Activate my team account**, enters their email and code, chooses their own password, and confirms their email. Sign-in then requires the initial MFA described above, which can be remembered in this browser for up to 90 days. On a shared workstation, the member also chooses a personal shift PIN. Existing accounts with a temporary password can still replace it at sign-in. 8. Confirm access with synthetic data before any planned activity. ### Validate additional provincial prescribing credentials After validating the licence, continue in the same team profile under **Additional provincial prescribing credentials** when that section is present. CliniqueRx displays the authorization or training evidence applicable to the establishment under server catalogue `2026-08-02.2`. For each requirement, open the official source, record an evidence reference containing no patient information, select a next-review date within 365 days, and confirm the owner attestation. This attestation records a verification; it does not itself grant a legal right to prescribe. In the current workflow, the credential becomes effective when verified and no separate expiry date is entered. A suspended, revoked, expired, or incoherent credential is excluded fail-closed. Suspension revokes sessions, shift-PIN access, and active case locks. Only credentials that remain current enter the snapshot bound to a clinical signature. ### Administer an existing account Depending on permissions, the manager can: - reset a password; - activate or deactivate a member; - update a professional profile; - verify that each active account still belongs to an authorized current team member with the required licence. Promptly deactivate the account of anyone leaving the team or changing duties. Never reassign that account to another person. Record the request, actor, time, and verification under the local joiner-mover-leaver procedure. ## 7. Choose accessible complaints and services In **Complaint availability**, each complaint or service line can have separate controls for the professional team and patients. 1. Enable only services the team is trained and authorized to provide. 2. Verify pharmacist availability. 3. Separately enable patient access when the corresponding form is approved and available. 4. Save, then test the result with one synthetic account for each role. The Global production profile exposes the exact checked-in clinical catalogue for supported Canadian jurisdictions without a separate external form- publication process. Professional scope, licence, workspace, establishment, and jurisdiction controls still apply, and a pharmacy chooses which eligible workflows it offers. Genital or anogenital warts must follow the configured referral pathway; they must not be presented as an autonomous pharmacist-treatment option when the pathway requires external referral. ## 8. Configure appointments In **Appointment services**: **Copy availability** copies one day to another, repeats ranges Monday through Friday, or uses the displayed schedule of another service. Check the preview, choose **Use this schedule**, then **Save this service**. Copying replaces the ranges on the target days and preserves breaks; it does not copy the source service's fee or duration. 1. create or select a service; 2. specify whether it is active; 3. set its duration and fee, where applicable; 4. add available weekly windows; 5. remove windows that are no longer valid; 6. save, then ask a team member to verify the result in the **Agenda** with a synthetic account. Avoid overlapping windows or times outside actual staffing hours. Patients can reschedule only when the configured notice period is met and another slot is available. ## 9. Review statistics The **Statistics** page filters activity by period, complaint, and pharmacist. It includes case volumes, completed cases, and average management times. Use these data for resource planning and operational trend review. Always verify the date range and filters before comparing results. Aggregated statistics do not replace the official patient record, a clinical quality analysis, or an individual performance measure considered without context. ## 10. Security and retention review When the role has access to **Security review**, use the audit-log and retention tabs to examine attributable activity and records that have reached their configured period. Any archive or deletion operation must follow the approved policy, retention schedule, and pharmacy record obligations. Verify the exact target before confirming. Deletion in CliniqueRx alone does not prove that every external copy or the official record has been addressed. ## 11. Start-up checklist Before opening a service: - organization, contract, and exact pharmacy link confirmed active; - exact physical establishment confirmed active against the official provincial or territorial source, and the approved-network boundary authorized, unexpired, and tested for that pharmacy workspace; - named manager account protected by a password and single-use codes sent to the confirmed professional email address; - named team accounts active, with confirmed email and sign-in tested with the required MFA followed, on shared workstations, by their personal shift PIN; - licences and cryptographic signing identities checked under the approved procedure; - training and a synthetic scenario completed; - complaints and patient forms approved, then tested in French and English; - services, durations, fees, schedules, and notice periods verified; - outage, emergency, incident, and official-record transfer procedures understood; - local owner and escalation contacts posted; - active Global release binding and applicable workspace controls verified before any real data is used. ## 12. Routine operations ### Every day - confirm that the correct pharmacy workspace is displayed; - confirm that a designated team member is monitoring unassigned requests and appointments; - review service or security notices; - promptly handle accounts that must be disabled. ### Every month - reconcile active accounts with the real authorized team roster and licences; - review permissions, access to the manager’s confirmed email address for code delivery, and team changes; - confirm which complaints and services remain offered; - review statistics in context; - confirm that procedures and escalation contacts remain current. ## 13. Outage or unexpected behaviour If CliniqueRx is unavailable, shows inconsistent information, or cannot complete a workflow: 1. never delay urgent care; 2. stop entering information if identity, pharmacy, or record integrity is uncertain; 3. return to the pharmacy’s approved official process; 4. do not copy real data into development, an unprotected screenshot, or an unapproved support tool; 5. note the time, screen, and permitted technical identifier; 6. report the event under the local procedure; 7. resume only after integrity and access have been confirmed. ## 14. Conditional functions and runtime status - APEx is a working name. APEx functions are limited to platform governance and no proposal is deployed automatically. - External providers must not receive patient information without approved review, contract, and consent. - While `ClinicalPilot:RealPatientUseEnabled` remains `false`, use synthetic people and synthetic information only. For assistance, use the current support and incident contacts approved by your organization; verify them against the deployed service and operating contract.