The institutional home of ProfileMD Mission • Publication standards • Public-information governance

SECURE DESTINATION STANDARDS

A public action should say exactly where it leads, who owns it, and whether it is ready.

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.

Exact destination Approved public wording Named clinic owner Visible publication status

INSTITUTIONAL PURPOSE

Turn a visual button into an accountable public pathway.

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

Organize links by what a person is actually being asked to do.

These categories define public communication patterns. They do not represent active services unless an exact destination has completed clinic approval and testing.

BOOKING

Official booking destination

A clinic-approved scheduling page operated by the clinic or its authorized booking provider.

Example label: Book through the clinic

SECURE FORM

Clinic-owned secure form

An authorized external form with confirmed purpose, routing, monitoring, and privacy responsibility.

Example label: Open the clinic's secure form

PATIENT PORTAL

Official portal access

A clinic-designated portal or account sign-in managed outside the ProfileMD public layer.

Example label: Visit the patient portal

SECURE COMMUNICATION

Approved messaging pathway

A clinic-authorized secure communication destination with a named owner and clear monitoring expectations.

Example label: Contact the clinic securely

PUBLIC EDUCATION

Preparation or information page

A non-clinical public resource that explains preparation, policies, or the appropriate official next step.

Example label: Read visit preparation guidance

PUBLICATION STATES

Status should describe readiness, not create an impression of readiness.

A destination can move forward, pause, or be retired as authority and operational conditions change.

  1. 01

    Planning concept

    A proposed purpose or label for professional discussion. It is not an active patient destination.

  2. 02

    Clinic approval needed

    The concept requires confirmation of the exact URL, authority, owner, wording, routing, and testing.

  3. 03

    Ready for publication

    The documented activation standard is complete and the approved destination may be linked publicly.

  4. 04

    Paused for review

    The public link is removed or disabled while ownership, safety, accuracy, or operation is reassessed.

  5. 05

    Retired

    The destination is no longer appropriate, authorized, or maintained and should not remain publicly available.

ANATOMY OF A RESPONSIBLE ACTION

The label is only one part of the public explanation.

A safe, understandable action combines a specific label with destination context, ownership, status, and appropriate safety or response-expectation language.

Read Secure Workflow Governance

APPROVAL RECORD

A published destination should have a reviewable record behind it.

The record supports accountable activation, future correction, and timely removal if the destination or clinic responsibility changes.

WORDING PRINCIPLES

Good labels are specific, restrained, and honest about the handoff.

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

Use specific, ordinary language.

A person should understand whether they are opening booking, a secure form, a portal, public guidance, or another clinic-approved destination.

IDENTIFY THE OWNER

Make the external handoff visible.

Surrounding language should clarify that the destination is operated or managed by the clinic or its authorized provider, not by ProfileMD.

STATE THE LIMITS

Avoid promises the pathway cannot support.

Do not imply continuous monitoring, guaranteed response times, automatic EMR updates, appointment access, triage, diagnosis, or treatment.

MATCH THE STATUS

A concept should look like a concept.

Planning examples and approval-pending destinations should not appear as active links or be mistaken for available patient services.

PROHIBITED PRACTICES

Some actions should never be published.

A destination that cannot satisfy the public-information and clinic-ownership boundary should not be represented as available.

  • Fabricated, guessed, placeholder, or bare-hash destinations
  • Public fields that collect symptoms, medications, documents, or other patient medical information
  • Labels that imply emergency response, guaranteed access, or a guaranteed clinical outcome
  • Activation without a clinic-approved owner, routing process, safety language, and completed test
  • Leaving a public link active after authority, ownership, accuracy, or operation becomes uncertain

VENDOR NEUTRALITY

The standard follows the responsibility, not the software name.

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

Use only an active pathway approved by your physician or clinic.

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 page

PROFESSIONAL REVIEW

Begin with authority and purpose before discussing a public destination.

ProfileMD can review professional context, proposed wording, ownership, status, and publication readiness without collecting patient information.