Editorial desk · Stanford, California
Contact the Bathava Editorial Team
If you have a question about payment automation, a correction to something we published, or a topic you would like us to cover, this is the place to send it. We read every message, and we do not sell software, so you will not get a sales call in return.
What to send us
Questions about healthcare payment solutions, claims disbursement, reconciliation workflows, or integration are all welcome. If you are evaluating a platform and want to understand a term or a workflow, ask. If you spotted an error in a guide, tell us the page and what is wrong. If there is a topic we have not covered, suggest it.
Short questions are fine. Long ones are fine too. What helps most is a sentence about what you are trying to decide and which page or workflow prompted the question, so the reply lands on the right part of the topic.
- Term and workflow questionsA definition, a step in a claims disbursement platform workflow, or how a payment method reaches a patient balance.
- Corrections with a page referenceName the guide and the passage, and add a link or citation if you have one so we can check it before editing.
- Topic suggestionsReconciliation edge cases, integration questions, or a workflow you keep seeing explained badly elsewhere.
What we can and cannot help with
We can explain how workflows generally function and point you to the right guide on this site. We cannot recommend a specific vendor, provide pricing, or give legal or compliance advice for your organization. Those decisions depend on your systems and your constraints, which we do not have visibility into.
Where we can help
- Explain how a remittance file, a payment posting, or a reconciliation step generally fits together, and where a definition sits in the wider healthcare payment solutions picture.
- Point you to the guide on this site that covers the topic in the most detail, including integration and reconciliation basics.
- Confirm what a published page currently says, and correct it if a vendor's documented capabilities have changed since we wrote it.
Outside our scope
- Vendor selection or pricing comparisons for your organization.
- Legal, tax, or compliance advice specific to your contracts and systems.
- Implementation work, data migration, or configuration inside your platform.
Corrections
If a vendor's published capabilities have changed since we wrote a page, let us know. We update guides when the underlying facts shift. Include a link or a reference if you can, so we can verify the change before editing.
Corrections are the highest-priority messages we receive. When a change is confirmed, we note what was revised so readers who relied on the earlier wording can see what moved. If we cannot verify a claim, we will tell you rather than quietly edit the page.
- The page name and the passage you believe is out of date.
- A vendor page, release note, or documentation reference we can check.
- Whether the change affects a workflow guide or only a term definition.
Response times
We aim to reply within a few business days
We aim to reply to substantive messages within a few business days. Vendor pitches and unsolicited marketing are unlikely to get a response. If your message is a correction, we will prioritize it.
Working hours are Monday to Friday, 9:00 AM to 6:00 PM. Messages that arrive over a weekend are read on the next business day, and nothing is auto-answered.
Vendor and press inquiries
If you work for a payment vendor and want to correct a factual statement about your product, send the specific claim and your published source. We do not publish sponsored content or paid placements.
How a vendor correction moves through the desk
A factual correction is read against the claim it touches, the source you supply, and the page it appears on. If the source supports the change, we edit the guide and note the revision. If it does not, we reply with what we could not verify, so the exchange stays on the record instead of drifting into marketing language.
Send
The exact sentence you are disputing, quoted as it appears on the page.
Attach
Your published documentation or release note for the capability in question.
Expect
A reply that says what we changed, or what we could not confirm from the source.
Send your message
Use the form for questions, corrections, and topic suggestions. Include the page name when you are writing about something we published. A reply goes to the address you leave here.
Mailing address
Bathava editorial
450 Serra Mall
Stanford, CA 94305
USA
Phone
Working hours
Monday–Friday, 9:00 AM – 6:00 PM
Where to find us
The editorial desk is on the Stanford campus. There is no walk-in service here; the address is for correspondence and deliveries. For anything time-sensitive, email reaches the desk faster than a letter.
Bathava editorial
450 Serra Mall
Stanford, CA 94305
USA
Monday–Friday, 9:00 AM – 6:00 PM
Before you write
Most questions we receive are already answered somewhere on the site. Checking these pages first often saves you a wait, and the reply can then go deeper on the part that is still unclear.