Telemedicine is the clinical act delivered over a distance: a licensed clinician examines, diagnoses, treats, prescribes for, or monitors a specific, identified patient who is somewhere else. The defining feature is not the video technology but the relationship — a genuine patient-provider relationship exists, which is exactly what pulls the activity into the body of healthcare law. The moment identifiable health information moves across the connection, the US Health Insurance Portability and Accountability Act (HIPAA) attaches, alongside clinician licensure rules, the applicable standard of care, and mandatory clinical documentation.
For a product team, "this is telemedicine" is therefore a scope statement with concrete consequences. It means you must verify who the patient and clinician actually are (identity proofing), capture and store informed consent, write an immutable audit log of who accessed what, and run the whole thing on infrastructure covered by a Business Associate Agreement (BAA) with every vendor that touches Protected Health Information (PHI). A consumer chat app and a telemedicine app can look identical on screen and be worlds apart underneath.
The common mistake is treating telemedicine as "video calling with a doctor skin on top." The video layer is the easy part; the regulated obligations — licensure across state lines, consent, documentation, retention, audit — are the part that determines whether the product is lawful to operate. Decide early that you are building a regulated clinical system, not a media app, because retrofitting those duties later is far more expensive than designing for them.
