Security

The Patient Access API ensures that each application can only access the data of the member who authorized it. Key security features include:

• Authentication and Authorization – Managed through OAuth 2.0 using SMART on FHIR standards. Access tokens are issued by the payer's IdP and validated by the SMART on FHIR Inbound Security module.
• Member-Scoped Access – The onAuthenticateSuccess callback script grants read access to the Patient compartment named in the token's patient claim. A token without this claim receives no access to member data.
• Scope Enforcement – By default, the SMART on FHIR Inbound Security module reduces the permissions granted by the callback script to those allowed by the scopes the member approved.
• Transport Security – All endpoints must support TLS 1.2 or higher.
• Usage Data Contains PHI – The Patient ID and user identifier written to the transaction log and Kafka topic identify the member. Restrict access to the topic and to any downstream reporting store accordingly, including the CMS trace repository and its endpoint. When enrichment is enabled, each trace also contains the member's name and member number.
• Enrichment Credentials – The enrichment lookups authenticate to the payer's FHIR repository with HTTP Basic authentication. Use an https base URL, and grant the enrichment user read access to Patient, Coverage, and Organization only.