AI in Nursing Homes: What HIPAA Allows and Where SNFs Use It First

PBJ Reporting Requirements for SNFs: 2026 Deadlines, iQIES, and Audit Prep

Last updated October 5, 2026 · By Hathr.AI

PBJ reporting is the quarterly, payroll-based submission of direct care staffing hours that each Medicare- and Medicaid-certified nursing home files with CMS under 42 CFR 483.70(p), due 45 days after each fiscal quarter and filed through iQIES since August 2026. Hathr.AI checks payroll exports, scanned agency invoices, and census reports against the staffing file under a signed BAA.

Reconcile one quarter of staffing data in Hathr.AI, free for 7 days →

Key takeaways

  • Each Medicare- or Medicaid-certified long-term care facility files Payroll-Based Journal data each quarter under 42 CFR 483.70(p). The file is due by 11:59 p.m. Eastern on the 45th calendar day after the quarter closes: February 14, May 15, August 14, and November 14.
  • PBJ moved to iQIES on August 17, 2026, and CMS retired the QIES version on September 15, 2026. The fiscal Q4 2026 file, due Saturday, November 14, 2026, goes through iQIES with a HARP account and an approved PBJ role.
  • CMS caps each employee ID at 22.5 hours a day and requires a 30-minute meal deduction for each full shift, whether or not the employee took the break. Paid leave and off-floor training stay out of the file.
  • Four or more days in a quarter with no RN hours under job codes 5 to 7, on days with residents in the building, set the staffing rating to one star for that quarter. A failed or unanswered staffing data audit sets it to one star for three months.
  • Hathr.AI reads payroll registers, time detail, scanned agency invoices, and the iQIES census report next to the PBJ file, and lists each mismatch with its source page. The DON and the staffing coordinator decide what goes in the file.
  • Hathr.AI runs Anthropic's Claude models on AWS GovCloud (US) inside a FedRAMP High boundary, with a signed BAA on every web app account, for $47 per user per month with no seat minimums and a 7-day free trial.

PBJ reporting meaning: what CMS collects and why

PBJ stands for Payroll-Based Journal, the CMS system that collects direct care staffing hours from nursing homes. Section 6106 of the Affordable Care Act required facilities to submit staffing data based on payroll and other verifiable and auditable data. CMS finalized the requirement in the FY 2016 SNF PPS final rule, and mandatory submission began July 1, 2016. The requirement now sits at 42 CFR 483.70(p), and surveyors cite it under F851.

Before 2016, the public staffing numbers came from a self-reported form tied to the annual survey. The journal replaced that snapshot with daily staffing records from payroll. A budget, a schedule, or a staffing grid falls short of the standard, and CMS can ask the facility for the payroll records behind any hour it reported.

Families comparing nursing homes can read the resulting staffing ratings on Medicare Care Compare. Readers new to the census side of staffing data can start with our MDS coordinator guide. This page serves the facility teams that build the PBJ file and defend it in an audit.

Who must submit PBJ data

Each long-term care facility certified for Medicare, Medicaid, or both files PBJ data, whatever its size, ownership, or occupancy. The regulation sets no small-facility or low-census exemption. A facility that pays a payroll vendor to submit keeps the legal responsibility for the file, according to the PBJ Policy Manual (V2.8, August 2026).

PBJ submission deadlines for the next five quarters

The system runs on the federal fiscal year, which starts October 1. Each file covers one quarter and is due by 11:59 p.m. Eastern Time on the 45th calendar day after the quarter ends, per the CMS staffing data submission page. We computed the weekdays below.

Fiscal quarterReporting periodDue dateDay of week
FY 2026 Q4July 1 to September 30, 2026November 14, 2026Saturday
FY 2027 Q1October 1 to December 31, 2026February 14, 2027Sunday
FY 2027 Q2January 1 to March 31, 2027May 15, 2027Saturday
FY 2027 Q3April 1 to June 30, 2027August 14, 2027Saturday
FY 2027 Q4July 1 to September 30, 2027November 14, 2027Sunday

Each of the next five deadlines lands on a weekend. CMS counts calendar days, and the Policy Manual states that the PBJ system accepts no submissions after the deadline, with no exceptions. Plan to submit by the Friday before, and earlier if you can.

An early file buys time to fix errors. After the final upload, the facility checks the Final File Validation Report in iQIES, which can take up to 24 hours to arrive. A file sent on day 44 leaves no room to correct what that report finds.

What CMS changed in staffing data submission in 2026

CMS made four changes to the submission process in 2026. Each one affects the file due November 14, 2026.

DateChangeWhat to do
February 6, 2026Data Specifications version 4.10.0 enforce a maximum of 22.5 hours per employee ID per day. Edit -4025 replaced edit -4015.Confirm your payroll vendor exports in version 4.10.0. CMS rejects XML files in other versions from April 1, 2026.
August 17, 2026The Payroll-Based Journal went live in iQIES. CMS locked the QIES version for viewing, and iQIES error -1025 blocks more than 22.5 hours on one employee ID in a day.Get a HARP account and an approved PBJ role for each facility you submit for.
September 11, 2026CMS posted the PBJ Policy Manual V2.8 and an updated FAQ for the iQIES transition.Update your written PBJ method to cite V2.8.
September 15, 2026CMS retired the QIES version.Run staffing and census reports in iQIES before each deadline.

AHCA notes that iQIES suspends access after 60 consecutive days without a login, per its September 2026 iQIES guidance. A submitter who logs in once a quarter can lose access between deadlines, so build a monthly login into the PBJ calendar.

What goes into a PBJ submission

Each PBJ record says that one employee ID, under one job title code and one pay type, worked a set number of hours on a set date. The Policy Manual counts the hours a facility pays staff to work on site.

Include: regular and overtime hours worked on site, agency and contract hours, and exempt staff hours as the facility pays them.

Exclude: vacation, sick leave, holiday pay, and other paid leave; meal time, with a 30-minute deduction for each full shift whether or not the employee took the break; training hours when the employee cannot perform the primary role; off-site and remote nursing hours; and on-call time with no on-site work.

Salaried staff follow the same rule. The Policy Manual example: a salaried employee who works 10 hours and receives pay for 8 reports 8. The CMS FAQ lets a facility report more than 40 hours a week for an exempt employee when the employment contract states the higher hours. A default of 8.0 hours for each weekday, including days the DON took off, fails the payroll test.

PBJ job title codes and pay types

CMS defines 40 job title codes. The nursing codes 5 to 12 feed the staffing star rating, and the Five-Star Technical Users' Guide (September 2026) groups them this way:

Job codeTitleCounts toward
5RN director of nursingRN hours
6Registered nurse with administrative dutiesRN hours
7Registered nurseRN hours
8LPN or LVN with administrative dutiesLPN hours
9Licensed practical or vocational nurseLPN hours
10Certified nurse aideNurse aide hours
11Aide in trainingNurse aide hours
12Medication aide or technicianNurse aide hours

Codes 5, 6, and 7 all count as RN hours, so moving an RN between the administrative and direct care codes leaves RN hours per resident day unchanged. RN hours drop when an RN lands in an LPN code, when the DON's hours go under the administrator code, or when an RN shift goes missing from the file. Map each HR title to the employee's primary duty, write the crosswalk down, have the DON sign it, and hold it steady across quarters. The CMS FAQ lets a facility split one shift across job codes when the employee's duties change mid-shift.

Each record carries a pay type: 1 for exempt, 2 for non-exempt, and 3 for contract, which covers agency staff. Each contract and agency worker needs a unique employee ID. IDs may not contain personal identifiers such as a Social Security number. If a vendor change forces new IDs, link old and new IDs in the same quarter, so the turnover measure does not read the change as departures.

Census: CMS builds it from the MDS

Facilities do not submit census in PBJ. CMS stopped loading census records from PBJ files in April 2019 and derives the daily census from MDS assessments. A discharge assessment ends a resident's census days on the discharge date. A resident with no assessment for 150 days leaves the census on the 150th day.

The 150-day rule explains a common star loss. A discharge assessment that CMS does not receive keeps the resident in the census for up to 150 days, which inflates the denominator and lowers each hours-per-resident-day ratio. The Policy Manual tells facilities to run the iQIES census report and confirm it before the deadline. PBJ accuracy and MDS transmission run on the same clock.

How PBJ data becomes the staffing star rating

CMS uses six measures in the staffing domain of the Five-Star rating:

  • Case-mix adjusted total nurse staffing hours per resident day (RN, LPN, and nurse aide)
  • Case-mix adjusted RN hours per resident day
  • Case-mix adjusted total nurse staffing hours per resident day on Saturdays and Sundays
  • Total nursing staff turnover over 12 months
  • RN turnover over 12 months
  • Administrator departures

CMS adjusts the hours for acuity with the nursing case-mix groups from PDPM, so the same MDS data that sets the nursing payment sets the expected staffing level. Turnover draws on six consecutive quarters of PBJ data. An employee counts as eligible after 120 hours in a 90-day period and counts as having left after 90 consecutive days without work.

Three conditions override the hours and set a one-star staffing rating, per the Technical Users' Guide:

  • A missed submission deadline.
  • Four or more days in the quarter with no RN hours under codes 5 to 7, on days with one or more residents in the building. The one star lasts for the quarter.
  • A PBJ audit that the facility does not answer, or one that finds significant gaps between reported and verified hours. The one star lasts three months.

The RN test reads the PBJ file. Federal rules at 42 CFR 483.35(b)(1) require an RN for at least 8 consecutive hours a day, 7 days a week, and surveyors cite that rule under F727. A weekend RN shift missing from payroll counts as a day with no RN, though an RN worked it. The 2024 rule that would have required an RN on site 24 hours a day no longer applies; our page on the nursing home staffing mandate covers the repeal and the rules that remain.

The errors that cost a staffing star

  • Paid leave left in worked hours. Payroll exports include PTO by default, and PBJ excludes it.
  • No 30-minute meal deduction for each full shift.
  • Salaried staff reported at a default of 8.0 hours a day instead of the hours the facility pays them to work.
  • Agency hours missing because the invoice arrived after the payroll cut-off.
  • RN hours coded outside codes 5 to 7, which creates days with no RN in the file.
  • Job code drift, with different staff mapping the same title to different codes across quarters.
  • Pay periods that straddle the quarter end, with hours booked to the pay date instead of the date worked.
  • Discharge assessments left untransmitted, which inflates the census.
  • Universal workers counted in full under each role. The Policy Manual requires a reasonable method to split their time.
  • More than 22.5 hours on one employee ID in a day, which iQIES now rejects.
  • A Final File Validation Report left unread until after the deadline.

Preparing for a PBJ audit

CMS audits PBJ submissions against payroll. The CMS FAQ lists three paths to a failed audit: large gaps between reported and verifiable hours, incomplete MDS discharges, and no response. The FAQ describes an appeal path for a failed audit, except for structural violations such as grouped employee IDs.

Keep these records for each quarter, so a new staffing coordinator can rebuild the file 18 months later:

  • The payroll register and time punch detail behind the file
  • Agency and contract invoices with hours by person and date
  • The job code crosswalk, signed by the DON
  • The written method for paid leave, meal deductions, salaried hours, and universal workers
  • The submitted XML file and the Final File Validation Report
  • The iQIES staffing and census reports run before the deadline

What is Hathr.AI?

Hathr.AI is a HIPAA-compliant AI platform that runs Anthropic's Claude models on AWS GovCloud (US) inside a FedRAMP High authorization boundary. Hathr, LLC, based in Springfield, Virginia, sells it as a web app at $47 per user per month and as an API for developers. The U.S. Department of Health and Human Services, prominent universities, healthcare organizations, and RCM teams trust Hathr.AI. Our page on HIPAA-compliant AI for skilled nursing facilities covers the facility deployment.

Staffing coordinators and payroll teams use Hathr.AI to compare the payroll register and time detail with the PBJ file before submission, read scanned agency invoices and handwritten timesheets, and list days with no RN hours. MDS coordinators use the same platform to check the iQIES census report against discharge records, and administrators use it to draft the written method and the audit response.

Can a nursing home put payroll and census data into an AI tool for PBJ reports?

Yes, and Hathr.AI accepts a signed BAA online at signup on every web app account, which covers the resident records that PBJ work pulls in. The two halves of the data sit under different rules. HIPAA's definition of protected health information at 45 CFR 160.103 excludes employment records that a covered entity holds in its role as employer, so payroll registers fall outside HIPAA. Payroll files carry wages, Social Security numbers, and bank details, so treat them with the same care.

The census side counts as PHI. The iQIES census report, MDS discharge lists, and resident rosters identify residents. Under 45 CFR 164.502(e) and 164.504(e), a covered entity needs a written BAA before it shares PHI with a business associate. A census report pasted into a chat tool without one counts as a disclosure.

Hathr signs as the business associate, so these terms are our obligations:

  • Hathr, LLC acts as the business associate, and your facility is the covered entity.
  • You accept the BAA online at signup, and Hathr signs BAAs within 24 hours.
  • The BAA covers the HIPAA Privacy and Security Rules and the HITECH Act.
  • Hathr reports breaches and security incidents to you within 20 business days of discovery.
  • On termination, Hathr returns or destroys your PHI within 30 business days.
  • The BAA supports access, amendment, and accounting of disclosures under 45 CFR 164.528, and Hathr flows the same duties down to its subcontractors.

PBJ carries its own rule. Under 42 CFR 483.70(p), the facility submits complete and accurate staffing data based on payroll and other verifiable and auditable data, and the Policy Manual leaves the facility responsible when a vendor submits for it. An AI tool can compare records and cite the gap. The facility owns the file. Our security and privacy page documents the boundary, and Why Hathr.ai compares it with general-purpose tools.

How do you reconcile PBJ data against payroll with AI?

You upload the quarter's payroll register, time detail, agency invoices, and PBJ reports to Hathr.AI, run one structured prompt, and have the staffing coordinator check each flagged line before submission. The steps:

  1. Export the payroll register for the quarter, with hours by employee, date, and pay code, plus the time and attendance punch detail.
  2. Collect agency and contract invoices with hours by person and date, including scanned or handwritten timesheets.
  3. Export the draft XML file or the iQIES staffing report, and run the iQIES census report.
  4. Upload the files to Hathr.AI. Built-in OCR reads scanned invoices and handwritten timesheets, so nothing needs retyping.
  5. Run the prompt below. Open each cited line, then correct the payroll source or the XML file before you submit.
  6. After the upload to iQIES, read the Final File Validation Report and file the reconciliation with the quarter's records.

The prompt:

Read the attached payroll register, time detail, agency invoices, iQIES staffing report, and census report for the quarter. For each employee ID and date, compare PBJ hours with payroll hours worked on site. List each mismatch and name the likely cause: paid leave, a missing 30-minute meal deduction, training time, more than 22.5 hours in a day, agency hours missing from the file, or a job code outside the crosswalk. List each date with no hours under job codes 5, 6, or 7. List each resident who appears on the census report after a discharge that the records document. Cite the file and page for each item. Do not change any hours, and mark an item uncertain when the records conflict.

Your first session: take last quarter's submitted file, run the prompt on one month of payroll and agency invoices, and compare the mismatch list with that quarter's Final File Validation Report. More templates sit in our HIPAA-compliant prompt library, and How It Works shows the upload flow.

Run this prompt on one month of payroll, free for 7 days →

What does a PBJ reconciliation gap look like?

A PBJ reconciliation gap is an hour that payroll and the staffing file count in different ways, and Hathr.AI's review lists each gap with its source line. Hathr.AI wrote the example below for this page. It is illustrative, it describes no real facility or employee, and it does not benchmark Hathr.AI output. We applied the Policy Manual rules to six made-up employees on one day.

Employee (illustrative)Job code and pay typeHours in payroll or invoicePolicy Manual rule appliedPBJ hours
RN, day shift7, non-exempt8.030-minute meal deduction7.5
CNA, evening shift10, non-exempt8.030-minute meal deduction7.5
LPN on vacation9, non-exempt8.0 PTOExclude paid leave0.0
Agency CNA, scanned invoice10, contract8.0Meal deduction, unique employee ID7.5
DON, salaried5, exempt8.0 paid, 10.0 on siteReport paid hours, then deduct meal time7.5
RN in an all-day class7, non-exempt8.0Exclude off-floor training0.0
Total48.030.0

Raw payroll and invoices show 48.0 hours. The Policy Manual rules leave 30.0 reportable hours, a gap of 18.0 hours, or 37.5% of the raw figure. We computed the totals. A file built from the raw export overstates staffing, and an audit that compares it with payroll finds the difference.

The census error runs the other way. We computed the day below for a made-up facility with 352.5 reportable nursing hours, 98 residents in the building, and four discharge assessments that CMS did not receive.

MeasureCensus per facility recordsCensus CMS derives from the MDS
Residents counted98102
Reportable nursing hours352.5352.5
Total nurse hours per resident day3.603.46

The facility staffed the same hours on both lines. Four missing discharge assessments cut its total nurse staffing by 0.14 hours per resident day, about 3.9%, before case-mix adjustment. The fix sits in the MDS office.

What should the DON check before AI findings change a PBJ file?

The DON or the staffing coordinator checks six points before any Hathr.AI finding changes the file:

  1. Open the cited payroll or invoice line and confirm the hours match the source.
  2. Confirm the facility paid each counted hour for work on site, and remove leave, meal time, and off-floor training.
  3. Confirm the job title code matches the employee's primary duty under the signed crosswalk.
  4. Confirm each day with residents in the building shows RN hours under codes 5, 6, or 7, and trace any gap to the schedule and the time punches.
  5. Run the iQIES census report and match it against transmitted discharge assessments.
  6. File the payroll export, the reconciliation, and the Final File Validation Report with the quarter's records.

Hathr.AI surfaces evidence, and the DON and administrator decide what the facility submits. We do not describe Hathr.AI output as a payroll determination or a clinical judgment.

What should a nursing home require from an AI tool for PBJ work?

A nursing home should require what Hathr.AI provides: a signed BAA before the first upload, a named hosting boundary, OCR for scanned invoices and timesheets, and output that leaves the file decision with the facility. Payroll and time-and-attendance vendors build and submit the XML file; our nursing home software buyer's guide covers that category. The table lists what to ask an AI vendor that checks the file.

RequirementAsk the vendor toHathr.AI answer
BAASign before the first upload, and state the turnaround.The web app accepts the BAA online at signup on every account. Hathr signs BAAs within 24 hours. Breach notice within 20 business days.
Hosting boundaryName where census and payroll data run.AWS GovCloud (US), inside a FedRAMP High authorization boundary, on government-approved models.
Security tierName the security framework and tier.FedRAMP High boundary, a tier the US federal government verifies. Controls conform to NIST 800-53 and NIST 800-171.
EncryptionName the encryption for data in storage and in transit.FIPS 140-2 encryption and TLS 1.3.
Data useConfirm whether the model retains or trains on your records.The models retain nothing and never train on customer data. Documents stay in your account, segmented, until you delete them.
Scanned invoicesConfirm support for scans, faxes, and handwritten timesheets.Built-in OCR with handwriting recognition. PDF, Word, Excel, and plain text.
CapacityState the document and page limits per account.Up to 100 documents and 100,000 pages per account. Single documents of more than 500,000 words.
File accountabilityConfirm the tool leaves the staffing file and its sign-off with the facility.Hathr.AI lists mismatches with citations. It does not build or submit the PBJ XML file.
PriceState the seat price and any seat minimum.$47 per user per month, no seat minimums, 7-day free trial.
System fitConfirm whether setup needs an integration project.The web app works alongside any payroll system or EHR through upload and copy-paste. The API is REST.

Hathr.AI operates inside a FedRAMP High boundary, a security tier the US federal government verifies. NIST 800-53 and NIST 800-171 are the baselines behind SOC 2 and HITRUST, Hathr.AI's controls conform to both, and its control set maps to the HITRUST CSF and SOC 2 criteria. Ask any vendor you evaluate to name its security tier and show the evidence.

Which nursing home teams use Hathr.AI for PBJ accuracy?

Payroll teams, staffing coordinators, DONs, MDS coordinators, and administrators use Hathr.AI on the records behind the PBJ file.

TeamStarts fromProduces
Payroll and HRPayroll registers, time punch detail, pay codesLists of paid leave, meal time, and training hours to remove before export
Staffing coordinatorsSchedules, agency invoices, handwritten timesheetsAgency hours by employee ID and date, and days with no RN hours
Directors of nursingThe job code crosswalk and job descriptionsTitles mapped to a code that differs from the primary duty
MDS coordinatorsThe iQIES census report and discharge recordsResidents counted on the census after a documented discharge
Administrators and complianceThe quarter's file, reports, and written methodA draft audit response that cites each source record

For the full facility picture, start at our hub on AI in nursing homes. Survey-side staffing tags, including F725 and F851, sit in F-tags explained. Turnover and staffing trends feed the QAPI program, and the survey readiness checklist shows how surveyors use PBJ data before they arrive. Hathr.AI reviews records 10x faster in documentation and chart review.

What does Hathr.AI cost, and how does the API work?

The web app. Hathr.AI costs $47 per user per month with no seat minimums, unlimited queries, uploads, and downloads, and a 7-day free trial. Pricing is current as of August 2026. See pricing.

The API. The API has separate pricing. HIPAA-compliant API plans run $225, $700, or $1,200 per month by token volume, and each includes a signed BAA. The $45 Base plan is not HIPAA-compliant and serves non-PHI use. Software teams that build staffing or census tools on resident data need a HIPAA-compliant plan. Details sit on the API page.

Hathr builds enterprise automations for Medicare quality assurance, coding and billing, and documentation review, and hosts customer applications inside the same boundary. Hathr prices those engagements by quote.

The math on one $47 seat for PBJ review

You buy a staffing file you can defend in an audit, and a staffing rating that reflects the hours your staff worked. Put a price on the review time first. We used the U.S. median wage for registered nurses in nursing and residential care facilities, $84,300 a year in May 2025 per the Bureau of Labor Statistics, which comes to $40.53 an hour over 2,080 hours. At that wage, $47 buys about 70 minutes of RN time. We computed both figures.

So the seat pays for itself if it saves your DON about 70 minutes a month on PBJ review. Set that against the cost of the manual path: a DON or staffing coordinator reading a quarter of payroll lines and scanned agency invoices by hand, three missed meal deductions or one uncoded weekend RN shift away from a one-star staffing quarter. We publish no time savings for this work. Your trial measures them on your own files.

Each $47 seat for PBJ work includes:

  • Payroll, invoice, and census review that cites the source line for each mismatch
  • OCR for scanned invoices, faxes, and handwritten timesheets
  • Up to 100 documents and 100,000 pages stored per account
  • Unlimited queries, uploads, and downloads
  • A signed BAA from the first login, on AWS GovCloud (US) inside a FedRAMP High boundary

You test the review on your own payroll during a 7-day free trial, with no seat minimums, so one staffing coordinator can check a full quarter before the facility adds anyone.

Frequently asked questions

What is PBJ in a nursing home?

PBJ, the Payroll-Based Journal, is the quarterly submission of direct care staffing hours, drawn from payroll, that each Medicare- and Medicaid-certified nursing home files with CMS. CMS uses the data for the staffing star rating on Care Compare.

Do facilities certified for Medicare alone have to file PBJ data?

Yes. Each long-term care facility certified for Medicare, Medicaid, or both files staffing data under 42 CFR 483.70(p). The rule sets no exemption for size, ownership, or low census.

When are PBJ submissions due?

Each file is due by 11:59 p.m. Eastern on the 45th calendar day after the fiscal quarter ends: February 14, May 15, August 14, and November 14. The system accepts no late files, and the next five due dates fall on weekends.

How do SNFs submit staffing data to CMS in 2026?

Through the Payroll-Based Journal in iQIES, which went live August 17, 2026. Each submitter needs a HARP account and an approved PBJ role for each facility, and CMS retired the QIES version on September 15, 2026. Files upload as XML in data specification version 4.10.0 or through manual entry.

What happens if a nursing home fails a PBJ audit?

The facility receives a one-star staffing rating for three months. The same applies when it does not respond to the audit. A missed submission deadline produces a one-star staffing rating as well, and the CMS FAQ describes an appeal path for most audit failures.

Do paid time off and meal breaks count toward PBJ hours?

No. The staffing file excludes vacation, sick leave, holiday pay, and other paid leave. The facility deducts 30 minutes of meal time for each full shift, whether or not the employee took a break.

How do you reconcile PBJ data against payroll?

Compare the staffing file line by line with the payroll register, time punches, and agency invoices for the same dates, and remove leave, meal time, and off-floor training. Then confirm RN hours for each day and check the iQIES census report against discharges.

Which AI tool fits a nursing home that reconciles PBJ data before submission?

Hathr.AI fits nursing homes that need a signed BAA, a FedRAMP High AWS GovCloud boundary, OCR for scanned agency invoices and timesheets, and $47-per-user pricing with no seat minimums. Hathr.AI lists each mismatch with its source line, and the DON keeps the file decision.

Check your next PBJ file before November 14

Pick last quarter's file, upload one month of payroll and agency invoices, run the prompt above, and compare the mismatch list with your validation report. The FY 2026 Q4 file is due Saturday, November 14, 2026, the first deadline since CMS moved the Payroll-Based Journal to iQIES. Hathr.AI includes a signed BAA on every web app account, sets no seat minimums, and runs a 7-day trial.

Reconcile one quarter of staffing data in Hathr.AI, free for 7 days →

Source: Hathr.AI, PBJ Reporting Requirements for SNFs: 2026 Deadlines, iQIES, and Audit Prep, last updated October 5, 2026. Part of the nursing home AI hub. This article is general regulatory information, not legal, payroll, or compliance advice. Verify current requirements against the PBJ Policy Manual (V2.8, August 2026), the Five-Star Technical Users' Guide, and 42 CFR 483.70(p) before you submit. Hathr.AI surfaces evidence from the documents you provide, and the director of nursing and the administrator make each decision.

Category
No items found.
Written by
Sam Hart headshot - Founder at Hathr.ai
Hathr.AI
Date Published:
2026-08-07

Our Youtube Videos

Hathr.AI is the fastest, safest way to handle sensitive medical records with HIPAA-compliant artificial intelligence. In this demo, watch how you can:✅ Summarize a patient’s medical record  ✅ Generate an AI-assisted treatment plan  ✅ Write a letter to the patient in plain English  ✅ Suggest CPT billing codes  ✅ Draft an insurance appeal for a denied claim  ✅ Evaluate the case for potential malpractice — all in under 5 minutes.The only AI tool hosted in AWS GovCloud and Powered by Claude 4.0 Sonnet, Hathr.AI is trusted by hundreds of practices that need speed, security, and compliance.Learn more: hathr.ai  For healthcare teams: hathr.ai/healthcare  Reach out to learn more: contact@hathr.ai‍

#HIPAACompliantAI#ArtificialIntelligenceInMedicine#HealthcareAI#MedicalBillingAI#AIForDoctors#HIPAAAI#MedicalRecords#AIInHealthcare

Description

‍

As Hathr.AI, we are dedicated to providing a private, secure, and HIPAA-compliant AI solution that prioritizes your data privacy while delivering cutting-edge technology for enterprises and healthcare professionals alike.

In this video, we’ll dive deep into the growing concerns around data privacy with AI tools—especially in light of recent revelations about Microsoft’s Word and Excel AI features. These new features have raised alarm over data scraping practices, where user data could be used without clear consent, leaving individuals and organizations exposed to potential privacy breaches. What makes this especially concerning is the "opt-in by default" design, which could lead to unintended data sharing.

In contrast, Hathr.AI ensures that your data stays yours. With a firm commitment to HIPAA compliance, we take the protection of sensitive healthcare data to the highest level. Our platform is built with the understanding that privacy is not an afterthought but a fundamental pillar of our design. We don’t collect, store, or sell user data, and we employ state-of-the-art encryption, secure access protocols, and clear user consent processes to keep you in full control.

We’ll also touch on why Hathr.AI, powered by advanced LLM (Large Language Models) like Claude AI, offers a secure and private alternative for businesses looking to leverage AI technology without compromising sensitive information. While some AI tools may collect or expose data through ambiguous or hard-to-find opt-out settings, Hathr.AI puts transparency and security at the forefront, offering peace of mind in an era of increasing digital vulnerability.

If you’re concerned about your privacy or looking for a HIPAA-compliant AI solution that respects your data, Hathr.AI provides the robust security, transparency, and ethical design that you need.

Key Points:

  • HIPAA Compliant AI: Built for healthcare professionals, ensuring compliance with privacy regulations.
  • Privacy-first: No data scraping, no data selling, full user control over information.
  • Claude AI: Secure, powerful LLM tools for advanced capabilities without compromising security.
  • Data Transparency: Say goodbye to hidden opt-in/opt-out toggles—Hathr.AI gives you clear, easy-to-understand privacy settings.

Tune in to learn how Hathr.AI ensures your AI tools remain private, secure, and trustworthy, while still delivering the performance and accuracy you need to thrive in a fast-evolving digital landscape.

Don't forget to like, comment, and subscribe for more insights on secure AI solutions and how to protect your organization from emerging privacy risks!

Description

‍

Discover how Hathr AI's advanced AI tools transform federal acquisition processes with unparalleled security and efficiency. Designed for government professionals, this video showcases Hathr AI’s capabilities, including secure AI data analysis, HIPAA-compliant tools, and AWS GovCloud integration, to help streamline decision-making and document management. Perfect for agencies seeking private, compliant, and powerful AI solutions, Hathr.AI delivers tools tailored for healthcare and government needs.
‍

Key Topics Covered:

AI-driven data analysis for governmentHIPAA-compliant, secure AI tools for federal agencies

Private deployment options with AWS GovCloud

Learn more about Hathr AI’s secure, high-performance solutions at hathr.ai and transform your agency’s acquisition process with cutting-edge AI.

Description

‍

Discover how Hathr.AI simplifies NSF grant evaluations with advanced AI-driven compliance and proposal review tools. This video showcases Hathr.AI’s capability to streamline grant compliance checks, enhance accuracy, and save time for evaluators and applicants alike. Ideal for research institutions, government agencies, and proposal writers, Hathr.AI offers secure, HIPAA-compliant AI solutions tailored to meet the complex requirements of NSF and other grant processes.Highlights:AI-powered compliance checks for NSF grant proposalsFast, accurate, and secure evaluations with Hathr.AITailored solutions for research, government, and healthcareOptimize your grant proposal process with Hathr.AI's private, secure AI tools. Learn more at hathr.ai and transform how you handle grant evaluations and compliance.

Description

‍

Join Hathr.AI at the Defense Information Systems Agency (DISA) Technical Exchange Meeting to explore innovative AI solutions tailored for federal and defense applications. In this session, we highlight Hathr.AI's secure, private AI tools designed for efficient data handling, HIPAA compliance, and seamless integration within government systems, including AWS GovCloud. Perfect for agencies seeking reliable AI for data analysis, document summarization, and secure decision-making, Hathr.AI provides cutting-edge technology for defense and healthcare needs.Highlights:AI tools for federal and defense data managementSecure, HIPAA-compliant AI solutions with AWS GovCloudEnhancing operational efficiency with private AI deploymentsDiscover how Hathr.AI's solutions empower government and defense agencies to stay at the forefront of innovation. Visit https://hathr.ai to learn more about our services.

Blog and articles

Latest insights and trends

AI Healthcare solutions with Hathr.AI
HIPAA Compliant AI

AI Healthcare Solutions: How a HIPAA Compliant LLM can Revolutionize your practice

Learn how HIPAA compliant AI healthcare solutions can revolutionize your practice. Hathr AI offers secure, HIPAA & NIST-certified tools that automate billing, enhance diagnostics, and improve patient care while ensuring complete data privacy and compliance.
deepseek-ai-is-dangerous-for-healthcare
Security & Compliance

DeepSeek AI: Interesting Methods, Dangerous Product

Analysis of DeepSeek AI's computational efficiency innovations and why its security risks, censorship issues, and compliance concerns make it unsuitable for healthcare, government, and other regulated industries in the United States.
Challenges Finding Compliant AI
Security & Compliance

Challenges Finding Compliant AI: ChatGPT is Watching You

This blog post explores the recent discovery of AI-powered surveillance by Chinese intelligence using ChatGPT, highlighting the vulnerabilities of commercial AI tools in terms of security, privacy, and compliance. It discusses the implications for regulated industries and offers guidance on implementing secure, HIPAA-compliant AI solutions like Hathr.AI to safeguard operations without compromising functionality.
HIPAA Compliant AI

Low-Code HIPAA Compliant AI: Hathr.AI Integrates with Pipedream.com to Deliver HIPAA-Compliant AI Integration

Hathr.AI partners with Pipedream.com to offer HIPAA-compliant AI integrations, transforming healthcare automation with secure, low-code solutions. This collaboration empowers healthcare providers and developers to create compliant workflows, enhancing efficiency and patient outcomes while maintaining robust data security.