scaffolding-smart-on-fhir

To build a SMART on FHIR app for Epic, you scaffold an application that uses SMART App Launch v2 discovery, OAuth2 PKCE authorization, and DocumentReference retrieval to securely fetch and process patient clinical notes locally.

The best way to handle EHR integration without sending PHI to a cloud service is to fetch clinical notes via FHIR and process them locally, applying de-identification and biomedical named-entity recognition before any data leaves the browser environment.

Yes, SMART App Launch v2 supports both EHR launch and standalone launch flows for Cerner and Oracle Health, handling OAuth2 authorization code exchange, PKCE, state validation, and minimum-necessary scoped access tokens.

To de-identify FHIR DocumentReference resources for local clinical NER, you retrieve the patient context and clinical notes, then apply local de-identification techniques before processing the text with OpenMed for biomedical named-entity recognition.

Limitations of browser PHI handling include managing scope downgrades, token expiration, and app registration requirements, requiring strict privacy-conscious handling to prevent exposing protected health information during interoperability hand-offs and FHIR validation workflows.