Minnesota telehealth launch guide · 2026
Start here
To launch a telehealth service in Minnesota, start with professional authority and the care model. Minnesota §147.032 allows qualifying doctors without a Minnesota license to use an interstate telehealth registration pathway. Conditions include unrestricted licensure in the state from which they provide services, annual registration, and limits on an in-state office or physical practice. The statute also applies Minnesota law and health-record requirements. Its exceptions have their own conditions.
This guide covers patients in Minnesota. Ownership, professional authority, prescribing, and payment depend on the service and care model.
Published by Bask Health · Editorial process
Updated
Your launch, mapped out
Minnesota
Review annual interstate registration conditions
The essentials
Start with the decisions that shape your legal structure and clinical workflow.
| Launch decision | Minnesota |
|---|---|
| State requirement | Minnesota has an annual interstate telehealth registration pathway with specific eligibility and practice conditions. |
| Regulators | Minnesota Board of Medical Practice |
| Professional ownership | Review the medical entity, permitted owners, clinical control, and management fees with state healthcare counsel. |
| Clinician authority | Check the issued license or applicable state pathway for each profession and service. |
| Patient location | Confirm where the patient is physically located at each encounter, including follow-up. |
| Care format | Have the clinical team match video, telephone, or asynchronous assessment to the patient and applicable rules. |
| Prescriptions | Review the clinician, medication, examination, monitoring, and pharmacy together. |
| Pharmacy fulfillment | Check the actual dispensing location and its authority to serve patients in the state. |
| Patient information | Map clinical and nonclinical data, vendor access, consent, and applicable privacy duties. |
| Payment model | Separate direct-payment terms from payer coverage, enrollment, and reimbursement requirements. |
Summary only, not legal advice. Confirm the requirements for your business with Minnesota counsel.
These references support the discussion in each step. Operational suggestions are separate from legal requirements.
Local planning
Define the first service area in the Twin Cities or a specific regional community. Include patients who need examinations outside the remote practice.
A useful launch plan starts with a narrow service definition. Specify the patient group, treatment, follow-up schedule, and geographic area. Then test whether your clinical team and local partners can deliver it.
Interview prospective patients about appointment access, travel, language, and payment preferences. Check their ability to use the intended care format. These interviews inform the operating plan; they do not establish market size or clinical eligibility.
Minnesota §147.032 allows qualifying doctors without a Minnesota license to use an interstate telehealth registration pathway. Conditions include unrestricted licensure in the state from which they provide services, annual registration, and limits on an in-state office or physical practice. The statute also applies Minnesota law and health-record requirements. Its exceptions have their own conditions.
Sources: Minnesota Statutes §147.032.
Compare the registered model with the actual clinician location and work arrangement. Record renewal dates and changes in license status. If a doctor will work physically in Minnesota, reassess whether the interstate route fits. Ask counsel to map Minnesota record obligations separately from HIPAA and to document any exception the practice intends to use.
The steps below are operating recommendations. The linked state material supports the specific legal summary above. Your advisers must apply current law to your actual entity, clinicians, products, and patients.
Step by step
Use these eight steps to turn the Minnesota service plan into assigned work. Finish the clinical and legal decisions before configuring the patient journey around them.
Minnesota gives a qualifying doctor outside the state a registration route that is different from opening a Minnesota practice. Section 147.032 requires an unrestricted license where the doctor provides telehealth, excludes specified adverse license histories, and limits physical practice in Minnesota. Annual registration is part of that route. Read the interstate requirements.
Start the business design with a map of where each doctor will actually work. A team member who takes appointments from a Minnesota home office creates a different licensing question from one working in Wisconsin. Put proposed office space, travel, and telephone coverage on that map before choosing the credential pathway.
Have counsel review the entity that contracts for care and the administrative company's role alongside this staffing decision. Interstate registration addresses a doctor's authority; it does not decide ownership or management fees. The useful output is a signed-off organizational plan with a specific credential route for each clinical position, rather than a generic description of a nationwide network.
The interstate statute requires immediate notice to Minnesota's board when a registered doctor's license becomes restricted in another jurisdiction. It also calls for information about current and previous licenses. That makes the whole licensing history relevant, not just the credential closest to Minnesota. See registration and notification duties.
Ask the credentialing team to establish a direct reporting route with each doctor. A scheduled annual review alone may miss a midyear change. Store the current practice location, annual registration evidence, and the person responsible for reviewing a status alert together.
Design the schedule so affected appointments can be reassigned without erasing clinical tasks. Pending laboratory results and prescription questions may still need attention after new bookings stop. For a planning exercise, remove one registered doctor from a fully booked week and follow every outstanding task to its replacement owner. Use the exercise to set an honest enrollment limit and budget backup coverage before advertising next-day availability.
Discuss the care model and integrations for your Minnesota launch.
Section 147.033 permits the patient relationship to begin through telehealth and applies the same standards of practice and conduct as in-person care. This supports a remote entry point, but leaves the practice responsible for obtaining evidence adequate for the actual condition. Review Minnesota's practice provision.
Write the first-visit specification with the medical director. For each offered treatment, identify which history is essential, which observations the doctor needs, and what would require another examination. Let intake collect information without making it the final clinical decision. If photographs are useful, define acceptable image quality and a route for patients unable to upload them.
Choose the initial service area partly around the examinations your remote team cannot perform. A launch focused on one regional community can build a workable referral routine before expanding. Track the reason a visit changes format so the team can distinguish a technology failure from a clinical need for hands-on care. Those problems need different operational fixes.
Minnesota's legend-drug statute identifies particular drug groups for which a valid order requires a documented evaluation, including an examination. The list includes controlled drugs, certain analgesics and muscle relaxants, and erectile-dysfunction use of PDE5 inhibitors. It describes several qualifying examination arrangements, plus a telehealth examination route for specified purposes, including medications for opioid use disorder. Read section 151.37, subdivision 2.
Have the prescribers classify the proposed formulary against that text. Do not treat all noncontrolled drugs alike or assume that a video connection resolves every examination requirement. Record which clinical evidence supports each pathway and where another practitioner's examination must be obtained.
Pharmacy review belongs in this design session. Ask how the dispensing team receives the information it needs and how it will communicate a rejected order. If a drug needs a different evaluation, change the patient's next step before charging for an assumed prescription. State requirements and federal controlled-substance conditions both need current review.
Interstate telehealth doctors must comply with Minnesota's health-record provisions. Section 144.293 generally requires a signed, dated patient consent, specific state authorization, or a qualifying representation that another provider holds consent before records are released. The statute also contains exceptions and duration rules. Review the release framework.
Map the records leaving the practice: an outside laboratory result, a referral packet, a pharmacy clarification, and a patient's own transfer request. Have privacy counsel identify the authority for each disclosure. A vendor's HIPAA contract should not be the only evidence supporting the Minnesota decision.
Give staff a way to see the scope and expiration of the applicable consent. If the patient authorizes one receiving practice, the export process should preserve that destination instead of treating the signature as universal permission. Test revocation and corrected recipient details with fictional records. Keep optional analytics and marketing uses out of the clinical-release workflow so a support agent can explain what the patient actually authorized.
Minnesota requires records or a relevant summary to be furnished promptly to another provider on the patient's written request identifying that provider. Its release law also addresses documentation when information is disclosed without consent under state authority. See transfer and documentation provisions.
Choose what a receiving clinician needs to continue this particular service. A weight-management referral may need the medication course, recent measurements, side effects, and outstanding tests. Sending the original enrollment survey alone may obscure why the remote doctor requested an examination.
Assign someone to resolve a rejected fax, an incorrect destination, or a missing result. In a regional launch, agree on a practical return channel with participating local practices rather than assuming they can access your portal. Measure how long a referral remains clinically unresolved, not only whether a message was transmitted. Include that coordination time in staffing estimates. The company should be able to explain who watches the patient's open question while two organizations exchange records.
The interstate statute exempts certain services from registration, including defined irregular or infrequent care, emergency care, and consultation in which the Minnesota doctor retains ultimate authority. These are distinct grounds with their own facts. They are not a general substitute for registering a roster serving a recurring patient panel. Read the exemptions.
If a specialist will advise a Minnesota practice, describe who requested the consultation, who discusses the recommendation with the patient, and who decides the treatment. If the brand instead recruits patients and assigns their care directly, describe that business honestly in the licensing review.
Keep capacity planning separate from exception thresholds. A clinician who is suitable for a limited consultation arrangement may not be the right coverage for a subscription promising regular follow-up. Ask counsel to review projected volume and the contracting model before a sales team counts that doctor as available. Then price the service using the personnel and coordination the approved model actually requires.
A useful Minnesota launch rehearsal combines clinical continuity with the state's distinctive administrative dependencies. Create a fictional returning patient whose doctor is approaching annual registration renewal and whose next examination will occur at a local practice. Follow the appointment, credential review, patient permission, referral packet, and result back into the chart.
The exercise should expose conflicting assumptions between recruiting, support, and the medical group. Recruiting may believe renewal is automatic; support may believe the outside practice already received the record; the doctor may be waiting for a result no one has requested. Resolve those gaps before expanding appointment inventory.
Also inspect the patient-facing price explanation. State which visits are included, whether outside testing is billed separately, and what happens when the doctor recommends a different service. Have clinical and legal reviewers approve the exact operating model represented by the page. Use those assessments to identify changes the service needs before it can deliver the promised care.
What to launch
Choose a Minnesota treatment category with your clinical team. These examples describe operating decisions, not promises of patient eligibility or partner availability.
Minnesota expressly includes PDE5 inhibitors used for erectile dysfunction in its evaluation provision and identifies a telehealth examination option. The clinical group should define the necessary assessment and exclusions for its own service. A product selection screen is not that assessment; the workflow needs room for a different diagnosis, additional information, or referral. See the examination provision.
A consultation model can connect an outside specialist with a Minnesota doctor who retains responsibility. Write the consulting relationship around the actual exchange of expertise and follow-up. Avoid displaying the specialist as the direct treating clinician if the licensing analysis depends on a different role. Patients should understand which practice will answer their next question.
Recurring care makes registration renewal, access to earlier results, and outside examinations recurring costs. Decide how home measurements enter the chart and how uncertain readings are checked locally. Offer a subscription only after the team can support those tasks across the communities included in its launch, with understandable charges for services delivered elsewhere.
Built for telehealth
Bring the Minnesota service plan to a Bask walkthrough. Review intake, clinical records, pharmacy connections, payments, and support against the actual workflow. Confirm integrations and state coverage before signing partner agreements.
Built with Bask
Customer experiences supplied with permission. These are individual testimonials, not independently audited results or evidence of Bask availability in another country.
“Bask has been a cornerstone in our growth at Eden since we first started as a company. Their EHR solutions have not only streamlined our processes but also provided invaluable insights into our business that have helped shape our strategic decisions. They consistently deliver software upgrades that enhance functionality, keeping pace with industry needs. We truly appreciate how responsive they are to feedback, making improvements based on partner requests. Bask’s dedication to innovation and collaboration has been instrumental to our success, and we look forward to what the future holds.”
The registration statute conditions the pathway on restrictions involving a Minnesota office, meeting patients in the state, and receiving patient calls there. A proposed move or temporary working arrangement therefore needs review. Confirm the correct professional authority before scheduling care from the new location rather than assuming registration travels with the doctor.
Yes. Section 147.033 permits a relationship established through telehealth while applying the same practice and conduct standards as in-person care. The doctor still needs an adequate assessment for the proposed treatment. Medication-specific examination provisions may affect what information or additional encounter is necessary.
Include Minnesota law separately. Section 147.032 expressly applies the state health-record provisions to interstate telehealth, and section 144.293 has its own release, consent, exception, and documentation rules. Have counsel examine the actual destinations and purposes of disclosure instead of treating one national privacy template as the completed review.
Evidence that the approved roster can maintain registrations and cover follow-up, that medication pathways have been reviewed, and that records reach real examination partners. Compare unresolved referrals and interrupted visits across the initial service area. Expansion should follow demonstrated capacity for continued care, rather than the number of counties a checkout form accepts.
Compare state, city, and country guides. Check the jurisdiction that applies to the patient, clinician, and business before you expand.
Bask Health publishes this AI-assisted guide from the references below. It has not received independent legal or clinical approval. Read the research method and correction policy.
Your next step
Bring your treatment plan, target patient group, and launch dependencies. Discuss the software and integrations your service needs.