Hello!
I'm not sure this forum is the best forum to ask these questions, so feel free to direct me to a correct one.
We already have standalone provider and system apps for postprocessing patient encounters and other tasks.
What I would like to know is how could we integrate our app directly into the Revenue Cycle app (Cerner)? I suppose these are our options:
- Option A: Add an external link to RevCycle app (it would open our standalone app in the default Windows web browser with
patientId and possibly encounterId).
- Option B: Create mPage app (a web browser within RevCycle with a different auth flow, but basically we could have
patientId and encounterId there as well).
My questions:
- Are my listed options correct? Are there any other possible options?
- Can we configure RevCycle ourselves (through the Bedrock app), or do we need Oracle SRs for these integrations?
- We have access to the Bedrock app, but it seems that we can only build reports there. I'm guessing there are different permission layers to the Bedrock app per clinic?
- Can we override certain buttons within RevCycle so that it would call our API? (So that clinic workers would maintain the same workflow routine but could use the benefits of our app as well).
Again, let me know if I should post this question to some other forum.
Thank you for your help!
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 Oracle Partner Network Member? Yes
If you answer Yes to the above, please answer the below as well:
Partner/Company Name: -
Is your company enrolled in the Industry Healthcare Path? No
Does your company have the Oracle Health Millennium Platform (OHMP) Environment Access Technical Accelerator? No
Are you developing on behalf of an Oracle Health client? No
If so, which client:
Application's Client ID and App ID, if relevant: Not relevant
Expected Result: -
Actual Result: -
X-Request-Id / Cerner-Correlation-Id / opc-request-id:
Date/time of the example: