Licensure follows the patient
The location that matters for telehealth is generally the patient’s, not yours. Sitting in one state and caring for a patient in District of Columbia generally means you need authority to practice in District of Columbia — via compact privilege or a District of Columbia license. See telehealth: patient in another state.
The law that governs this in District of Columbia
Caring for a patient located in District of Columbia is practice in District of Columbia, so it is District of Columbia’s own nurse practice act that defines what you may do and the District of Columbia Board of Nursing that applies it. That act is District of Columbia nursing licensure law (Board of Nursing, DC Health).
There is no compact statute to cite for District of Columbia, which is the substantive point rather than a gap in our research: District of Columbia has not adopted the compact, so the practice act above is the whole of the law that applies to you here.
Compact status is not the only consideration
Even where a multistate license reaches District of Columbia, your employer and the District of Columbia Board of Nursing may impose additional requirements, and some roles carry their own rules. Compact status answers one question — it is not a blanket authorization to practice remotely.
APRN telehealth is separate
The compact covers RN and LPN/LVN licenses only. If you work as an APRN, your advanced-practice authority is granted state by state and is not carried by a multistate RN license — a point that catches out a lot of remote NP roles.
Why compact privilege does not reach District of Columbia
District of Columbia has not adopted the compact. Either way the practical answer for caring for patients located in District of Columbia is the same today: a multistate license from another state does not authorize it, and you generally need a District of Columbia license from the District of Columbia Board of Nursing. Re-check before a start date rather than assuming — this is precisely the fact that changes.