Federal Quality Reporting Logins: Managing Identity-Proofed Accounts

A long-serving quality coordinator gives notice. On her last Friday she offers to hand over her login for the federal quality reporting system so the facility can keep submitting data. It seems helpful. It is also the wrong move, and the account may not survive it.

Many federal accounts are built on identity proofing, meaning the government verified that a specific real person is who they claim to be before granting access. Such an account belongs to that person, not to your facility.

Why these accounts are personal

When a system verifies someone's identity, it records that this individual is accountable for what is submitted. Sharing the login means a different person is acting under that verified identity. That can violate the program's terms, and it makes it impossible to tell who did what.

Beyond the terms, there is a practical problem. If the person leaves and the facility has no other authorized user, the facility may have to start the process of establishing a new account, which can take time. Specific timelines and requirements are set by the program, so confirm them with the program's help desk or your state association.

Common ways facilities get stuck

One person holds all access, and they are the only one with the verified identity.

Recovery goes to that person's personal email or cell phone, which disappears when they leave.

The program's roles are misunderstood, so the facility does not know it can have more than one user or a designated backup.

The sign-in uses a second step on a personal device that goes with the employee.

Nobody remembers who approved the account in the first place.

Plan for successors before they are needed

Look at how your reporting programs handle roles. Many have a role that approves other users on behalf of the organization, and separate roles for people who submit data. The names and rules vary, so confirm them with the program directly.

List each federal reporting program your facility uses.

For each, write down who holds which role and what their verified identity means for them.

Identify at least one backup who has completed their own identity verification and holds their own account.

Make sure the person who approves users is not also the only person who can submit.

Set the recovery email and phone to company-controlled options when the program allows it, while respecting any rule that ties the account to an individual.

Calendar a review every six months, and again whenever staff change.

Start the backup's verification early. The process can take longer than expected, and it needs the person's own documents and sometimes their own time.

When someone is about to leave

Treat departure as a project with a checklist.

Confirm which roles the departing person holds and which they should hand off.

Have the backup, or the new hire, complete their own verification before the departure date when possible.

Remove the departing person's role from your organization in the program, and make sure their access ends.

Update contact information tied to the organization.

Capture notes on submission steps, deadlines and data sources, so the next person is not starting blind.

Do not ask the departing person to leave their credentials behind, and do not keep using them after they go.

A word on reporting deadlines

Quality reporting has its own schedules and consequences, set by the program. Rather than guess, ask your state association or the program help desk how missed windows are handled, and tell them early if a staffing change threatens a submission.

Keeping notes the next person can use

The identity-proofed account may belong to one person, but the knowledge around it belongs to the facility. Keep a plain document that explains each submission cycle: what data is gathered, which systems it comes from, who reviews it and when it is due. Add screenshots of where to click, with any resident details removed. A successor who has this guide and their own verified account can pick up the work in days rather than weeks, and the facility is no longer hostage to one person's memory.

How we can help

UnityCare IT can help you inventory these outside accounts, move recovery email and phone numbers to company-controlled options and build offboarding checklists that include them. We work with administrators and quality staff on the practical side, and we leave program rules and identity verification to the programs themselves.

Related service

Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support