THE WORKFLOW, SIDE BY SIDE
Explore PA LogiQ (PAL) through three synthetic spine cases, from referral to a staff-reviewed packet.
EPIC INTEGRATION · EVIDENCE TO DATE
PA LogiQ (PAL) has locally reviewed standalone and chart-initiated SMART launch mechanics using scripted responses. Its Epic sandbox app is saved at Test stage, and the official LaunchPad setup is available. Real OAuth, patient/visit context and FHIR retrieval remain unverified.
Local scripted checks cover session/callback binding, replay rejection, PKCE and chart-launch context custody across staff sign-in.
FHIR normalization retains provenance and checks identity. Missing or unsupported clinical evidence stays unconfirmed; document metadata alone cannot establish readiness.
The actual authenticated application exercised authorize, callback, fetch, HOLD and acknowledgement with scripted Epic responses and isolated synthetic stores.
REMAINING WORK & PROOF
NEXT CONCRETE STEP
The Epic app is saved at Test stage; Draft is an expected saved-sandbox label. LaunchPad setup is available. Next, bind the reviewed adapter to an admitted runtime and synthetic context, then verify OAuth, context delivery and FHIR retrieval. Embedded-window validation remains separate.
All Epic-style visuals here are illustrative; no real Epic patient workflow is shown.These evidence excerpts describe reviewed local components. This page is a static presentation, not a live integration, clinical validation or submission service. Use “PAL overview” to explore the three synthetic cases.
WHERE PAL FITS
Estimated workflow • illustrative layout, not an Epic screenshot. Local configuration and launch location require customer validation.
Epic Launchpad ↗ documents application launch with patient/visit context. Our PAL launch here is simulated; customer enablement and the actual launch location are unverified.
Epic Hyperdrive ↗ describes its Web Developer Test Harness for websites in an iframe or embedded window. Harness access requires login; the current Epic sandbox app and LaunchPad setup are available. This illustrative layout has not been validated in Hyperdrive.
Authorization workqueue placement, writeback and payer submission are proposed, not validated. Standalone and chart-initiated mechanics are locally reviewed; real Epic OAuth/context/FHIR and embedded-window use remain unverified. The reviewed application policy blocks iframe embedding. The checks below are recorded PAL examples with synthetic data; they do not establish a working Epic integration.
Epic-style simulation · illustrative layout
Evidence → checks → action