| This article is part of our series on Custom Dermatology Practice Platform Development for US Dermatology Groups: Building a Dermoscopy Imaging, Pathology and Cosmetic Billing System |
Three Questions That Decide This Before Any Feature Does
A dermatology technology consultant earns their fee before a single feature enters the conversation. Most platform projects for medical, surgical and cosmetic practices take shape around three questions a product demonstration will never answer. Does the practice participate in federal quality programs, and does that limit what a custom clinical system can become? What happens to the image archive during a migration, and can its lesion associations survive the move, since an archive without them is a folder of photographs rather than a clinical record? And how many pathology results are currently open, waiting on provider acknowledgment or a recorded patient notification?
The first question decides whether a full build is viable. The second identifies the largest hidden cost. The third is a patient safety measurement that stands on its own, whatever the practice builds. This article covers why those questions come first, what a scoping engagement examines and how to read the answer. It builds on the custom software development behind a practice platform and the web application development supporting a patient portal and store-and-forward intake.
Why This Question Is Live in 2026
Three developments have brought dermatology groups to this build versus buy decision, none of them a deadline. Consolidation is the first. Groups have grown through acquisition, and a practice running a dozen sites on inherited systems has a standardization problem that per-provider subscription licensing makes expensive to solve alone.
The cosmetic side of the business is the second. What used to be a small adjunct is, for many practices, now a substantial retail operation built around packages, memberships, product lines and active marketing, and clinical software designed around medical dermatology tends to handle that thinly.
Imaging expectations make up the third. Patients and referring physicians increasingly expect asynchronous access, comparison views and portal delivery, and the image archive has grown large enough that the architecture chosen years ago is showing its limits.
One constraint works the other way. Certification requirements make replacing a clinical system harder than it once was, which is part of why the sensible shape for most groups has shifted from replacement toward a targeted layer around a retained core. None of this settles whether a practice should build. It means the question deserves a structured answer.
What a Consultant Establishes First
A practice platform assessment starts with three items, and each changes the shape of what follows.
The Certification Position
Whether the practice participates in federal quality programs, what that requires of its clinical technology and whether a custom clinical system is viable should be settled in the first week. This certification constraint shapes everything downstream, and a partner who has not raised it early has not understood what they are being asked to design around.
The Image Archive Reality
How many images exist, how they are associated with patients and anatomical sites today, what the incumbent will export and whether those associations survive migration. An archive that moves without its lesion associations loses the comparison capability that made it valuable, and this assessment often reshapes the timeline and budget. How new images enter that archive matters too, which is where custom mobile app development sits in the scope.
The Result Loop Audit
A count of pathology results awaiting acknowledgment, patients not confirmed as notified and follow-up not yet completed. This is the most useful output of any scoping engagement in the specialty, standing apart from the software decision. If the number is not zero, the practice has a patient safety finding worth acting on this month, regardless of the platform decision.
What Else the Engagement Examines
A thorough engagement extends past those gating items. It includes direct observation in clinic across all three service lines, since a medical session, a surgical day and a cosmetic consultation are different operations, and a partner who has only watched one designs for it alone. It examines the pathology arrangement, whether in-house or outside, the certification position, the self-referral structure and whether counsel has reviewed it.
It looks at how the billing split runs today, how the medical versus cosmetic determination is made and recorded, and whether the current system leans on that determination in any way it should not. It reviews the cosmetic operation, including packages, memberships, product lines and how claims currently appear in marketing material, since a claims review is often overdue. It covers the telehealth footprint where the practice reviews out-of-state submissions, measures prior authorization workload rather than estimating it, and tests current systems against what genuinely cannot be configured, alongside the practice’s own numbers on documentation time, cosmetic conversion and package utilization. What that compliance scope has to cover, from privacy and laboratory certification through to telehealth rules and claims about devices and skincare, is set out in HIPAA, CLIA Requirements for In-Office Pathology, MIPS Quality Reporting, State Teledermatology Rules and FDA Limits on Device and Cosmetic Claims Compliance for US Dermatology Software.
What the Engagement Should Produce
An imaging platform scoping engagement of this depth produces defined deliverables rather than a general impression. A certification position statement, with its consequence for the project’s shape. An image migration assessment that answers the association question directly and quantifies that effort separately from the build. A result loop audit with findings and remediation recommendations, delivered regardless of the software decision.
It also produces a compliance scope covering the laboratory arrangement, telehealth footprint, marketing claims position and quality participation, built with counsel where the answer is unclear, plus a current-state cost analysis from the practice’s own numbers, a tested configuration review and a defined first release with its exclusions written down. This article is educational and strategic content, not legal advice.
The final deliverable is a costed comparison of at least three paths, configuring existing systems, building a targeted layer around a retained certified core, and a fuller custom build, with development, migration and five-year running costs separated in each, and imaging storage growth modeled explicitly.
Reading the Answer: Configure, Layer or Build
Configuring makes sense when an established dermatology platform already handles the practice’s service lines and the frustration comes from setup nobody has revisited in years. For most single-site and small group practices, this is the correct answer.
Layering makes sense when the clinical core already works and the real gap sits elsewhere, in the cosmetic retail operation, the patient experience, multi-location reporting or an imaging workflow the existing product handles thinly. Building only that layer against a retained certified core avoids taking on certification, pathology interfaces and quality reporting machinery directly, the components most practices would rather someone else maintained. This is the right answer for many groups, and the one priced least often.
Building fully makes sense when scale makes per-provider licensing costly across many providers, when the cosmetic business warrants its own platform, or when a management company is unifying acquired practices onto one model. Whatever gets built must be maintained as quality reporting, telehealth rules and product regulation change, and a practice without a maintenance plan should weigh the layer option heavily. What each of those three paths costs, stage by stage and across five years, is broken out in Cost to Build a Custom Dermatology Practice Platform for a US Dermatology Group: Full Budget Breakdown.
Red Flags in the Conversation
Some warning signs are practical. A fixed price offered before discovery. No question about certification or quality participation. Migration priced as a plain data transfer with no mention of preserving associations. No proposal to audit the result loop. The layer option never priced. Imaging storage growth left out of running costs. Counsel never proposed for the laboratory arrangement or marketing claims.
Others should end the conversation outright: any proposal to build image analysis that assesses or classifies a lesion, since that is a regulated medical device rather than a feature, any workflow where a result can be filed without provider acknowledgment, any prompt or default that would influence the medical versus cosmetic determination, and any marketing feature drawing on clinical images without specific authorization. The strongest positive signal is a partner who asks for the open result loop count before anything else.
Final Thoughts
Owners who settle the certification position, image migration reality, and result loop count before discussing features can make a more informed platform decision. The outcome may be a correctly scoped custom build, a targeted layer around a retained core, or no new development at all. If the result loop is not closed, that finding deserves attention regardless of which software path the practice chooses.
When a custom platform is justified, working with a leading software development company can help turn the assessment into a defined technical scope. The important point is to carry the certification, imaging, pathology, billing, and compliance requirements established during discovery into the architecture rather than treating them as later additions.
