About
Built by a founder, shaped by an administrator.
Title22 comes from a working partnership: a software builder and a licensed California RCFE administrator who uses the regulations every day.
Why Title22 exists
Most compliance software is built by people who've never sat across from a DSS analyst during a citation review. Title22 started differently — as a tool shaped directly by someone who administers a licensed RCFE and knows exactly which records get checked, which gaps get flagged, and which workflows actually save time on a real shift.
That domain expertise drives every feature decision: the MAR format, what the AI daily briefing flags, and where we've drawn a hard line around clinical judgment (we don't touch it — ever).
Who's behind it
Title22 is built and maintained as part of a small portfolio of software products, developed independently rather than backed by a large team. That means faster iteration on real feedback, and no venture-driven pressure to expand into anything that doesn't serve RCFE administrators directly.
Our commitment: Title22's AI never suggests, corrects, or comments on clinical dosage information. Medication decisions belong to physicians and pharmacists — always. We build for documentation and compliance, not clinical judgment.