ProfileMD places the button
The physician profile explains the doctor, practice access, patient preparation, and approved next steps.
Secure workflow model
How ProfileMD + secure clinic workflows work
ProfileMD helps patients find the right physician profile and click the right clinic-approved pathway. Clinical information stays inside the physician or clinic's secure system.
The preferred model
ProfileMD handles public navigation. The clinic owns clinical intake and review.
The clinic owns the secure form
The secure form or booking pathway belongs to the physician or clinic, not ProfileMD.
Patient information goes directly to the clinic
ProfileMD does not receive, store, or review the patient's medical answers by default.
Implementation options
Start with the safest default, then add help only when the clinic wants it.
Clinic-approved secure link
The clinic creates or approves its own OceanMD, Hushmail, booking, or secure workflow link. ProfileMD places that approved link on the physician profile.
- Clinic pays the secure workflow provider directly.
- Clinic owns the inbox and review process.
- Patient data goes directly to the clinic.
- Best default model for individual physicians and groups.
ProfileMD helps organize the workflow
The clinic wants help creating or organizing the secure workflow. ProfileMD may help with planning, wording, form/template structure, testing, and button placement.
- Guided setup with clinic admin is preferred.
- Temporary delegated access may be used if approved by the clinic.
- Password sharing should be avoided.
- Clinic still owns and monitors the secure workflow.
Who pays for what?
Financial ownership stays transparent.
Doctor/clinic pays ProfileMD
Profile page, profile maintenance, button placement, workflow strategy, and concierge setup if purchased.
Doctor/clinic pays OceanMD, Hushmail, or booking provider
Secure form infrastructure, clinical inbox, messaging, booking, and EMR-connected tools.
Patient data goes to clinic
Patient medical information does not go to ProfileMD by default.
Before a secure button goes live
Activation requires ownership, routing, and wording to be clear.
ProfileMD can place approved secure buttons only when the destination is real, the clinic has approved it, and staff know where submissions or notifications are reviewed. EMR behavior must be understood and not overpromised.
- Exact secure URL exists.
- Physician or clinic approves the destination.
- Submission inbox or notification route is configured.
- Provider/staff owner is assigned.
- Review frequency is defined.
- Emergency and response-time wording is approved.
- Test submission is completed using fake data.
- EMR behavior is understood and not overpromised.
- ProfileMD button label is approved.
Connect the public profile to the right secure clinic pathway.
Start with clear physician-controlled information. Add secure buttons only when the physician or clinic has approved the destination.