Key Points
- Setting is a separate field from the service itself, so one code delivered in a clinic and in a home can be adjudicated as two different things.
- ABA moves between settings more than most specialties do, which makes this a fact about each session rather than a default sitting on the client record.
- Telehealth causes the most trouble, because the setting and the modifier have to agree with each other and with a payer rule that has kept moving.
Place of Service (POS) Explained
Every claim has to say where the service happened. The place of service code is that statement, drawn from a standard national list, and it sits alongside the procedure code rather than inside it: one field says what was delivered, the other says where. Payers read both, and a service covered in one setting is not automatically covered in another.
ABA makes this field harder than most specialties do, because the setting is a clinical decision rather than an administrative constant. A program deliberately runs where the skills are needed - a clinic for structured teaching, the home for daily routines, a school or the community for generalization - and the same client can be seen in three settings in a week. Where a session happened is therefore a per-session fact, not something set once on the client record and left alone.
It also affects money in ways that are easy to miss. Payers commonly reimburse the same service differently by setting, and some restrict particular services to particular settings outright. A claim carrying the wrong one can be denied, paid at an unintended rate, or paid correctly while quietly misdescribing where care happened - and the last of those is the version an audit finds.
Telehealth is where the field causes the most trouble. Remote delivery has its own designations, and payers have revised their positions on which ABA services may be delivered remotely, and how those claims should be coded, more often than they have revised most other policies. The setting and the modifier have to agree with each other and with the payer's current rule, which is three things to keep aligned rather than one.
The setting also has to match what the rest of the record says. A session note describing work in the family's kitchen, a claim coded to a clinic, and an electronic visit verification record placing the clinician at the home are three sources that should be telling one story. Where a payer requires visit verification, that mismatch is caught automatically, which makes this one of the few billing fields with an independent check sitting against it.
The practical safeguard is capturing the setting where the session is recorded rather than reconstructing it at billing time. If scheduling and the session note already carry it, the claim inherits it; if they do not, someone is inferring last month's locations from memory, which is how a run of sessions ends up coded to whichever setting the client usually attends.