Evaluate an Article 31 telehealth workflow from scheduling and patient instructions through documentation, billing review, and connection exceptions.
A telehealth software evaluation should test appointment setup, patient instructions, actual delivery, documentation, exceptions, and billing review as one operational sequence. A video connection is one component of that sequence, not the whole clinic workflow.
For a New York Article 31 program, begin with the organization's approved clinical and operational model and current applicable guidance. This article provides a purchasing and implementation test method. It does not establish whether a particular service or delivery method is authorized or payable.
Article 31 telehealth workflow testing starts with scope
The OMH telehealth guidance is a primary reference for OMH providers. Review the applicable scope with the clinic's clinical and compliance leads rather than assuming a generic telehealth feature matches the organization's program.
Define the services, patient populations, locations, staff roles, and payer arrangements in the proposed workflow. Separate what the clinic does today from an expansion being considered. The test pack should reflect the approved operating model, with unresolved policy questions identified before configuration.
Record dependencies. Video delivery, scheduling, reminders, documentation, and billing may be handled by one product or several services. Ask who owns setup, support, agreements, and troubleshooting for each component. A smooth demonstration can conceal a dependency the clinic has not budgeted or staffed.
Test appointment setup as ordinary staff
Have a scheduler create a fictional appointment under the account type used in daily work. Inspect delivery method, clinician, date, time, location-related fields, and patient instructions. Test a recurring series and a single-appointment change.
Verify what the patient-facing communication actually says. Does it contain the correct appointment information and approved contact instructions? If the appointment moves, determine whether the old link or message remains usable and how the patient receives the update.
Include a staff coverage change. Reassigning a clinician may affect a meeting link, reminder, or documentation assignment differently. Record what updates automatically and what staff need to check manually. The clinic should know the operational cost of an ordinary schedule change before launch.
Inspect the actual encounter record
The scheduled delivery method may differ from what occurred. A connection can fail, a participant may be unable to join, or the clinic may use an alternative process approved for the circumstances. The record should describe the actual encounter under the organization's policies.
Use a fictional test where the planned video session does not proceed as expected. Ask the clinician to document the facts without inventing care that did not occur. Then inspect the appointment status, encounter, and any draft charge to understand the downstream effect.
Keep service date, documentation date, and correction history distinguishable. A later administrative update should not silently rewrite the story of the encounter. A reviewer should be able to identify what happened and who made the relevant decision.
Review clinical and operational exceptions separately
Clinical appropriateness and patient safety belong in the clinic's established clinical process. A software error queue does not replace that process. Staff should know how to contact the appropriate clinical person when an encounter raises a care-related concern.
Operational exceptions include a missing link, incorrect reminder, access problem, or a schedule change. Give these a named support route and enough reproduction detail to investigate without placing unnecessary patient information in a general ticket.
| Exception | Demonstration question |
|---|---|
| Patient cannot open the link | What approved support instructions are available? |
| Clinician assignment changes | Which meeting and record fields update? |
| Encounter does not occur | How are appointment and documentation statuses handled? |
| Delivery circumstances change | How does the record capture facts and route review? |
| System becomes unavailable | Which clinic contingency process applies? |
Test one exception at a time before testing several together. That makes it easier to identify whether the problem is configuration, training, an external service, or a product limitation.
Give billing current, service-specific evidence
The OMH MHOTRS billing and fiscal guidance is a separate billing reference. Have billing staff review the actual service, payer, delivery circumstances, and current instructions before defining the proposed claim workflow.
Ask where billing fields originate and how they change when the actual encounter differs from the scheduled appointment. A calendar label alone should not be treated as the final determination of coding or coverage. Record the reviewer and any manual step.
Use a fictional encounter with an intentional mismatch to test the control. Determine whether the issue appears before submission and who resolves it. A successful connection or completed note does not guarantee payment, and a software configuration does not establish payer policy.
Evaluate privacy and access in the proposed setup
Have the organization's authorized security and privacy leads review the proposed services, access, information flow, and agreements. Ask the vendor for current evidence rather than relying on a broad compliance label in a sales slide.
Test the intended staff roles and participant experience using fictional data. Review which information appears in meeting invitations, reminders, shared screens, and exports. Each channel can expose different information even when the chart itself has appropriate access controls.
Record what is included in the proposed commercial scope. A capability demonstrated in a sales environment may involve an add-on, configuration, or external subscription. The written proposal should identify those dependencies before the clinic treats them as part of the launch plan.
Make acceptance a repeatable test
Save the fictional cases, expected results, observed results, and unresolved issues. Ask clinical, intake, billing, and IT representatives to sign off on their own responsibilities. An overall positive impression is less useful than a documented answer to each important workflow question.
Repeat the tests after significant configuration changes. A new reminder template or meeting integration can affect an otherwise stable workflow. Keep the test pack small enough that the clinic can actually rerun it.
Ease Health publishes this guide and offers a unified CRM, EHR, and RCM platform for behavioral health. Ask the team to demonstrate the proposed telehealth setup and its dependencies. Related material includes the EHR overview, off-site documentation guide, and Article 31 evidence checklist.
The useful purchasing result is a tested sequence with accountable exceptions. That gives the clinic a clearer view of readiness than a successful video call alone.
Related reading
Frequently Asked Questions
Does a working video link establish that an Article 31 telehealth workflow is ready?
No. The clinic also needs an approved clinical process, suitable patient instructions, documentation, privacy and access controls, exception handling, and billing review for its actual services and payers.
Should a telehealth appointment record the intended and actual delivery method?
Make the actual encounter circumstances understandable and retain the history of relevant changes. A scheduled delivery method can differ from what occurred, so test how staff document and review that difference.
Can one telehealth billing setup apply to every payer?
Do not assume that. Review current New York program guidance and the relevant payer's instructions, including the service and circumstances involved. Keep payer-specific decisions documented.
What exception belongs in a telehealth demo?
Use a fictional failed connection or delivery-method change. Ask who documents what occurred, how the appointment status changes, and which clinical and billing actions remain for review.
