Official booking destination
A clinic-approved scheduling page operated by the clinic or its authorized booking provider.
Example label: Book through the clinic
SECURE DESTINATION STANDARDS
ProfileMD uses clear publication states and approval standards for links to booking, secure forms, portals, messaging, and public education. A button is the visible endpoint of a governance process, not the beginning of one.
INSTITUTIONAL PURPOSE
A public button can appear simple while carrying significant responsibilities. Its label shapes expectations. Its destination determines where information goes. Its status suggests whether the clinic is prepared to receive and act on the next step.
ProfileMD's standard is therefore broader than visual design. It addresses naming, authority, destination ownership, routing, safety language, testing, maintenance, and removal.
Clarity at the point of action is part of responsible publication.
DESTINATION CATEGORIES
These categories define public communication patterns. They do not represent active services unless an exact destination has completed clinic approval and testing.
A clinic-approved scheduling page operated by the clinic or its authorized booking provider.
Example label: Book through the clinic
An authorized external form with confirmed purpose, routing, monitoring, and privacy responsibility.
Example label: Open the clinic's secure form
A clinic-designated portal or account sign-in managed outside the ProfileMD public layer.
Example label: Visit the patient portal
A clinic-authorized secure communication destination with a named owner and clear monitoring expectations.
Example label: Contact the clinic securely
A non-clinical public resource that explains preparation, policies, or the appropriate official next step.
Example label: Read visit preparation guidance
PUBLICATION STATES
A destination can move forward, pause, or be retired as authority and operational conditions change.
A proposed purpose or label for professional discussion. It is not an active patient destination.
The concept requires confirmation of the exact URL, authority, owner, wording, routing, and testing.
The documented activation standard is complete and the approved destination may be linked publicly.
The public link is removed or disabled while ownership, safety, accuracy, or operation is reassessed.
The destination is no longer appropriate, authorized, or maintained and should not remain publicly available.
ANATOMY OF A RESPONSIBLE ACTION
A safe, understandable action combines a specific label with destination context, ownership, status, and appropriate safety or response-expectation language.
Read Secure Workflow GovernanceAPPROVAL RECORD
The record supports accountable activation, future correction, and timely removal if the destination or clinic responsibility changes.
WORDING PRINCIPLES
The public action should support comprehension without implying that ProfileMD operates the external workflow or guarantees what happens after the link is opened.
DESCRIBE THE ACTION
A person should understand whether they are opening booking, a secure form, a portal, public guidance, or another clinic-approved destination.
IDENTIFY THE OWNER
Surrounding language should clarify that the destination is operated or managed by the clinic or its authorized provider, not by ProfileMD.
STATE THE LIMITS
Do not imply continuous monitoring, guaranteed response times, automatic EMR updates, appointment access, triage, diagnosis, or treatment.
MATCH THE STATUS
Planning examples and approval-pending destinations should not appear as active links or be mistaken for available patient services.
PROHIBITED PRACTICES
A destination that cannot satisfy the public-information and clinic-ownership boundary should not be represented as available.
VENDOR NEUTRALITY
A destination may use OceanMD, Hushmail, online booking, a patient portal, secure messaging, or another clinic-approved system. Product references do not imply endorsement, partnership, interoperability, or a guaranteed connection to an EMR.
The clinic remains responsible for its licensing, configuration, privacy practices, monitoring, clinical review, and vendor relationship. ProfileMD does not promise automatic PS Suite or EMR chart updates.
PATIENT SAFETY BOUNDARY
The examples on this page are publication patterns, not clinical services. ProfileMD public pages do not collect patient medical information. Do not send symptoms, medical questions, appointment reasons, test results, documents, or other personal health information to ProfileMD.
For a medical emergency, call 911 or go to the nearest emergency department.
Visit the patient-facing ProfileMD.ca contact pagePROFESSIONAL REVIEW
ProfileMD can review professional context, proposed wording, ownership, status, and publication readiness without collecting patient information.