Plan an Article 31 satellite clinic EHR setup across scheduling, encounter locations, staff workflows, billing review, and reporting.
A satellite clinic setup is ready for testing when scheduling, clinical encounters, billing, and reports identify the intended service location consistently. Adding a second address to a settings page is only the beginning of that work.
For a New York Article 31 organization, separate the operational launch from software configuration. A working calendar does not establish that a location has the appropriate approval or payer enrollment. This checklist helps the implementation team identify the configuration and evidence needed for its own launch decision.
Article 31 satellite clinic EHR setup begins with a site record
Create an authoritative site record outside the vendor demonstration. Include the location's official name, physical address, relationship to the primary program, approved scope, planned hours, staff contacts, and billing review owner. Record who can approve changes to each item.
The OMH MHOTRS programmatic guidance contains a dedicated section on program satellites. Use that as a reference with the clinic's own operating documents. Do not assume that the software term location corresponds exactly to the regulatory term satellite.
During discovery, ask the vendor to map the clinic's organizational structure to the system's structure. A site, department, program, billing entity, and service location may be different objects. Write down those relationships before importing staff or scheduling patients.
Inspect scheduling defaults with ordinary staff accounts
Build a small set of fictional appointments at the primary site and satellite. Ask a scheduler to create, reschedule, cancel, and restore them using the account type they will have after launch. A demonstration under an administrator account can conceal the experience of everyday users.
Watch what happens when the same clinician works at both locations. Does the selected location persist after changing the clinician? Does a recurring appointment series retain the intended site? If a room is reassigned, is the actual service location still understandable?
Test reminders and patient-facing instructions when those functions are in scope. An appointment can be correct internally while the message sent to the patient still names the primary clinic. Keep those communication checks in the launch worksheet, with an owner for correcting the template.
Follow the location into the clinical encounter
Next, open the appointment as the clinician and create the encounter. Identify the location shown in the chart and any place it can be overridden. Ask what happens when the patient arrives at a different site than originally scheduled.
Use a fictional example: a Tuesday session is scheduled at the satellite but moved to the primary location after a building issue. The clinician documents where the service occurred. The scheduling change, encounter, and billing review should tell a coherent story even if the system stores the original appointment history separately.
Do not accept a screen label without understanding its source. A header may display the patient's home clinic while a claim uses an encounter-specific location. Both can be legitimate dimensions, but staff need to know which question each field answers.
Review staff visibility and access separately
A location filter makes a calendar easier to navigate. It does not by itself establish a security boundary. Ask the vendor to distinguish display filters, staff assignments, role permissions, and patient-record access. Request demonstrations under the actual proposed roles rather than inferring restrictions from a filtered list.
Build a role matrix for satellite staff, covering scheduling, documentation, supervision, billing, reporting, and administrative settings. Include float staff and coverage arrangements. If a staff member covers the satellite only occasionally, define how access is granted, reviewed, and removed under the organization's policies.
Keep access decisions with the clinic's authorized security and operational leads. A vendor can explain functionality and configuration, but the clinic decides which staff activities are appropriate and what controls it will operate.
Give billing a location-specific test pack
Have the billing lead provide fictional cases representative of the satellite's actual services and payer arrangements. Inspect the relevant provider identifiers, location fields, service information, and routing. The purpose is to verify the proposed configuration, not to infer payment from a successful software action.
The OMH MHOTRS billing and fiscal guidance is a separate reference from the programmatic guidance. Keep current payer instructions and enrollment evidence with the billing test pack. Avoid hardcoding a rate or rule simply because it worked for the primary location.
Include a deliberately incorrect site assignment and confirm how staff detect and correct it before submission. Then test a correction after an encounter is finalized. Record whether correction involves clinical amendment, charge review, claim replacement, or another process, with the appropriate owner at each step.
Reconcile reports to known satellite activity
Ask for a report showing the fictional satellite encounters only. Compare the total to the test pack, then move one appointment, cancel another, and add an encounter at the primary location. Rerun the report and explain every change.
| Report question | Definition to settle before launch |
|---|---|
| How many patients use the satellite? | Assigned patients, active episodes, or patients actually seen |
| How many visits occurred there? | Completed encounters, appointments, or billed services |
| What revenue belongs to the site? | Charges, allowed amounts, payments, or another accounting basis |
| Which staff delivered care? | Scheduled professional, rendering professional, or supervising professional |
These definitions can all be useful. The problem arises when a dashboard uses one definition while leadership assumes another. Save the filter settings and a short explanation alongside the launch report.
Prepare launch and correction ownership
Before the first live schedule, review open issues with operations, clinical, billing, and IT leads. Distinguish a blocker from a training item or a documented manual process. Assign an owner and a decision date to each unresolved item.
Plan the first-day support route. Staff should know where to report a wrong reminder address, a missing site option, an unexpected billing default, or an access problem. Collect enough information to reproduce the issue without copying patient details into unsecured channels.
After launch, review a small authorized sample of real satellite activity under the clinic's quality process. Compare it with the tested workflow. Configuration can drift as staff add recurring appointments or copy templates, so a one-time sign-off is not the end of site governance.
Ease Health is the publisher and a behavioral health software vendor. Ask any vendor, including Ease, to demonstrate the specific satellite workflow and document dependencies. The EHR overview, RCM overview, and Article 31 evidence checklist provide related evaluation context.
The launch artifact should be a tested site map and a short exception list that named people can resolve. That gives the organization a practical way to distinguish a configured address from a functioning satellite workflow.
Related reading
Frequently Asked Questions
Is adding an address enough to configure a satellite clinic?
No. Test how the location appears in appointments, encounters, staff workflows, billing fields, and reports. Also confirm the clinic's operating approvals and payer arrangements separately from software configuration.
What is the most useful satellite launch test?
Run a fictional appointment through clinical documentation, billing review, and a location-specific report. Repeat it after moving the appointment or changing the rendering professional to expose inconsistent defaults.
Should a satellite copy every setting from the primary clinic?
Use shared settings where appropriate, but review differences in services, staffing, schedules, billing arrangements, and local workflows. A copied default can be wrong even when the screens look familiar.
How can a clinic identify satellite reporting errors?
Reconcile a small location report to known encounters and inspect the field used to assign location. Determine whether the report counts scheduled location, actual service location, or another organizational dimension.
