Resident identity controls should prevent one person from being registered twice and prevent information from being filed, viewed, or acted on under the wrong profile. In an Adult Family Home, a duplicate or misidentified record can separate medication orders from the MAR, split care-plan history, misroute pharmacy deliveries, or expose another resident's information.
This guide covers record design and workflow, not a universal identity policy. It was reviewed on August 8, 2026. Providers should verify current Washington requirements and align the process with resident rights, privacy duties, facility policy, and authorized source documents.
Create one durable resident identity
Assign each resident a system-generated identifier that does not depend on name, room, facility, payer, or admission status. Names change, rooms change, and residents may leave and return. The internal identifier should remain stable while the profile preserves historical changes.
Keep these identifiers distinct:
- System resident ID
- Facility-specific record or chart number
- Medicaid, insurance, or external identifiers when authorized
- Pharmacy and practitioner patient references
- Room assignment
- Current and former legal or preferred names
Do not use Social Security number as the visible primary key. Limit access to identifiers that users do not need for daily work.
WAC 388-76-10320 lists minimum resident-record content, including identifying information, contacts, medical history, assessment, care plan, medications, admission and absence history, belongings, and financial records. A durable identity connects these records without making every field visible to every role.
The resident record requirements checklist provides a related completeness review. Identity controls make sure every required component stays attached to the correct resident.
Search before creating a profile
The new-resident workflow should run an authorized duplicate search before saving. Compare normalized combinations such as:
- Legal and former names
- Date of birth
- Phone or email when available
- Prior facility or archived status
- Representative or contact
- External record reference
- Existing resident photograph when policy permits
Display possible matches with only the information needed to decide. A caregiver should not gain access to an unrelated resident merely because a name is similar.
Offer three deliberate outcomes: open the existing profile, request an authorized merge review, or create a new resident with a reason. Do not automatically merge records. Two people can share a name and date of birth; one person can have spelling differences.
Verify identity from approved sources
Define which source documents or people may verify each field. The profile can store:
- Value entered
- Source type
- Source date
- Verifying user
- Verification date
- Confidence or pending status
- Supporting document reference
Avoid copying unverified data from an inquiry, email, or prior draft into the live record without labeling its status. The home should distinguish information supplied by the resident, representative, practitioner, pharmacy, referral source, or official document.
The 2025 ONC SAFER Patient Identification Guide addresses practices for reliably associating information with the correct person in electronic health records. AFH software may not be a certified EHR, but its identity-safety principles are useful for resident records.
Keep resident identity visible at action points
Identity verification is most valuable where a wrong-profile action could cause harm. Keep the resident's name, photograph when authorized, facility, and another approved identifier visible on:
- Medication administration and pharmacy acceptance
- New prescription and refill workflows
- Incident and appointment forms
- Care-plan and assessment updates
- Document upload and signature screens
- Transfer and discharge actions
- Messages and notifications
- Reports and exports
Do not rely on color or initials alone. At large text and mobile sizes, identity should remain visible without scrolling away from the save or administer action.
After switching residents, clear resident-specific selections, hidden form values, attachments, and cached recipient lists. A draft should either remain explicitly assigned to its original resident or require confirmed reassignment; it must not silently follow the user.
Prevent cross-facility mix-ups
For a provider managing several homes, the active facility boundary must be obvious. Search results should show facility and resident status, while the server returns only residents the user is authorized to access.
Use facility name and ID in administrative selection. Require a deliberate facility switch before entering a resident workflow. On switch:
- Clear previous facility search results
- Close resident-specific dialogs
- Reauthorize the destination facility
- Reset report and message recipients
- Preserve unsaved work only under a clearly labeled original facility
- Log the boundary change
Never solve multi-facility navigation by loading every resident into the browser and hiding unauthorized rows with CSS.
Manage names without rewriting history
Store legal name, preferred name, former name, pronunciation, and effective dates as appropriate. A name correction should not create a new resident. A name change should not make old pharmacy, medication, or incident documents appear to belong to someone else.
Show the preferred display name in everyday care when appropriate, while retaining the legal or label-matching name where the workflow requires it. Reports should state which name type is displayed.
Corrections need original value, corrected value, reason, evidence, author, and timestamp. Search should find authorized former names without exposing them unnecessarily.
Use photographs with consent and controls
A current resident photograph can support identification, but it is sensitive information. Document the applicable consent or authority, purpose, date taken, uploader, and review date. Provide an accessible alternative when a photograph is unavailable or inappropriate.
Do not use facial recognition or automated biometric matching unless the organization has completed a separate legal, privacy, security, and bias review. Ordinary photo display does not require an algorithm.
Control downloading, sharing, and exports. A medication report may need a photo under facility policy; a general occupancy report may not.
Detect duplicates continuously
Duplicates can arise after migration, offline entry, facility transfer, or concurrent creation. Run background checks when identity fields change or new external records arrive.
Route possible duplicates to a restricted review queue showing:
- Profiles involved
- Matching and conflicting fields
- Facilities and statuses
- Linked medications, MAR events, documents, messages, and reports
- Creation source and user
- Proposed disposition
- Risk of merging
Do not let a similarity score perform the merge. It should prioritize review and explain which fields matched.
Merge only through an authorized case
When two profiles are confirmed to represent one resident, the merge must be deliberate and reversible through audit evidence. Record:
- Surviving resident ID
- Duplicate ID retained as an alias
- Reviewer and approval
- Evidence
- Date and time
- Field conflicts and resolutions
- Child records moved or linked
- Records intentionally left separate
- Notification and downstream synchronization
- Validation results
Never delete the duplicate profile before every linked item is accounted for. Medication schedules, administrations, incidents, documents, signatures, billing records, and messages may have different integrity constraints.
If two profiles represent different people, mark the non-match so the same pair does not generate endless alerts, while permitting re-review when material fields change.
Reconcile connected systems
Identity resolution must propagate safely to pharmacy, eMAR, reporting, notifications, and integrations. Use stable mappings rather than matching on name.
After an authorized merge, verify:
- Active medications and schedules are not duplicated
- MAR events remain attributed to their original authors and times
- Pharmacy orders point to the surviving identity
- Allergies and alerts are complete without conflicting values
- Documents and signatures retain provenance
- Appointment and incident histories are chronological
- Authorized contacts remain correctly scoped
- Exports no longer split the resident
Do not send an automatic external identity update until the destination and change are verified.
Preserve confidentiality and audit evidence
WAC 388-76-10315 requires resident records to be confidential and protected from loss, destruction, unauthorized use, and alteration. Identity search, possible-match review, merge, unmerge, and export should all produce audit events.
When HIPAA applies to a covered entity or business associate, HHS describes audit controls and review of information-system activity. Applicability depends on the organization and activity; do not label every AFH a HIPAA covered entity by default.
Report identity quality without exposing residents
Useful restricted reports include:
- Possible duplicates awaiting review
- Profiles missing required identity fields
- Unverified high-impact fields
- Recent merges and non-match decisions
- Cross-facility transfer mappings
- External references without a resident match
- Wrong-profile corrections
Filters should include facility, status, creation source, reviewer, and date range. Aggregate dashboards can show counts; detailed exports require explicit authorization.
Test failure and recovery cases
Use demonstration records to test:
- Same legal name for two different residents.
- One resident with a spelling variation or former name.
- Archived resident returning to the home.
- Concurrent profile creation on two devices.
- Offline creation synchronized later.
- Facility transfer without a duplicate medication schedule.
- Photo unavailable or consent withdrawn.
- Wrong-profile document upload corrected with audit history.
- Confirmed duplicate merge with field conflicts.
- False-positive duplicate marked as a non-match.
- Mobile resident switching while a form is open.
- Unauthorized cross-facility search and export.
Confirm that a network retry cannot create a second resident when the first save succeeded but the response was delayed.
Frequently asked questions
Should the system merge residents automatically?
No. Similarity should create a review candidate. An authorized user must compare evidence, resolve conflicts, and approve the merge.
Is a resident's name a sufficient unique identifier?
No. Names can be shared, changed, misspelled, or formatted differently. Use a durable system identifier and verify multiple attributes.
What happens when a resident returns after discharge?
Search archived records first. Reuse the durable identity when it is the same person, while creating the appropriate new stay or status history.
Can duplicate profiles simply be deleted?
Not when they contain connected records. Resolve every medication, MAR, document, incident, message, and audit event through an authorized merge process.
Should all staff see every identity field?
No. Show only what a role needs for safe work and enforce access on the server, especially for sensitive identifiers and cross-facility searches.
Keep every action attached to the right person
Reliable identity management combines pre-create search, source verification, visible identity at action points, facility boundaries, controlled merges, downstream reconciliation, and durable audit history.
Explore AFH Manager to evaluate resident identity controls across profiles, medications, documents, incidents, appointments, pharmacy coordination, and reports. Test duplicate and wrong-profile scenarios with demonstration residents before production use.