Workflow or API calls:
Reminder: If this is referring to a client domain or EHR activity—not the public sandbox—do not include API request data or live patient data.
Background Information:
Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:
Are you an OPN Member? No
Have you signed up to be in the Healthcare Developer Track? No
Are you a registered Code Program member? No
Does your App have a presence on the Oracle Healthcare App Marketplace? No
_____________________________________________________________________________________________________________________
Hello Oracle Health FHIR team,
We are exploring a patient facing SMART on FHIR application pattern where patients can authorize a third party application to access their clinical data and share it with a requesting organization of their choice.
On the Epic side, a similar use case is supported through dynamic client registration combined with automatic client ID distribution for patient facing apps, allowing apps to be registered and approved centrally rather than requiring manual client registration at each individual institution. This approach helps support patient choice at scale and aligns with the goals of the 21st Century Cures Act around third party app access.
We would like to understand whether Oracle Health supports, or plans to support, any of the following capabilities for patient facing SMART on FHIR applications:
- Dynamic client registration
- Centralized client approval or trust management
- Automatic or delegated client ID distribution across tenant organizations
- Any alternative recommended pattern to enable broadly deployable patient authorized third party apps without per site manual registration
If any of these capabilities exist today, we would appreciate links to relevant documentation or guidance. If not, any insight into the current roadmap or recommended best practices for this use case would be very helpful.
Thank you for your time and assistance.