Set Up and Explore a Demo of the Healthcare Action Engine
- Get Started with the Healthcare Action Engine Demo
- Deploy a Demo Environment
- Download and Import the Healthcare Action Engine Demo Walkthrough Postman Collection
- Import Sample Patient Data into Your FHIR Resource Server
- Hello, CDS Hooks!
- Disable CDS Hooks Token Validation
- Request 1: Discover HAE Services (no CDS Hooks OAuth)
- Request 2: Hello CDS Hooks! (no FHIR Fetch, no CDS Hooks OAuth)
- Fetch and Evaluate FHIR Data
- Configure Authorized Access to Your FHIR Resource Server
- Unified Care Record Only: Enable Access to the ODS FHIR Endpoint
- Request 3: Acquire OAuth Access Token for FHIR Fetch
- Request 4: Service Request (with FHIR Fetch, no CDS Hooks OAuth)
- Secure Client Requests to the Healthcare Action Engine
- Re-enable CDS Hooks Token Validation
- Configure CDS Hooks Authorization
- Discover HAE Services Securely
- Execute a Complete Service Call
- Alternative Workflow: Prefetch FHIR Data
- Request 10. Acquire CDS Hooks Token for Prefetch Service Request
- Request 11. Prefetch Service Request
- Deploy the Client Application to Test Synchronous Healthcare Action Engine Services within Unified Care Record
- Prepare Your Demo Environment
- Load the HAE Client App Container Image
- Create the Environment File and the Docker Compose File
- Configure HAE Allow Lists
- Start the HAE Client Application Container
- Embed the Client within the UCR Navigation Application
- Invoke HAE Services Using the Client Application
- Sample Data