Launching a dermatology telehealth brand requires a defined clinical scope, an intake and image workflow suitable for that scope, and independent providers who can decide when remote care is appropriate. The brand should make the service easy to understand without presenting every skin concern as suitable for the same online treatment.
Which dermatology service should the brand launch first?
Dermatology is a broad field, while a launch needs a specific service definition. Decide which concerns the program intends to evaluate, which patient groups it serves and what requires another setting. A narrow initial scope can create a clearer customer experience and a more manageable operation than a promise to address every skin condition.
An existing dermatology office may want to extend a familiar service. A skincare brand may want to connect an existing audience with independent evaluation. A creator may have a community asking for more than general education. Each route begins with different assets, but none permits the commercial team to diagnose visitors from their interests.
Write a program brief that connects the audience, clinical service, provider arrangement, pharmacy needs and support scope. Review the white-label telehealth model so the brand understands which responsibilities it owns and which remain with licensed professionals.
What should the intake and image workflow accomplish?
The independent clinical organization should define the information and encounter format required for its program. Images may be useful, but their presence alone does not establish that remote evaluation is adequate. The workflow needs a route for missing context, unclear images and concerns outside the program's scope.
Give patients practical submission instructions approved for the service. Explain how to provide the requested views and how to correct an incomplete upload. Make the process accessible on a phone without silently reducing image usefulness through an aggressive compression or cropping choice.
Preserve chronology and context. An image's upload date may differ from when it was taken. A patient may submit several concerns in one set of photographs. The record should help the clinical team understand which information belongs to which question rather than presenting an undifferentiated gallery.
Review image handling in the TEHR platform. Ask how providers request clarification, how patients respond, who can access the photographs and how a case is routed when the remote service is not appropriate.
How should the program handle cases outside its scope?
Define the escalation and referral process before launch. The brand should know how a clinician identifies the next appropriate step and how that recommendation reaches the patient. Support staff need a route for questions without being asked to interpret a skin image or decide its urgency themselves.
Separate technical problems from clinical uncertainty. A failed upload may require support help; an adequate image that still does not support a clinical decision requires professional judgment. Both need clear status messages, but the resolution is different.
Do not design the commercial flow so every case must result in a product. The provider may request more information, recommend another setting or decide that the proposed treatment is not appropriate. The patient should understand the administrative consequences, including the actual payment terms, without feeling that a clinical decision is a failed purchase.
For state and entity planning, use the CPOM review framework. Brand presentation does not change who controls clinical decisions or which professional arrangements are required.
Why do some dermatology medications need a distinct workflow?
Do not assume that every medication can use the same intake and renewal process. FDA's iPLEDGE explanation describes a restricted program for isotretinoin involving prescribers, pharmacies and patients. It also identifies modifications approved in February 2026. That is an example of why current product-specific requirements matter.
This example does not assert that TEHR offers an isotretinoin program. It shows why a broad dermatology platform claim should not be interpreted as automatic support for every drug and its associated process. Establish the actual available program with the clinical organization and relevant partners.
If a proposed service involves a special program, map its enrollment, documentation, timing and dispensing dependencies separately. Confirm what the platform supports and what remains an external step. A product card should not conceal a required workflow that only becomes visible after payment.
Keep changes under review. A regulatory modification may reduce one burden while leaving other requirements intact. The implementation should follow the current program, not an old checklist or an optimistic summary.
How should topical and compounded products be described?
Describe the actual preparation and its status. Topical does not automatically mean free of meaningful risks, and a compounded combination should not inherit FDA approval from a separate ingredient or product. The clinical and pharmacy teams should determine the appropriate information for the patient.
FDA's telehealth marketing warning cautions against misleading compounded-drug approval, equivalence and compounder-identity claims. A brand should not imply it manufactures a preparation merely because its name appears prominently in the customer experience.
Use the 503A and 503B guide to structure partner diligence. Verify the exact pharmacy entity, proposed preparation, supported states and process for clarification. Align the product page, prescription record, pharmacy instructions and support information.
Plan for a changed preparation or discontinued product. The commercial team should not substitute a visually similar item on its own. A defined professional review and communication process helps the patient understand the actual change.
What should a launch workflow make visible?
| Workflow | What the customer should understand | What the team should verify |
|---|---|---|
| Image submission | What is needed and how to retry | Images remain usable and correctly linked |
| Clinical review | A decision may require more information | Tasks have a clinical owner |
| Pharmacy clarification | Which step is pending | The correct professional receives the question |
| Follow-up | How to report a concern or change | Messages reach the right team |
| Billing | What renews and how to cancel | Commercial status does not overwrite clinical facts |
Test these handoffs with fictional cases before launch. Include an unsupported concern, a missing photograph, multiple attachments and a message sent after a subscription is canceled. The service needs an answer for each state, not only the path that ends in a shipment.
Review staff permissions during the same exercise. Images and clinical messages should not become available to every commercial role simply because a shared dashboard makes access convenient.
How should subscriptions and marketing set expectations?
Explain what the service includes and what a customer is paying for at each stage. A recurring skincare-style subscription can look familiar, but a clinical program includes independent decisions that may change the next step. Make that difference clear without making the experience difficult to use.
Do not guarantee clear skin, a particular response time for treatment or a universal before-and-after result. Support claims with evidence appropriate to the actual service or product. When using photographs in marketing, obtain the relevant permission and avoid presentation choices that create a misleading impression.
Price the entire operating model. Include clinical work, image review, pharmacy coordination, support, payment costs and implementation. TEHR's flat platform subscription and flat transaction fee involve 0% revenue share; request a scoped quote to understand the actual included responsibilities and additional costs.
For domain and advertising planning, read the LegitScript guide. A platform relationship does not automatically certify the brand's own website or guarantee acceptance of its creative.
What should an existing dermatology business preserve when migrating?
Preserve clinical context alongside images: dates, source, relevant notes, prior decisions, current orders, consents and open questions. A folder of photographs is not equivalent to a coherent patient record. The receiving team should understand what each image was intended to document.
Keep marketing permissions separate from care records. An image retained for clinical use should not automatically become available for a new campaign. Maintain purpose and access boundaries during the transition.
Use the migration checklist to pilot representative records and active tasks. Include patients awaiting review, those needing additional images, outstanding pharmacy clarifications and paused subscriptions. Test historical image display and attachment associations, not just account totals.
Communicate the practical change to patients: where to sign in, how upcoming reviews work and who handles questions. HHS's cross-state licensure guidance is a reminder that expanded reach must match actual professional authority and program availability.
How should the brand improve after launch?
Review incomplete submissions, repeated questions and lost handoffs. If people repeatedly upload the wrong view, improve the instructions. If pharmacy status is unclear, fix the event mapping and communication. If customers misunderstand renewals, revise the offer where the decision is made.
Keep clinical judgment outside conversion pressure. A case routed to another setting may represent the program working correctly. Measure whether the route is clear and completed rather than treating every non-prescription outcome as a defect.
Expand the service deliberately. A new condition, population, state or medication can require new clinical and operational support. A well-run brand adds scope when its actual capability supports the promise.
What else should you know?
Can a dermatology brand handle every skin concern remotely?
No blanket claim should be made. The independent clinical program defines its scope and when another encounter or setting is appropriate.
Does uploading a photo guarantee a prescription?
No. Images support evaluation when appropriate; clinicians may need more information or recommend a different route.
Does TEHR automatically support every dermatology medication?
No product-wide assumption should be made. Confirm the actual program and any special requirements with TEHR and the independent clinical organization.
Can patient images be used in advertising?
Clinical use and promotional use are different purposes. Preserve appropriate permissions and avoid misleading image presentation.
What is the most important migration check for image-based care?
Verify that images retain their dates, source, clinical context and relationship to the correct patient and encounter, alongside active tasks and access controls.
Which sources support this guide?
Public sources reviewed as of 2026-10-22. Vendor statements describe the vendor’s published offering; your contract determines actual scope.
Build around your operation.
Discuss your categories, patient experience and costs with TEHR.