Maryland telehealth launch guide · 2026
Start here
To launch a telehealth service in Maryland, start with professional authority and the care model. Maryland's medical-board FAQ describes patient identity checks, professional disclosures, oral or written consent, secure connections, and emergency protocols. For real-time encounters it also addresses a backup contact method, patient location, and people present at each site. These requirements affect the visit itself, not just a privacy policy displayed on the website.
This guide covers patients in Maryland. Ownership, professional authority, prescribing, and payment depend on the service and care model.
Published by Bask Health · Editorial process
Updated
Your launch, mapped out
Maryland
Prepare for consent, connection failure, and emergencies
The essentials
Start with the decisions that shape your legal structure and clinical workflow.
| Launch decision | Maryland |
|---|---|
| State requirement | Maryland guidance addresses consent, backup contact details, people present, and emergency protocols. |
| Regulators | Maryland Board of Physicians |
| 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 Maryland counsel.
These references support the discussion in each step. Operational suggestions are separate from legal requirements.
Local planning
Include patients who move between Maryland, Virginia, and Washington, DC. Check the encounter location even when the patient keeps the same home address.
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.
Maryland's medical-board FAQ describes patient identity checks, professional disclosures, oral or written consent, secure connections, and emergency protocols. For real-time encounters it also addresses a backup contact method, patient location, and people present at each site. These requirements affect the visit itself, not just a privacy policy displayed on the website.
Sources: Maryland Board of Physicians: telehealth FAQ.
Add a location and callback check to the encounter. Make it clear when another person is present and may hear health information. Test a dropped connection while the clinician is assessing the patient. Document who initiates the backup contact and when local emergency services are necessary. Keep these procedures available to the care team during the visit.
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 Maryland service plan into assigned work. Finish the clinical and legal decisions before configuring the patient journey around them.
A practice serving the Washington region should treat location as information about each appointment. A Maryland resident may join from a workplace in DC or a hotel in Virginia. The Maryland board says its license authorizes Maryland practice and directs doctors to the laws where an out-of-state patient is located. It does not require a separate special telehealth license for Maryland patients. Board licensing answers.
Build the appointment roster around the jurisdictions the team actually covers. Let booking staff see which doctors have issued authority for each intended location. Confirm the encounter location again when care starts, because the patient's schedule may have changed since booking. Keep this separate from the address used for billing or correspondence.
Describe the service area precisely in marketing. Access across the metropolitan region may require more credentialed coverage than a Maryland-only service. If that coverage is not ready, offer truthful rescheduling options. Include the support time in the launch budget so a predictable border issue does not become a confusing dispute about why a paid appointment cannot proceed.
Maryland allows a practitioner-patient relationship to be established through synchronous or asynchronous interaction if the practitioner verifies patient identity, discloses professional name and contact information and license type, and obtains oral or written consent from the appropriate person. Health Occupations section 1-1002. These steps should be visible even when no video introduction occurs.
For an asynchronous program, show the assigned clinician's identity in the care journey rather than only a generic medical-team logo. Give the patient a way to contact the treating practice later. Record the consent and identity verification with the encounter so a subsequent clinician can understand how the relationship began.
Design carefully for a parent or guardian. The statute refers to that person's consent when state law requires it, not a universal rule that any adult associated with an account can decide treatment. Have the practice define the relevant pathway for its patient population. Keep a separate route for resolving unclear authority before the clinical service begins, without asking general customer support to make the legal determination.
Discuss the care model and integrations for your Maryland launch.
The board's real-time encounter guidance addresses individuals present at both locations, including people who may be off camera. It says participants should be identified and the patient should agree to discussing confidential information with those people present, or they should leave. Board privacy guidance.
Turn this into a brief opening conversation. A family member helping with the phone, an interpreter, a medical assistant, and an information-technology employee have different reasons for being present. The clinician should know who is involved and whether the patient wants to proceed with them listening. A camera showing only one face does not establish that the room is private.
Apply the same thinking to the clinician's workspace. Headphones do not prevent someone behind the clinician from reading the screen. Define how staff handle technical assistance during an active appointment and how they limit access to the necessary task. Test the process with a fictional interpreter-assisted visit. The goal is to preserve useful help while making the patient's privacy choice clear, rather than excluding support people automatically or assuming their presence is always authorized.
Maryland's board calls for an alternate way to contact the patient during a technology failure, identification of the practice setting, and emergency safety protocols. Real-time encounter and safety guidance. Those details become important precisely when the usual video interface is no longer available.
Collect a callback number that the patient can answer during the visit. Identify the actual setting and location with enough precision for the intended safety protocol. A stored mailing address may lead staff to the wrong place if the patient is elsewhere. Make the information readily available to the treating clinician rather than hiding it inside an administrative enrollment screen.
Rehearse a dropped connection during a clinical concern. Determine who initiates the callback, what happens if there is no answer, and who directs further escalation. The correct action depends on the clinical situation; support staff should have a route to the responsible professional. Also test an ordinary technical failure so patients do not receive alarming instructions for a routine reconnection problem. Document the outcome and the next care step in the record.
Maryland requires an evaluation appropriate to the patient and condition before treatment or prescribing. The statute permits synchronous or asynchronous evaluation and requires in-person care or another telehealth format when clinically appropriate. Health Occupations section 1-1003. An asynchronous business therefore needs a way to change course when submitted information cannot support the decision.
Ask the medical director which questions, images, measurements, and tests are necessary for each proposed service. Then decide which can be collected reliably through the chosen format. A completed online request should not conceal a missing examination behind a technically successful submission status.
Give the clinician clear outcomes: proceed, request clarification, arrange another encounter, or refer for examination. Show the patient the resulting task and expected response time. If the business charges before evaluation, explain how a different care recommendation affects that charge. Track the proportion of cases that need another format during the pilot. That information helps set staffing and pricing more accurately than assuming every submission becomes a short, self-contained remote consultation.
Maryland section 1-1003 restricts prescribing the specified Schedule II opiates for pain through telehealth, with listed circumstances involving a healthcare facility, a declared catastrophic health emergency, or a qualifying established relationship with a prior in-person assessment. Other state and federal controlled-substance rules still apply. Current prescribing statute.
A broad medication-management label can hide this distinction. Review the actual drug, indication, encounter history, and clinician relationship before deciding whether a proposed service fits. Do not assume a prior prescription from an unrelated practice establishes the relationship described in the statute. Keep the relevant assessment evidence available to the prescribing clinician.
If the business is not equipped for this pathway, define how it handles a request that falls outside scope. The patient needs an accurate explanation and an appropriate clinical next step. Avoid allowing the sales catalog or an automated refill message to imply availability. A different treatment program should not inherit pain-medication permissions merely because both programs use the same electronic prescription integration.
The medical board's FAQ contains useful practice guidance but also references a historical insurance period ending in 2023. For a present Medicaid launch, use the Department of Health's current program page and linked policy guide. That page describes synchronous audio-video and audio-only visits, remote monitoring, and specified store-and-forward services. Maryland Medicaid telehealth program.
Map the intended service to its provider-specific rules and enrollment requirements. The program says a patient site can be a secure location approved by the patient and provider, but that does not make every service billable from every organizational arrangement. Its page includes separate clinic guidance and an outpatient mental-health-center update, illustrating why provider type matters.
Ask the billing team to validate the exact configuration before forecasting revenue. Record the service, professional role, modality, site, and applicable contract. When a clinical encounter changes format, the billing record should reflect what occurred. For direct payment, explain independent medication or testing charges so a patient does not confuse your care membership with coverage of every downstream service.
Maryland's board says it does not provide advice on corporate formation or corporate issues; it licenses individuals unless an exception applies. Corporate-issues FAQ. A verified medical license therefore does not answer how the new company may be owned, managed, or compensated.
Prepare the ownership chart, clinical-services agreement, management agreement, and fee flow for counsel. Ask who controls clinical policies and who remains responsible when the technology vendor, brand, and medical practice are different organizations. Translate the approved arrangement into system permissions and patient contact information. The person managing marketing campaigns should not become the final authority on clinical eligibility through an administrative role assignment.
Complete the release review with a visit that crosses the state border, an off-camera participant, an asynchronous case needing examination, and a dropped connection. Each should produce a clear decision and a usable record. Approve the launch only for the services and locations those workflows support. Retain the legal and clinical review questions that remain unresolved rather than treating a successful software demonstration as evidence that every business arrangement is ready.
What to launch
Choose a Maryland treatment category with your clinical team. These examples describe operating decisions, not promises of patient eligibility or partner availability.
Maryland permits asynchronous relationship formation and clinical evaluation under the statute's conditions. An image-based service still needs identity, clinician disclosure, consent, and sufficient clinical information. Let the doctor ask for new photographs or an examination. For Medicaid, separately check the program's store-and-forward coverage provisions; practice authority and payment rules answer different questions about the same encounter.
The real-time privacy discussion matters when another person helps the patient participate. Identify the interpreter or support person and clarify what the patient permits them to hear. Preserve a chance for the patient to speak privately when clinically appropriate. Include connection-loss and emergency procedures in the service design, especially when the visit involves a time-sensitive concern.
A regional program can be useful for people whose daily activities cross jurisdictional lines, but its roster must support where encounters occur. Keep the location check easy to update and connect it to scheduling. Explain available alternatives when the assigned clinician cannot serve the current location, and avoid making the patient repeat an entire enrollment simply to correct that information.
Built for telehealth
Bring the Maryland 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.
“The Bask team really care about their customers and are always willing to go the extra mile to make sure we’re taken care of and have our back. The ease of use and turnkey nature of the platform really helped us launch our business. We couldn’t recommend them higher to anyone starting a telemedicine company. Choose Bask if you want to be supported by a company that cares about your success.”
The board says a valid Maryland license authorizes telehealth for Maryland patients without an additional special telehealth license. That does not establish permission for a patient located in another jurisdiction. Verify the actual credential and encounter location, then review any applicable exception separately. The business should not confuse a technology registration with the professional authority needed to treat.
Section 1-1002 permits oral or written consent from the patient, or the parent or guardian when state law requires that person's consent. The practice should choose a process that documents the decision reliably and meets any additional applicable requirements. A policy demanding a signature may be an operating choice, but the cited statute does not impose writing as the only format.
The board's guidance recognizes that remote participants cannot readily see everyone present at the other location. An unseen person may hear sensitive information even though they never appear in the video. Identify people at both sites and establish whether they may remain for the conversation. Apply this to technical and clinical staff as well as family members.
No. The board states that it does not give reimbursement advice, and its FAQ includes historical payment language. Use current program guidance and the actual payer contract for the service, provider type, and format. Keep that review separate from the clinician's authority and standard-of-care decisions. A permissible encounter does not by itself establish the amount you can collect.
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.