Proposed Sandbox Changes

This page catalogues ideas for CDS Hooks Sandbox changes. Each one of these will be spun out into Github issues with much more detail. This page serves as an quick place to capture / solicit ideas.

• Push to master deploys automatically

• Rename from "CDS Hooks Demo" -> "CDS Hooks Sandbox". Change url accordingly (sandbox.cds-hooks.org)

• Default the initial view to the patient-view hook page. This more closely matches EHR workflow (the user starts by opening a chart) [JM: I like this. Can we think of an interesting patient-view service to include by default?]

• Enhance "Change Patient" to not be a simple text box but rather a pick list of known test patients

• Allow the developer to hook up their own FHIR server (outstanding question: how is this going to work with our security model)? [JM: Great! Note that this is actually supported as a "hidden feature" today; you can pass a fhirServiceUrl parameter to the sandbox index]

• Show the CDS Service request in the side panel, similar to how we show context today [More directly: replace the side panel with a full view of the CDS Service request? With a hide button and a "log to console instead" checkbox so folks can just more over to dev tools]

• Show the CDS Service response in the side panel, similar to how we show context today [JM: Yes, and are we imagining two side panels? Stack panels in one column? Other ideas for layout?]

• Allow the developer to write a card directly via JSON and see it render (inspiration from https://api.slack.com/docs/messages/builder)

• Make "Quick Add" more clear that we're hitting the discovery endpoint ("Discover"?). Also, make it prettier (vs the current text box)

• Rename "Configure Hooks" -> "Configure CDS Services"

• Style the current "Configure Hooks" panel better

• Collapse "Quick Add", "Reset", and "Configure Hooks" under a single button/section?

• Add the ability for the developer to hook up an arbitrary hook (eg, my-custom-hook) [JM: For hooks that need context data or EHR UI, this is a tough thing to generalize, but I agree it's worth adding a simple starting point]

• Try to push all relevant state to the URL (including any services that have been added) to support sharing deep links that show off a hook (currently, "getting things set up" is a pain point for a quick demo).