Design Article 31 off-site documentation so actual service location, staff responsibility, clinical records, and billing review stay connected.
An off-site documentation workflow should distinguish the actual service setting from the home clinic, scheduled location, and billing location fields. Those values can look similar on a screen while serving different operational purposes.
For a New York Article 31 MHOTRS program, start with the service and setting approved for the actual circumstances. This guide addresses record design and handoffs. It does not authorize a service location, establish coverage, or provide a universal rule for services delivered away from a clinic office.
Article 31 off-site documentation starts before configuration
The OMH MHOTRS programmatic guidance includes an off-site services section. Use the applicable guidance and the clinic's operating documents to define the scope before asking a software administrator to add a location option.
Write down the service, intended setting, responsible staff, documentation expectations, communication route, and billing review owner. Distinguish an off-site encounter from a satellite encounter and from a remote encounter according to the clinic's approved process. Similar scheduling labels should not collapse different operational arrangements.
Identify the evidence needed to resolve an unusual setting. Staff should know who can answer the program question and who can answer the payer question. A configurable dropdown is not evidence that every option is appropriate for every encounter.
Define each location field in plain language
Inventory the location fields used by scheduling, clinical documentation, patient assignment, reporting, and billing. Name the question each field answers. A patient's home clinic may identify an ongoing organizational relationship while the encounter location identifies where a particular service occurred.
Ask the vendor which fields are copied from an appointment and which are entered or confirmed during documentation. Determine whether changing one field updates another automatically. Hidden defaults can be convenient until the actual service differs from the original plan.
Create a fictional example in which a planned office appointment becomes an authorized off-site encounter. Inspect the record after the change. The clinical story, administrative history, and billing review should remain understandable without pretending the original appointment never existed.
Capture context without overcollecting information
The clinical record should explain relevant service circumstances under the organization's policies. That does not mean every operational report needs a detailed address or sensitive narrative. Decide which information belongs in the chart and which information belongs in a broadly accessible worklist.
Use an appropriate identifier and an authorized record link for coordination. If a manager only needs to know that location review is pending, avoid copying the patient's circumstances into a general task title. Apply the organization's privacy and access decisions to exports as well as screens.
Review any device or connectivity arrangement with the responsible security and operational leads. Staff working away from the office may encounter different access conditions, but the solution should follow the clinic's approved process rather than informal personal notes or unapproved storage.
Keep service delivery and documentation time distinct
If documentation is completed after the encounter, preserve the actual service date and the record's entry and signature history. Do not use a later entry date as a substitute for when care occurred, and do not alter history merely to make a report appear consistent.
Define the approved process for an unavailable system or connection. Staff need to know how to document through the organization's contingency workflow and how authorized reconciliation occurs when access returns. A vendor's mobile screen alone does not establish that the clinic has a complete downtime process.
During testing, include an encounter entered after the service and a correction to its location. Ask a reviewer to explain the sequence from the record. If the system obscures the difference between service time and documentation time, record the limitation and the proposed control.
Give billing the actual setting and a review route
The OMH MHOTRS billing and fiscal guidance provides a separate billing reference. Have the billing lead determine which information is needed for the clinic's actual service and payer arrangements.
Test the path from the clinical encounter to the draft charge or claim review. Identify where location information is sourced and what happens when it is corrected. A clinically accurate note can still leave an incorrect billing default if the two fields are maintained separately.
| Location issue | Owner to identify |
|---|---|
| Setting outside the expected workflow | Authorized program or clinical lead |
| Appointment differs from actual service | Operations and documenting clinician |
| Billing field differs from encounter | Billing reviewer with clinical clarification as needed |
| Report groups the encounter unexpectedly | Reporting owner and system administrator |
The table names decision routes, not universal job titles. The clinic should assign actual people or roles that can act and provide coverage when the usual owner is absent.
Reconcile location reports to known encounters
Choose a small set of fictional encounters with known settings. Run a report by location and inspect each row. Determine whether the report groups by home clinic, appointment location, encounter location, or a billing dimension.
Change one scheduled location without changing the actual service setting, then rerun the report. This reveals which field drives the result. Keep the definition with the report so leadership does not interpret a home-clinic summary as a count of services physically delivered at that site.
Include corrected and canceled encounters in testing. A report that counts historical appointments differently from finalized encounters can be useful, but staff need to understand the distinction before using it for staffing, service, or financial decisions.
Build an exception review staff can sustain
Create a focused worklist for missing or conflicting location information. Include encounter identifier, service date, issue, owner, and next action. Avoid a generic error list that requires every reviewer to reopen the full chart to discover the question.
Review recurring causes after a pilot. If staff repeatedly select the wrong setting, the problem may be unclear labels, inherited defaults, or training rather than individual carelessness. Test a configuration change against the same fictional cases before applying it broadly.
Ease Health publishes this guide and offers a unified CRM, EHR, and RCM platform for behavioral health. Ask shortlisted vendors to demonstrate the proposed off-site workflow and document any manual steps. Related material includes the EHR overview, satellite setup checklist, and appointment reconciliation guide.
The work product is a location map and an exception process that preserve what actually happened. That makes the record useful across clinical, operational, and billing review.
Related reading
Frequently Asked Questions
Can a clinic treat every service away from its office as the same workflow?
No. The actual service, setting, program authority, delivery method, and payer instructions can differ. Have authorized clinical and billing staff define the applicable workflow before configuring software.
Which location should appear in an off-site record?
Make the actual service setting understandable and preserve any other organizational location fields with clear definitions. Do not assume that the patient's home clinic or the original appointment location answers the same question.
Does recording an off-site location establish payment eligibility?
No. Accurate location data supports review, but payment depends on the applicable service, program, coverage, coding, provider, and payer rules. Keep billing review separate.
What should an off-site EHR test include?
Use a fictional encounter whose actual location differs from the original schedule. Check clinical documentation, location correction history, billing fields, reporting, and any approved downtime or connectivity process.
