PubLedge

A participant operating AI-assisted prescription renewal must adhere to Utah's telehealth provider requirements in §26B-4-704, with specific subsections deemed satisfied by following the patient-journey and escalation protocols described in the participant's Proposal (Schedule B). Certain subsections (e.g., the patient-records portability default) are inapplicable; others are substituted by Proposal-section conformance.

What Counts

• Adherence to §26B-4-704 as the baseline telehealth framework
• Compliance with subsection (2)(b)-(c) and subsection (4) is established through the participant's documented patient-journey and clinical-workflow protocols
• Compliance with subsection (2)(e) is established through the participant's documented escalation protocols
• Patient-records portability (where required by agreement, e.g., Legion §17(B)) through a portable format or user download/share option

What Does Not Count

• Operating telehealth outside the Proposal-documented processes
• Asserting §26B-4-704 compliance without the RMA-specified substitute protocols in place
• Treating the substitution as extending to subsections not named in the agreement

Implementing Legal Instruments