canvas-medical / embed Goto Github PK

Mobile	Desktop

• Calendar should have a header with a button to close the dialog
• Calendar should have a Month / Year Select
• Calendar should have a forward / back button to navigate through months
• Calendar should list out dates Sunday to Monday.
• Calendar should list out dates for the month.
  • The user's selected date should be highlighted
  • Dates in the past and dates without appointments(?) should be disabled.
  • Clicking on a date should close the dialog and set the user's selected date.

Questions to Answer

• How far out should users be able to select in the Month / Year select?
  Initially, aim for three months? Might be able to infer from data from API.
• Should dates be disabled if there are no time slots available for that date?
  Pretty sure this is also true, just trying to figure out how to get that date from the API.

This code will be run in front of all of our endpoints that accept a patient_id.

It takes a patient_id and a token and validates that the token belongs to that patient id.

If the keys match, the request continues.

If they do not match, return 401 unauthorized

Just add a link to the proxy README from the main README, like Nick did for Widgets

Feedback to be tackled from #13

• Add overflow auto to AppContainer
• Removed unnecessary max/min heights from popover
• Verify root font size
• Replace radio button time slots with regular buttons
• Handle focus on popover open
• Return focus on popover close

• Get better data from instance

The proxy will use the "Client Credentials" flow. We can store the client_id and client_secret in environment variables

This does not include deployment to aptible yet, this is just a local dockerfile.

Our design docs provided the following config options that needed to be passed to the embeds.

• DOM element to attach interface
• Patient identifier
• Provider identifiers (multiple possible)
• Location identifier
• Visit type (telehealth, office, phone, home, lab) see appointment_type for supported options
• Reason for visit (string)
• Appointment duration
• Proxy service preshared key (string)
• Brand color (optional hex)

Which fields are required fields?
How should the embed respond if required fields are missing?

Add rubocop to proxy code for formatting/linting purposes.

The proxy will issue requests to the FHIR API and return the results, including headers, to the requester. It should operate completely transparently.

This ticket is complete when the proxy can make and forward requests to the FHIR API.

Blocked by #18

When should we have their devs review our code? Every PR? If other, let's discuss.

What kind of integration tests should we be running? Do they have a preference?

Wk 3 or Wk 4 -- need to set up a test for embed. how do they want us to do this?

Deploy the proxy to aptible

The way that the API is built, there will be a performance issue if we have to keep hitting it for each provider. Flag for Canvas. But potentially there will only ever be 1 provider.

blocked by #17

Modify the application to accept a REDIS_URL param

rails new api mode, no db

set up testing, set up coverage thresholds

Resources

• Invision
  

Blocked by #21

Currently the known required endpoints are:

• GET /Schedule
• GET /Slot
• POST /Appointment
• GET /Appointment
• UPDATE /Appointment

Should these be 10% darker? What's Gabriel's preference?

Date Picker

• Enabled state should use the primary brand color
• Disabled state probably shouldn't use white, but a light grey

Standard Brand	Custom Brand

• Adjust focus / hover states of buttons to look better
  • Round forward / back date picker buttons hover / focus
  • Give all date picker buttons a better color for focus / hover (maybe darker color used for time slot buttons focus)

Date Picker Toggle	Forward / Back

Iconography

• Replace calendar icon with mock's calendar icon
• Fix scaling issue on calendar icon
  Currently, the calendar icon won't appropriately scale to different sizes. The svg "scales" but the path doesn't. The quick solution was to make a second, bigger version of the svg.

Current	Mock

Get Schedule

Headers - local has the following additional headers

• Last-modified
• Content-Type
• Vary
• Cache-control
• X-request-ID
• X-Runtime

Local does not have the following headers

• Content encoding (value: gzip)

Get Search Appointment

Local Body has a total of 12 while the FHIR API has a total of 15

Get Search Slot

Noticed that locally, the date is today, but hitting the FHIR API, the date is tomorrow.

Wondering if that's why the totals are different in the Body -- 135 vs. 130 (local).
Not local

Local

Not local

Local

Create Appointment

There are more Headers locally (17 vs. 11). Noticing the same date difference here as well.

Local

Not Local

Update Appointment

There are more headers locally (again, 17 vs. 11). Same date difference as before.
Local

Not Local

Making an appointment mobile
Making an appointment desktop

Viewing scheduled appointments mobile
Viewing scheduled appointments desktop

Docker compose maybe?

Resources

• Invision

This endpoint will accept a pre-shared key and a patient id and return a key that is scoped to that patient id

1. Check that the key matches our pre-shared key
2. Generate a patient scoped key
3. Store that key in redis
4. Return that key

we need to be able to embed the embed code into a staging environment

Get Github Actions to build and run rspec

For the Scheduler embed, when user schedules an appointment, display popover on bottom of screen to confirm or cancel.

Mobile	Desktop

For the Appointment embed, we'll use the same component when a user attempts to cancel an existing appointment.

Desktop	Mobile

How do they plan on distributing the CDN?

Show options to Canvas for approval or developer decision.