Part 2 personal-representative definition

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Current rule checkpoint

Live 42 CFR 2.11 defines a personal representative as a person with authority under applicable law to act for a patient who is an adult or emancipated minor in health-care decisions. Within Part 2, that person has authority only over patient records relevant to the personal representation. The legal source, patient status, decision, and record relevance set the boundary.

Verify the legal source and action

Current 42 CFR 2.11 makes applicable law and health-care decision authority central. Record the instrument or law, jurisdiction, adult or emancipated-minor status, decision type, limits, duration, activation condition, revocation, reviewer, and records relevant to that authority.

Scope access field by field

Configure role-limited access for the permitted action and information. Keep an involved person, emergency contact, support person, personal representative, and disclosure recipient as separate records. Recheck changes in capacity, court orders, instruments, emancipation, or law.

Preserve the case-specific boundary

The HHS Part 2 fact sheet does not create representative authority. Privacy and legal roles verify the source and scope. Qualified clinicians address capacity and clinical decisions within their roles; operations records the decision without inventing it.

Verify authority under applicable law

Identify the jurisdiction, statute, court order, guardianship, power of attorney, advance directive, surrogate rule, or other instrument supporting authority. Preserve the patient, representative, adult or emancipated-minor status, activation condition, health-care decision, scope, limits, effective date, expiration, revocation, signatures, verification, and reviewer.

Family relationship, caregiving, emergency contact, payment, portal access, or physical possession of a document does not establish the full authority without review.

Match authority to the requested action

Determine whether the person can consent to treatment, authorize or revoke disclosure, request access, receive records, make a specific health-care decision, communicate with a provider, or perform another act. Read the source carefully because an instrument may cover some decisions but not others, or activate only after a condition is met.

Keep clinical capacity assessment, legal authority, and operational identity verification distinct. Qualified roles own each decision within scope.

Limit records to relevance

Identify which Part 2 records are relevant to the personal representation and the particular decision. Use dates, services, topics, fields, and purpose rather than a full-chart default. Exclude unrelated episodes, counseling notes, payer material, or other patient information unless the authority and request support them.

Document the relevance analysis and actual release or access. Reassess when the requested decision changes.

Configure roles and changes

Store personal representative, support person, caregiver, proxy, guardian, emergency contact, disclosure recipient, and payer as separate effective-dated roles. Link evidence, scope, activation, verification date, owner, and review trigger. Restrict portals, messaging, statements, phone access, and exports accordingly.

Recheck capacity, emancipation, court orders, instruments, revocation, death, relocation, and law changes. Remove access promptly when authority ends while preserving historical evidence.

Handle disputes and monitor access

Route conflicting instruments, multiple claimants, suspected coercion or fraud, safety concerns, uncertain relevance, and urgent care to privacy, clinical, and legal owners. Communicate holds without disclosing the records in dispute. Preserve requests, decisions, notices, and appeals or corrections.

Audit representative profiles, access, releases, denials, role changes, stale documents, overly broad portals, manual workarounds, and incidents. The HHS fact sheet provides context but does not create authority.

Before disclosing, independently verify the representative's identity and current contact route. Record which instrument and scope were presented, what information was withheld as irrelevant, the period covered, delivery method, and acknowledgment. When a representative asks for a full record, explain the case-specific boundary and offer a process for clarifying the represented decision. Do not expose other patients or family members whose information appears in a shared note without separate review. Train staff to pause when portal settings and legal evidence conflict.

Example

Sixteen representative profiles reach review. Thirteen include applicable-law source, instrument, action, record scope, limits, dates, verification, access configuration, and change trigger; three rely on relationship labels. Readiness is 13 of 16 profiles.

Personal-representative checklist

• verify applicable law, instrument, jurisdiction, patient status, and activation;
• match authority to the exact health-care decision or records action;
• limit access to records relevant to that personal representation;
• separate representative, caregiver, support, contact, payer, and proxy roles;
• recheck capacity, instruments, court orders, revocation, and other changes; and
• audit access, releases, denials, disputes, stale evidence, and incidents.

Representative authority is case-specific and record-specific. Relationship labels should never substitute for its legal and factual boundaries.