AT&TSample data
Enterprise Data & Governance · Privacy & Security

Privacy & Security Controls

The technical and policy controls that protect workforce health data, enforce access boundaries, and prevent re-identification.

Sample dataObserved
Enforced
6
data-layer controls
Active
1
system-wide controls
Documented
1
policy controls
Encryption
AES-256
at rest · TLS 1.2+ in transit

Privacy controls

Measured
Small-cell suppression (≥11 minimum)

No aggregated view is shown for any group smaller than 11 members. Prevents re-identification through small populations.

EnforcedData-layer (server-side)
No employer access to individual records

Employer admins can never retrieve individual clinical records, member-level health data, or raw measurements. Access is restricted to aggregated, privacy-safe views.

EnforcedData-layer (server-side)
Filter combination protection

Filter combinations (division + location + period) that would produce a group under 11 members are automatically suppressed. No partial results are shown.

EnforcedData-layer (server-side)
De-identification methodology

PHI is de-identified per HIPAA Safe Harbor and Expert Determination methods where applicable. De-identified data is used for analytics and benchmarking.

DocumentedPolicy + technical
Role-based access control (RBAC)

Access is granted by role, not by page visibility. Data-layer enforcement ensures users cannot access data their role does not permit, regardless of UI state.

EnforcedData-layer (server-side)
Audit logging

All data access, modifications, and exports are logged with user identity, timestamp, and action. Logs are retained for 7 years and available to auditors.

ActiveSystem-wide
Encryption in transit (TLS 1.2+)

All data in transit is encrypted using TLS 1.2 or higher. Certificate management and rotation are automated.

EnforcedInfrastructure
Encryption at rest (AES-256)

All stored data is encrypted at rest using AES-256. Key management follows industry best practices with regular rotation.

EnforcedInfrastructure

Data classification & access boundaries

Observed
PHIProtected Health Information

Weight, BMI, blood pressure, HbA1c, prescription records, clinical outcomes

Access: PayRX Care Team, PayRX Clinical Staff
Storage: Encrypted at rest, access logged, BAA-covered
Records: 839 · Retention: 2555 days
PIIPersonally Identifiable Information

Name, email, employee ID, department, location, role title

Access: PayRX Admin, Employer HR (eligibility only)
Storage: Encrypted at rest, access logged
Records: 5,000 · Retention: 1095 days
AggregatedAggregated / De-identified

Workforce KPIs, cost summaries, participation rates, trend charts

Access: Employer Admin, Benefits Director, Finance, CHRO
Storage: Privacy-safe aggregates (≥11 members), no individual records
OperationalOperational & Vendor Data

SLA metrics, vendor performance, system uptime, audit logs

Access: PayRX Admin, Procurement
Storage: Standard encryption, operational retention

The 11-member minimum aggregation rule

Every aggregated view in this platform enforces a minimum group size of 11 members. If a filter combination (division + location + period) produces a group smaller than 11, the view is suppressed — no partial results, no counts, no percentages. This prevents re-identification through small populations and is enforced at the data layer, not just in the UI.

Enforced server-sideNo partial resultsFilter combination protection

Employee Privacy Protected by Design

Employer reporting is designed to present aggregate workforce and health-program insights without exposing individual clinical records. Small-group reporting restrictions help reduce the risk of employee identification.

Sample dataPrivacy-restricted reporting

Aggregated information is not described as HIPAA-de-identified unless applicable de-identification requirements have been satisfied and verified.

Sample Data — Demonstration Only. Fictional data, not actual patient records or validated outcomes.